Syncthing (the most recent versions, at least) also allows for password-encrypted sharing. So even if you are syncing across a relay, no data is in clear.
I built this a while back for small projects where I wanted to build a static site without introducing the whole npm/js ecosystem.
The main advantage is having re-usable parts for the HTML/CSS/JS instead of writing duplicated markup.
I usually couple this with htmx.org when I want to introduce flask/django/fastapi in the project and things work out wonderfully since I'm already in the python ecosystem.
If you have your own server and need a Github-like webinterface, gogs [0] and Gitea [1] (a fork of gogs) are stable and very easy to set up. I have been running gogs for a few years now. For me it contains the perfect subset of Github features. Previously I just pushed to a bare repo on my server via SSH.
The git.sr.ht service is just the tip of the iceberg, though. It also provides you with CI, issue tracking, mailing lists... And it works perfectly in Lynx so you don't even have to leave command line to use the browser interface.
For what it's worth, at my previous place we built a YOLO based model for detecting paragraphs/tables/headlines/page layouts mixed with traditional rule based OCR/layout detection.
> With this both share he same view but can move cursors independently.
Does this mean they have 2 separate cursors, or that that can control the same cursor? Your can sort of do the same thing in screen by using a nested screen session and sharing the outer session with the other user.
Even better than raw tmux is using tmate. I fumbled with tmux sessions and permissions for awhile but tmate makes it trivial. It's a free service but it really seems like they're leaving money on the table (I'd pay for it, anyway).
