I am just digging through the #golang #activitypub library.

I am just digging through the #golang #activitypub library. Sadly, I can't find the entry point to get started. Anybody has a good idea for a starting point or a blog post that shows a minimal example?

The GoActivityPub Library

(go-activitypub.federated.id)

@oliverandrich @mariusor is the person to help out here and can direct you to the right spot.

@oliverandrich
Maybe join us at forgejo federation ?

@oliverandrich hey, what kind of application are you interested in? I'm AFK until Monday to give you more specific information, but maybe the list of modules can give you a better idea of what it can do: https://go-activitypub.federated.id/lib/index.html#the-module-layout

@mariusor I am building my own blog engine in Go and want it to be a first class citizen on the fediverse from day one.

So far, I have looked into your package and I will definetly use the vocabulary, which is an awesome library. Inbox, Outbox and Storage I have to implement myself, as I will use my ODM, my handlers and so on. But I am digging through your code and learn.

@oliverandrich you can look at this project of mine which is basically a blog operated with activitypub: https://github.com/mariusor/oni

@oliverandrich so I'm back behind a keyboard, if you need more help with using GoActivityPub.

And as a separate thing, since this discussion started from the documentation website, I would be interested in how it failed to provide you with the information that could have helped you.

@mariusor Sorry, for the late response. I was a few days off myself.

I think, what I was looking for was a "How to write a minimal AP server"-type of article. I know, a tough request for such a complex topic. But I also underestimated the complexity.

@oliverandrich I'll ponder on this and see if I can come up with some starting points.

The library does have a "reference server implementation"[1] but it's not entirely "minimal", because in it's smallest form an ActivityPub server needs to do quite a lot already:

1/ dispatch locally stored objects when requested
2/ process remote activities targeted at local actors
3/ process and dispatch client activities of local actors

On top of these actions, a server might need to have additional behaviours attached to certain Activity+Object combinations.

GitHub - go-ap/fedbox: Reference implementation of a generic ActivityPub service using the GoActivityPub library (mirror repository)

Reference implementation of a generic ActivityPub service using the GoActivityPub library (mirror repository) - go-ap/fedbox

GitHub (github.com)