Embedded images on lemmy are loaded directly from the servers they're stored on, often not your home instance. Bam, adversary has your ip and access time and what caught your attention.
When i'm 90, wheel me out to the orchard and I'll watch the chickens. If you give me a stick i'll wave it to scare the parrots off the apples.
Excellent! Based on ConverseJS with a custom UI. OMEMO is intended but requires work to detangle ConverseJS's implementation from the ConverseJS UI.
I think a lot of comments have missed that ntfy.sh does not use UnifiedPush, the ntfy server is a UnifiedPush provider and the ntfy app is a UnifiedPush distributor.
Regarding encryption of the push message, from https://unifiedpush.org/developers/spec/android/ :
Push message: This is an array of bytes (ByteArray) sent by the application server to the push server. The distributor sends this message to the end user application. It MUST be the raw POST data received by the push server (or the rewrite proxy if present). The message MUST be an encrypted content that follows RFC8291. Its size is between 1 and 4096 bytes (inclusive).
Reader mode exposes a much better headline:
Scientists testing deadly heat limits on humans show thresholds may be much lower than first thought
"Current AI models cannot forget data they were trained on, even if the data was later removed from the training data set," Han's report said.
Bullshit. You delete the entire model and start again.
Huh. Even Boeing doesn't want to be associated with Boeing:
Boeing executives have repeatedly sought to make clear that the Starliner program operates independently from the company’s other units — including the commercial aircraft division that has been at the center of scandals for years.
"South Africa, which is functioning as the legal arm of the Hamas terrorist organization [...]"
-- https://twitter.com/LiorHaiat/status/1745427037039280207 (https://archive.md/L7AwX)
Even though the company didn’t really do anything truly wrong in this case, as it’s simply users reusing passwords, they still should have been better/more proactive especially with such sensitive information
There's nothing special or new or unique or unforseen about the security requirements of 23andMe.
They absolutely failed to implement an appropriate level of security measures for their service.
Mandatory 2FA could've prevented this.
Here are the github repository, issues and comments immortalised for posterity in IPFS:
- ipfs://QmeeRa15gofL1UGxMGgb9vnv6VjA8MmNBNxPeAxB36KsNT/
- https://ipfs.io/ipfs/QmeeRa15gofL1UGxMGgb9vnv6VjA8MmNBNxPeAxB36KsNT/
- https://bafybeihsjcljogr7k25knn6nsivwegas53ouko6pzmqtnzgqncrwwexeiq.ipfs.dweb.link/
The issues and comments are in github json format -- if anyone wants to collate them into a human-readable text or html file, please do so.
Edit: Its immortality of course depends on you to access and pin the content.
What will this mean for Lemmy instances? XMPP servers? Email servers?
What if a 15 year old runs their own personal Mastodon server? LoL this is gonna be yet another entertaining Australian government shitshow.