Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Neko – Self hosted virtual browser that runs in Docker and uses WebRTC

github.com

Post reply on HN
Print view View original

31–40 of 61 posts

Re: Show HN: Neko – Self hosted virtual browser that runs in Docker and uses WebRTC

#31

Post by m1k1o »

JeremyNT wrote: post #30
m1k1o wrote: post #4

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.

This repository features all custom writen code. Go backend and Vue frontend. It is publised as a container because of lots of dependencies and the overall environment setup.

Although, I think about publishing the core of it as a package, fully fledged alternative to noVNC. Where X server desktop can be shared using WebRTC technology to a browser.

Re: Show HN: Neko – Self hosted virtual browser that runs in Docker and uses WebRTC

#32

Post by m1k1o »

jfrunyon wrote: post #28

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.

Re: Show HN: Neko – Self hosted virtual browser that runs in Docker and uses WebRTC

#33

Post by JeremyNT »

m1k1o wrote: post #31
JeremyNT wrote: post #30

Earlier quoted context omitted.

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.

This repository features all custom writen code. Go backend and Vue frontend. It is publised as a container because of lots of dependencies and the overall environment setup. Although, I think about publishing the core of it as a package, fully fledged alternative to noVNC. Where X server desktop can be shared using WebRTC technology to a browser.

> Although, I think about publishing the core of it as a package, fully fledged alternative to noVNC. Where X server desktop can be shared using WebRTC technology to a browser.

I think that would be nice! There are a lot of ways to approach this (I've used xpra, vnc, remote X, xrdp...) and there are pros/cons to them all. It might be useful for more people without the docker requirement :)

Re: Show HN: Neko – Self hosted virtual browser that runs in Docker and uses WebRTC

#34

Post by noobermin »

m1k1o wrote: post #32
jfrunyon wrote: post #28

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.

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.

Re: Show HN: Neko – Self hosted virtual browser that runs in Docker and uses WebRTC

#35

Post by mirotalk »

Wow! So there is the possibility of having remote screen control using the WebRTC for the stream and then other trick for the mouse coordinates and keyboard! I hope to be able to integrate it also in https://github.com/miroslavpejic85/mirotalk that would be great! Thank you so much for sharing! Maybe I can try to do it looking from: https://github.com/maxogden/screencat

Keep it up!

Re: Show HN: Neko – Self hosted virtual browser that runs in Docker and uses WebRTC

#36

Post by ScottyFillups »

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 few reasons why shared browsing is more appealing than video sync and screenshare for this use case:

1. Screenshare requires good uplink—some people only have good download speeds

2. Some people are uncomfortable with sharing their screen, nobody likes being judged for their bookmark choices

3. Nobody acts as a "host", control can be passed around to anyone and people can leave whenever they want

In other words, you get the content variety of screenshare, but with the convenience of video sync.

And now for a shameless plug :)

Hyperbeam (formally Tutturu.tv) is a site I built in 2019 for my capstone project at the University of Waterloo. I built it because I wanted an easier way to watch anime with my friends, and decided to build something similar to Rabb.it. It's hosted and free! https://hyperbeam.com

Re: Show HN: Neko – Self hosted virtual browser that runs in Docker and uses WebRTC

#37

Post by Orphis »

mirotalk wrote: post #35

Wow! So there is the possibility of having remote screen control using the WebRTC for the stream and then other trick for the mouse coordinates and keyboard! I hope to be able to integrate it also in https://github.com/miroslavpejic85/mirotalk that would be great! Thank you so much for sharing! Maybe I can try to do it looking from: https://github.com/maxogden/screencat Keep it up!

There are no APIs in WebRTC about remote screen control. You can share a screen, but that's it.

Re: Show HN: Neko – Self hosted virtual browser that runs in Docker and uses WebRTC

#38

Post by JasonFruit »

SavantIdiot wrote: post #21
kitd wrote: post #17

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. https://en.wikipedia.org/wiki/Neko_(software)

Obviously less relevant.

Re: Show HN: Neko – Self hosted virtual browser that runs in Docker and uses WebRTC

#39

Post by numpad0 »

jcun4128 wrote: post #26
funnyflamigo wrote: post #25

Earlier quoted context omitted.

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.

“userland” is a UNIX term that roughly means “apps” but in ancient sense. UserLAnd is just an app for Android using that word stylized as its name.

Re: Show HN: Neko – Self hosted virtual browser that runs in Docker and uses WebRTC

#40

Post by hedora »

JasonFruit wrote: post #38
SavantIdiot wrote: post #21

Earlier quoted context omitted.

It's also a 30-year-old X app that draws a cat which chases your cursor. https://en.wikipedia.org/wiki/Neko_(software)

Obviously less relevant.

My first question was whether I could run the cat thing in this.
Post reply on HN