The web release involves changes to the cdn hosting and boy did THAT just fail hard on us. Looks like a CORS issue. Backend team is going to wrap a meeting and then try again.
So, rollout paused for a second
RE:
)
I suspect they'll be able to make progress on this, but I do want to point out this is one of the primary concerns we had with ActivityPub that led us to build atproto instead
RE: