Both first posts (also “addendum”) are now wikis –
everybody should be able to edit them now.
Placeholders are not possible I think.
@Sebastian thx! I’ve done a first pass at redrafting as three guides. I’ve also pulled out most of what was in the section “Potential models and building blocks”. Instead I’ve pointed to some places to discover ActivityPub implementations and I’ll open an issue on Fediverse.Party to add in the projects I’d compiled that aren’t there already.
I’d like to start figuring out some next steps. If this is potential content for the draft activitypub.rocks improvements, how do we get from here to there? Maybe we need a documentation team? Maybe there is one already? In any case, I’d be happy to participate.
We’re hitting the length limit for posts, so I’ll add here a stub of a last section of the implementers’ guide on how to improve ActivityPub as suggested earlier by @Sebastian:
Improving ActivityPub
Aided by a culture of collaboration among Fediverse advocates and participants, there is ongoing work to improve both the ActivityPub specification and interoperability among different ActivityPub implementations. Initiatives like FediConf, Feneas, and the ActivityPub forum on Activitypub.Rocks are great places to connect with other implementers and help move things forward.
2 Likes
@nedjo: I’ve gone ahead and upped the post length limit, so at least until we find a better place for it we can continue on with posting here. I think we should also split a couple of these sections out into their own threads, like “Introduction to Activitypub” and “Guide for new Activitypub users”—would you mind making new threads for these? I think that would make this post a lot more navigable.
@nightpool: done:
When you get a chance, please convert those other two pages into wikis. Thx!
1 Like
done!
I use it too. Mostly because of LD-signatures.
I created a topic to discuss this again: Easing the onboarding of new developers to the Fediverse (and this post will bump the wiki guide to the top again, which is also good for attention 
)
There are some great resources in the guide including many protocols and implementation docs, so I made a list. #7 - Problem: There is no comprehensive list of federation standards in use - the-fediverse - Codeberg.org
How do we add these two AP codeing projects, can’t find in CMS
Open Governance Body #OGB and Indymediaback #indymedia
As the coding is starting on these projects
This is a great introduction! Kudos.
1 Like
I added a notification at the top to indicate that the document can be edited by anyone (Press ‘Edit’ in bottom-right below the top post)…
Note: This is a Wiki Post that anyone can edit. Please help improve and extend this document !
The idea once was to collect sufficient information, restructure and then publish on a dedicated website (though the wiki post is published as separate html page through the forum as well).
1 Like
There is a feature in Discourse that enables time-limited contents. E.g., in this topic, we could enable a time limit so that we can freely discuss the wiki, and additions or changes to it, then integrate those changes, and the conversation would be cleaned up once a month or so. Does it make sense?
It might make sense. It should be part of some more effort to turn this into a high quality chunk of documentation. It needs a process then, and people dedicating to it. Right now I think most people do not realize that the top post is a wiki that they can freely update, and are even encouraged to do so.
An improvement to this documentation process isn’t useful if at the same time @gabek and @j12t are coordinating the fedidevs.org initiative that intends to do the same. Hence I mentioned the “Fediverse Developer Documentation Website” bullet point in the wiki about organizing for more cohesion of initiatives.
I notice Zap has been moved to a different location in the same forge, Codeberg:
This would affect the url pointer in the section on fediverse.md
Does anybody know the correct update to provide?
1 Like