neko

The spirit is alive with https://github.com/m1k1o/neko The 'co-watching/co-streaming' is the best. I love watching a crappy horror movie with friends and bantering.

Eh but that's a commercial tool. They don't even seem to have a free community version. I wouldn't pay for that. And prefer Firefox anyway. For remote browser tools I use neko https://github.com/m1k1o/neko But with Tor I like to have more safeguards. So I prefer to run tails in an isolated environment.

https://github.com/m1k1o/neko before VNC check neko out. I worked on a project that started with VNC and had lots of problems. Slow connect times and backpressure/latency. Switching to neko was quick/easy win.

Have you tried https://github.com/m1k1o/neko yet?

Hey HN, We’ve been building on top of our browser-unikernel repo [0] and wanted to replace the noVNC remote GUI with something much faster. NoVNC is okay but it’s super laggy with any JS-heavy website (basically anything besides Hacker News…). We added remote GUI support using WebRTC, which supports: - low latency read/write live view into the sandboxed browser (scrolling, clicking, typing feel way more responsive) - can launch directly as a Docker container or on Unikraft unikernels - process real-time streams with a fast boot up time (<20ms) if you’re using unikernels WebRTC is powerful (supports all types of media and data transmission) but not trivial to implement. We adapted the Neko [1] library to play nicely with our base Chromium image. We also tailored the frontend to our use case. Would love any thoughts/feedback from folks who’

Still not enough. You are using Chromium but your software might not be secure enough. You are dealing with sharing data all over the internet and part of your code is not opensource. If we cannot inspect or reproduce what you are doing , we cannot trust our work with your browser. We might as well consider you are stealing our data. If you launch self-host option , you should opensource it. What we have for opensource alternatives are : https://github.com/BrowserBox/BrowserBox https://github.com/m1k1o/neko

And don't forget Neko! They make a great browser, and their logo is/was "cat's bum": https://github.com/m1k1o/neko They just posted (send some love!): https://news.ycombinator.com/item?id=36467219

Hey, you do you. It just sounds like an expensive way to avoid owning the hardware you want to debug to me. Also, not to burst your bubble, but there are a few projects out there that do more-or-less what you're describing: - https://store.steampowered.com/remoteplay/#together - https://github.com/m1k1o/neko If you're having fun, then continue by all means. I've just been nerd sniped by your cloud costs and I'm having flashbacks to seeing six-figure monthly AWS bills at startups that refused to buy their own GPU compute.

Agree. There's things you can do by virtualizing or instrumenting the browser that you can't with just screen sharing. It's a more specialized technology that powers more specific use cases. If folks like this, they may also be interested in the neko project: https://github.com/m1k1o/neko Or even a similar work of my own company: BrowserBox Pro -- where you can share a link to a single browser with multiple people. Co-browsing or co-operative / collaborative browsing is the "term of art" I believe. https://github.com/dosyago/BrowserBoxPro

I ran into neko recently which has similar. It's more application centric than desktop centric, but both offer multi-player experiences & I just think that is the absolute coolest. I hope someday hardware video encoding & modest sized slices of gpus (VDI) becomes a regular offering on cloud systems. These projects feel well suited to home servers, but to really run very well it feels harder to do on the cloud. Being able to share these huge beefy gpus we have, to parcel up the many 1080p encoders should be a straight shot to blowing the cloud market wide open but alas dividing up these resources is harder & more expensive than it should be. https://github.com/m1k1o/neko https://hn.algolia.com/?query=Neko%20m1k1o

Fork of neko; differences can be seen here: https://github.com/m1k1o/neko/compare/master...wanjohiryan:q... Commit messages seem like a bit of a mess at first glance, but otherwise seems like a really cool project!