Using AP federation to re-unify fediverse dev discussion across multiple forums
ActivityPub Client-to-Server
2
Posts
2
Posters
0
Views
-
Continuing the discussion from Possible C2S Implementation in LAUTI:
Possible C2S Implementation in LAUTIWhat is the reason that this thread does not federate? It looks like it should..
SocialHub federation has been broken for a long time, and shows no sign of being fixed. This is another reason I'm abandoning it for greener pastures. It's great that @angus is maintaining SH as a historical archive to keep the many links that point here from breaking. But it's clearly no longer the community centre it once was.
Possible C2S Implementation in LAUTIEven though it is a medium that is not up to the task of holding a grassroots open-standards based ecosystem together, microblogging has become the preferred channel for communication in the app-centric fediverse.
I agree this is far from ideal. As I made pretty clear in my topic last year arguing against forum fragmentation. But I'm not sure that's exactly what's happening.
Some dev discussion seems to have moved to ActivityPub.space, which is a nodeBB forum, not a microposting service. Other discussions seems to be happening in communities on Lemmy services, etc. The challenge now is to realise the promise of the "threadiverse". By figuring out how to use AP federation to weave all these discussions together, so it feels like it's all happening in a unified space, and all the discussions can be discovered via any of the participating forums.
-
Continuing the discussion from Possible C2S Implementation in LAUTI:
Possible C2S Implementation in LAUTIWhat is the reason that this thread does not federate? It looks like it should..
SocialHub federation has been broken for a long time, and shows no sign of being fixed. This is another reason I'm abandoning it for greener pastures. It's great that @angus is maintaining SH as a historical archive to keep the many links that point here from breaking. But it's clearly no longer the community centre it once was.
Possible C2S Implementation in LAUTIEven though it is a medium that is not up to the task of holding a grassroots open-standards based ecosystem together, microblogging has become the preferred channel for communication in the app-centric fediverse.
I agree this is far from ideal. As I made pretty clear in my topic last year arguing against forum fragmentation. But I'm not sure that's exactly what's happening.
Some dev discussion seems to have moved to ActivityPub.space, which is a nodeBB forum, not a microposting service. Other discussions seems to be happening in communities on Lemmy services, etc. The challenge now is to realise the promise of the "threadiverse". By figuring out how to use AP federation to weave all these discussions together, so it feels like it's all happening in a unified space, and all the discussions can be discovered via any of the participating forums.
To head off any potential accusations of impropriety, ActivityPub.Space is simply meeting ActivityPub discussion where it already is — the fediverse. The same people who post on SocialHub continue to post on SocialHub 🙂
In fact, ActivityPub itself heads off the need for tribalism between forum communities. Both Discourse and NodeBB can federate with each other.
NodeBB just has additional tooling that helps soften a bunch of federation's rough edges, plus first-class threadiverse support and discovery features for non-forum content (read: mastodon, et al.)
As for questions about which format is best: it doesn't have to matter. Participate on a forum, participate on a microblog, it shouldn't matter because the conversations should be accessible to both kinds.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
To head off any potential accusations of impropriety, ActivityPub.Space is simply meeting ActivityPub discussion where it already is — the fediverse. The same people who post on SocialHub continue to post on SocialHub 🙂
In fact, ActivityPub itself heads off the need for tribalism between forum communities. Both Discourse and NodeBB can federate with each other.
NodeBB just has additional tooling that helps soften a bunch of federation's rough edges, plus first-class threadiverse support and discovery features for non-forum content (read: mastodon, et al.)
As for questions about which format is best: it doesn't have to matter. Participate on a forum, participate on a microblog, it shouldn't matter because the conversations should be accessible to both kinds.
-
Continuing the discussion from Possible C2S Implementation in LAUTI:
Possible C2S Implementation in LAUTIWhat is the reason that this thread does not federate? It looks like it should..
SocialHub federation has been broken for a long time, and shows no sign of being fixed. This is another reason I'm abandoning it for greener pastures. It's great that @angus is maintaining SH as a historical archive to keep the many links that point here from breaking. But it's clearly no longer the community centre it once was.
Possible C2S Implementation in LAUTIEven though it is a medium that is not up to the task of holding a grassroots open-standards based ecosystem together, microblogging has become the preferred channel for communication in the app-centric fediverse.
I agree this is far from ideal. As I made pretty clear in my topic last year arguing against forum fragmentation. But I'm not sure that's exactly what's happening.
Some dev discussion seems to have moved to ActivityPub.space, which is a nodeBB forum, not a microposting service. Other discussions seems to be happening in communities on Lemmy services, etc. The challenge now is to realise the promise of the "threadiverse". By figuring out how to use AP federation to weave all these discussions together, so it feels like it's all happening in a unified space, and all the discussions can be discovered via any of the participating forums.
-
Check out this intro to HDA (Hypermedia-Driven Applications);
https://hda.daz.is/architecture/why-hypermedia-driven-architecture/
This seems relevant to the ongoing discussions about C2S APIs for the fediverse, especially the proliferation of the monolithic server+web-app antipattern. If Daz (@daz@social.coop) is correct, properly RESTful APIs that use an HDA architecture might be a way to realise Christine Webber's original vision. Fediverse web apps with specific purposes, like browsing and posting video, as ways to login to generic AP servers hosting general-purpose accounts.