rustdesk-server VS hyperswarm

Run 2 instances of the Docker container rustdesk/rustdesk-server with hhbr and hhbs and it will work locally. It can also work in a single container with the s6 overlay variant.

https://github.com/rustdesk/rustdesk-server

WD=/opt/rustdesk #rm $WD/ -R mkdir -p $WD/{setup,data,web} cd $WD/setup cat << 'EOF' >docker-compose.yaml version: '3.7' #Links #https://hub.docker.com/r/rustdesk/rustdesk-server/tags #https://rustdesk.com/docs/en/self-host/rustdesk-server-oss/docker/ #https://github.com/DoTheEvo/selfhosted-apps-docker/tree/master/rustdesk #https://github.com/rustdesk/rustdesk-server#s6-overlay-based-images #https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/relay/ #https://rustdesk.com/docs/en/dev/build/web/ services: rustdesk_server: container_name: rustdesk_server hostname: rustdesk_server image: ${SERVER_IMAGE} # network_mode: host networks: - rustdesk_net ports: - 21115:21115 - 21116:21116 - 21116:21116/udp - 21117:21117 - 21118:21118 - 21119:21119 volumes: - type: bind source: /opt/rustdesk/data/ target: /data environment: - 'TZ=${TZ}' - 'RELAY=${RELAY}' - 'ENCRYPTED_ONLY=${ENCRYPTED_ONLY}' - 'KEY_PUB=${KEY_PUB}' - 'KEY_PRIV=${KEY_PRIV}' rustdesk_web: container_name: rustdesk_web hostname: rustdesk_web image: pmietlicki/rustdesk-web-client:latest # network_mode: host networks: - rustdesk_net ports: - 5000:5000 volumes: #docker cp rustdesk_web:/app . #sed -i -e 's/supportdesk.itportaal.nl/sub.domain.com/g' ./app/build/web/main.dart.js #sed -i -e 's/OvYPJS8I5xV+d6sx3a7Ce9TVakfKdT3Zy3T7C1jjx+A=/PUBKEY/g' ./app/build/web/main.dart.js - type: bind source: /opt/rustdesk/web/app/ target: /app - type: bind source: /opt/rustdesk/data/ target: /root environment: - 'TZ=${TZ}' networks: rustdesk_net: driver: bridge EOF

git clone https://github.com/rustdesk/rustdesk-server.git --branch 1.1.7-4

Rustdesk also may or may not require the installation of a relay/rendezvous server, which is where the confusion starts: one may use the free Rustdesk public server, or install one's own, custom-built server, for which Rustdesk provides a "free open source and free server program"; dub this "server2."

Ever wanted to remotely access your desktop from anywhere, then tried software like TeamViewer, but it eventually stopped working? Try open source RustDesk that is simple to set up, and you can even self-host your own rendezvous/relay server (or use the free public server). RustDesk allows you to access your desktop computer from your BOOX device. I often use it to see what is going on when I am running some simulations remotely (below is a screenshot of my Tab Ultra accessing my laptop). Because I use a dark theme on all my LCD/OLED devices, I invert the display colors of my laptop to get a better-looking video feed on my Tab Ultra (I believe light themes look much better on e-ink).

The last I checked the Windows version of the server was a few versions behind. So if you use that version it might not have all the features of the current server version on Linux. You can go here https://github.com/rustdesk/rustdesk-server/releases and look for release 1.1.6-2 to find the Windows version of the server.

It took me a minute to realize this, but HyperShell seems to be (or can be thought of as) a demo app for the (previously unknown to me) "hyper ecosystem"---Hyperswarm, Hypercore, Hyperdrive, etc: https://docs.holepunch.to/ . Perhaps an even tighter example than HyperShell is hyperbeam [1]: look at the usage section and API, and then note that it's all implemented in like 200 lines of code.

I'm no expert in this field, but this stuff looks like legos for cutting-edge P2P solutions. I think this is the coolest thing I've seen since Tailscale.

[1]: https://github.com/mafintosh/hyperbeam

- https://github.com/hyperswarm/hyperswarm

Thanks for all of your great questions!   We're using Hypercore protocol which uses something called Hyperswarm to connect peers over DHT/Kademlia. What's really neat about a Hyperswarm version that was released is you can create a firewall and whitelist specific public keys of peers that are allowed to connect to you. If a peer is not whitelisted then no exchanging of IPs happens.   We've also thought about eventually adding a mix net like I2P over the network for added anonymity.

With things like Hyperswarm [0], building things like that is easier than it used to be

[0]: https://github.com/hyperswarm/hyperswarm