MIfoodie (@MIfoodie@social.vivaldi.net)
i absolutely hate how #mastodon / #activitypub / #fediverse users are treated like second class citizens. like every once in a while (twice a month if lucky) @ wikipedia@wikis.world posts something but peeking at their official bluesky account they are super active with many posts in the last 24 hours.
whyyyyyy
Show Original Post
smallcircles (@smallcircles@social.coop)
#SocialHub community forum has the #ActivityPub plugin enabled yet 1st with full open, untweaked federation settings. Accessiblity for any #fedizen got a real boost. Yet with big negative impact on 'sense of community'. It's up for debate whether adding #fediverse support in early stages of dev was a wise move. And whether the result is net negative or positive (I think the former).
Any fedi dev: Think hard what it means to be federated. It's more than just 'plugging in'. Consider the #SX side.
Show Original Post
smallcircles (@smallcircles@social.coop)
"Mastodon better than expected.." on HN
https://news.ycombinator.com/item?id=46376652
Show Original Post
novaTopFlex (@novaTopFlex@mastodon.social)
Does anyone else believe #Amherst and #Northampton (MA) feel like the #ActivityPub and the #Fediverse platforms?
Show Original Post
TheVoidTLMB (@TheVoidTLMB@social.vivaldi.net)
And... my last Mastodon archive is now imported into my #Wordpress via #ActivityPub. (Thx #Dreamhost support for help!) Phew! 🙂
Show Original Post
display (@display@my-place.social)
Salut le #Fédivers et la #Fédiverse !
Mon instance #Friendica ferme dans 1 semaine et je cherche 1 endroit fiable d'où publier mon actu musicale.
Dans l'idéal
- compatible avec tout les réseaux #ActivityPub et #Diaspora
- durable dans le temps
- pas limité aux 500 signes du microblogging (pas #mastodon donc)
Une suggestion ?
Show Original Post
objects (@objects@epiktistes.com)
I rolled out a lot of features over the last several weeks and created a lot of bugs in the process. Release v3.2.5 of Ktistec is mostly about fixing those bugs. I did implement two requested features, however: support for editing posts in Markdown and support for Open Graph metadata. Here's the full list of new features:
Added
- Support for editing posts in Markdown. (fixes #25)
- Support for Open Graph metadata on actors and objects. (fixes #71)
- Support for uploading a site image.
- Internal table of contents page.
- Poll expiry notifications.
🎄 I'm working on support for poll creation and management now. It's also time for a performance improvement pass or two.
#ktistec #crystallang #activitypub #fediverse
Show Original Post
post (@post@lemmy.ml)
Fedify 1.10.0: Observability foundations for the future debug dashboard
https://lemmy.ml/post/40746886
Show Original Post
post (@post@lemmy.ml)
Fedify 1.10.0: Observability foundations for the future debug dashboard
https://lemmy.ml/post/40746885
Show Original Post
fedify (@fedify@hollo.social)
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.receivedevent onactivitypub.inboxspan — records the full activity JSON, verification status (activity verified, HTTP signatures verified, Linked Data signatures verified), and actor informationactivitypub.activity.sentevent onactivitypub.send_activityspan — records the full activity JSON and target inbox URLactivitypub.object.fetchedevent onactivitypub.lookup_objectspan — records the fetched object's type and complete JSON-LD representation
Additionally, Fedify now instruments previously uncovered operations:
activitypub.fetch_documentspan for document loader operations, tracking URL fetching, HTTP redirects, and final document URLsactivitypub.verify_key_ownershipspan 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 prefixSqliteKvStore— usesLIKEquery with JSON key patternPostgresKvStore— uses array slice comparisonRedisKvStore— usesSCANwith pattern matching and key deserializationDenoKvStore— delegates to Deno KV's built-inlist()APIWorkersKvStore— uses Cloudflare Workers KVlist()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), 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) 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.
Show Original Post
ishii00141 (@ishii00141@mastodon.social)
RE: https://ishii00141.stars.ne.jp/20251224-0707-4873/
#WordPress の #プラグイン #ActivityPub に新たなバグ。
記事中のハッシュタグを拾う際に、WordPressのタグのIDで拾っているのか、記事中に#27～とか#30～とかあると、ID=27やID=30のタグをハッシュタグと認識して拾ってしまう。「～」の部分に条件があるのは分からないけれど、私が試したケースでは「～」は「ae60;」だった。
Show Original Post
20251224-0707-4873 (@20251224-0707-4873@ishii00141.stars.ne.jp)
特定のタグが勝手に付けられるバグが再現されるかテスト？
#ActivityPub #WordPress #テスト #ハッシュタグ #バグ #仕様
テスト１：新規投稿で任意の６個のタグを付けてみる。
テスト１の結果：タグの数は関係なさそう。
https://ishii00141.stars.ne.jp/20251224-0707-4873/Show Original Post