You're welcome.
SwooshBakery624
These comments are crazy. Did no one actually check the publication date?
shocked pikachu face
It's an optional field in the userdb JSON object. It's not a policy engine, not an API for apps. We just define the field, so that it's standardized iff people want to store the date there, but it's entirely optional.
Hence, please move your discussion elsewhere, you are misunderstanding what systemd does here. It enforces zero policy, it leaves that up for other parts of the system.
And sorry, I am really not interested in these discussions here. it's not the right place for this, and please don't bring it here. Thank you.
https://github.com/systemd/systemd/pull/41179#issuecomment-4090834541
Yes. Russian companies pay taxes to the Russian regime, and the Russian regime uses that tax money to fund their war. Therefore, if you do business with Russian companies, you sponsor the Russian war.
Just out of curiosity: Should we boycott DuckDuckGo for using the Bing API, since Microsoft is an American company whose tax dollars go toward funding the genocide in Palestine, the war in Iran, and the economic blockade of Cuba?
I didn't know about this response, thank you for pointing it out. However, this response fails to address the main criticism of the XMPP+ONEMO:
To understand why this is true, you only need check whether OMEMO is on by default (it isn’t), or whether OMEMO can be turned off even if your client supports it (it can).
Both of these conditions fail the requirements I outlined under the End-to-End Encryption header in that other blog post.
And that’s all that I should have needed to say on the matter.
OpenBSD (and it's subprojects) are highly secure, moreso than Linux.
I highly doubt that OpenBSD is more secure than Qubes OS or secureblue.
KeePassXC 2.7.9 was released before the statement
An alternative is the old version of KeePassXC.
If only there would be a dedicated community for me to post these.