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

Hello Fediverse

  • Hello Fediverse

    If everything works out according to plan, when I hit publish on this post it will show up in the . After a year of on-and-off attempts, to implement on this website, with no success, I have hopefully cracked it! Well, when I say “I have hopefully cracked it,” what I mean is @pfefferle@mastodon.social and the “open office hours” program, have cracked it. It turns out; if you have a problem with the WordPress ActivityPub plugin, the best thing to do is disable other plugins and, though a process of elimination, see if one of them is the issue. So big thanks to Mathias and WordPress for your help on this.

    Now this is working and I am broadcasting out into the Fediverse, I feel like I should modify my content a little to appeal to all of you woke, leftists, godless, communists 🙂 out there. For a while I was far too smitten with the every little initiative, every little carbon reduction program, and every other bit of  #GreenWashing that was put out there by brands. Full confession I actually believed that ElonMusk wanted to save the planet! Yeh I know, I was naive…

    While I do continue to applaud any actions that a corporation takes, that materially helps either people or planet, it’s clear that problems are systemic. We need corporations to shift from Shareholder Primacy to Stakeholder Capitalism, valuing environmental and social impact alongside profit. Or try someting completely different. Right now, if there is a more sustainable or ethical brand choice to be had, we should always take it, but we must understand, that we are not “saving the planet” with those choices, just minimising our impact. Nebula TV channel, Our Changing Climate,  has this excellent video on the subject of Ethical Consumerism.

    It turns out, that whoever first pointed out “Corporations are Psychopaths” was mostly correct – How a corporation is designed to function, putting shareholders before people and planet, is psychopathic behaviour. (Psychopathic behaviour includes a lack of empathy and remorse, superficial charm, manipulation, and a disregard for social norms and the rights of others.) The only solution is to rewrite corporate charters and incorporation acts and include specific legal provisions that mandate environmental and social responsibility, shifting the core purpose of business beyond mere profit maximisation. Ultimately Corporations and their leaders are never going to fully act in the best interests of people and planet, because that’s not what they were created to do.

    So the plan, for 2026, is to be posting more content here that challenges both brands and the whole system. To shine a light on the negative impacts to people and planet that brands are having. And to share more content about organisations and companies working on regeneration and decarbonisation.

    Please follow and share your thoughts and ideas below.

  • System moved this topic from General Discussion on

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 0 Votes
    1 Posts
    7 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
    11 Posts
    22 Views
    @Linkshaender Thank you! You too!
  • Good morning Fedi friends!

    Fediverso fediverse
    6
    0 Votes
    6 Posts
    20 Views
    @teddythepreacher @_elena @niccolove @morloi Musk to me is like an old boss out of a Donald E. Westlake Parker novel. He's bad for everyone's business directly and indirectly. As he runs a long con-artist game. Along with feeling an unnecessary goal to inflate his and Trump's ego as well.
  • 0 Votes
    2 Posts
    17 Views
    The Discourse ActivityPub plugin is developed by a sole developer but I believe it is ready for use. I also believe he is still working on the plugin so that's positive news. Federation with Discourse forums is tricky, it's been difficult getting NodeBB to work reliably with Discourse. Are you able to load Discourse categories in Lemmy?