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

Eurosky dawns: Building Infrastructure for Sovereign Social Media – Open Future

General Discussion
1 1 11

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
    7 Views
    ActivityPub doesn't need task forces to build onboarding resources.It just takes one person and a bit of courage.For both developers and the public.https://fediverse.info - for the publicactivitypub.social - for devs (coming soon)#activityPub
  • 0 Votes
    2 Posts
    18 Views
    @WorldTravelerAll7 that’s a mourning dove! So pretty. How cool you got them to eat out of your hands. How did you do it?
  • 0 Votes
    1 Posts
    13 Views
    This is an extension of the discussion from Topic removal from a category/community. In it, rimu@piefed.social shared the Lemmy federation primer which details that Delete(Object) is federated whenever a post is removed from a community. I needed a way to communicate when a topic/context (not the top-level post) is removed from a category/audience, but is not deleted. You might ask — how is removing a context different from deleting it? In this case, a removed context still exists and is still resolvable. A context can removed from an audience in NodeBB. Note that Lemmy and Piefed don't have a concept of an audience-less context, so if a context is removed from an audience, it would simply be deleted. No additional logic required. Anyhow — when a topic is moved into Uncategorized (which is a catch-all bucket for... you guessed it, uncategorized content), NodeBB will federate a Remove. It looks something like this: { id: '#activity/remove/', type: 'Remove', actor: '', to: [], cc: [, object: '', origin: '', } This is live on activitypub.space already. This goes hand-in-hand with topic moving, which would follow similar mechanisms, except it'd be a Move instead of a Remove. I will likely write an FEP with technical details for both Remove and Move, and will include existing behaviours (Delete(Object)) as well.