Med-Mastodon

0 posts0 participants0 posts today

洪民憙 (Hong Minhee)Fedify 1.6 <a href="https://hackers.pub/@hongminhee/2025/fedify-1-6" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://hackers.pub/@hongminhee/2025/fedify-1-6</a>

Fedify: an ActivityPub server frameworkWe're excited to announce the release of <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/Fedify" target="_blank">#Fedify</a> 1.6.1, which marks the beginning of the 1.6 series following the retraction of version 1.6.0. This release introduces significant new capabilities that expand Fedify's deployment options and enhance security compatibility across the <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/fediverse" target="_blank">#fediverse</a>.🌐 Cloudflare Workers supportFedify 1.6 introduces first-class support for <a href="https://workers.cloudflare.com/" rel="nofollow noopener noreferrer" target="_blank">Cloudflare Workers</a>, enabling <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/serverless" target="_blank">#serverless</a> deployment of <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/ActivityPub" target="_blank">#ActivityPub</a> applications at the edge.New components<ul> <li><a href="https://fedify.dev/manual/kv#workerskvstore-cloudflare-workers-only" rel="nofollow noopener noreferrer" target="_blank"><code>WorkersKvStore</code></a>: A key–value store implementation using <a href="https://developers.cloudflare.com/kv/" rel="nofollow noopener noreferrer" target="_blank">Cloudflare's KV API</a> for persistent storage in Workers environments</li><li><a href="https://fedify.dev/manual/mq#workersmessagequeue-cloudflare-workers-only" rel="nofollow noopener noreferrer" target="_blank"><code>WorkersMessageQueue</code></a>: A message queue implementation leveraging <a href="https://developers.cloudflare.com/queues/" rel="nofollow noopener noreferrer" target="_blank">Cloudflare Queues</a> for reliable message processing</li> </ul>Key features<ul> <li>Seamless integration with <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/Cloudflare" target="_blank">#Cloudflare</a>'s serverless runtime</li><li>Automatic handling of queue message processing through Workers' <code>queue()</code> method</li><li>Support for <a href="https://developers.cloudflare.com/workers/runtime-apis/nodejs/" rel="nofollow noopener noreferrer" target="_blank">Node.js compatibility flag</a> required for Fedify's cryptographic operations</li><li>Manual queue processing via <code>Federation.processQueuedTask()</code> method</li> </ul>For a complete working example, see the <a href="https://github.com/fedify-dev/fedify/tree/1.6-maintenance/examples/cloudflare-workers" rel="nofollow noopener noreferrer" target="_blank">Cloudflare Workers example</a> in the Fedify repository.🏗️ Federation builder patternFedify 1.6 introduces the <code>FederationBuilder</code> class and <code>createFederationBuilder()</code> function to support <a href="https://fedify.dev/manual/federation#builder-pattern-for-structuring" rel="nofollow noopener noreferrer" target="_blank">deferred federation instantiation</a>. This pattern provides several benefits:<ul> <li>Deferred instantiation: Set up dispatchers and listeners before creating the federation object</li><li>Better code organization: Avoid circular dependencies and improve project structure</li><li>Cloudflare <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/Workers" target="_blank">#Workers</a> compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals</li><li>Modular setup: Build complex federations piece by piece before instantiation</li> </ul>The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.🔐 HTTP Message Signatures (RFC 9421)Fedify 1.6 implements the official <a href="https://www.rfc-editor.org/rfc/rfc9421" rel="nofollow noopener noreferrer" target="_blank">HTTP Message Signatures standard (RFC 9421)</a> specification, the final revision of the HTTP Signatures specification.Double-knocking mechanismTo ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:<ol> <li>Primary attempt: <a href="https://www.rfc-editor.org/rfc/rfc9421" rel="nofollow noopener noreferrer" target="_blank">RFC 9421</a> (HTTP Message Signatures) for modern implementations</li><li>Fallback: <a href="https://datatracker.ietf.org/doc/html/draft-cavage-http-signatures-12" rel="nofollow noopener noreferrer" target="_blank">Draft cavage version</a> for legacy compatibility</li><li>Adaptive caching: The system remembers which version each server supports to optimize future requests</li> </ol>This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.Interoperability testingThe RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:<ul> <li>Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures</li><li>Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to <a href="https://github.com/mastodon/mastodon/pull/34814" rel="nofollow noopener noreferrer" target="_blank">Mastodon PR #34814</a>, though Mastodon 4.4.0 has not yet been released)</li> </ul>These tests confirm that other ActivityPub implementations can successfully verify RFC 9421 signatures generated by Fedify, ensuring proper federation as the ecosystem gradually adopts the official specification. While these implementations currently support verification of RFC 9421 signatures, they do not yet generate RFC 9421 signatures themselves—making Fedify one of the first ActivityPub implementations to support both generation and verification of the modern standard.🔍 WebFinger enhancementsDedicated WebFinger lookupThe new <a href="https://fedify.dev/manual/context#webfinger-lookups" rel="nofollow noopener noreferrer" target="_blank"><code>Context.lookupWebFinger()</code></a> method provides direct access to <a href="https://datatracker.ietf.org/doc/html/rfc7033" rel="nofollow noopener noreferrer" target="_blank">WebFinger</a> data, offering developers more granular control over account discovery and resource resolution beyond the higher-level <a href="https://fedify.dev/manual/context#looking-up-remote-objects" rel="nofollow noopener noreferrer" target="_blank"><code>Context.lookupObject()</code></a> method.🛠 Context API improvementsContext data replacementThe new <a href="https://fedify.dev/manual/context#replacing-the-context-data" rel="nofollow noopener noreferrer" target="_blank"><code>Context.clone()</code></a> method enables dynamic context data replacement, providing greater flexibility in request processing and data flow management. This is particularly useful for middleware implementations and complex request routing scenarios.🚀 Migration considerationsBackward compatibilityFedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.Node.js version requirementImportant: Fedify 1.6 requires Node.js 22.0.0 or later for Node.js environments. This change does not affect applications using Deno or Bun runtimes. If you're currently using Node.js, please ensure your environment meets this requirement before upgrading.New deployment optionsFor new deployments, consider leveraging Cloudflare Workers support for:<ul> <li>Global edge deployment with low latency</li><li>Serverless scaling and automatic resource management</li><li>Integration with Cloudflare's ecosystem of services</li> </ul>🎯 Looking forwardFedify 1.6 represents a significant expansion of deployment possibilities while maintaining the framework's commitment to broad compatibility across the fediverse. The addition of Cloudflare Workers support opens new architectural patterns for federated applications, while the RFC 9421 implementation ensures Fedify stays current with emerging ActivityPub security standards. For detailed migration guides, API documentation, and examples, please visit the <a href="https://fedify.dev/" rel="nofollow noopener noreferrer" target="_blank">Fedify documentation</a>. Join our community on <a href="https://matrix.to/#/#fedify:matrix.org" rel="nofollow noopener noreferrer" target="_blank">Matrix</a> or <a href="https://discord.gg/bhtwpzURwd" rel="nofollow noopener noreferrer" target="_blank">Discord</a> for support and discussions.<a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/fedidev" target="_blank">#fedidev</a> <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/RFC9421" target="_blank">#RFC9421</a> <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/HTTPSignatures" target="_blank">#HTTPSignatures</a> <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/HTTPMessageSignatures" target="_blank">#HTTPMessageSignatures</a> <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/CloudflareWorkers" target="_blank">#CloudflareWorkers</a>

RiussiAny C# developer want to contribute a C# example of how to do HTTP Signing to go along with our existing Java, JavaScript, Python and Go examples?<a href="https://docs.upvest.co/documentation/getting_started/http_signatures/implementing_http_signatures_samples" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://docs.upvest.co/documentation/getting_started/http_signatures/implementing_http_signatures_samples</a><a href="https://github.com/upvestco/http-signature-examples" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/upvestco/http-signature-examples</a><a href="https://hachyderm.io/tags/dotnet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dotnet</a> <a href="https://hachyderm.io/tags/csharp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#csharp</a> <a href="https://hachyderm.io/tags/http" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#http</a> <a href="https://hachyderm.io/tags/httpsignatures" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#httpsignatures</a>

洪民憙 (Hong Minhee) 🤏🏼This document, edited by <a href="https://fed.brid.gy/r/https://snarfed.org/" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@snarfed.org</a>, is really helpful for implementing <a href="https://todon.eu/tags/Fedify" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fedify</a> in practice.<a href="https://swicg.github.io/activitypub-http-signature/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://swicg.github.io/activitypub-http-signature/</a><a href="https://todon.eu/tags/fedidev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fedidev</a> <a href="https://todon.eu/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActivityPub</a> <a href="https://todon.eu/tags/httpsignatures" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#httpsignatures</a>

spla :fed: :vim:Si no ho he entés malament, si vols que un servidor <a href="https://mastodont.cat/tags/Mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mastodon</a> et faci cas quan li envies una activitat <a href="https://mastodont.cat/tags/Activitypub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Activitypub</a>, per exemple "Follow", et cal signar amb la clau privada del usuari emissor, xifrada amb el hash SHA256, l'activitat en format json que li envies. Si el servidor Mastodon receptor no rep la signatura vàlida en els "headers", no fa ni cas. <a href="https://mastodont.cat/tags/HTTPSignatures" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HTTPSignatures</a>

@reiver ⊼ (Charles) :batman:I hate this requirement of having to sign the HTTP request to see the Activity-JSON for ActivityPub actor.I hate it so much....It makes it so I cannot do a simple "curl" command to get an ActivityPub actor's activity-JSON.<a href="https://mastodon.social/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActivityPub</a> <a href="https://mastodon.social/tags/ActivityStreams" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActivityStreams</a> <a href="https://mastodon.social/tags/Fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fediverse</a> <a href="https://mastodon.social/tags/HTTPSignatures" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HTTPSignatures</a> <a href="https://mastodon.social/tags/Mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mastodon</a>

Kingsley Uyi Idehen<a href="https://mymath.rocks/endpoints/SYn3cl_N4HAPfPHgo2x37XunLEmhV9LnxCggcYwyec0" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@helge</a>,Is <a href="https://github.com/HelgeKrueger/bovine/blob/main/docs/client_to_server_activitypub.md#this" rel="nofollow noopener noreferrer" target="_blank">https://github.com/HelgeKrueger/bovine/blob/main/docs/client_to_server_activitypub.md#this</a> your Client built to work with a generic <a href="https://mastodon.social/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActivityPub</a> server? I am interested in clients that want to work with our backend. Note, <a href="https://mastodon.social/tags/DBMS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DBMS</a> and Authentication matters are none issues since our servers implement most of these protocols (including the likes of <a href="https://mastodon.social/tags/HTTPSignatures" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HTTPSignatures</a> etc). /cc <a href="https://social.gabekangas.com/users/gabek" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@gabek</a> <a href="https://flipboard.social/@mike" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mike</a> <a href="https://mastodon.social/@atomicpoet" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@atomicpoet</a> <a href="https://mastodon.social/@davew" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@davew</a> <a href="https://mastodon.social/@judell" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@judell</a> <a href="https://mastodon.social/@Mastodon" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Mastodon</a> <a href="https://social.coop/@smallcircles" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@smallcircles</a>

Raphael LuckomNotes so far on <a href="https://indieweb.social/tags/Mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mastodon</a>'s <a href="https://indieweb.social/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActivityPub</a> implementation, covering basics on <a href="https://indieweb.social/tags/WebFinger" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebFinger</a>, <a href="https://indieweb.social/tags/HTTPSignatures" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HTTPSignatures</a>, <a href="https://indieweb.social/tags/JSONLD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#JSONLD</a> signatures, and <a href="https://indieweb.social/tags/ActivityStream" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActivityStream</a> vocab. Pretty much a loosely-organized collection of links to useful specs and implementations for understanding how Mastodon specifically does things.<a href="https://raphaelluckom.com/posts/Things%20I%27ve%20learned%20about%20ActivityPub%20so%20far.html" rel="nofollow noopener noreferrer" target="_blank">https://raphaelluckom.com/posts/Things%20I%27ve%20learned%20about%20ActivityPub%20so%20far.html</a>

Recent searches

Search options

Administered by:

Server stats:

#httpsignatures