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

New Fediverse features that actually aren't new


Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 0 Votes
    8 Posts
    6 Views
    Guest?
    super, danke dir fΓΌr den Hinweis! :)
  • 3 Votes
    65 Posts
    62 Views
    @julian i'd say the confusion is primarily that we've shifted topic around several different things and i'm still not sure which is the intended topic of the discussion :x- deleting posts that are in a thread- removing posts from a thread- implications for downstream posts in a thread when some ancestor in the reply chain is deleted/removed- deleting a thread that is in a forum- removing a thread from a forum- moving a thread to the "uncategorized" forum- ...?
  • A Peak At Piefed

    PieFed Meta piefed webdev threadiverse fedihost rimu
    3
    1
    0 Votes
    3 Posts
    5 Views
    What's the secret to Rimu's speed? Piefed is young, so any accumulated technical debt doesn't interfere with new functionality... Yet... Sorry rimu@piefed.social, that time will come for you πŸ˜‚
  • 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.