podcastindex.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Intended for all stake holders of podcasting who are interested in improving the ecosystem

Administered by:

Server stats:

162
active users

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: browser.pub/https://mastodon.s

or posts:
browser.pub/https://mastodon.s

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

or even usernames (defaults to mastodon.social for now):
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...

... or a less JSON-ey structured outline

It'll work on ActivityPub-enabled wordpress sites:

browser.pub/fediversereport.co

For known collection properties (like outbox, followers, featured, etc), it will preview the collection and support paging via a "next" link:

browser.pub/davew

Threads posts and profiles are also available, for users that have checked the magic box

Here's a post:
browser.pub/https://www.thread

While Threads does not support the replies collection yet, they do support the inReplyTo pointer, which BrowserPub renders above

browser.pub/https://www.thread

Hmm, I'd love to be able to render a more dynamic og:image at some point 🤔

BrowserPub also tries to render custom emojis in content and profile headers, these are in the ActivityPub payload after all

even animated ones

browser.pub/https://bolha.one/

and of course Flipboard is supported (cc @mike) nothing special, just the same ActivityPub spec implementation

browser.pub/https%3A%2F%2Fflip

so even though Threads doesn't return collection items in the ActivityPub payload yet, it _does_ include the counts - so at least I can display those

just pushed it live

browser.pub/https://threads.ne

Polls are not a Mastodon-specific feature, they can be expressed well in standard ActivityPub, which means standards-based apps like BrowserPub can render them

Here is a recent poll example from @evan

browser.pub/https://cosocial.c

and looks like Ghost got their outbox and posts ActivityPub working

although they are not in reverse chron like everyone else (@johnonolan, was this intentional?)

browser.pub/index@activitypub.

So as I'm bopping around looking at everyone's in browser.pub, I wanted to have the ability to follow interesting people while I'm browsing.

I just pushed a new update that adds a "Follow" button next to every profile in the visual view

e.g. browser.pub/mastodon@mastodon.

Ideally, I'd like to have these follows take effect here in my main account and not have to create a brand new profile on a brand new site.

This is where OAuth comes in - many existing fediverse servers supported federated login in a standard way

Just enter your account to start the login flow in browser.pub

browser.pub requests the ability to add new follows to your account...

... then stores the login info in the browser

For OAuth dorks, it'll show the token expiration and granted scope

Also whether or not the server supports the excellent OAuth server metadata spec, and whether the server supports PKCE (a security improvement that is a newer part of the spec)

You'll see that only the newest Mastodon 4.3 (still beta only?) supports this new metadata, but it should be rolling out widely soon.

anyway, once you have an active login it will be displayed in the top-right corner, and you can follow profiles with a tap of the "Follow" button

now Pleroma is special here, it supports following like this in bog-standard ActivityPub!

ie just posting a small json payload to the logged-in user's outbox endpoint

hopefully more ActivityPub servers support this soon, as it should be very similar to what they already do for S2S

misskey and micro.blog from @manton both support client registration for clients like this by simply providing a website url

it's called "indieauth" (displayed in the login info row, otherwise falls back to mastodon-style app-creation-based registration)

there is a newer emerging standard for dynamic client registration, but no one supports it yet - I'll add it when one does!

micro.blog doesn't support C2S follows via the outbox yet, but we can fallback to the micro.blog api here

you'll notice that browser.pub not only requests the ability to follow, but _also_ to read, generally

this gives the logged-in user the ability to explore ActivityPub collections that may not be public, only accessible via auth (if the server supports such collections over ActivityPub C2S)

in theory, you could imagine building a thing on top of these collections that looks like your personal mastodon timeline, but using spec-standard ActivityPub

in practice, tho, here is my mastodon inbox 🤦‍♂️

Pleroma, however, is a different story - a better story

here is my Pleroma account, listing my private inbox collection - essentially my home timeline

this is not public, but available to ActivityPub C2S clients like browser.pub with a valid auth token

Under the hood, the personal inbox is represented as an essentially infinite ActivityPub OrderedCollection, with no 'totalItems' count property, and no 'last' pointer

I can keep iterating down my inbox reverse chron this way in the json...

... or by hitting "next" in the visual view

maybe I should add some sort of automatic revealing of the next item on scroll

John Spurlock

and of course you can't see my personal Pleroma 'inbox' collection here, since you aren't logged in as me

as it should be

if anyone finds any additional endpoints available to read over C2S when authed (on any AP server impl), let me know - I'd be very curious to know what's supported out there

one more for today: just got @pixelfed oauth working too

similar to mastodon, you can add an existing pixelfed.social account, and follow any fediverse user directly from browser.pub

and, similar to mastodon, pixelfed does not seem to support any additional ActivityPub over C2S when authed

just pushed an update out this morning to handle @subclub 's ActivityPub payload for declaring subscription information - renders as a green badge

example subscribers-only profile: browser.pub/@petadventures@sub

thanks to @bnolens for surfacing this important metadata as json-ld here

@js all the collections on FedBOX federated.id filter out activities that don't have the Public namespace as recipient/audience when viewed without an Authorization header. For authorized actors it shows the non public activities that have them as a recipient.

I wonder why more people don't implement this type of filtering.