Probably within their moderation pipeline, so neither the PDS nor the AppView.

I suppose if you uploaded a bunch of hashes of, say, popular memes, bsky would have a tool on their end where after reviewing the match they just say “ignore this hash going forward” and their system never flags it again and clears any matches that are being held for review immediately.

so you guys just don’t know what day it is I guess right?

They planned to force him to crash or shoot him for recording their crimes. They then accused him of assaulting them. www.charlotteobserver.com/news/local/c...

sometimes i pull up atproto.netlify.app and just see what types of record are coming across the firehose in real time, and there’s often something i haven’t heard of.

but we already have what’s called a threadgate that limits who can interact with posts. isn’t that what you’re asking for here?

As far as limiting who can interact with your posts, you can do that in settings » moderation » post interaction settings to configure the default on all new posts going forward.

Because people assume “private account” = nobody can see my posts unless I let them, which makes them more likely to post things unknowingly that shouldn’t be public.

Most people don’t even know likes are public on here. Imagine if they thought their posts weren’t.

Private accounts would require the posts to be inaccessible to those who shouldn’t have access.

The devs have explained repeatedly why that can’t happen on a system where the data must be public by design to facilitate data and account portability. There is no simple solution for this problem.

That’s how it works on this protocol. That’s what we’re talking about. But even so, calling a system like, say, Mastodon open is kind of a joke. That’s a closed system with a veneer of openness, and you don’t have free access to your data. There are no truly open systems where the data isn’t public.