[verdverm]

We might be able to do this with permissioned spaces. There are instances or use-cases where you want an outside entity to make changes to a user's repo

- email / inbox [or @mail since it is @atproto :]

- unsubscribe from email

- notifications / rsvp

The cool thing is that we could use the stackable moderation infra for dealing with bad actors

https://bsky.social/about/blog/03-12-2024-stackable-moderati...

[jazzyjackson]

stackable moderation for ignoring senders is a cool idea. I'll keep an eye out for permissioned spaces, is there encryption and signatures involved at all? (everything on bluesky is signed with PKI, iirc?)

And just unsolicited feedback but "Blebbit" is a deeply terrible name. It turns my stomach for some reason. I don't even know what a bleb could be or what it could represent besides, like, an ulcer.

[verdverm]

Your content is signed with a key, but there isn't PKI in the same sense as certificates

There are two efforts around "permissioned" and "encrypted" spaces/content, where encrypted is the E2EE / signal like stuff and permissioned is more like Google Docs or the Discord like permissioning systems. There are use-cases for both

re: name, the second person to dislike, outnumbered by those who do like, will add you to the tally

the name is a play on plebeians / plebs / blebs, not to belittle, but to emphasize this is for the people, not the oligarchs.

Credible Exit Philosophy is important to me and the ATProtocol ecosystem. It means that users can leave an app without losing their data, that they can move their database without losing access, that the majority of Bluesky users could switch to an alternative if they become adversarial.

What it means is that ATProtocol bakes competition into our shared social fabric that all apps build on