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

Bonfire pushed a big release last week, and I'm excited to try out all the new shiny things on my test instance.'nPost migration and Quote Posts among them.'n#Bonfire #ActivityPub

General Discussion
7 4 21

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 0 Votes
    2 Posts
    1 Views
    @bengo>What does ActivityPub + Ethereum look like?This was the first thing I tried. Mitra had NFTs, token gate and subscriptions:https://codeberg.org/silverpill/mitra-contractsBut there was very little interest, and self-hosting Ethereum node is too expensive anyway, so I removed the integration later. We still support Sign-In with Ethereum, though.
  • Auto-import of deny lists

    Technical Discussion dni activitypub iftas
    7
    0 Votes
    7 Posts
    31 Views
    Just spend the tiny bit of extra time and implement basic support for federation policies. Keep track of data snd where it comes from, such that you can react to changes over time
  • 0 Votes
    1 Posts
    9 Views
    No, am not particularly worried about my government reading my posts. Not if it requires Kristi Noem to understand #activitypub.
  • 0 Votes
    1 Posts
    10 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.