Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone

@julian are there any plans to add #RSS support to #NodeBB?

Fediverso
9 4 74

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 0 Votes
    1 Posts
    11 Views
    #Citiverse è il nuovo forum federato con il #Fediverso. L'avete provato? #NodeBB è una delle piattaforme forum più utilizzate e adesso, grazie al suo fantastico sviluppatore, è perfettamente integrato con tutto l'ecosistema #Activitypub. Fateci sapere se l'avete provato e se vi piace! https://citiverse.it/@fediverso
  • 0 Votes
    1 Posts
    11 Views
    Kind of wild #cooklang has its own federation setup now. 😅Sure it uses #rss. No fancy #ActivityPub. Still, fascinating to see something like this. More of the web trying to index itself as primary search engines lose all their meaning to what search means. 🫠https://cooklang.org/blog/13-the-dishwasher-salmon-problem/
  • 0 Votes
    3 Posts
    19 Views
    @julian Yes, I was bored and thought that was still missing in the fedi
  • 0 Votes
    1 Posts
    21 Views
    At Piefed office hours, rimu@piefed.social and I got to talking about what's next for Piefed and the Threadiverse WG. One of those things is moving stuff between communities (or in bbs parlance: moving topics between categories/forums). Rimu suggested we use the already-existing as:Move activity, sent by the community (a group actor), with origin and target set, and with object being the post id itself. I suggested we update this to use the resolvable context collection as object instead, which Piefed has supported since v1.2. That should be enough to get a proof-of-concept implementation going between Piefed and NodeBB... a question remained as to whether this should be Announce(Move(Object)) or simply Move(Object). Argument for former was that it was similar verbiage to other 1b12 actions. Argument for the latter was that this is merely 1b12 adjacent and needn't follow prior art. We'll likely put together an FEP for this.