By “shared” servers I mean hosters like https://tchncs.de/en/ who offer a bunch of services (they do a great job at it by the way) including Matrix and Lemmy.
I’m thinking of moving my close family to a Matrix chat over there, but I guess long term they might have to implement the ChatControl scanning.
This whole thing is just stupid.
By the way, if you are using Gmail for Email, have files stored on GDrive, OneDrive (Documents are by default in OneDrive on Windows) or iCloud, use Messenger, Whatsapp, Skype, Snapchat, Xbox or Instagram to communicate, your files and messages are already being scanned for the last 5 years, since 2021.
ChatControl was already voluntary, and the products I mentioned villingly joined and are already doing it. For most of the people suddenly complaining, not much actually changes. They could do something about it for the past 5 years - not use the apps that do it, but “I don’t want to install another chat apps, I have everyone on messenger” have been forcing people like me to choose between privacy and having a way how to contact friends and familly. And I’m 90% sure that most of them vouldn’t switch even if this new law did not pass.
Anyway, if you haven’t already, look up “Matrix ansible project”, it’s an extremely easy way how to set up a server, with awesome guides and actually a very robust implementation. It will save you a lot of time. I"m just paying 6$ a month for Hetzner cloud, and setting it up took like an hour tops.
Self-hosted open source solutions will always be an alternative, the major problem is that they will soon ban side-loading of apps to phones, so you won’t be able to install a FOSS messenger that connects to your solution, or a browser that doesn’t scan you, unless you have something like GrapheneOS.
Hopefully this announcement will still push people to FOSS messengers.
I personally moved most of my data from Google and Microsoft around 2 years ago. Sure, they still have the data until 2021, but there’s no time machine, we can only act on the present.
My main issue with Matrix is the onboarding process. I just tried myself with two accounts, one on Fluffychat, the other on ElementX, the verification process is buggy (didn’t work the first time, I had to restart the apps for it to work), and even after you verify, ElementX will still show FluffyChat messages with a red warning because “this message has been sent from a device not verified by the sender”, while there is no way to verify the device on FluffyChat.
And I had to use FluffyChat as multi-account is still not available in Element X.
Anyway, I just set up DeltaChat on my girlfriend’s phone, we’ll try in out in the coming days. I keep an eye on second-hand Pixels with GrapheneOS, but one step at a time.
To be honest, I’m only using Matrix for the bridges into every other service, so I can talk to people on messenger, signal, telegram, discord and whatsapp through a single app, the Matrix client, so I at least don’t have spyware on my phone, even though they’ll get my messages. And E2E encryption doesn’t apply in that case, so I never had to deal with it.
With self-hosted solution, your main advantage is that you can simply create the accounts on the server side, and don’t need any verification. After the first login, it usually asks for every new device, that you have to confirm the session on a device that’s already confirmed, but I never had issues with that.
But I don’t have experience with actuall Matrix to Matrix communication, I just used the bridges. Haven’t tried DeltaChat yet, but tbh I’ve just given up convincing people to switch and am glad I can at least have the bridges working, so I never have to login or use any apps or websites of FB/Discord/whatever.
It’s still a good idea because the clients will show a scary warning for everyone else
just install LineageOS or but a fairphone or vollaphone or shiftphone or furyphone with it preinstalled. or get a linux handheld device like the comet or pinephone or precursor et al
there is no using exploitative tech without financially running off a cliff. sooner you change the better
Good point about LineageOS. I’m just afraid of bricking the devices.
i find i overcame the fear after rewriting the how-to on lineage os’s site. it is shite, seriously fifty “steps” to do something that takes 3
edit: i am recalling downloading the OS and the “bootstrap OS” (think of mobile-computers as having two OS:s. in the case of every thing good ever i use TWRP as the bootstrap OS as it is the facto and free libre open-source. each OS on a mobile-computer is coded to fit that mobile-computer, so in a sense it is stepping back to the time before the PC and undoing the case for portability. like undoing GNU/Linux. which runs on any PC. the bootstrap OS TWRP is uniquely programmed for each mobile-computer. as is the OS LineageOS. think of it like an ignition motor and a car engine. you need both to be fitted to the (mobile computer.) that all typed out: so i download both for that specific brand/series/model/variation and that’s done. seems overly complicated because it is unusual for us who otherwise just install the same Linux on any computer we have.
no worry about bricking if you flash wrong OS version. you reflash and don’t read what the fearmongerers type online. the mobile distro community ar worse than the bad parts of Windows & Arch followers combined: lots of l33t h4ck3r5 without substantial claims to what they’re frightening you about or suggesting you do (“it just works trust me bro”) and elitism about which opinion is the best opinion to hold. like “oh, you use That? idk anything about that but use this one it never failed me =)” links to a google drive with a proprietary file they just asked you to install based on Trust Me Bro.
so anyways TWRP and LineageOS stands out as the most organizational or institutional in that uh digital landscape oe whatchamacallit.
second is to enter the phone’s BIOS into a “flashing mode” to install the bootstrap OS TWRP. next you restart and directly boot into the bootstrap OS TWRP - shittified as mobile-computers are the BIOS will delete TWRP and reinstall the factory default bootstrap OS if we start the main stock Android OS… inside TWRP the OS LineageOS is installed. once this is done the main OS will keep the bootstrap OS.
that was all the steps. done.
download TWRP & LineageOS to your Linux distro. turn off your phone, connect it to your computer.
turn to your phone and boot it into flash mode, turn to your computer to have it send TWRP across the wire: this is installing TWRP.
turn to your phone and boot it into TWRP, inside you have an install mode that mimics the BIOS’ flash mode. turn to your computer to have it send LineageOS across the wire: this is installing LineageOS.
programs required on your Linux distro: ADB (Android Debug Bridge). period. you use ADB to verify if your connected phone is picked up by ADB by using a command to list all devices found by adb. i take this as a given troubleshooting step after rebooting my phone for the first time. into flash mode. it is assumed to be all good while rebooting the second time. (into TWRP.) by te third reboot the phone it’s already done so no need to verify ADB picks up the phone.
depending on brand you can require a program for flashing the bootstrap OS & main OS. Samsung brand phones require a program called heimdall to send TWRP & LineageOS since doing it by ADB is - thanks enshittification - made tedius to do by hand. think of heimdall as an automation script for using ADB on specifically Samsung phones.
ask for more experience. remember this is daunting because people are scaremongers and you are missing out on something child’s play simple.
Thank you for the edit!
you and all lurkers are welcome =)
wouldn’t be motivated to divulge anything without ya asking or bringing it up
I’m glad I just got it installed!