Do you have a team member who is dedicated to nothing but docs? Also, you should fine-tune an LLM on all of your engineering docs and discussions etc so users can converse with it and learn faster

a local filter probably does pretty well if it just downloads the video title, person who posted it, and maybe a description. no need to scan the entire video

On the other hand, at 400 bytes per post we're talking like 1 MB to download 2500 messages. Even if you download every post by people you follow, and also by people followed by people you follow, you'll still get hours of data per second of downloading.

If the labeling is client side, you can have 'secret likes' that update a user's filter model, but don't broadcast anywhere else that the content is preferred by them. I am sure there are lots of horny lurkers that want more but don't want their preferences publicly visible, for example

How hard would it be to make all of those filters client-side? Then people can pop in their own, you can get a whole hacker culture around custom filters and really be the platform that can service every niche.

@nomieturtles.bsky.social don't let me down

bsky isn't the only allowed hosting platform though right? Some other service could opt for different content removal rules?

The big question for everyone is censorship resistance and audience retention. And the test is when all the hornyposters show up and start pushing the limits. When they get banned from bsky, will they still be able to use AT protocol?

Who is missing?

No weights available yet, based on the dev chatter I think that's expected in 2-4 weeks.