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

It seems like #ActivityPub was always supporting username changes when implemented correct.

General Discussion
5 3 1

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 0 Votes
    1 Posts
    6 Views
    This week I added the ActiviyPub plugin to our college's WordPress blog server. It's a MultiUser server, so each group has their own independent blog hosted by the same WordPress install.People here don't post a whole lot however the student newspaper does post their articles there weekly.Just trying to do my part to increase the human generated content shared here in the Fediverse.Oh, and of course the server is dual stacked and available over #ipv6 #ActivityPub #WordPress
  • 0 Votes
    6 Posts
    17 Views
    Yeah, it's frustrating -- people have been asking for this since forever (well 2018 but close enough .There are some interesting perspectives from Claire on the challenges of adding this to Mastodon in a Github discussion in https://github.com/mastodon/mastodon/issues/7135#issuecomment-636767048@julian @miriamrobern
  • 0 Votes
    1 Posts
    12 Views
    #nextcloud and #syncthing and #deltachat are the real revolutionary technologies of recent. I guess #activitypub too
  • 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.