BrowserPub: A browser for debugging #ActivityPub and the ⁂fediverse
-
John Spurlockreplied to 洪 民憙 (Hong Minhee) last edited by
@hongminhee thanks!
ah I see you work on Fedify, so you might like to know that the entire backend and frontend for browser.pub is all TypeScript, zero deps except a few Deno std lib functions
-
Perhaps! It does not use Fedify, but it is all basically vanilla TypeScript
-
Fedify: an ActivityPub server frameworkreplied to John Spurlock last edited by
We've added the Inspecting ActivityPub objects section to the #Fedify docs, introducing BrowserPub and the
fedify lookup
command!Testing | Fedify
Testing a federated server app is a bit tricky because it requires a federated environment. This document explains how to easily test your federated server app with the help of several tools.
(unstable.fedify.dev)
-
洪 民憙 (Hong Minhee)replied to John Spurlock last edited by
@js I'm glad to hear you're using Deno!
By the way, I've just introduced BrowserPub in the Fedify docs:
We've added the [*Inspecting A…
We've added the [*Inspecting ActivityPub objects*](https://unstable.fedify.dev/manual/test#inspecting-activitypub-objects) section to the #Fedify docs, introducing [BrowserPub](https://browser.pub/) and the [`fedify lookup`](https://fedify.dev/cli#fedify-lookup-looking-up-an-activitypub-object) command! #ActivityPub #BrowserPub #fedidev
(hollo.social)
-
John Spurlockreplied to 洪 民憙 (Hong Minhee) last edited by
@hongminhee thanks, the docs look great
I guess I do almost everything in Deno these days, deployed to Cloudflare via Denoflare (denoflare.dev)
-
洪 民憙 (Hong Minhee)replied to John Spurlock last edited by
@js Oh, I didn't realize there was Denoflare, thanks for letting me know!
-
@js thanks! We’ll fix
-
-
-
John Spurlockreplied to John Spurlock last edited by
So as I'm bopping around looking at everyone's #ActivityPub 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. https://browser.pub/mastodon@mastodon.social
-
John Spurlockreplied to John Spurlock last edited by
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
-
John Spurlockreplied to John Spurlock last edited by
browser.pub requests the ability to add new follows to your account...
-
John Spurlockreplied to John Spurlock last edited by
... 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)
-
John Spurlockreplied to John Spurlock last edited by
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.
-
John Spurlockreplied to John Spurlock last edited by
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
-
@js you'll probably be better waiting until Client ID Metadata Documents are implemented, otherwise you'll be maintaining a tonne of OAuth App registrations
You could also implement this through authorized interactions, iirc.
-
John Spurlockreplied to John Spurlock last edited by
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
-
John Spurlockreplied to John Spurlock last edited by
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
-
@thisismissem yes I can't _wait_ until that spec is supported in popular implementations
right now I maintain a minimum number of mastodon app registrations based on unique attributes (they are not user-specific), but would love to rely on this less in the future
let me know if you know of a server I can get an account on that implements Client ID Metadata Documents for testing