- Joined
- Jan 27, 2022
just fucking make client-side block lists for known CP hashes (or some CLIP-based Computer Vision model for it) and just patch it into the client. Even IPFS, a piece of shit protocol, has BadBits to help with this problem. Even if this is just a hack solution, its one that can be built onto (i.e, a trust-based system so you can follow individuals or central groups on the protocol that publish bad hashes).Monthly Matrix Horrors Update (bi-weekly edition):
A user went out of their way to register for the Fedora 42 release afterparty, just so they could spam cp once it had concluded.
View attachment 7426572
View attachment 7426573
Matrix Momento
All centralized services just do this on the server-side instead of the client side, like Microsoft's PhotoDNA is an obvious thing to copy from and consider. That's all it'd take to make the CP problem go from "catastrophic nightmare" to "manageable".
The fact that every tech-bro schizo chatting application fails flat on its face in fixing these basic problems just shows that there are no serious FOSS developers interested in liberating communications for anyone but themselves, and no one wants to talk to tech-bro schizos because they all have autism and a platform with 100% of them would be trans and insufferable.