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! :)
  • 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
    6 Posts
    32 Views
    Honestly? Neither am I. This post is mostly a trial balloon to see what people think about the abstract high level idea of potentially talking cross-protocol with BlueSky users.
  • 0 Votes
    13 Posts
    50 Views
    In a nutshell, it's because you don't have to build the entire kit and kaboodle all at once. Lots of BlueSky is centralized so you don't have to worry about distribution, user, hosting, scaling, etc. and just focus on the frontend. It's the same reason why all the Lemmy and Mastodon apps look way better than the web versions, because all those other parts are no longer relevant and the creator(s) can focus on just putting out a polished product.