adry

this is self-hosting local-first apps. There’s some local-first manifesto somewhere… one of their greatest ‘backend’ developments were CRDTs. The idea, is that the app can be turned off, synchronization can be interrupted and resumed, and so on. Those CRDTs allow people to use a text editor even when the client(s) are disconnected from the server. Of course, depending on how much your version differs, the merge conflict of diverging versions will be easier to solve…

Ah, I saw this term in the past. Never understood, I could barely see the relationship to US elections. And, I’m a complete alien to the sophisticated methods billionaires use to sustain their US dictatorship, but it seems to me that this only works because of some “given” stuff like having only 2 parties, and having electorates… Disclaimer: I don’t want to bother that much into understanding this, like going through lengthy articles on the web. But will definitively read your answers (thanks!)

+1 I use it to on all of my devices for sharing 1 folder, just set one as introducer, and keep adding nodes (e.g. phone, Work mini, laptops, PC, …) Once you have that set, start adding folders as needed for specific cases (e.g. a folder shared among all mentioned except for Work mini.)

As other comments mentioned, Push Notifications, your main issue has workarounds. So, the answer would be Yes.

BUT Google Play Services is much more than that. This dependency can’t be worked around really and it’s one more way that Google establishes his stance in this oligopoly. I’m certain Apple has something similar if not more aggressive. This is the reason why the year of the Linux Phone is so far away.

Personally, I think Linux Phones will catch-up when their hardware allows for emulation of an android subsystem where we could sideload (illegally?) Google Play Services…

Spain? check guifi.net ;)

People had LAN Partys playing video games “offline” in the 90s… Setting up a network is easy, the difficulty comes from scaling up to many nodes, and spreading through the geography (e.g. if you were to use antennas for WLAN, they would need a mostly unobstructed vision) which in urban areas gets tricky.

But those “topology” issues can be flattened, e.g. you can always have a raspberry pi (or any device) acting as server in the corner of a neighborhood. A virtual bulletin board, emails, etc. all could be self-hosted locally there and then people could go grab a coffee and consume the local news just like in the middle ages, but with a screen, digital assets and some healthy amount of trolling :P

Precisely this is what I was about to comment, Thanks. Let me add that I’m using uBlue KDE flavor (Aurora) and don’t get me wrong, I love it… but for many reasons I’d rather not be using an immutable distro. As a personal decision. I prefer the Snapper approach, it gives you the benefit without any of the ‘costs’. But that’s how I see the ‘other differences’. To me, an experienced user and programmer, these ‘features’ are drawbacks. Immutable distros are quite good for non-power users (or whatever we may call them). Anyone without enough experience to understand the output of env | grep PATH (to put it in some random terms). If you want to fiddle with your system, customize the shell, etc… some simple stuff that made me fall in love with Linux might be just too difficult in an immutable system… at least this was my experience as a +10 year Linux user. Just adding ZSH to the distro is somewhat difficult enough, so the distro mantainers added a ‘just recipe’ (which is just a Makefile, see uBlue ujust docs) to do the stuff you would consider normal if you had any CLI experience; so stuff like tweaking your system (e.g. in the past I’ve used arch btw) will now be alienated from usual sources like simple online documentation… But I had to try this to get to know it. So, all in all, I think these immutable distros are great for someone who just starts on Linux or programming, and forces them to keep a clean home directory, nothing crazy like conda, pip install, pipx, etc. which I’ve learn as a dev to use; and have full knowledge of what they do with my env. Forced me to use devcontainer, cool… I guess… So, that’s the “safety” that I got from an immutable system, just being forced to keeping it tidy. Not bad, specially for a rolling distro like Fedora (the base for universal blue/ aurora.)