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

It gets tiring to write Piefed/Lemmy/Mbin to call our part of the Fediverse, is Threadiverse now the accepted term?

Fediverso
37 19 488

Gli ultimi otto messaggi ricevuti dalla Federazione
  • @Ali_per_Viaggiare

    Purtroppo non è semplice sostituire YouTube per chi questo canale rappresenta una fonte di reddito irrinunciabile (ma lo stesso vale per qualunque altra piattaforma).

    La mercificazione dei contenuti, per cui il creatore è incoraggiato economicamente a postare contenuti "richiesti" o "di successo" funziona, altrimenti non ci avrebbero tirato su piattaforme di ogni tipo.

    I contenuti dei content creator professionisti sono video di buona qualità, perché "professione" è una cosa seria, non si gioca con il reddito imponibile. Ma se non c'è domanda non c'è nemmeno offerta. E nessuno domanda su Peertube: anche solo la piattaforma galleggia sulle donazioni private. Mentre su YouTube è la piattaforma che paga, e pertanto ha più capacità della somma dei content creator che ospita.

    Nessuno acquisterebbe attrezzature, spenderebbe tempo nell'editing o nei testi perfetti per farlo senza un ritorno, con alcune notevoli eccezioni, ovviamente, come per tutto: c'è chi ama fare qualcosa di utile e divertente e lo vive come un hobby, e c'è chi ama semplicemente potersi esprimere liberamente.

    Vi immaginate il paradosso di un produttore che guadagna più denaro della piattaforma che lo hosta? Non è sostenibile, non credete?

    Certo ci sono anche le piattaforme di fidelizzazione individuale, come Patreon o Onlyfans, che però paiono funzionare bene solo con particolari e casi d'uso o poche selezionate eccezioni alla regola. E non credo che con Activitypub si possa implementare nativamente una ACL così articolata e granulare come richiesto da questo tipo di piattaforme.

    Penso che su Peertube non si potrà mai pensare di superare la soglia dell'amatoriale, che spesso va più che bene, eh, a meno che qualcuno, dai semi-pro in su, non decida di usarla come piattaforma *pro-bono* secondaria.

    Alla fine la domanda da rispondere è sempre la stessa: quale è il modello di business che rende praticabile e sostenibile questo modello di interazioni sociali? Ricordiamoci che l'unico modello "in perdita" ammesso è quello hobbistico-amatoriale.

    @deedend @filippodb @peertube @morrolinux @fediverso @anaru_sensei

    read more

  • read more

  • @storiespettinate @artematiko ahahahah bravissima! Io sono stata sconfitta proprio dalle musiche diffuse nel centro storico di Viterbo! Tra vasche per acquisti regali, semplice passeggio e presidio per la Palestina, non potevo non cadere. Ci riprovo l'anno prossimo!

    read more

  • ascolta: ho superato il Whamageddon! E l'ho fatto sprezzante del pericolo: centri commerciali, bar, mercatini natalizi e due fiere di Natale. Anche le musiche natalizie di Viterbo, ma lì mi ha salvata @artematiko ❣️ E due inviti a cena con gli amici che hanno bonificato le playlist.

    E da questo traggo un insegnamento:
    non importa quanto sia scemo il tuo obiettivo, chi ti vuole bene ti sostiene anche nelle scemità.

    Vi auguro amici così.

    read more

  • @GillesLeCorre2 bonne journée !

    read more

  • Salut et adelphité de la et du

    Je vous souhaite un doux réveil et un heureux 25, que vous ayez fêté le 24 ou non.
    Ce matin ici il pleut, je doutes qu'on aille monter la T. comme prévu s'il avait neigé.
    Ce matin nous avons découvert au petit déjeuner les livres que nous nous sommes offerts pour notre petit Noël. Pas de surprises mais ça va nous faire notre journée de tout façon.

    Aimez vous !
    🤗 ✊ 🥰 🤗 ✊ 🥰 🤗 ✊ 🥰

    read more

  • @Gina Merry Christmas to you, too, Gina.

    read more

  • @Gina Merry Christmas to you as well!

    read more
Post suggeriti
  • 0 Votes
    1 Posts
    0 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
    5 Views
    Should posts with images without alt text be excluded from Trending Posts?#Polls #AskFedi #Mastodon #PixelFed #Fediverse #Trending #Images #Photos #NoAltText #Survey #Poll
  • 0 Votes
    1 Posts
    7 Views
    Website LeagueAn island network using Fediverse technologies in allowlist-only mode.#SocialNetwork #SocialNetworking #Fediverse #ActivityPub
  • 0 Votes
    1 Posts
    13 Views
    What do you do when you've found a PeerTube video and you want to like or reply to a comment without having to create a PeerTube account on every instance? Activity Pub makes this easy from a number of popular federated services. Written Version: https://fedihost.co/blog/slug/how-do-i-comment-on-peertube Get A PeerTube Instance: https://fedihost.co/hosting/peertube