Hardly surprising since they were acquired by Google.

Earbuds are worse, it's always one that's dead because it didn't sit properly in the charging case.

My experience: via iPhone 8 + Apple adaptor, it couldn't drive big cans, and even for earbuds they lose significant volume. My phone has the 3.5mm jack, and it can deafen me. This matters more when hooking up to sound systems because it raises the noise floor.

It's better than nothing, but it's not good. I don't know about the USB-C alternatives though - I can only hope they are better than the 'lightning' connector ones.

No headphone jack, no sale. I have three hard criteria:

headphone socket usb-c charging expandable storage

I'll stick with my Sony. Two-out-of-three isn't good enough.

CP is something that's prevented me from hosting imaging solutions in the past, out of risk-avoidance so I've given it a lot of thought over the years. The lack of support from Cloudflare hasn't helped, and making it USA-only weakens it as a general solution. That said, I'll still run some sites via Cloudflare because I'm certain it tracks the content regardless without the mandate to enforce or alert, and that tracking may help lead to the original source [pure opinion here with hard facts, but I use CF for other reasons].

Now that I want to host fediverse things safely, it's still a concern. I'm not in the US, I'm in the UK and host in Canada. Doesn't matter greatly. They'd still take all my equipment while they investigate IF they had sufficient evidence to charge. But they WON'T because the CP is attributable to someone else. The main takeaway from all of this, for me, is to NEVER take backups of actual content, only settings/accounts. Holding archives is dangerous because only I would have access to their contents.

Defederate aggressively, block paths as needed, keep logs, don't run it from home, etc etc. Keeping records gets most folk out of sticky legal situations.

451 or 403 would be more appropriate as it's not available for legal reasons. 410 Gone would also fit well if it's a permanent block. I'd steer clear of 5xx server side because it encourages retry-later. The client has requested something not served, firmly placing it into the 4xx category. The other problem with 503 in particular is that it indicates server overload, falsely in the case of a path ban.

In no particular order: Fastmail, Proton, ~~Outlook~~, ~~iCloud~~, ~~Yahoo~~, Gandi (free if you buy a domain), I've heard Hey is ok, but haven't used it.

For this much data I'd want to use multiple vans in case one suffers an unexpected hardware failure 😃

It's much the same when I send .tar.gz / .tgz files. Folk get uppity about it not being .zip. I don't bother with other formats purely because I know I can expand them anywhere without installing additional software.

As for .rar, I always view them with suspicion. Dodgy.

kiro5hin

I seem to recall spending time on there, but that's about all I remember about it.

I think I'll stay on Mastodon. I don't like the Firefish UI. I haven't tried Akkoma yet.

I use Ansible, Docker, and Emacs OrgMode files committed to Git. Diagrams are a mix of Miro and Graphviz. There's also a few markdowns in there too. Joplin is used for rough notes only.