The one that survived without needing to be shut off essentially serves as proof of viability, and combined with the data from the ones that was repaired it helps them figure out how to adjust the design and manufacturing to make every unit last longer. Basically, future turbines should be cheaper to run.
When an attached image is loaded, then if the loading fails the app should check if it's using proxying (domain belongs to posters'/forums' instance or user's instance & contains redirect format URL pointing to another domain) and give you a button to press to retry, which would suggest bypassing the proxy and requesting the original image directly
Motivation: I keep seeing broken image embeds and can't be bothered to view source and try the redirect section in my browser after rewriting it to a proper link for every failed image load
Let the app do that for me
I have alts. No automatic sync, but you can list your alts in your profile like I do.
On mobile make sure to use a client which makes it easy to switch between accounts (I use Thunder, which additionally shows server status in the account switcher!)
[Windows subsystem] for [executable environment] is the naming scheme. The default is Win32, there's one for POSIX (practically never used), and Linux runs in another.
Malicious compliance is when you follow a order or law knowing that it will backfire on those who issued it.
"Lawfare" is a comparable term but not quite it (basically legal harassment campaigns).
This affects the view of posts via the bluesky servers, but not via mirrors or other servers
And the use of content addressing means you can be sure it hasn't been modified
Several Android manufacturers have their own settings in the OS for battery longevity (automatic schedule based smart charging, or charging limits)
Don't think it's native in Android. Charging limits need support in the charging controller chip, plus driver support in the OS.
I use my backup headphones when my Bluetooth headset has run out of battery
Wireguard is most reliable in terms of security. For censorship resistance, it's all about tunneling it in a way that looks indistinguishable from normal traffic
Domain or IP doesn't make much of a difference. If somebody can block one they can block the other. The trick is not getting flagged. Domain does make it easier to administer though with stuff like dyndns, but then you also need to make sure eSNI is available (especially if it's on hosting) and that you're using encrypted DNS lookups
There's also a big difference between published specifications and threat models for the encryption which professionals can investigate in the code delivered to users, versus no published security information at all with pure reverse engineering as the only option
Apple at least has public specifications. Experts can dig into it and compare against the specs, which is far easier than digging into that kind of code blindly. The spec describes what it does when and why, so you don't have to figure that out through reverse engineering, instead you can focus on looking for discrepancies
Proper open source with deterministic builds would be even better, but we aren't getting that out of Apple. Specs is the next best thing.
BTW, plugging our cryptography community: !crypto@infosec.pub
Looks like the same dev from reddit
https://www.reddit.com/r/crypto/comments/1iumxl3/how_far_can_i_push_closesource_code_towards_being/
No audits and doesn't want to share the code
https://www.reddit.com/r/crypto/comments/1iumxl3/how_far_can_i_push_closesource_code_towards_being/
Can you install noise insulation in the home? Or get the kind of active noise filtering headsets which let voice through
Reddit keeps opting communities to features that make no sense for them. Recap, talks, community awards, etc, which only fit a tiny number of communities.
... But not for Uyghurs
I was going to post the whitespace programming language but this wins
Sheldon’s widow is one of the richest women in the world, and she’s willing to spend her fortune to support Israel.
Cryptography nerd
Fediverse accounts; Natanael@slrpnk.net (main) Natanael@infosec.pub Natanael@lemmy.zip
@Natanael_L@mastodon.social
Bluesky: natanael.bsky.social