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

Big thanks to @pfefferle and @obenland for the #ActivityPub @WordPress plugin office hours today.

General Discussion
2 2 7

Gli ultimi otto messaggi ricevuti dalla Federazione
  • Esteemed Fediverse, a personal remark

    it currently matters again to have a chair who knows what is going on, is striving for facts, understanding fascism and having a will to resist imperialism. And the capacity to save net neutrality.

    Hey @darius
    thank you for this:
    https://lists.w3.org/Archives/Public/public-socialweb/2026Jan/0000.html
    !

    ---
    Currently we move our projects to codeberg and so i just published a first document there about our fedi projects.
    https://codeberg.org/Menschys/fedi-codebase
    We would really like to have building blocks for ahealthy and fair Client-To-Server supported ActivityPub.

    Current Issues are linked. If you want, I can give you an overview of the Social CG dev meetings since 2016 and the European Events like fedicamp, fediday, Public Spaces, 3C etc.

    read more

  • @zaire

    " I absolutely do not see how this is in any way worse for Black people than oligarch-controlled centralized spaces"

    Which is the difference between me and you. Which is the difference between millions of Black people and you.

    And you are not owed an explanation. Just go away before I block you.

    And no, Black people can't exist here without being bothered unless they're on an unmoderated instance. For example, right now, I, a proud son of Africa, I'm being bothered by some weirdo with Zaire in their handle, that's trying to tell me how moderation works on the Fediverse.

    read more

  • @achim@social.saarland I have found activitypub.academy to be a very helpful implementation to test against as well!

    read more

  • @mekkaokereke the very inherent factors that let nazis set up camp on the Fediverse work both ways. good people can hang out here on the fediverse without being interfered with by any state or corporation. and said good people can, and do fediblock the fuck out of the vocal minority of fash. I absolutely do not see how this is in any way worse for Black people than oligarch-controlled centralized spaces that range only from fascist to mediocrily centrist.

    read more

  • @mekkaokereke

    But there is more CSAM on the Fediverse than on other social media, including BlueSky, and it’s not close. There are more nazi instances on the Fediverse than on BlueSky, and it’s not close.

    This only means anything if you’re on an unmoderated instance yourself. and even then, I figure it’s because BS has 200 times less instances in general…?

    Mind you, I do think myself quite clever, and I do think the Fediverse is morally superior to the fascist-platforming BS, and I have good reasons for it.

    The Fediverse is less welcoming to Black people than either BlueSky or Twitter

    When you bring up X as more welcoming to any minority and more worth using than fedi I start to have trouble taking you seriously.

    read more

  • @zaire

    I said what I said.

    People like you try to tell everyone that corpo vs open source is the line between good and evil. And you think yourself so clever for pointing out that "Mastodon is not the whole Fediverse."

    But there is more CSAM on the Fediverse than on other social media, including BlueSky, and it's not close. There are more nazi instances on the Fediverse than on BlueSky, and it's not close. The Fediverse is less welcoming to Black people than either BlueSky or Twitter, and it's not close.

    You prioritize anti-corp as most important, and that's fine for you. I define anti-racism and safety for Black people as mine. When the Fediverse is less dangerous for Black people than all the other social media, I'll encourage more people to come to it. Until that day, I'll work to make that true, and I'll tell people like you to pipe down when they try to pretend that the Fediverse today is some type of utopia, or even morally superior to BlueSky. It's not.

    But it could be.

    read more

  • How to setup a local instance for debugging my own AP development:

    https://blog.achims.world/mastodon-for-activitypub-development.html

    read more

  • @mekkaokereke “I’m unapologetically backing improvements across […] ATProto” “You can just back both teams”

    lets be real no you shouldn’t back a corpo project that acts purely to divide people and push a centroid & centralized ecosystem

    I know i’m saying this to someone who talks about Mastodon as if it were the entire Fediverse and allegedly works for Google but dude no BS is not our friend here

    read more
Post suggeriti
  • 0 Votes
    1 Posts
    1 Views
    Fedify 1.10.0: Observability foundations for the future debug dashboard Fedify is a #TypeScript framework for building #ActivityPub servers that participate in the #fediverse. It reduces the complexity and boilerplate typically required for ActivityPub implementation while providing comprehensive federation capabilities. We're excited to announce #Fedify 1.10.0, a focused release that lays critical groundwork for future debugging and observability features. Released on December 24, 2025, this version introduces infrastructure improvements that will enable the upcoming debug dashboard while maintaining full backward compatibility with existing Fedify applications. This release represents a transitional step toward Fedify 2.0.0, introducing optional capabilities that will become standard in the next major version. The changes focus on enabling richer observability through OpenTelemetry enhancements and adding prefix scanning capabilities to the key–value store interface. Enhanced OpenTelemetry instrumentation Fedify 1.10.0 significantly expands OpenTelemetry instrumentation with span events that capture detailed ActivityPub data. These enhancements enable richer observability and debugging capabilities without relying solely on span attributes, which are limited to primitive values. The new span events provide complete activity payloads and verification status, making it possible to build comprehensive debugging tools that show the full context of federation operations: activitypub.activity.received event on activitypub.inbox span — records the full activity JSON, verification status (activity verified, HTTP signatures verified, Linked Data signatures verified), and actor information activitypub.activity.sent event on activitypub.send_activity span — records the full activity JSON and target inbox URL activitypub.object.fetched event on activitypub.lookup_object span — records the fetched object's type and complete JSON-LD representation Additionally, Fedify now instruments previously uncovered operations: activitypub.fetch_document span for document loader operations, tracking URL fetching, HTTP redirects, and final document URLs activitypub.verify_key_ownership span for cryptographic key ownership verification, recording actor ID, key ID, verification result, and the verification method used These instrumentation improvements emerged from work on issue #234 (Real-time ActivityPub debug dashboard). Rather than introducing a custom observer interface as originally proposed in #323, we leveraged Fedify's existing OpenTelemetry infrastructure to capture rich federation data through span events. This approach provides a standards-based foundation that's composable with existing observability tools like Jaeger, Zipkin, and Grafana Tempo. Distributed trace storage with FedifySpanExporter Building on the enhanced instrumentation, Fedify 1.10.0 introduces FedifySpanExporter, a new OpenTelemetry SpanExporter that persists ActivityPub activity traces to a KvStore. This enables distributed tracing support across multiple nodes in a Fedify deployment, which is essential for building debug dashboards that can show complete request flows across web servers and background workers. The new @fedify/fedify/otel module provides the following types and interfaces: import { MemoryKvStore } from "@fedify/fedify"; import { FedifySpanExporter } from "@fedify/fedify/otel"; import { BasicTracerProvider, SimpleSpanProcessor, } from "@opentelemetry/sdk-trace-base"; const kv = new MemoryKvStore(); const exporter = new FedifySpanExporter(kv, { ttl: Temporal.Duration.from({ hours: 1 }), }); const provider = new BasicTracerProvider(); provider.addSpanProcessor(new SimpleSpanProcessor(exporter)); The stored traces can be queried for display in debugging interfaces: // Get all activities for a specific trace const activities = await exporter.getActivitiesByTraceId(traceId); // Get recent traces with summary information const recentTraces = await exporter.getRecentTraces({ limit: 100 }); The exporter supports two storage strategies depending on the KvStore capabilities. When the list() method is available (preferred), it stores individual records with keys like [prefix, traceId, spanId]. When only cas() is available, it uses compare-and-swap operations to append records to arrays stored per trace. This infrastructure provides the foundation for implementing a comprehensive debug dashboard as a custom SpanExporter, as outlined in the updated implementation plan for issue #234. Optional list() method for KvStore interface Fedify 1.10.0 adds an optional list() method to the KvStore interface for enumerating entries by key prefix. This method enables efficient prefix scanning, which is useful for implementing features like distributed trace storage, cache invalidation by prefix, and listing related entries. interface KvStore { // ... existing methods list?(prefix?: KvKey): AsyncIterable<KvStoreListEntry>; } When the prefix parameter is omitted or empty, list() returns all entries in the store. This is useful for debugging and administrative purposes. All official KvStore implementations have been updated to support this method: MemoryKvStore — filters in-memory keys by prefix SqliteKvStore — uses LIKE query with JSON key pattern PostgresKvStore — uses array slice comparison RedisKvStore — uses SCAN with pattern matching and key deserialization DenoKvStore — delegates to Deno KV's built-in list() API WorkersKvStore — uses Cloudflare Workers KV list() with JSON key prefix pattern While list() is currently optional to give existing custom KvStore implementations time to add support, it will become a required method in Fedify 2.0.0 (tracked in issue #499). This migration path allows implementers to gradually adopt the new capability throughout the 1.x release cycle. The addition of list() support was implemented in pull request #500, which also included the setup of proper testing infrastructure for WorkersKvStore using Vitest with @cloudflare/vitest-pool-workers. NestJS 11 and Express 5 support Thanks to a contribution from Cho Hasang (@crohasang@hackers.pub), the @fedify/nestjs package now supports NestJS 11 environments that use Express 5. The peer dependency range for Express has been widened to ^4.0.0 || ^5.0.0, eliminating peer dependency conflicts in modern NestJS projects while maintaining backward compatibility with Express 4. This change, implemented in pull request #493, keeps the workspace catalog pinned to Express 4 for internal development and test stability while allowing Express 5 in consuming applications. What's next Fedify 1.10.0 serves as a stepping stone toward the upcoming 2.0.0 release. The optional list() method introduced in this version will become required in 2.0.0, simplifying the interface contract and allowing Fedify internals to rely on prefix scanning being universally available. The enhanced #OpenTelemetry instrumentation and FedifySpanExporter provide the foundation for implementing the debug dashboard proposed in issue #234. The next steps include building the web dashboard UI with real-time activity lists, filtering, and JSON inspection capabilities—all as a separate package that leverages the standards-based observability infrastructure introduced in this release. Depending on the development timeline and feature priorities, there may be additional 1.x releases before the 2.0.0 migration. For developers building custom KvStore implementations, now is the time to add list() support to prepare for the eventual 2.0.0 upgrade. The implementation patterns used in the official backends provide clear guidance for various storage strategies. Acknowledgments Special thanks to Cho Hasang (@crohasang@hackers.pub) for the NestJS 11 compatibility improvements, and to all community members who provided feedback and testing for the new observability features. For the complete list of changes, bug fixes, and improvements, please refer to the CHANGES.md file in the repository. #fedidev #release
  • 0 Votes
    10 Posts
    1 Views
    @jansenspott @herrjemineh @kaffeeringe oh! das muss ich mir gesondert nochmal anschauen!
  • Whoop Whoop!

    Moved Uncategorized activitypub wordpress
    1
    0 Votes
    1 Posts
    3 Views
    Whoop Whoop! 🚀 Das #ActivityPub-Plugin für #WordPress bekommt lokales Caching für die Avatare!https://github.com/Automattic/wordpress-activitypub/pull/2610
  • 0 Votes
    1 Posts
    13 Views
    #WordPress #ActivityPub #Mastodonいつものことだけど、いしい@試行錯誤のコメント欄からの投稿はマストドンのハッシュタグタイムラインに表示されない。