Signal is fundamentally centralised. It’s not going to become a distributed system like the fediverse, because the protocol’s design doesn’t work that way. (Also, its maintainers haven’t shown any interest in adopting that approach.)
If e2ee email is really what you want, you can already have it with PGP. Various email clients exist that make using PGP possible for a mortal. Good luck getting many of your contacts to use it.
If you also want modern encryption guarantees, like forward secrecy, then consider Matrix instead of email. It already does e2ee and is already decentralised.
Broken link.
To paint a more complete picture, PrivacyGuides.org comes from the subreddit of the same name. When I was last there (about a year ago) some of the people behind that subreddit had a habit of pushing misguided views as if they were facts, and did so with an air of authority that came from their control of the subreddit and the site.
My point is not to support either group, but just a warning: They are not “the privacy community”. Please take their advice with a grain of salt. Sometimes it’s good, and sometimes it is not so good.
I am not suggesting specific changes to your canary document. I am (a) explaining someone else’s question that you said you didn’t understand, and (b) pointing out that you might find better response if you clearly and briefly explained at the top of your post why you are posting it here.
To underscore (b): This community is not typically used as a vault for warrant canaries. An argument could be made that they don’t belong here. I don’t feel strongly about it so long as they don’t become a common source of noise, but if you can’t find a better place for them, I think the least you could do is say in one or two sentences why you’re posting one. Without requiring eighteen thousand subscribers (and uncounted additional readers) to sift through off-site links, or make sense of a single field in a wall of monspaced copypasta that has no obvious meaning to the majority of readers.
I think you’ve misunderstood my comment.
Warrant canaries are most noteworthy when they’re not published.
Something cannot be a warrant canary at all unless it is published. Did you mean to say it is most noteworthy when it has been published at least once, and then stopped being published? That would be an example of what I meant by a “change” in my comment.
Back to the original point: You said you don’t understand monk’s first question, so I tried to explain it to you: It was asking whether some change has taken place; some cause for alarm. A change in the document, or its removal, or a failure to update it.
The only way to know that it’s not published is to – publish it. Widely. And routinely.
Indeed. As I said in the last paragraph of my earlier comment.
Edit: In the future, if you’re going to post canaries to general forums like this one, you might want to include a short explanation for community members who aren’t familiar with warrant canaries, or who wonder why you’re posting one here of all places. You didn’t provide any context. I understand the value of posting it, but to most people, your post can easily be seen as irrelevant noise polluting their news feeds.
I’m not GP, but regarding 1:
Warrant canaries are only noteworthy when they are updated. GP is asking if this one was updated, as in whether some attestation was removed, implying that a warrant affecting that attestation has been served since the last one.
If no such change has taken place, then it’s still useful to have a copy of the canary publicly archived (e.g. here) for comparison to future versions, but there’s no reason for the people in this community to spend their time reading it.
I believe Matrix has this in beta, sometimes referred to as MatrixRTC or Element Call.
Edit: Recent status update here:
https://matrix.org/blog/2024/10/29/matrix-2.0-is-here/#3-native-matrix-group-voip-video-matrixrtc
I feel like matrix is a better alternative, but yeah it’s not ready yet since it lacks the call features discord has.
I haven’t used Discord in years. What call features are you referring to?
See also: The constant push by governments to take away our right to private (encrypted) communications.
IMHO, this community should be about technology. Novel inventions. Interesting or creative applications. Discoveries. Dangers, advances, impacts, experiments, tutorials, etc.
Instead, it’s overrun with stock market and business news having no more to do with technology than CEOs of wood pulp factories have to do with literature.
I wish Rule 2 was phrased in a way that clearly excludes the latter, and enforced.
Some of us do, but that doesn’t remove the unending flood of business news and corporate drama that we don’t want in our feeds, so it doesn’t solve the problem.
I think it has to be focused on software or hardware as a rule.
I don’t. Those fields are but small slivers in the realm of technology, and they’re not even particularly novel any more. A community dedicated to one or both of them might make sense, but there’s no reason to let them dominate the technology community.
News about stocks, CEOs, rebranding etc should not be allowed.
I agree with you there.
SimpleX has some interesting ideas, but also some shortcomings for people who want a practical messaging service. For example:
I look forward to seeing how its design decisions develop in the coming years, but outside of a few niche use cases, it is not a suitable replacement for Matrix or Signal.
Micropython is an interpreter, implemented in C. Anything running in it wouldn’t be an operating system in the sense that we usually mean. Anything incorporating it wouldn’t satisfy OP’s goal of being “only Python”.
If a CPU were developed that used Python bytecode as its official instruction set, perhaps using micropython implemented as microcode, then it might work.
We’ve reached the point where Chromium is essentially the de-facto web standard because Chromium engineers do the lions’ share of feature testing and development,
Most of the web standards driven by Chromium are not particularly beneficial to the web, but are beneficial to Google. This is not an accident. It is how Google has made itself gatekeeper of the web while maintaining the facade of an open and standards-compliant browser.
This is not a good thing. Community-focused projects investing time and money into supporting it is a bit like digging one’s own grave.
I hear people wondering, “WTF is LAHF?”
It’s a CPU instruction.
https://www.dapsen.com/X86/html/file_module_x86_id_148.html