

It’s not about believe. And it depends on the company; though they’re legally required nonetheless.
See also: https://www.dataprivacyframework.gov/


It’s not about believe. And it depends on the company; though they’re legally required nonetheless.
See also: https://www.dataprivacyframework.gov/


They do; foreign companies must comply with the GDPR when processing or storing European citizen’s personal data.
See: GDPR Art. 3


Depends on your provider.
Personal attacks are used by people who lack valid arguments; therefore, I will block you to protect my psychological well-being.
Anyone interested in discussing actual Signal flaws, like the unecessary phone number requirement is free to reply and do so.
I read the article in the past, and it is still as flawed as it used to be. You’re quite extremist without much legitimate reason. Signal is and will likely stay for the foreseeable time one of the most secure and private messengers.
Everyone who uses signal and supports it, is falling for this pitch.
No, because it does not reflect the truth. You’ve to see the full picture.


So that I understand you right, you’re looking to replace your FP3 with a newer model that comes with /e/OS?
I spoke to one of their team members and they said: “Regarding our SPL (“Security Patch Level”), typically our builds are made mid-to-end-of-the-month to include the newest SPL updates that trickle in from upstream (sometimes our updates are delayed to make sure they are integrated before we build). You should see the newest update made just at Christmas time includes the December SPL patches which weren’t available when we made the earlier monthly builds.”


I would recommend replacing Openboard with Heliboard, since Openboard isn’t actively maintained, while Heliboard is a fork of it and in active development.


@[email protected] Please ban this user. This is advertising, the shared blog contains a affiliate link.
Do not use CalyxOS at the moment. It lacks importmant Android security updates. I would recommend LineageOS or IodéOS (which is slightly more secure due lockable bootloader, etc.). I feel difficult about /e/OS since they have done questionable things.
DivestOS is dead and won’t come back.


That would be a violation of EU law. You cannot change such agreements without notice.


Thanks for sharing, awareness matters.
Sadly not that I’m aware; we have to wait until the time comes.
I can recommend following tools:
https://github.com/xM4ddy/OFGB (Non tech savvy friendly) https://www.oo-software.com/en/shutup10 (Beginner friendly) https://privacy.sexy/ (Advanced)
Please make sure to verify which changes you do and what possible side effects they could have.


Appeal to authority.
?
Unfounded claim.
I’ve done my research.
Has yet to be seen
I’m relatively confident that they well do the things they’ve promised.
https://getsession.org/blog/session-protocol-v2
Additional, more technical details on why you shouldn’t use Sessions:
Session has responded to that blog post, mostly debunking it. There is also a response from Soatok to their response, and they edited their original response afterward to address Soatok’s response to Session’s original blog post. Session was also audited by third parties, which had already pointed out some of the things Soatok mentioned in his blog post, and that does not mean Session is insecure or unable to compete with SimpleX, Threema, DeltaChat, Briar, and many other “private messengers.” Signal requires a phone number, which in Germany where I live, is by law attached to your identity and is also a unique identifier and an attack surface. I use and prefer Signal over Session, but Signal also has many small flaws.
https://soatok.blog/2025/01/20/session-round-2/
https://getsession.org/blog/a-response-to-recent-claims-about-sessions-security-architecture
I will also not continue this conversation further if nothing that I have not already clarified is brought up.


I believe your technical understanding is flawed, I’m a IT-Specialist for application development and Session is indeed a good competitor, thought they had some flaws which there upcoming V2 protocol would’ve fixed.
Can you provide a source for that? See also: https://www.dataprivacyframework.gov/