27
Open Source Paid Remote Desktop
(piefed.ca)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 11 Jun 2025
27 points (90.9% liked)
Selfhosted
53650 readers
81 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
How so?
There are a number of software packages in Debian that implement VNC. To grab one random example, the last commit to their git repo was last month.
VNC has long been abandoned by the engineering world. It's inefficient, it has no transport security, and the implementations are very subjective.
The last time I used a commercial VPS, I'm pretty sure it used VNC to provide console access.
The VNC software I linked to above appears to support TLS. If TLS isn't sufficient transport security, then most Internet-using software is going to be in trouble.
I'm not sure what you mean by subjective.
I haven't looked at the VNC protocol for a while, but I don't think that it imposes any terrible inefficiencies. A couple of decades back, I needed to implement something quick-and-dirty similar to VNC, and went with rendering window contents and handling dragging of windows locally, which I don't believe that VNC can do (or didn't then) but IIRC VNC has a tile cache, which, if intelligently used, should avoid most traffic. Dunno if it can deal well with efficiently rendering visual effects.
I don't mean to be rude, but the last time you used a "commercial VPS" must have been a decade ago.
Get with the times.
There is not a single datacenter provider on this planet who uses VNC as anything. Every major player is working towards Zero-Trust AT BEST, so you wouldn't even be able to leave a weird VNC port open to the internet even if you wanted to without an IDS going off.
I don't want to spend time digging into your outdated dumbshit, so I'll just slap it down: AWS, Google, Azure, Cloudflare...just name anyone. NOT WORKING WITH VNC.
Get current. Nobody does this old ass shit anymore. Sorry. It's dead as fuck, guy.
I was mostly with you right up until paragraph/linebreak/whatever 4. Took a pretty civil discussion and went bonkers. Put down the keyboard, go rub one out, and relax my dude.
We use VNC as we can record the sessions easily for later priof / discussion with our customers.
It's in a VPN tunnel of course.
But of course, we also don't use Google, AWS, etc as they're not secure enough for us and we have our own SOCs