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

Context removal from an audience

Technical Discussion
1 1 12
  • 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.

  • nodebb@fosstodon.orgundefined nodebb@fosstodon.org shared this topic on

Gli ultimi otto messaggi ricevuti dalla Federazione
  • @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
    - ...?

    read more

  • @julian if the intent is to signal what happens when nodebb moves a thread to "uncategorized", then i think the simplest thing is for nodebb to treat "uncategorized" as a forum in itself, still. you already assign them an id of -1, so you are in effect treating the "uncategorized" category as a category still.

    read more

  • @julian the confusing thing to me, though, is that both Delete and Remove already don't imply anything about posts in the thread if the thread is deleted/removed from the forum.

    by default, if you Delete a thread, the forum might still have a broken link to the now-deleted thread, and the posts also have broken links to the thread.

    by default, if you Remove a thread from the forum, the posts still exist within the thread.

    read more

  • trwnh@mastodon.social specifically however, is that you're not deleting the context. Just removing it.

    NodeBB has the concept of a context not belonging to an audience (the "uncategorized" pseudo category.) in those specific situations, contexts would be removed from the audience, not deleted.

    Lemmy and Piefed don't have these concepts, so they simply delete them. So therein lies some of the confusion I believe.

    read more

  • @julian like removing a whole thread from the forum? Remove(object=thread, target=forum)? this seems like something altogether different than removing posts from a thread.

    removing threads from a forum is possible but if the thread is owned by the forum then the forum can also delete them.

    the part that differs between impls is whether Delete(thing that is a context) should do anything to objects where context = the Delete.object, right? i think it makes the most sense to just orphan them.

    read more

  • trwnh@mastodon.social it signals that the actor is removing the context from the targeted audience.

    The audience can optionally announce it, and receivers synchronizing with that audience (per 1b12) should follow suit and remove the context as well.

    read more

  • @julian what does Remove(Context) mean here?

    read more

  • trwnh@mastodon.social said in Deleting a post vs deleting an entire comment tree:
    > Remove(object=[n posts],target=thread)

    That would indeed be the most explicit, but that isn't needed from threadiverse because that information is already contained when you set object to the context itself.

    It's even resolvable! So there's no need to send your own array of items that might be out of date by the time it is delivered.

    Hence why I advocate for Remove(Context)

    read more
Post suggeriti
  • 0 Votes
    1 Posts
    5 Views
    #WordPress #ActivityPub #Mastodonいつものことだけど、いしい@雑談のコメント欄からの投稿はマストドンのハッシュタグタイムラインに表示されない。
  • 0 Votes
    1 Posts
    12 Views
    You may notice the Follow button on Loops.video is clickable even when logged-out.I added a modal that explains how to remote follow, isn't that neat?#loops #tikTok #activityPub #fediverse
  • 1 Votes
    1 Posts
    17 Views
    RE: https://mastodon.social/@MastodonEngineering/115337952873418574Uy... 👀 Interesante...> Change the identifiers used in ActivityPub to numeric IDs (instead of their username) for new users. This is a first step towards allowing account renaming. — Github PR #32724 (by ClearlyClaire)#mastodon #activitypub #fediverso #fedi #fediverse
  • 0 Votes
    1 Posts
    19 Views
    Running a community in the Fediverse means balancing openness with safety. Every year, @iftas takes the pulse of administrators, moderators, and community managers with their Annual Needs Assessment. This survey helps identify what’s working, where support is needed, and which tools can make a difference for those keeping decentralized spaces safe.The 2025 survey is now openTake part in the IFTAS Needs Assessment (5–10 minutes).Take the survey now(If you haven’t seen them before, you can also take a look at last year’s report)Last year’s responses represented moderators of over 4.3 million accounts across ActivityPub platforms. With WordPress now the largest group of federating instances, it’s especially important for our community of hosts, site admins, and moderators to be heard.Moderation in WordPress: From Site-Wide to Personal ControlsWe recently introduced a major update to the ActivityPub plugin for WordPress: personalized and site-wide moderation tools.Site administrators can now set domain, keyword, and actor-level blocks that protect the entire site.Individual users can fine-tune their own experience with personal blocks, managed directly from their profiles.Content is checked against both global and personal rules—so moderation works at every level.These improvements directly address needs raised in previous IFTAS surveys, making moderation more discoverable, flexible, and effective for WordPress communities in the Fediverse.Your Input MattersIFTAS uses the Needs Assessment to guide tools, policies, and advocacy that reflect the real-world challenges of moderators—especially those in under-resourced communities. The more representative the responses, the stronger the outcomes for everyone.If you’re running a federating WordPress site, please consider:Filling out the survey yourself.Sharing it with other admins, moderators, and community organizers.Reminding folks that it’s anonymous, quick, and impactful.Take the 2025 Fediverse Needs AssessmentTogether, we can keep building a safer, healthier Fediverse—one that reflects the needs of its communities.