4 ms·
I'm not entirely sure I see what your describing with certainty, but are you talking about essentially a "barrier client appliance?" A dongle you plug into all
by loxias 5y ago
I'm not entirely sure I see what your describing with certainty, but are you talking about essentially a "barrier client appliance?" A dongle you plug into all the machines you want to control using barrier, which connects wirelessly to the barrier server daemon running on your main computer?
If so, neat idea, and I've done stuff like that before. You can even have the client appliances be configuration free -- they announce themselves to the network and the server pushes out after pairing.
Interesting and fun to build, but I don't quite see the use of such a thing. It would still require running the barrier server on your laptop. I'd try to possibly go a different direction: A cheap device (RP2040 based?) that sits in between an external keyboard and your laptop. Other copies of the same hardware plug into the usb ports of other computers you'd wish to control.
- zanecodes 5y agoMore or less, but in my case I would only have to run the barrier server on my personal desktop, and won't have to install any software on the client I wish to control (in this case, my work laptop). I'd like to piggyback off of the existing Barrier code, since I already use Barrier to control my personal Surface Pro, which also sits on my desk. I really wish my 49" Samsung Odyssey G9 supported DDC over DisplayPort, so I could also switch my monitor input via software, and essentially have a KVM without buying any additional hardware. A major consideration for me is avoiding introducing any extra input latency between my input/output devices and my personal desktop, since I use it for gaming. I'm okay with trading off additional latency when controlling my work laptop in exchange for lower latency on my main desktop. That said, I may end up using my BeagleBone rather than my Photon, since it has an ethernet port, and running Linux may prove advantageous.