Hutch

The rubber on mine turned sticky and I got rid of it. It was nasty to touch. I’d get another if it was a different material. Ended up with a G903 but not keen and want something new after just a year.

I do hope so. Temporary things have a stickiness that makes them semi-permanent. May as well go with 418 then :o)

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.

Here’s hoping that happens, but it still won’t fix two things: Firefox is kinda weird and clumsy on mobile, and it’ll still need attestation if that’s implemented on key websites as a hard-barrier to usage. I’m now on Android (I alternate between the two, so next cycle will be Apple), and even as a highly technical type I don’t sideload on there anyway, so I think few will sideload on iOS either.

Probably, which gives more ways to collect data and still uses WebKit underneath.

While you are at it, convince Apple to allow Firefox on iOS, and decline to use WEI in Safari. Otherwise there’s no way to avoid WEI on iPhone, and only one mainstream rendering engine free of this insidious malware. Many companies will shy away from it if it breaks mobile apps on the Apple platform.