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
  1. Home
  2. Categories
  3. General Discussion
  4. Other projects we work on include old-school social networks relaunched with Fediverse software.

Other projects we work on include old-school social networks relaunched with Fediverse software.

General Discussion
2 2 0
Log in to reply

Feed RSS
Other projects we work on include old-school social networks relaunched with Fediverse software.

Gli ultimi otto messaggi ricevuti dalla Federazione
@pierobosio@soc.bosio.info
Post suggeriti
  • Mims, Most Basic of Bitchesundefined

    still fucking mystified why i cant limit posts to mutuals.

    General Discussion mastodon activitypub
    6
    0 Votes
    6 Posts
    1 Views
    Jonundefined
    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
  • julianundefined

    Moving topics/contexts between communities

    Technical Discussion context fep audience activitypub
    13
    0 Votes
    13 Posts
    47 Views
    julianundefined
    silverpill@mitra.social I have been reflecting on the use of Remove/Move vs Update and I am thinking that Update isn't explicit enough. If I am removing a topic from a category, I'd be sending an Update with the group actor removed from the audience property. However recipients wouldn't know which audience was removed, merely the new state of that context's audience.
  • Week in Fediverse :fediverse_light:undefined

    Week in Fediverse 2025-10-24

    Fediverso fediverse activitypub weekinfediverse
    1
    0 Votes
    1 Posts
    14 Views
    Week in Fediverse :fediverse_light:undefined
    Week in Fediverse 2025-10-24Servers- Betula v1.5.0- Vernissage Server v1.25.0- Mastodon v4.4.8- Ktistec v3.1.1- Wafrn v2025.10.01- Mobilizon v5.2.0- Misskey v2025.10.1- NeoDB v0.12.4- Merp Relay v0.3.0- comments: Server component for comment tracking systemsClients- IceCubesApp v2.0.8- Mangane v1.18.1- Photon v2.1.1- Blorp v1.9.26Tools and Plugins- Poduptime v5.5.4- Fediverse follows quiz- Vulpes Porto: Bot to post remotely or locally hosted photos daily at set timesFor developers- Fedialgo v1.2.23- apkit v0.3.3- roboherd v0.1.12Protocol- Server-Sent Events For the ActivityPub APIArticles- Understanding Decentralized Social Feed Curation on Mastodon- Fediverse Report #139-----#WeekInFediverse #Fediverse #ActivityPubPrevious edition: https://mitra.social/objects/0199f3d4-c2ce-a6c6-de48-dcb254582434
  • julianundefined

    Context removal from an audience

    Technical Discussion activitypub threadiverse
    1
    0 Votes
    1 Posts
    8 Views
    julianundefined
    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.