Thats a very fair point. My mistake was, that when I say “talk to each other”, my brain implicitly says “talk via text over messages”. Even then omemo is not universally supported yet, I think, so, encrypted messages can also be hit or miss.
But in OP’s case, this still kind of works, in the sense of, it doesn’t matter which instance of movim they and their friends are on, they will still be able to intercommunicate, right?
There are some misconceptions here, probably because your experience with the internet outside of these decentralised / federated services has taught you those.
1.) Servers are expected to be online 24x7. Clients can go offline and online as they please, but servers are always always always online. Otherwise very strange things start happening.
2.) Peer to peer stuff is generally speaking, somewhat brittle, because of the kinds of compromises it comes with.
3.) Signing up on an xmpp server managed by someone else is still not signing up to a centralised service. Its still just one node on the XMPP super network. Your friends can still sign up on some other server, and you can still talk to each other, with whatever clients you prefer.
There may still be a case to be made for installing movim on your own computers, but I’d say, go with the easy route and pick any movim instance from the link shared above.
This is maybe a bad idea: if you want reliable services, you need a hosting with some experience and reliability. You also want things to run on a real server, not your desktop. Servers are expected to be online 24x7, not only when you are awake. Also, AFAIK, bazzite is meant to be a desktop distro, not a server distro.
If you just want to enter the XMPP ecosystem, the answer is not necessarily self hosting: you could opt for one of many open sign up servers (for example, conversations.im).
You also dont need to self host movim, just pick any instance you want from https://join.movim.eu/ .
The beauty of XMPP is this: you can use any server, and any client, and you can talk to anyone connected to the larger XMPP network, even if they made different server/client choices than you did.
On the other hand, if your primary motivation is to learn, disregard all of the above. You learn by trying things and making errors and reading documentation and trying again, and reliability is a remote possibility that might come true (or might not) at the very end of your journey.
You aren’t missing anything about jellyfin.
I should’ve been more specific. I meant, internet of terrible things.
I’m a big fan of small appliances talking to each other and reporting status and being remote controlled, but not in its current commercial form. And yes, ever since we have had networking, we have had nerds attempting to make small devices talk to each other and do useful things remotely.
In the late 19th century, wasnt it just Karachi, India?
So, the web works on http (and https). When you ask for some content (“make a request”) on the web, the place you asked (“the server”) replies with the best content they can find for what you asked, along with a short code as a hint of what the reply contains (“the response”). You may be familiar with the response code 404, which signifies the thing you asked for could not be found, and the actual reply usually contains a cute error message saying the same thing. You can think of the response content as the part of the response meant for humans, and the response code as the part of the response meant for other computers.
Response code 418 is a joke response code put into the standard (it was an RFC document for the 1St of April for some year). It is meant to signify that the server cannot really fulfill your request, because in reality, you aren’t talking to a real server, but a teapot some nerd managed to hook up to the internet (this was before the era of IoT was upon us and every appliance wanted to be smart and connect to the internet.)
So, it can be viewed as the “sir this is a Wendy’s” joke counterpart of the http response codes.
Me: “Hey computer, go find me the post with most activity in the past 6 hours.” Server response: “error 418. Sir, this is a teapot…”
Possibly because the version stored on disk is heavily compressed (the keyword squashfs comes to mind), and its expanded to its full form when its in memory?
I’ll try and believe in the guy to not be a troll.
It could just be bad UX from a Lemmy app. In voyager, for example, it isn’t always clear while browsing a feed, that an image post also has text in its body. But the app lets you reply from the feed view. So, you see a screenshot in your feed, tap the image instead of the post, so you just see a bigger screenshot, and there’s no hint in this view, that there might be text in the body. So, you just type up a reply from there.
I think you are using RSS the way it was meant to be used, or, at least, the way I have been using it for years.
I my opinion, RSS isn’t meant to be your primary source of consumption, but your primary source of notification. For learning about new content being available. Instead of signing up for 165 newsletters, email subscriptions, or, in the worst form, downloading an app -> register an account -> subscribe to feed, you put the feed in your RSS client (which doesn’t require identifying yourself to the content provider in any form, registering interest, etc), and are notified when something new pops up.
Youre right, it was in British India, where the British government came up with this scheme of rewarding the locals with money for captured / killed snakes in hopes of controlling the local snake population.
Hey look, a pawrio!
Exactly, yes. One key difference in android v/s OSMand is that organic maps’ route calculation is way faster.
Maybe take a look at VOD Ninja ?
If you don’t mind paying for a solution, you could setup peertube on any vps, and connect it to any S3 compatible storage. Self hosted doesn’t always have to mean “self hosted in my basement”
When you hit enter on the DD command, and your main storage light suddenly starts flashing.
Germans, many hundreds of years ago : “hold my beer”.
(German word for Wednesday is called Mittwoch, literally, “weekmiddle”.)