Just FYI, Neko is also the name of the VM for the Haxe language: https://haxe.org/manual/target-neko.html
It's also a 30-year-old X app that draws a cat which chases your cursor.
Show HN: Neko – Self hosted virtual browser that runs in Docker and uses WebRTC
21–30 of 61 posts
Re: Show HN: Neko – Self hosted virtual browser that runs in Docker and uses WebRTC
#22https://getmetastream.com/ is an also-FLOSS alternative, instead of a server, it syncs site interactions (e.g. opening up the same video on each person's browser, and then automatically hitting play, seek, etc) So, pros and cons of each approach
How does this approach handle different internet speeds? Video playback will be out of sync if buffer times differ.
Re: Show HN: Neko – Self hosted virtual browser that runs in Docker and uses WebRTC
#23I can't take this project seriously with that name and that logo. Weebs are so insufferable.
"Cats are assholes. Hehe does anyone else le reddit?"
Re: Show HN: Neko – Self hosted virtual browser that runs in Docker and uses WebRTC
#24Neko is a fantastic project, I love telling people about it. It does so much more then the title says :) Being able to watch videos with someone in perfect sync is a great experience. It's not the same to just sync two video elements, but you actually can scroll the page and feels like you are sharing the same screen. This and https://github.com/giongto35/cloud-morph I think have the chance to really inspire/change t…
Seems like you could also use it as an alternative to Twitch where you watched someone play a game, or Picaro.tv which you watch people draw stuff
Re: Show HN: Neko – Self hosted virtual browser that runs in Docker and uses WebRTC
#25Earlier quoted context omitted.
It is using a WebRTC Data Channel. You can send binary/text data over the same connection that is receiving the media. The other exciting thing about Data Channels is that you can send lossy/unordered messages and get flow control. You can know how much data you can send and how fast. You can build faster and more responsive data APIs that way!
What I'm saying is from the gif (repo README) you see this localhost web thing. I'm aware you can screenshare say from Chrome and show a tab or your whole desktop. In this way you have mouse control/people would just watch your screen. I'm not clear on how they're clicking into that shared browser (to use YouTube). Normally for this kind of thing you need an OS-level component. There's something on the GO side but tr…
It's in a container with xorg running. It doesn't need kernel level access but it does need userland access which it does have access to in the container.
Re: Show HN: Neko – Self hosted virtual browser that runs in Docker and uses WebRTC
#26Earlier quoted context omitted.
What I'm saying is from the gif (repo README) you see this localhost web thing. I'm aware you can screenshare say from Chrome and show a tab or your whole desktop. In this way you have mouse control/people would just watch your screen. I'm not clear on how they're clicking into that shared browser (to use YouTube). Normally for this kind of thing you need an OS-level component. There's something on the GO side but tr…
It's in a container with xorg running. It doesn't need kernel level access but it does need userland access which it does have access to in the container.
> UserLAnd
Hmm that's cool I was not aware of this thing, not surprising but still cool to find out now.
Re: Show HN: Neko – Self hosted virtual browser that runs in Docker and uses WebRTC
#27This is great for when you have a corporate laptop and you want to separate your personal browsing session from your work browsing session easily. I also like it because I setup a VPN for the browser and have access to some self-hosted stuff. It also raises the bar for MiTMs to intercept your session cookies significantly.
you should never have a personal browsing session on a work laptop. DISCOVERY. not even once!
That's exactly what this would solve.
Re: Show HN: Neko – Self hosted virtual browser that runs in Docker and uses WebRTC
#28I don't quite understand how this is better than just streaming your desktop? The readme says "author made this because ... his internet could not handle streaming" but this is just streaming the (in-docker) display, no?
Re: Show HN: Neko – Self hosted virtual browser that runs in Docker and uses WebRTC
#29I was kinda confused as to what this is, but I think it's meant so you can host a browser as a "server" and have multiple people stream that "browser server"? When I first clicked I thought it was going to be for programmatic testing of code.
[deleted]
Re: Show HN: Neko – Self hosted virtual browser that runs in Docker and uses WebRTC
#30I was kinda confused as to what this is, but I think it's meant so you can host a browser as a "server" and have multiple people stream that "browser server"? When I first clicked I thought it was going to be for programmatic testing of code.
Alternative to having browser (or any app) in a container and accessing its gui using noVNC (or Apache Guacamole). Except, this is done using WebRTC, what makes it perfect for viewing videos + audio of course.
I also find it confusing.
Is this just a docker-compose setup, or did you write the code? I see some go code in there, did you write the WebRTC server stuff yourself? If so, how come it's not published as a normal package which doesn't require docker?
I'm asking because I'm interested in remote desktop solutions, but in many cases I don't want/need docker, so any novel remote desktop utilities are interesting to me.