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

if you have issues with the #ActivityPub plugin for #WordPress or curious about how it works.

General Discussion
22 5 17

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 0 Votes
    1 Posts
    9 Views
    Am 14 November kommt Loops die Fediverse tiktok alternative auch auf denn Google Play Store. Endlich kann ich Doom scrolling auch auf dem Fediverse betreiben. Ich freue mich.😁 #fediverse #activitypub #loopsapp #pixelfed #tiktok
  • 0 Votes
    3 Posts
    17 Views
    Or maybe just use OAuth with the profile scope that'll give you exactly what you need, and handle all the potential security implications?
  • 0 Votes
    1 Posts
    12 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
    20 Views
    @box464 we started drafting a section on "how do boundaries federate" in this document: https://docs.bonfirenetworks.org/boundaries.htmlThe short story is we interoperate with Mastodon's newly introduced canQuote and and GoToSocial's canReply/canLike/canAnnounce for general boundaries like only follows can reply or everyone can quote, and for everything else it's enforcement at the level of your instance (e.g. "basically just drop replies you don't want"). Feedback on that and on the docs as well is more than welcome!