How to Install #Pleroma on #Ubuntu #VPS (5 Minute Quick-Start Guide) This article provides a guide demonstrating how to install Pleroma on Ubuntu VPS.What is Pleroma?Pleroma is a free, open-source, self-hostable microblogging server that speaks the #ActivityPub federation protocol—so your users can interact with people on other #Fediverse platforms (e.g., Mastodon) while you keep full control over your server ...Continued 👉 https://blog.radwebhosting.com/how-to-install-pleroma-on-ubuntu-vps/?utm_source=mastodon&utm_medium=social&utm_campaign=mastodon.raddemo.host #selfhosting #selfhosted #letsencrypt

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.

@evan @phi > We have some ad hoc ways to move from one to the other, but they aren't built into the SMTP or IMAP specsyes they are, though? in IMAP, you can just copy your messages and folders from one inbox to another. in SMTP, we have email forwarding.using your own DNS name can make things easier, but the main challenge in fedi is that we don't have a common storage/access abstraction (equivalent to IMAP folders), and we don't recognize HTTP redirects (equivalent to SMTP forwarding).

@hongminhee It's a place where our loosey goosey style goes into nondeterminism. We should tighten it up in the next version. My main answer would be: publishers, don't do that.