michael-bey

One of the most frustrating decisions from them was to stop allowing signal to be a catch-all messenger for encrypted and non-encrypted messages. I was able to onboard so many people, including very non techy relatives, because switching to a secure app for a small subset of people was never something they really wanted to do.

For security and privacy to really win out and raise the bar, it has to be able to happen in the background without the user even realizing it.

Making an app for enthusiasts is fine but Signal is going to remain niche if they can't make it more of an open ecosystem.

The US was founded originally with a much narrower electorate in mind. John Adams essentially argued that people who didn't own property were too dependent on other people to be trusted with important decisions that affected the future of the country.

I think this populist race to the bottom you are describing is a symptom of voting simply being a button to press to enrich your own specific financial interests. This happens on both the left and right of the aisle.

I don't really know how to reconcile this in the current system. Elected representatives seem to be more concerned with career-making and personal enrichment than actually advocating for the people they are supposed to represent.

I'm not advocating for stripping rights, but I am a little bothered that perhaps Adams had a point. As an outsider to Serbian politics, it seems like an academic movement is perhaps an attempt at a nuanced solution to this problem.

What a nightmare scenario to tabletop. How do you even begin to recover from something like this?

I was really disappointed when Signal went away from being used as an "everything" messenger, including regular SMS. I onboarded all my family and now because it's not a default messenger, nobody is using it.

>this is not a eulogy, it's a reckoning

100%

>There's been some skepticism about whether they are truly high severity

To be honest this is an even bigger problem with Semgrep and other SAST tools. Developers just want the .1% of findings that actually lead to issues, but flagging patterns will always lead to huge false positive rates.

I do something similar as what you suggested and it does work well -pattern match + LLM. The downside is this only applies to SAST and so far nobody has found a way to address the findings that make up 90% of a security team's noise, namely SCA and container images.