this post was submitted on 28 Aug 2024
608 points (97.9% liked)
Technology
59357 readers
4279 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That got me interested and apparently, they fear forks running out of date.
While that statement got plenty of thumbs down, I hate to admit that F-Droid is indeed out of date quite often. I currently can't find a source for this but I once read this has something to do with their signing process.
Yes, they manually sign every package.
But they could easily have their own F-Droid repository, I have repositories for FUTO apps like Grayjay and their keyboard, Bitwarden, and Newpipe, among others. Those are run by the projects themselves, so they're in charge of how often they update it, as well as how they sign it. So if they have issues with the "official" F-Droid repositories, they can always host their own. I honestly prefer projects that host their own repos precisely because they should, in theory, update faster.
That said, a self-updating APK is good enough for me. However, I didn't see an install option easily listed on their website and had to search for "signal android apk" to find the page. It should be listed on the regular install page on their website, next to the link to Google Play. I found three separate pages for getting it for Android, and all three had a link to Google Play and only one had the APK.
Hmm, ok, thanks. But I'm kind of tired of version churn: who needs to keep changing a chat program? IRC has been around since the 1980s or so and still works fine.
some people like texting their family who doesn't use IRC, and they'd rather not send messages in plain text for one reason or another.
I get that IRC is old school and encryption is important. My question is why the program has to keep changing. If the task is simple enough, there shouldn't be incompatible changes required if there are new versions at all.
With new possibilities due to new tech user demands rise, too. People asked for features like group or video chats or coupled devices (not trivial with E2EE) and since good companies listen, they developed those and still do.
Also, I don't think there's a single IRC client still in use that hasn't been updated since the 80s. I wouldn't be surprised if your favorite client got an update in the last couple of months - and that despite it being a trivial protocol.
https://media.ccc.de/v/3e0a51f5-f60a-4a90-a78a-3a311c6ffe41 here the author explains why and it all sounds like a bucket of bullshit
Thanks, I might try to watch some of that.