51–60 of 61 posts
Hi all, after glancing at the comments it seems that a few people are confused about Neko and what its purpose is. Neko is a self-hosted shared browser, which was built in response to a product called Rabb.it shutting down. Rabb.it had ~4 million MAUs and raised a series B before shutting down due to investors pulling out last-minute during their series C fundraising. Rabb.it was focused on watch parties. There are a…
Just FYI, Neko is also the name of the VM for the Haxe language: https://haxe.org/manual/target-neko.html
This 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!
Or is it about corporate laptops possibly spying by taking screenshots and key logging?
Earlier quoted context omitted.
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.
I 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?
But if you share your screen, you need to stream it to the peer. If this solution is already in the cloud on your VPS, meaning you only need to stream video to your computer. You send only small data of mouse/keyboard events. So if you have better down link than uplink, what is really common with asynchronous digital subscriber lines, this is definitely the better choice.
Earlier quoted context omitted.
But if you share your screen, you need to stream it to the peer. If this solution is already in the cloud on your VPS, meaning you only need to stream video to your computer. You send only small data of mouse/keyboard events. So if you have better down link than uplink, what is really common with asynchronous digital subscriber lines, this is definitely the better choice.
Probably not your fault, the title of this post saying "Self hosted" isn't clear, I thought it meant "hosted on my PC" instead of being hosted elsewhere...I had the same question until I read readme and thought about it for a moment.
Hi all, after glancing at the comments it seems that a few people are confused about Neko and what its purpose is. Neko is a self-hosted shared browser, which was built in response to a product called Rabb.it shutting down. Rabb.it had ~4 million MAUs and raised a series B before shutting down due to investors pulling out last-minute during their series C fundraising. Rabb.it was focused on watch parties. There are a…