a
Copies can't be trusted implicitly unless there is some proof that they came from the origin server. Historically this has been done with LD Signatures, but they are very complicated...
One current problem is that the source app is not federated between servers, so currently it is only visible on local statuses. I do agree that this would be an...
Federating the `application` should be enough, shouldn't it? Name-based filtering would probably be enough, and there wouldn't be a real need for ID-based filtering. Yes, this probably opens up avenues...
#8476 is still a blocker on this
I don't think it would get annoying if it's only shown once per new person. It could also be considered unnecessary if you're already mutuals before the feature goes live?...
> If it gets annoying that's probably a sign you're being weird I don't think that's the right framing. You'd only see interaction rules if that person defines them (unless...
sure it's a client-side feature but that's kind of the whole point. a generic warning could be added to any frontend, but a user-defined `rules` needs api/federation modification.
still interested in this
@danhunsaker It's not even a protocol thing I'd say. It's a more general search engine problem: you need to be able to discover and index content before you can search...
idk about automatic detection of what constitutes "seizure-inducing" but it would probably be a good idea to take hashes of media uploads and allow admins to ban certain hashes. pixelfed...