A lot of technologies are at hand for P2P communication, which, if you abstract and design it somewhat intuitively, means even more stability and comfort than with just a server.
And no one is saying that there should be no server ever. Forcing a connection to a proprietary server without alternative options is obviously bad, but having a FOSS, self hosteable server with a managed option for non-selfhosters would pretty much be perfect.
So you’d have an application level, eg. for native functions like a shared clipboard.
An API level, so third party apps can synchronize/move to other devices.
A remote device level, which represents all devices you can push data to. Also manages automatic (0/1 click) pairing over NFC and LAN, and manual pairing over Bluetooth, Direct Wifi, and Servers.
A transport level, which presents NFC, Bluetooth, Direct WiFi, LAN, Server(s) and whatnot as an option for the device level, and manages the availability of transports per device. Transports are chosen based on eg. privacy * speed.
Now I want to implement that shit but have no time to do that :c
A lot of technologies are at hand for P2P communication, which, if you abstract and design it somewhat intuitively, means even more stability and comfort than with just a server.
And no one is saying that there should be no server ever. Forcing a connection to a proprietary server without alternative options is obviously bad, but having a FOSS, self hosteable server with a managed option for non-selfhosters would pretty much be perfect.
Now I want to implement that shit but have no time to do that :c