NodeBB is at this year's FediForum, and one of the breakout sessions centred around the Theadiverse, the subset of ActivityPub-enabled applications built around a topic-centric model of content representation.
Some of the topic touched upon included:
Aligning on a standard representation for collections of Notes
FEP-1b12 — Group federation and implementation thereof by Lemmy, et al.
Offering a comparatively more feature-rich experience vis-a-vis restrictions re: microblogging
Going forward: collaborating on building compatible threadiverse implementations
The main action item involved the genesis of an informal working group for the threadiverse, in order to align our disparate implementations toward a common path.
We intend to meet monthly at first, with the first meeting likely sometime early-to-mid April.
The topic of the first WG call is: Representation of the higher level collection of Notes (posts, etc.) — Article vs. Page, etc?
Interested?
Publicly reply to this post (NodeBB does not support non-public posts at this time) if you'd like to join the list
As an aside, I'd love to try something new and attempt to keep as much of this as I can on the social web. Can you do me a favour and boost this to your followers?
The newly formed Hubzilla Association is tasked with writing documentation for Hubzilla. We'd love to collaborate and contribute to developer documentation on the Fediverse Developer Network.
There are certain technologies we would like to see propagate, such as nomadic identity, federated single sign on, and federated discussion groups/forums (of course). We can help with documentation on those topics, for those who are interested.
Also, Federated Works, my new baby, along with my company WisTex, is working on several projects that might be of interest of the developer network, such as a federated project management software, and a documentation website called Federated Hub.
Instead of duplicating our efforts, perhaps we should work together and collaborate on these things.
Unnecessary duplication of resources would be unfortunate, so let's avoid that.
Part of the discussion on the fedidevs session (which I think you were in?) centred around building that one central directory for resources.
I'm not sure whether @andypiper or @J12t have any specific software in mind (oooh, federated wiki? haha), but could be Federated Hub; have you got a link?
I'm focusing on getting category actors up ASAP so I can make a followable category for the WG.
@julian@scott@J12t so far we've been in scrappy mode and using Hugo, but I am not opposed to alternatives that might make sense - I believe both Johannes and I are of the view that building and doing are the key elements here.
@andypiper@julian@scott Hugo is really easy to do once set up and GitHub hosts it for us. It has its limitations but we haven’t run into them. Are there requirements that the current setup doesn’t meet?
@julian Can I suggest you gang this up under the umbrella of the Fediverse Developer Network. That way, we can coordinate documentation and community. @andypiper and I will run a session on FediDevs tomorrow where we could discuss practicalities.
@J12t@julian@andypiper perhaps off topic & more the "getting devs started", but I am working on stuff for trust & safety, it's just slow because I don't get much time to work on it. (and Julian, I've your email to reply to later this week)
Add comment