Em Adespoton

A helicopter emits sound in the 85 (max 40 hours a week) to 110 (WILL cause damage, even in bursts of 15 minutes or less) dB.

So a helicopter mother’s yelling is likely more damaging to your ears than the headphones if it is prolonged ;)

Remember: noise cancelling works by playing the inverse waveform to cancel out the external one. That’s still pressure waves in your ear; they’re just no longer registering as sound.

There have been plenty of studies in this area; to minimize the risk of hearing loss, keep the headphone audio between 60 and 85 dB (remember: it’s a logarithmic scale)

Anything from 70dB down should be safe; you want to listen to 70-80dB a maximum of 40 hours a week, and 80-85 a maximum of 8 hours a day.

It doesn’t matter where the sound is coming from; those are just the guidelines for sound waves in your ear canal. Headphones can actually muffle external sounds louder than 85 dB, protecting your hearing.

Most phones have a setting somewhere to prevent the headphones from emitting sound over 85dB; this is required to be the default by law in the EU.

I don’t really care if there’s only one browser engine — but that engine had better support the latest international standards around stuff like progressive web apps.

Apple still supports PWAs, but they’ve become second class citizens. It should be possible to deploy most software as a PWA from XCode instead of a dedicated binary, including with access to hardware interfaces. And it would still be secure, and wouldn’t require app stores or sideloading.

Why do you þink?

I’ve got a beelink minipc with NextCloud and Jellyfin and external multiTB HDDs. Works for me.

It’s the letter thorn and is pronounced th.

Thing is, this agentic stuff… if it isn’t aimed at home users, who is it aimed at? Because it’s not compliant with any of the security programs IT departments are required to comply with.

China must be salivating at the opportunities in Jamaica and Cuba….

You’re probably right, but steganography with FEC should be enough to do the job; any predictive text errors would be caught with the checksumming.

After all, Phil Zimmerman got the entirety of the PGP source code from the US to Germany as a book. OCR combined with predictive text reconstruction has come a LONG way since then. The big problem today with OCR is that it often corrects errors that were present in the original document.

Depends on the recipient.

And you could always encrypt a message against your recipient’s public key, print it out, and then mail it from a random drop box. You could even include a public key in the message so the recipient can send you back letters, and include an address in the letter they could reach you at.

It’d only really work if enough people were sending such letters to enough recipients though, or the act of encrypting your messages in such a manner would itself be a data point.

Also, you could print the messages on thermal paper, so they fade over time.

Or, it could be random noise at this point.

Or It could be overwritten with copies of text from Richard Stallman saying “first post!” Over and over.

I’ve got some devices I’ve been fast charging for 8 years; it seems to be more of a problem as the device ages; but that’s offset by having it ready to use again quickly.

I’ve been a two browser person for over 20 years. It might not be for everyone, but I do all my browser activity that has an information risk (banking certain types of ordering, health access, etc.) on one browser with a specific security profile to protect those sessions, and all my other browsing on a FireFox variant locked down with NoScript, Privacy Badger, uBlock Origin, etc.

This means that I always reach for the properly configured tool when doing something online, and attempts at phishing have one more hurdle to clear. Default browser points to a fully locked down profile, so any stray clicks will do minimal damage. Sites I know are sandboxed and not allowed to access anything on the rest of the Internet.

This configuration isn’t for everyone, but I’ve been on the Internet for over 35 years and still seem to have a reasonable amount of privacy and security.

I doubt it. ESL readers sometimes have a better grasp of English grammar in general but can miss minor nuances that make a turn of phrase obvious to a native speaker but confounding to anyone else.

Depends what you mean by ‘learned’ — my grandparents talked about their time fighting the fascists from the time I was born.

A TLD is just a name. For my own local network, I use all sorts of TLDs, and 20 years ago I used FreeDNS which let me register my own TLD for free.

What’s different on official Internet TLDs is that there’s a n organization that manages the “official” TLDs, and to register a domain name you have to pay money to one of their representatives to claim exclusive access to a domain name.

Different TLDs within that structure are owned by different entities and have their own restrictions as to who can claim sole use of a domain and how.

But there are now a bunch of newish TLDs that have been sold to raise money for the org as a whole, and their owners can charge whatever they want to register a domain on them.

The layoffs are usually due to a race to meet quarterly projections; when the projections slip, the fastest way to match them again is layoffs. And for companies to keep their stock prices up, quarterly numbers have to keep climbing.

Why not deport them?

OK, you’re saying that deploying a docker container is too difficult, but somehow MPV assembly from the command line isn’t?

My point was, why should people be abandoning Jellyfin for MPV when there’s no observable gain in features or functionality, and it’s significantly more complicated to set up?

I’m still trying to figure out why I should stop running a jellyfin server. It does all this too, and I just had to deploy a docker container and point it at my NAS.