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

#ActivityPub developers only please: how many items should be in a full collection page?

General Discussion
9 5 3

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 0 Votes
    6 Posts
    16 Views
    Yes. If no one on, say, mastodon.social is following you then none of your posts will show up in the global timeline there or in searches or in hashtags. Also if you have few followers your posts will receive few boosts so hardly anyone will follow you. So we end up with a handful of wildly popular accounts dominating the conversations which mostly happen on the big instances. Centralised power. Bad. The threadiverse solves this. People don't follow other people, they join communities and it's their membership that determines where the federation traffic goes. So nearly every instance has all the conversation and everyone is on an equal footing.
  • 0 Votes
    1 Posts
    14 Views
    I'm working on federation issues.👻 Release v3.1.2 of Ktistec improves support for Lemmy and community servers like it that distribute content by wrapping it in Announce activities (FEP-1b12: Group federation support). Ktistec also supports the audience property, although support for that was removed from Lemmy earlier this year.🎃 This release also adds support for delivering to shared inboxes, which are widely supported by other ActivityPub servers. Despite being federated, the Fediverse is not highly distributed, and this optimization can reduce outbound delivery traffic by 10-20x.AddedSupport for the Dislike activity.Support for the audience property on activities and objects.Support for delivery to shared inboxes.Support for full-width hash signs in hashtags (e.g. #日本語) commonly used in Japanese and other Asian languages.FixedStrip HTML from object summaries rather than escaping it.Properly unwrap Lemmy-style Announce activities.ChangedDestroy discarded drafts instead of deleting them.Enjoy!#ktistec #fediverse #activitypub #crystallang
  • 0 Votes
    1 Posts
    16 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
    1 Posts
    16 Views
    Checking out Bonfire's latest release. This Federation Status dashboard is pretty cool. And get this - it's not just visible to admins - end users can see the same, just filtered to their OWN processes.That's really helpful if you're trying to debug an issue with another platform development team.#ActivityPub #Bonfire