Smh, just use protobufs and make EVERYTHING optional, let the person who actually has to use it figure out those pesky details

This sounds like something that someone who is trying to get rich on their crypto scam would say....

Or they do so in this way because the underlying Merkle tree approach lazily passes the resource requirements for validating the dataset to who should ne the end consumer. This is a consequence of the biggest platform having been built on what are now outdated cryptographic primitives.

Btw, the protocol isn't what VC money wants, the value is what can be captured from running the genesis instance that will be basically the default experience everyone flocks to.

The beauty of a protocol is no one ultimately owns it if they shit the bed and just make another hellscape of a social media. The ultimate experiment is if this protocol will be mature enough to build well moderated safe, digital spaces without being tied to a VC funded dev team in the future

The composability will only for those extremely small handful of devs, who are able to stand-up an alternative instance for when the VC backed experiment we're all on chooses to drop the ball. It solves nothing on how everyone experiences this place in the current.

Because the obvious answer is a software architecture design choice doesn't by itself create the needed tools. The opportunity to create tools is here, but the plans for funding, adoption, and user experience around selecting your tools obviously aren't.

I'm not here to argue that the architecture is going to result in well built moderation streams, but the benefit is that if you were sufficiently technical and motivated, you could write your own add-on moderation function, and then you only need to add your function in one place to integrate it.

Composability in this case looks to be a programmatic term. From just a cursory look at the docs and GitHub, it looks to me that the moderation tools here are designed to all follow the same input/output type guarantees, and that the output of one can be chained into the output of the other.

I've been in a similar place before, core team of <4, a prioritization fuck up that sent the wolves flocking to the visible devs, and having to come up with non-trivial solutions on an extremely short window. Really fucking impressive turnaround here for fixing this in a way that's not a quick hack!

You realize the platform is called "Bluesky" right, the part of the design phase where everything under the sun is on the table? The business plan is that the techo-solution allows for passing the monster cost of trust and safety onto the community a-la reddit (hint, it's a bad one for users)