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

Could I ask #fediverse for some #fedihelp?


Gli ultimi otto messaggi ricevuti dalla Federazione
  • @julian hmm, kind of like how you, on a NodeBB forum, saw a post on Mastodon, and our collective conversation is magically appearing at the bottom of a WordPress blogpost.

    Translated:

    Everyone can see everyone's comments, even if they're on a different web site.

    read more

  • This is the direction the Fediverse needs to go.

    Not about instances and federation jank, but apps and websites that talk to each other and you don't have to think twice about it.

    read more

  • @blog very interesting!

    read more

  • @blog "Private Mentions have their own space. You cannot create a private mention in the main composer and you will not see them in your timeline. We have put them in a dedicated “Conversations” tab to reduce mistakes and keep privacy intentional."

    THANK YOU

    read more

  • Recently, I was sitting with my sister-in-law talking about social media. She has that nagging, familiar concern about corporate social: the feeling that we are all just products in someone else’s machine. I pulled out my phone, showed her my toot.wales feed, and started explaining how she could “save the web site to her home screen”.

    She listened politely, then said the thing I believe most people genuinely feel:

    “It’s lovely! If only there was an app…”

    She does not want a “protocol”. She does not want to hear about “the Fediverse”. She just wants that feed on her phone without a homework assignment.

    When I started toot.wales, I knew this instinctively. In the early days, I even paid a developer to fork a couple of open-source apps and hard-code them to our server. It was expensive and eventually I simply couldn’t sustain it, but I never lost sight of that goal.

    Now, working with our brilliant friends at the Newsmast Foundation, we have finally delivered it: a simple, opinionated, “people-first” social app.

    One community. One door.

    The biggest design decision we made was the simplest: the app is hard-locked to toot.wales.

    There is no “pick a server” screen or “find your instance”. There is no friction. This is not “a Mastodon app”; it is the Tŵt app, purpose-built for our community.

    I’ve spent years building tools like StartHereSocial to help people navigate the “maze” of the Fediverse. However, for toot.wales, I realised the answer should not be a better map. It should be an inviting, open front door. If you want to join us, you should be able to step right in.

    Croeso: A warmer welcome

    Alongside the app, I built a promotional web site at croeso.toot.wales. Croeso is Welsh for “welcome”, and that is exactly what it provides. It strips away the jargon. There is no talk of federation or decentralisation. Instead, it offers clear language about why this is “Better Social”.

    It is joyful and unthreatening on purpose. We are not here to preach at you to quit X or Facebook, and we are not shaming anyone. We are simply inviting you to try something different. If you like the vibe, stay. If not, that is fine too. People stay because it feels good, not because they have been talked into a boycott.

    A Fediverse of communities

    Some people see the Fediverse as one giant global town square. I see it differently. For me, it is a constellation of communities.

    When people tell me “mastodon.social is too big”, my gut feeling is no, your server is too small. Communities only grow when we intentionally nurture them. It is not up to a company in Germany to grow Tŵt. That’s on us, it’s our problem.

    I want everyone in Wales (and the world!) to have a social option that is not drowned in surveillance and ad-tech. To get there, we have to design for clarity rather than complexity.

    What’s inside the Tŵt app?

    We have made some very deliberate choices to keep the app “human-shaped”:

    Private Mentions have their own space. You cannot create a private mention in the main composer and you will not see them in your timeline. We have put them in a dedicated “Conversations” tab to reduce mistakes and keep privacy intentional.Three simple tabs. You get Home (your personal feed), Tŵt (the “local” feed plus replies), and Explore (your lists and hashtags, plus curated feeds for news, sport, culture and more). This creates a natural flow from your own interests to the wider community.Search is just search. There are no “trending” nudges or unsolicited content. If you are looking for something, we help you find it. We don’t try to distract you along the way. Trending is it’s own Channel.True Bilingualism. English and Cymraeg sit side-by-side as equal choices. Digital spaces should reinforce our identity, not flatten it.Celebrating the pioneers

    The Tŵt ecosystem is already thriving because Welsh media organisations took a leap of faith into the open web. Groups such as Nation.Cymru, Golwg360, Swansea Bay News, and Wrexham.com did not wait to see which way the wind was blowing. They just started building, and are long-time social web citizens.

    Whether it is weather updates from North Wales Storms or local sports teams, these partners make the app feel “live” from the moment you log in. The app offers two pathways to consume this content, via Channels you can drop in and out of, or Starter Packs you can follow to bring them into your feed.

    Why this matters

    For those already comfortable with the Fediverse, using a web interface is fine. But for everyone else, “just install the web site” is not meaningful advice.

    People want “the app”. They want to tap an icon and feel at home, rather than feeling like they are doing a technical chore.

    If you run a community and like our approach, please feel free to use it. Whether it is the onboarding flow, the “Better Social” messaging, or the focus on language equity, you are welcome to use my work as a template. If we want a healthier internet, we need more communities feeling empowered to build their own front doors.

    The Tŵt app is our doorway. It is built for Wales and the Welsh, at home and abroad. It is simple, it is ours, and I cannot wait for you to try it. We plan on launching on Dydd Dewi Sant, a special day for Cymru, in the meantime you can get a preview at https://croeso.toot.wales/en/less-clutter-more-cwtch/

    read more

  • Thanks! Good to know.
    @ivan @maikel

    read more

  • @osma@mas.to @maikel@vmst.io ​mastodon api are in development github.com/bonfire-networks/...

    read more

  • @maikel@vmst.io ​we use it as our individual and project presence

    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
    1 Posts
    7 Views
    Has anyone evaluated headless #activityPub servers? I'm thinking of something that could be used with Ghost subscriptions giving posting access to a site forum and blog comments. I suppose it doesn't have to be truly headless as long as there's some sort of authentication API.
  • 0 Votes
    5 Posts
    28 Views
    @thibaultmol @activitypub.blog I added the alt-text, thanks for the reminder!
  • 0 Votes
    1 Posts
    9 Views
    これ見るとあらためて mixi2 には 対応してほしいという気持ちになるな〜 あと #Bluesky という回答思ったより少なかったhttps://mstdn.guru/@keita99/115491723823364128#ActivityPub #Fediverse