SMS/MMS was working but only with individual conversations. Any group messages would fail. RCS is supposed to fall back on MMS when some recipients can’t use RCS but something about the handshake was broken and it never would do that. I spent two months trying to sort it out and I never could.
Buying a Google phone in order to get rid of Google seems sort of counterproductive, doesn’t it?
You’re correct. EU users didn’t adopt, or at least continue to utilize, SMS based messaging like users in the US did. This is not a problem for anyone using web based messaging like the ones you mentioned.
I switched away from e/OS for this very reason. As much as I hate SMS based communications it just isn’t practical to ditch them completely in the US. It’s simply too widespread.
Just so happens I have some myself. It is air pressure based.
It’s pretty good stuff. Plant based, easy to apply, higher smoke point than olive oil.
It doesn’t work that way. There will be many reasons to celebrate, sure, but this problem doesn’t go away with a few obituaries.
That’s what she said
Then acknowledge you’re making a conscious choice to accept the sandwich someone else made
Same. When I first started down that path I kept finding posts about how it was impossible to set up and maintain but it’s been pretty painless for me. I basically had no clue what I was doing and I figured it out just fine.
There are certainly things you can do with a server at home that would be off topic for this community, right?
I don’t want to hear about hosting CSM but anything else is fair game imo
If you click through some of the options on this page: https://jellyfin.org/contribute/
It links to a donation option here: https://opencollective.com/jellyfin
If you use it weekly it shouldn’t be free to you, certainly if you use it more frequently than that. Give money to the projects you depend on or they will disappear.
Ah, that makes sense. If only straight lines were the norm 😁
What does the electrician need to get up there for? It looks to me like that is already done. I’m not saying you’re wrong just that I think caulk is the best you can do to finish it out from this point both in terms of finished look and ease of removal in the future. Of course it would be better if you had a square and plumb room to work with but that ship has long since sailed.
Caulk is removable
Copy/paste from another comment I made a while back:
Look into docker containers in general. If I was going to start from scratch in your position this is what I’d do:
Install a Linux distribution on the computer you plan to use for self hosting. This can be anything from a raspberry pi up to a custom build but I would recommend starting with something you have physical possession of. I found Debian with the KDE plasma desktop environment to be pretty familiar coming from Windows. You could technically do most of this on Windows but imo self hosting is pretty much the only thing that a casual user would find better supported through Linux than Windows. The tools are made for people who want to do things themselves and those kinds of people tend to use Linux.
Once you have a Linux distribution installed, get docker set up. Once docker is set up, install portainer as your first docker container. The steps above require some command line work, which may or may not be intimidating for you, but once you have portainer functional you will have a GUI for docker that is easier to use than CLI for most people.
From this point you can find the docker installation instructions for any service you want to run. Docker containers have all the required dependencies of a given service packaged together nicely so deploying new services is super easy once you get the hang of it. You basically just have to define where the container should store it’s data and what web port you want to access the service on. The rest is preconfigured for you by the people who created the container.
There’s certainly more to be said on this topic, some of which you would likely want to look into before you deploy something your whole family will be using (storage setup and backup capability, virtual machines to segregate services, remote accessibility, security, etc). However, the above is really all you need to get to the point where you can deploy pretty much anything you’d like on your local network. The rest is more about best practices and saving yourself headaches when something breaks than it is about functionality.
That’s overly dramatic phrasing and you know it. Adding this kind of hyper technical quip to a thread aimed at beginners is insane. Stop doing that.
Look into docker containers in general. If I was going to start from scratch in your position this is what I’d do:
Install a Linux distribution on the computer you plan to use for self hosting. I found Debian with the KDE plasma desktop environment to be pretty familiar coming from Windows. You could technically do most of this on Windows but imo self hosting is pretty much the only thing that a casual user would find better supported through Linux than Windows. The tools are made for people who want to do things themselves and those kinds of people tend to use Linux.
Once you have a Linux distribution installed, get docker set up. Once docker is set up, install portainer as your first docker container. The steps above require some command line work, which may or may not be intimidating for you, but once you have portainer functional you will have a GUI for docker that is easier to use than CLI for most people.
From this point you can find the docker installation instructions for any service you want to run. Docker containers have all the required dependencies of a given service packaged together nicely so deploying new services is super easy once you get the hang of it. You basically just have to define where the container should store it’s data and what web port you want to access the service on. The rest is preconfigured for you by the people who created the container.
There’s certainly more to be said on this topic, some of which you would likely want to look into before you deploy something your whole family will be using (storage setup and backup capability, virtual machines to segregate services, remote accessibility, security, etc). However, the above is really all you need to get to the point where you can deploy pretty much anything you’d like on your local network. The rest is more about best practices and saving yourself headaches when something breaks than it is about functionality.
I don’t know for sure but my guess is that a lot of US users thought you were wrong because they don’t know that SMS / MMS is essentially dead in the EU. It’s still the primary text based communication method in the US.
MMS supports all the things you mentioned (albeit in a shittier way) except encryption. RCS adds a new layer that is more like Signal in that it supports encryption and emojis and a few other things but it is controlled by Google and there are no open source alternatives currently.