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

Un server ActivityPub in un singolo file PHP?

Fediverso
1 1 14

Gli ultimi otto messaggi ricevuti dalla Federazione
  • @socialnetwork @fediverso sarò controcorrente ma a me Reddit piace 😅

    read more

  • ... und übrigens. und sind DAS Feature! Das funktioniert inzwischen super reibungslos und mich wundert, dass das noch nicht vollkommen explodiert ist. Was geht ab?

    read more

  • @mapto io non ho dubbi sul fatto che Blue Sky possa aver avuto grosse difficoltà nella moderazione, ma il paragone con il Fediverso non è possibile.
    Per quanto esista un evidente problema di centralizzazione anche qui nel Fediverso, come dimostra il caso di mastodon.social che oggi (è sottolineo oggi, perché in futuro Sono certo che quella percentuale diminuirà) cannibalizza il 70% delle nuove iscrizioni, la struttura stessa del Fediverso è fatta per accrescersi in maniera distribuita tra diversi server.

    Come ti potrebbe confermare @filippodb , l'istanza mastodon.uno con meno di 80.000 utenti dispone di più di un quarto dei moderatori che aveva BlueSky fino all'anno scorso (erano 50 e Bluesky ha dovuto raddoppiare questo numero solo negli ultimi mesi).

    Capisci adesso il motivo per cui sono così ottimista sulla moderazione all'interno del fediverso? Naturalmente esistono molte criticità, ma molte di queste si risolvono proprio Grazie all'architettura distribuita e, non dimentichiamocelo, al fatto che i gestori dei server non sono mai spinti da un interesse commerciale ma sono fortemente animati dall'intenzione di migliorare l'ambiente digitale.
    Questo è un aspetto importante perché sebbene questa sia tra le "Mission" dichiarate da Blue Sky È ovvio che l'obiettivo primario di quelle ecosistema sia la monetizzazione.

    read more

  • @mapto

    È una precisa legge che hai in mente? Di quale paese?

    In Italia, in base alla legge che ha accolto il GDPR, i minori sotto i 14 anni possono iscriversi a un social network solo con il consenso dei genitori. Tuttavia nessuna istanza del Fediverso è tecnicamente in grado di verificare se un genitore ha autorizzato il figlio. Il limite di età consigliato dal gdpr è comunque di 16 anni, e alcuni paesi europei hanno accolto quel limite. Proprio a novembre è stata approvata dal Parlamento Europeo una risoluzione che fissa irrevocabilmente a 16 anni l'età del consenso digitale e pertanto, anche se questa risoluzione deve essere ancora accolta da tutti i paesi membri, ti fa già capire qual è l'intendimento futuro. In Italia Inoltre si sta discutendo una legge per consentire l'accesso ai social network solo attraverso SPID o CIE...

    Considera infine che l'anonimato è un valore irrinunciabile per tutta la comunità del Fediverso e anonimato non va d'accordissimo con verifica dell'età... 😂
    Nelle mie istanze infatti ho stabilito questa "regola":

    Politica sull'età: il Fediverso è anonimo e noi non vogliamo sapere la tua età ma NON PUOI ISCRIVERTI A QUESTO SERVER SE NON HAI COMPIUTO I 16 ANNI e se a nostro insindacabile giudizio dimostri meno di 16 anni, sospenderemo il tuo account

    Che fondamentalmente si rifà al vecchio metodo del carabiniere di provincia che quando vedeva un ragazzino che guidava un motorino lo fermava solo se quel ragazzino guidava come un coglione... 😂

    read more

  • Per quello che è la mia esperienza

    Ci sta che abbiamo fatto esperienze diverse. Il mio punto era che qui non abbiamo avuto la pressione che riceve una rete d'impatto. Avevo questo esempio in mente:

    In its recently released moderation report for 2024, Bluesky said it grew by about 23 million users, jumping from 2.9 million users to nearly 26 million. And, its moderators received 17 times the number of user reports they got in 2023 — 6.48 million in 2024 compared to 358,000 the previous year.

    https://www.engadget.com/social-media/blueskys-2024-moderation-report-shows-how-quickly-harmful-content-grew-as-new-users-flocked-in-000149354.html

    read more

  • legalmente non possono esistere istanze aperte all'iscrizione di ragazzi sotto i 14 anni (anche se il limite è quasi sempre sotto i 16)

    È una precisa legge che hai in mente? Di quale paese?

    read more

  • @Neko0001 bonjour!

    read more

  • BONJOUR LE
    ❤️🧡💛💚💙💜❤️🧡💛💚💙💜

    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
    2 Posts
    21 Views
    @weekinfediverse also, @stegodon v1.2.3
  • [Read in full on NHAM]

    Fediverso fediverse nham
    1
    2
    0 Votes
    1 Posts
    6 Views
    [Read in full on NHAM]Goodbye @mixtape, Hello @nham!When the NHAM website launched, it was in fact an extension of a previous site dedicated to Sam’s fabulous NHAM Mixtapes, hence our somewhat awkward and misleading @mixtape handle on the fediverse. And until fairly recently, it wasn’t technically feasible to change the handle without potentially wreaking havoc… or so we thought!Our new fediverse handle is @nham, and while we thought we’d be able to change handle and port our followers over, sadly that has not been the case.So we now need you to follow our new handle!And if you haven’t yet followed us on fedi, this is the perfect time to do so!Goodbye @mixtape. We will miss you. Or not.#Fediverse #NHAM
  • 0 Votes
    1 Posts
    12 Views
    实例(ControlNet Social Space; 简称CSS)搭建的告一段落了,稍微总结一下:1. 选型阶段(#ActivityPub 生态对比)先稍微 review 一下现在已有的 #fediverse 平台,选择以 ActivityPub 作为协议的平台,毕竟联邦的话还是得尽可能有更多人用才行。类似于用于实时通讯的 matrix。然后评估了 #Mastodon / #Pixelfed / #Pleroma / #Misskey / #Sharkey 等,确认不同实现可互联互通(Pixelfed ↔ Mastodon 等)。然后偶然得知 #Threads 也是Fediverse中的一员。然后,研究“主域 abc.xy 显示身份、实例跑在 social.abc.xy”的可行性。结论是这样不靠谱,所以放弃了。。最终决定考虑到Sharkey比起Misskey有一些不错的feature就选了Sharkey。2. 部署与运行按官方文档与 docker compose 在用 #Unraid 系统的 #NAS 上部署 Sharkey。邮件服务器使用free-tier的#Resend 。然后还稍微折腾了一下如何设置管理员。3. 联邦互动与内容获取学会了站内搜索关注远端用户(用 @user@domain 或贴对方资料页 URL 解析)。然后是关注 Threads 用户的实操(前提对方开联邦)。但是这时候实例里没有什么联合,时间线完全没东西,就考虑有没有订阅别人一整个时间线的方法,好像不太可行。4. 存储与图片体积了解到 Misskey/系每用户默认 100 MB 网盘,附件都会落地到服务器(非纯外链)。而且没办法通过引用外链来渲染图片。试了一下本地上传+压缩,发现会自动压缩到webp,勉强还行。6. 二步验证(2FA)故障 & 解决刚才开启 2FA 后出现“authentication failed”,连恢复码也无效,日志报:Endpoint: i/change-password ... {"message":"authentication failed", ...}尝试各种排查均失效,最后只能直接改数据库里的,把 2FA 关掉,然后再重新绑定 2FA和passkey。7. 默认不显示在线状态发现这个需要在用户设置里修改,并且没找到如何让用户默认就是显示的,只能先放弃了。8. 注册与邀请码觉得发放多个一次性邀请码麻烦,想找可重复使用的邀请码。结果发现不行,只支持一次性的,感觉除非自己之后魔改一个web服务用于自动发放邀请码并且自动填写,不然想分享到别的群里,确实有点难度。也没有那种私人邀请的链接。TODO: 未来感觉还是有很多可以做的1. 能够自动探索别的实例的某些方法,找到一些有意思的用户去follow。2. 部署一个chat agent用于增强活跃度,但是又不能感觉像是纯骚扰,如何设计是个问题。3. 做一个方便remote follow的工具