znep

I wonder who would be best equipped to see if any of those keys are traceable to individuals involved in special government affairs lately? There have been some good leaks...

Users and (at least before the last run through the meat grinder) moderators.

That doesn't make any sense technically and sounds a lot like victim blaming.

It is far from certain that any application has such a "steady state", most of the ones I've worked on sure don't. There are obviously ways to analyze things and correlate enqueued and dequeues, but it is far from as simple and black and white as you suggest, especially with truly distributed systems and unknown cause of the reported behavior.

Heck, we don't even know if the messages are being "dropped" or just duplicated.

Generally somewhere between terrible and non-existent if you stick with Fire OS. They will drop occasional small patch releases with broken links to non-existent release notes.

True, now they are just used against you in the press when they get released one way or another, legally or not.

Then, the entire point for some lawsuits existing is to set the stage for that information to come out for no good legal reason.

You can think of it as legal hacking.

I regret writing that last sentence.

Even Google can't solve all the downsides of things being in the cloud.

Or they at least want you to think that.

Spring4Shell is entirely a flaw in Spring, however is somewhat understandable because it was only exploitable due to a new feature in Java (modules) that added new methods to java.lang.Class, which is a very significant change. You could argue the very existence and nature of Java object serialization deserves blame as well, but that gets nuanced quickly.

Modules are also part of the reason why so many folks got "stuck" on java 8.

It is definitely an interesting study in the challenges of trying to make advances in a platform when a lot of the ecosystem is very much in maintenance mode and may not have a lot of eyes on the combination of existing libraries vs new versions of Java.

I'm not sure what they are using right now, but they currently have the "AWS-LC Cryptographic Module" listed as being in process for validation which may be sufficient for s2n.

I know there are other AWS features/services that are lined up behind that validation for FIPS support.

...and almost every time I end up on a mobile link to a tweet in a web browser I have to refresh the page to get anything but an error. Which has been going on for years, or at least seems like it.