What I Self Host

There seems to be a fad for "self hosting" things now. What I don't understand is: what happened to just having a single device and having it run the code directly and show you the result directly? For example, why can't the thing that connects to the Spotify API just... do that, from a program that runs locally, independent of a web browser, with a GUI created using a standard non-web GUI toolkit? Why would I want to use it by pointing my browser at a machine name (of another device I own) and port number, rather than by launching a dedicated program?

I think people don't know what they want, but they like fiddling with computers. So, they imagine future scenarios where they would have problems (which they don't) and imagine solutions for those problems they don't have, and spend time implementing those solutions.

For example. Whenever RSS comes up, I say that newsboat is the best thing. People don't like it because it doesn't synchronize devices. Really? Why not have a device for reading, and read there? I have newsboat on my laptop and I A) don't have to read on my phone, B) can't read on my phone, and C) don't have to spend my free time doing unpaid maintenance for a job which I created for myself. Win-win-win.

> Why not have a device for reading, and read there?

I'm curious to know why you think this way of doing is "correct"? I like reading my RSS feeds on my phone. And on my laptop. And on my tablet, sometimes.

I didn't use the word "correct", you did.

In any case, if you're reading on your phone it's most likely because you're addicted to your phone and open the app impulsively. Consider that.