vas

joined 1 month ago
[–] vas@lemmy.ml 2 points 3 weeks ago

Not sure yet, a bit too far away to tell. Living in NL though, so could definitely try to join if the tickets are affordable enough for me..

[–] vas@lemmy.ml 3 points 1 month ago (1 children)

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.

[–] vas@lemmy.ml 4 points 1 month ago

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.

[–] vas@lemmy.ml 1 points 1 month ago (1 children)

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)

[–] vas@lemmy.ml 2 points 1 month ago

No problem; thanks for trying to help!

[–] vas@lemmy.ml 1 points 1 month ago (2 children)

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?)

 

Hi! On the official web page for "Proxy Support - Signal Support" they mention that setting a proxy is not supported on the desktop clients.

However, when did such labels ever fully deter skilled Linux users?

My question is, did anyone succeed in rootless SOCKS5 configuration for Signal? I know it can be done with e.g. a new network namespace by executing a series of root commands. For example, like whonix does to put Signal-desktop in Tor. Is there anything a bit more gentle and localized? Ideally I'd include it into a bubblewrap (bwrap) configuration that I already have around.

If you've looked into that at any moment but didn't find any straightforward solutions, please write as well. It's OK, but still valuable to read.
Thx!

[–] vas@lemmy.ml 7 points 1 month ago* (last edited 1 month ago)

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.

[–] vas@lemmy.ml 2 points 1 month ago

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

[–] vas@lemmy.ml 1 points 1 month ago* (last edited 1 month ago) (1 children)

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

 

Good day dear Lemmy community!
When I try to use lemmy's private messages, I get the following warning:

Warning: Private messages in Lemmy are not secure. Please create an account on Element.io for secure messaging.

It is very good to have this warning! However, can it be improved?
When I first encountered this wording, I was completely unsure whether the DMs would be totally public due to lemmy's limitations or its open stance, or whether the messages would have a similar security to e.g. email where your trust relies on TLS and the servers involved.

My proposal would be to change the wording to something like:

Warning: Private messages in Lemmy are not End-to-End encrypted. Please create an account on Element.io for secure messaging.

Or if the team is open to it,

Warning: Private messages in Lemmy are not End-to-End encrypted. Please use a platform with E2E encryption for private messaging.

Or if the team is even more open to it,

Warning: Private messages in Lemmy are not End-to-End encrypted. Please use a platform with E2E encryption for private messaging. Lemmy recommends Element.io and XMPP.

Thoughts? I'm ready to create a PR.

[–] vas@lemmy.ml 1 points 1 month ago

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.)

[–] vas@lemmy.ml 9 points 1 month ago* (last edited 1 month ago) (1 children)

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.

[–] vas@lemmy.ml 1 points 1 month ago (1 children)

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.

view more: next ›