Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
Fewer Letters More Letters Git Popular version control system, primarily for code NAS Network-Attached Storage RPi Raspberry Pi brand of SBC SBC Single-Board Computer
[Thread #17 for this sub, first seen 10th Aug 2023, 17:55] [FAQ] [Full list] [Contact] [Source code]
Us, selfhosters - sure.
Average person who value convenience over privacy/cost - no. They’ll continue to pay and be in prisoned by the cloud.
Some might say they’re freeing themselves in a way though. Self hosting requires dedicating time you could spend doing other things especially when things break. People pay for convenience and saving time. When we simplify self hosting and updating to a point people can just download apps and press go then it will make sense for the average person
This. Self-hosting doesn’t need to be a nerd thing.
Docker kinda does it by being like an app store but for servers. It’s not very flexible but everyone using a particular image gets the same experience.
Looking at old defunct forums and blogs on the Wayback Machine, spam and security problems are frequently-cited reasons for shutting down or going read-only.
Over time, the internet has gotten more hostile.
This article, as much as I agree with it, conflates cloud hosting and remote-only software design. Cloud hosting really is a prison, but mostly for developers that are lured by its convenience and then become dependent on its abstractions. What we experience today in most mainstream software isn’t necessarily coupled to cloud hosting, but is instead a conscious product design choice and business strategy to deny users power and control of their data. In short, cloud providers like AWS, Azure, and GCP are doing to software companies what those companies are doing to us. There is a way to use shared data centers without this kind of software design philosophy. As mobile continues to dominate, the solution we need likely involves remote servers but with a model that treats them with skepticism and caution, allowing data portability and redundancy across a variety of vendors. I should be able to attach a few hosting services to a software experience I use and transfer my data between them easily. The idea that local-first software is “freed from worrying about backends, servers, and [hosting costs]” is misleading, since my local device has to become the client and/or server if there is any connectivity happening over the internet. Wresting control of our data from the dominant software companies will require creating experiences that are not only different, but better, and doing that with a mobile phone passing between cell towers functioning as the server is a tall order. We have grown to expect more than intermittent connectivity with conflict resolution. Nonetheless, we absolutely should not accept the current remote-only software paradigm, but instead need to devise better ways to abstract how remote hosts are inhabited and create a simple multi-host option that is intuitive for consumers.
Hey, you make a great point. There’s a false dichotomy being presented here. As you see it, local-first is a bit of a misnomer when you already expecting your device to join a remote environment.
Yes, makes sense that we’re being lured by the so-called cloud hosting. Following a business model that sells convenience in lieu of data control, cloud providers are distorting our current understanding of remote hosting. They’re breaking the free flow of information by siloing user data.
Now, with that being said, I’d like to add something about your presentation. I’d suggest you avoid walls of text. Use paragraph breaks. They’re like resting areas for the eyes. They allow the brain to catch up and gather momentum for the next stretch of text.
Regardless. You brought light to this conversation. For that, thank you.
I’m glad you found my take engaging!
Paragraph breaks now enabled.
