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

Hey #ActivityPub friends.

General Discussion
18 6 3

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 0 Votes
    7 Posts
    22 Views
    @awiro_median @awiro-median 👋 habt ihr den WP-Cron richtig konfiguriert? Die Bestätigung wird über den Cron verschickt und wenn der nicht oder nur selten läuft, funktioniert es nicht oder dauert entsprechend.
  • 0 Votes
    1 Posts
    14 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
    13 Views
    Transparency update: Web framework integration progress We're sharing a public project board to track our progress on web framework integrations for #Fedify, work commissioned by the Sovereign Tech Fund (@sovtechfund@mastodon.social). You can follow along at: https://github.com/orgs/fedify-dev/projects/1 About this work The Sovereign Tech Fund invested in Fedify to expand its ecosystem through official integrations with popular web frameworks. This investment enables developers to add federation capabilities to their existing applications without changing their technology stack. Notably, some of these integrations were completed between our initial application submission and the official kickoff of the #STF investment. This demonstrates both our commitment to the project and the community's active development momentum. Current status Already completed: Next.js integration supporting both App Router and Pages Router (completed before STF kickoff) Elysia integration optimized for the Bun ecosystem (completed before STF kickoff) In progress: Fastify integration (PR currently under review) Upcoming: Koa integration Comprehensive documentation for all integrations Why this matters These integrations make Fedify accessible to developers across different JavaScript ecosystems and runtime environments. Each integration follows established patterns from our Express and h3 integrations, ensuring consistency and ease of adoption. Investment details Fedify has been awarded a service agreement by the Sovereign Tech Fund for this work, with a budget of €‎32,000 and completion target of November 30, 2025. The Sovereign Tech Agency supports the development, improvement, and maintenance of open digital infrastructure through investments like this. We believe in transparent development and welcome community input and contributions. #ActivityPub #SovereignTechFund #opensource
  • 0 Votes
    14 Posts
    49 Views
    @dansup @thisismissem Hopefully, at least testing will become a bit easier now https://friend.camp/@darius/115300222885243971