@drq @cwebber i get why you'd design things like this tbh, that neatly solves a lot of issues, or at least make them a lot easier to deal with

you can much more easily reason about complete up-to-date information without a need for custom update logic and strategies; comparatively, current-world ActivityPub is a mess in that regard

but a world where everything is public, shared and mediated by a world-knowing entity (even if it can “easily” be replaced with an equivalent one) is not what i'm looking for

@eramdam @cwebber the front-facing Bluesky app is built to use Bluesky PBC's AppView, i don't think it has any provision to switch to another provider with the same API (but i might be wrong)

you can theoretically build an equivalent relay+AppView that works in the same way with the same data (although you have yet to build some of the pieces yourself, not everything in bsky is open source afaik), but it's unclear what incentives you'd have to do that

@julian @mro i'm indeed not aware of a normative use of Reject being described, and there is also some talk about using Reject for e.g. messages rejected by a user's policy to block messages from strangers, so those would be two quite different use cases

@mro @renchap @julian @trwnh Mastodon did not reject the post, but rather failed halfway processing it because it was malformed; in other words, the failure was not intentional, a bug in NodeBB triggered a bug in Mastodon