Notices by Jeremy (jdormit)

I wrote up the API I'm thinking about for my #ActivityPub #PHP library! If you're interested in building federated PHP applications, I'd really appreciate if you check it out:

https://github.com/pterotype-project/activitypub-php

I opened an issue where people can give feedback and discuss the API so that we can make sure it will meet the needs of Fediverse developers. If you have any feedback or suggestions, please contribute to the discussion:

https://github.com/pterotype-project/activitypub-php/issues/1

Still no documentation and not anywhere close to done, but my #ActivityPub #PHP library is open source at https://github.com/pterotype-project/activitypub-php.

My goal is to provide a well-tested, flexible library that handles the complicated parts of ActivityPub (JSON-LD, persistence, addressing, etc.) in a way that can be plugged into an existing PHP codebase with no hassle. That'll help me refactor #Pterotype, and will also make it easy for other developers to make developers to make plugins for Joomla, Drupal, etc.

@patrickloonstra @dansup
This is the problem we need to solve as Fediverse app developers. The vast majority of people don't know or care about ActivityPub or decentralized protocols. If we want federation to become the new paradigm, we need a better answer to this question.

I've switched to not use the phrase ActivityPub as much as possible. It just doesn't resonate. Fediverse is better, but I still don't have a good sound byte to explain it to the layperson.

Current #Pterotype roadmap:

1. Iron out federation kinks - make sure posts are displayed properly, searchable from the Mastodon search bar, etc.
2. Make the Actor name configurable so not everyone's blog is called @blog ?
3. Write a blog post? Something about content creation and business and how to not be shitty internet citizen, which has been influencing how I think about Pterotype and ActivityPub
4. Onboard beta users and get feedback
5. Synchronize WordPress comments with Mastodon replies