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

Would you like to see full default interoperability between #ATproto and #ActivityPub without a bridge?

General Discussion
47 8 2.5k

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 1 Votes
    2 Posts
    12 Views
    @lqdev@lqdev.me indeed, now I no longer see raw markdown 😁
  • 0 Votes
    1 Posts
    11 Views
    At this year's Solid Symposium, we gave a presentation on the lessons we've learned from building and maintaining several ActivityPods applications since 2022. The result is 14 key learnings that we're glad to share with the Solid community. More informations at https://activitypods.org/key-learnings-from-building-social-apps
  • 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.
  • 0 Votes
    2 Posts
    15 Views
    jeffries@ieji.de yes, it is beautifully presented and hits on some good points. I believe the author was a Bluesky employee, hence the lack of ActivityPub mention.