Ethan

Honestly, BlueSky’s AT Protocol fixes pretty much all of these issues (save for having a single actor controlling things as for the moment it’s still in active development and not adopted by any other project).

Even if you never intend to sign up for or use their protocol, I’d give it a read- it’s a really fascinating system design:

https://atproto.com/guides/overview

I think you’re fundamentally misunderstanding how data is handled in federated systems. When an account from Threads interacts with your post or you interact with a Threads post, information is exchanged exclusively through Actions sent between the servers- never to or from your or their client and another server. It looks like this:

Client <=API=> Instance <=Action=> Instance <=API=> Client

They don’t get any information that isn’t already available publicly to any random user on your instance- no IP address or anything otherwise. Threads’ mobile app data collection has no bearing on their ability to collect information on you.

Edit: To be clear- there is theoretically a set of protocols in the ActivityPub spec that allows for direct client to server communication (unimaginatively called ActivityPub Client-to-Server), but it hasn’t been adopted by any current Fediverse software implementation that I’m aware of.

They wouldn’t be able to get it even from a federated instance as long as you don’t use their frontend.

I don’t know of any major instances that have enabled any of those… And all getting around it would take is to create an account on the instance- which for instances without admin approval can be done fully programmatically anyway so it wouldn’t even require human intervention, just a few extra lines of code.

As long as the jacket’s properly constructed the pockets should be just as watertight as the rest of the outer shell.

When purchasing a raincoat, you can look at the pocket stitching and zipper model to try to gauge how it’ll hold up (or just buy it, experiment on it, and return it if it fails).

“Consumer Reports factors build quality issues that require repair into our reliability calculations, but they are not weighted as heavily as more serious problems, such as those with the engine, transmission, or drivetrain.”

I’ll take a guess that this is the source of the weird counterintuitive results. EVs have a bunch of minor QC issues resulting from their comparatively newer and less tested assembly lines, while ICE vehicles have fewer but much more severe issues. Thus they’re rated as more reliable by CR even though the average cost of maintenance is far higher.

I’d be quite curious to know exactly what their weights and standards are for determining repair severity, because their current results don’t line up with any previous direct cost of maintenance studies.