I’ll copy my comment from that other thread (since I’m subscribed to both communities):

Though it’s nice to have support from wealthy people… Building a cult around any single rich person for them to give grants to their liking is not a good idea.

Instead I believe you need to fight for your right to have privacy. Currently it’s Europe who is at risk with ChatControl ( https://fightchatcontrol.eu/ ). At other times, it’s other countries. Some open projects (like Lemmy!) get funded by the European Commission. I believe this is a healthier approach than to believe in good rich guys who’d save you.

Though it’s nice to have support from wealthy people… Building a cult around any single rich person for them to give grants to their liking is not a good idea.

Instead I believe you need to fight for your right to have privacy. Currently it’s Europe who is at risk with ChatControl ( https://fightchatcontrol.eu/ ). At other times, it’s other countries. Some open projects (like Lemmy!) get funded by the European Commission. I believe this is a healthier approach than to believe in good rich guys who’d save you.

It’s not only the efficiency boost. What about safe concurrency? Or about the tooling - does sbt really compare favorably to cargo? (I’d say “no”, having used both over multiple years)

No problem; thanks for trying to help!

Do you know if it works with Signal? (Doesn’t seem to be… Dunno why. Static build of the app? Non-http-based transport technology used by Signal?)

Based on the comments so far, maybe something like this makes sense:

Warning: Private messages in Lemmy are not End-to-End encrypted, so the respective instance owners are technically able to read them. Please use a platform with E2E encryption for private messaging. Lemmy recommends Element.io and XMPP.

I agree. That’s why I propose to clarify the wording.

Yes. And I think saying “messages in Lemmy are not End-to-End encrypted” is clearer communication than “messages in Lemmy are not secure”.

Congratulations to the team and to everyone who supports the project!

Thanks for the response! I think I’d personally try something like that, but I have no idea whether it’ll stick.

Overall, the idea of a significantly simpler (than HTML) protocol sounds intriguing, especially to break the google chrome near-monopoly.

I wanna use JXL locally. It’s quite amazing technologically, you can losslessly compress a JPEG to 0.8 or so of the original size.

I compress my photos for long-term storage anyway, so why not do it with JXL.

Thanks for the app recommendation!

(Fossify is a fork of the discontinued SimpleMobileTools.)

Personally, I’ve found Fossify Gallery so far: https://f-droid.org/packages/org.fossify.gallery/ Tried it out, it works well. Any other recommendations would be nice, too.

Signal, for example, does not support JXL as of today. But saving the photo and opening in Fossify Gallery works.

I’m using disroot a bit and I’m interested to understand this, however, what is an “html capsule”? Or should I split the sentence differently, e.g. “gemini/html” capsule? (I’ve tried searching some of those terms, but I’m getting a lot of wrong hits I think.)

Also, how does it differ from lemmy? I mean, lemmy’s pretty lightweight from what I can tell.

If I’m not the target audience for this question feel free to tell, I don’t claim that I am but I’m interested in understanding

If you’re in Europe or in the UK, and if you choose to NOT have coreboot, you can buy for half the price from PCSpecialist. I’ve been using them since 2020, totally recommend. The model that I had (Lafite pro 14) with an identical CPU, twice as much memory as reviewed (64Gb) costed just over 1k EUR in 2024. The build quality is very good.

But again, it won’t have coreboot, which is a significant downside. So I’m not saying anything against the reviewed notebook.

Good to know! I was really eyeing Triodos back in the day, due to what looked like a good ethical stance, but it didn’t work out at the time. Nice that they’ve fixed it! (I’ve updated my message above as well to include the bank.)

With respect to 2FA, if you want to be more ready for any future next time, you could migrate to an open-source TOTP app. E.g. andOTP. I use this one, it’s fine. The underlying standards don’t change in decades, so you can choose any compatible client and be without trouble for years and years. And it may be good to do in any case, googlified phone or not. Good apps also tend to provide password-protected backups.

I have no knowledge about RCS though, never used it so can’t tell. Otherwise GrapheneOS user for ~2 years, before that LineageOS, before that CopperheadOS for another few years.

You can use andOTP if you want a FOSS app on Android. If you’re a hardcore no-Android-at-all user (or considering), you can use KeePassXC on the desktop. This kind of defeats the purpose of 2FA, but on the other hand people with KeePassXC tend to have strong passwords due to ease of their maintenance, so you don’t need 2FA as much to begin with.

TL&DR; use andOTP on Android or KeePassXC on Linux Desktop.

(And noteworthy that ING has a million of different apps)

I’ve re-tried ING now, the app starts fine and the first steps to create an account are fine (I went up to the phone number and email). However, IIRC they used to break on further steps such as ABN AMRO breaking when wanting to scan my ID card for verification. But then again, you may not need it if you already passed that verification. Anyway, just letting you know if you’re curios; I’m aborting here.