ファイルへ移動
Cory Slep 0fc1556d17 Fix comments and HandlerFunc 2018-05-30 23:37:59 +02:00
deliverer Fix deliverer with *url.URL changes 2018-05-29 22:02:10 +02:00
pub Fix comments and HandlerFunc 2018-05-30 23:37:59 +02:00
streams Use *url.URL instead of url.URL. 2018-05-29 21:57:39 +02:00
tools Tools now pass go vet 2018-05-30 21:40:20 +02:00
vocab Fix go vet issues 2018-05-30 21:33:05 +02:00
LICENSE Initial commit 2018-01-23 22:53:17 +01:00
README.md Move the DelivererPool out of ActivityPub. 2018-04-04 20:36:23 +02:00
go.mod Add go.mod and go.modverify for vgo 2018-05-30 21:44:17 +02:00
go.modverify Add go.mod and go.modverify for vgo 2018-05-30 21:44:17 +02:00

README.md

activity

go get github.com/go-fed/activity

This repository contains three libraries for use in your golang applications:

  • An ActivityStreams Vocabulary library
  • A convenience library for the ActivityStreams Vocabulary
  • ActivityPub Social API (Client-to-Server) and Federation Protocol (Server-to-Server).

This library is biased. It forgoes understanding JSON-LD in exchange for static typing. It provides a large amount of default behavior to let Social, Federated, or both kinds of ActivityPub applications just work.

Status

There is no stable version of this library (yet).

See each subdirectory for its own README for further elaboration.

Core ActivityPub Libraries

  • vocab - ActivityStreams Vocabulary: Functional and tested
  • streams - ActivityStreams Convenience Library: Functional and tested
  • pub - ActivityPub: Under development and testing

Supplemental Libraries

  • tools - Code generation wizardry and ActivityPub-spec-as-data.
  • deliverer - Provides an asynchronous Deliverer for use with the pub lib

How To Use This Library

This section will be fleshed out once the library is approaching its first stable release.

FAQ

Why does compilation take so long?

The vocab and streams packages are code generated on order of hundreds of thousands to a million lines long. Use go install or go build -i to cache the build artifacts and do incremental builds.

Useful References

Thanks

I would like to thank those that have worked hard to create the technologies and standards that created the opportunity to implement this suite of libraries.