mariusor, 5 months ago

This usage is meant for connecting to the local storage (disk, database,etc) that is used by the projects above.

However with just minimal changes it can be converted into a full blown fediverse TUI client that can connect to any instance that supports the Client to Server part of the ActivityPub protocol.

#C2S #ActivityPub

OpinionatedGeek, 5 months ago

@mariusor Interesting stuff! One quick question - how does it log in? Does it follow the Mastodon Oauth flow, FEP-d8c2 Oauth flow, or something else? (I'm implementing a server with C2S and I'd like other tools to be able to log in.)

mariusor, 5 months ago

@OpinionatedGeek this is not an ActivityPub client at the moment.

I made it for admin/maintenance work on the server that hosts one of my projects.

It works by accessing the GoActivitypub storage backends directly. They are custom Go packages that conform to a specific interface: https://pkg.go.dev/github.com/go-ap/fedbox#FullStorage

My own ActivityPub servers use something like Evan's proposal, but it predates it by about 4 years, so the finer details might be different.

mariusor, 5 months ago

@OpinionatedGeek in summary, the clients are represented by ActivityPub Application actors on the server (that need to be created manually by the admin at the moment).

They use the exposed authorization and token endpoints of the Actor representing the user that wants to log in and, after that, there's a standard OAuth2 authentication/authorization flow.

I don't care about being compatible with Mastodon clients, as they work with a completely foreign UX paradigm.

benpate, 5 months ago

@mariusor Awesome progress! And I love the retro UX.

mariusor, 5 months ago

@benpate programmer UI FTW!! :D