[0] https://ish.app/
66 karma · joined October 19, 2013
[0] https://ish.app/
KRdp on Plasma/Wayland is still much more fragile. It depends on a logged-in Plasma session, has rough edges around unattended access, session startup, reconnection, display sizing, authentication/cert handling, and general automation. Those are exactly the things cloud desktops and disposable VM images need to be boringly reliable.
I’m not against deprecating X11 long term, but deprecating it before KRdp is a solid replacement leaves server/VM/remote-desktop users in a bad spot, hopefully now the team can focus solely on Wayland, KRdp will receive some much needed love.
Website went offline about 30 mins ago, repo and twitter are also gone. Looks like it's been hacked or pulled?
Neo is an anagram of One.
It would be interesting to know how this works under the hood though, is this just built on top of docker swarm load balancing?
We're using pm2 [1] for this if anyone's interested.
- Using an IP, netrange and information regarding the network owner (contact and abuse info). Gathered from the Regional Internet Registry (RIR) databases.
- Using a domain, registrant info --if public, abuse details etc..
It would be interesting to know if the developer looked at btapp.js and if so, why did he decide not to use it? Getting this technology web embeddable will go a long way to start making peer-to-peer a convenient method of downloading content vs directly downloading from a server, there's always going to be further hurdles to overcome with reliability in a case where the swarm lifetime is very short, but seeding with a few servers can help in that situation. If a web app could upload the torrent and data to a server to seed, then replicate it in a few locations it could be a decent DCDN.
[1] http://pwmckenna.com/2012/06/29/making-of-paddle-over.html