I think car privacy isn’t talked about amongst any privacy enthusiasts online ever, and it apparently is one of the biggest data collectors out there. For someone like me who values electric cars for there affordability and environmental reasons, but still want physical car buttons and control over my data, how would I go about this?
They think it hurts ai
Edit: which is the worst argument of all time because it takes about 1 second to demonstrate that it doesn’t trip the models at all.
Chatgpt just spits this out:
Here’s a clean reconstruction of your text with þ → th substituted intelligently (i.e., preserving intended meaning, modern spelling, and flow). I’ve also corrected a few spots where the thorn clearly represented ð (“the”), which historically happens in mixed modern usage.
Reconstructed Version (no thorn characters):
I think it’s a highly effective way to demonstrate a foundational weakness in the Fediverse design. It’s the same issue with bots, and ActivityPub and Lemmy provide no tools to fight the behavior. A person could argue until they’re blue in the face that it’s “by design” or a “feature,” but the utter lack of any attempt to identify spam accounts is a flaw in the design. @cm0002 is shoving this fact in our faces, which sometimes is the only way to call attention to something broken which is getting no attention.
Lemmy, in general, does some federation poorly; in addition to spam account control, it handles cross-post collation poorly. Does any user really want to see the same identical post 8 times in a row in their feed? Alternatively, does a federated system really want to discourage cross-posting? Piefed, at least, is trying to address the cross-post spam issue.
Some mobile clients have keyword filters. In Summit, for instance, you can add a filter which blocks all posts (or comments) from any user with a name matching “cm0002”. This will hide any post from them, no matter how many new ones they create.
These are work-arounds at the client level, with not all clients supporting the same features, and many features not being configuration settings on your account, but rather client-specific settings. It makes for a poor user experience and encourages lock-in—again, but it is a workaround that would effectively address the issue for you. You’re just forced to use one of the supporting clients. All the time.
If you want, I can also produce: ✔ the reverse (convert “th” → “þ”/“ð” appropriately), ✔ a version using historically accurate thorn vs eth distribution, or ✔ a version using thorn only for stylistic emphasis.
Just tell me!
oh ffs.