Back

The idea here is to make it a bit easier to see how well the various players in the fediverse support the C2S side of the ActivityPub spec.

You can punch in any ActivityPub discoverable web url or fediverse handle, and BrowserPub will discover and display the underlying AP:

e.g.

social profiles: https://browser.pub/https://mastodon.social/@mastodon

or posts:
https://browser.pub/https://mastodon.social/@Gargron/113005517546136592

or fediverse handles:
https://browser.pub/@Gargron@mastodon.social

or even usernames (defaults to mastodon.social for now):
https://browser.pub/Gargron

BrowserPub defaults to a visual representation of the object (if a known type)

everything here is powered by ActivityPub, no server-specific APIs

you can also view the underlying ActivityPub object as JSON...

@evan hopefully this can help to make sure folks are supporting C2S as much as possible

I would love to get a standards-based oauth to inbox flow working, do you know of any implementations that support it?

was going to check out Mastodon's new oauth thing in 4.3, but I'm not sure they have any additional AP endpoints behind the auth wall

@js onepage.pub do es. However, we need better specs. I'd like us to set up a taskforce for it at the SocialCG. It's very core!