Hacker News new | ask | show | jobs
by jqpabc123 59 days ago
Interesting from a technical perspective but with native RDP clients readily available on just about every platform, I don't see the need for it.
5 comments

When it’s in a browser you don’t need to install anything on the local machine. I used to use Apache guacamole to access my machine at home from work when I was stuck in a cube all day.

https://guacamole.apache.org/

1 contributor, 1 commit, new project... gives me vibe-coding feels.
If you have factual observations to make that's fine but can we stop with the "smells like vibe coding" attacks? It's like an AI version of an ad-hominem attack.
Browsers are sandboxes, your native client often isn't, there is definitely a huge advantage, portability and embeddability as well, it's also simpler to sniff traffic (and MITM it).
Doesn't this limit your ability to share resources and transfer data?
Why would it? You have access to your entire filesystem via the browser.
Not many good MFA options for native RDP/RDG. Putting it in the browser lets you wrap the whole thing with OAUTH/passkeys etc
Having just implemented OAUTH into a Go app this week, I can assure you that it’s surprising easy to do so without making your entire application a website.
I don’t disagree but none of the native RDP clients support oauth for non azure computers.
Perhaps as a web client for the remote desktop on the BMC chips?