# Rfc 9421

**URL:** <https://discuss.write.as/t/rfc-9421/20843>\
**Category:** Feature requests\
**Created:** [August 17, 2026, 3:02am UTC](https://discuss.write.as/t/rfc-9421/20843 "2026-08-17T03:02:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![evanp](https://discuss.write.as/user_avatar/discuss.write.as/evanp/32/5982_2.png) [@evanp](https://discuss.write.as/u/evanp)\
**Post date:** [August 17, 2026, 3:02am UTC](https://discuss.write.as/t/rfc-9421/20843/1 "2026-08-17T03:02:53Z")

</div>

The Fediverse runs on an old draft version of the HTTP Message Signatures standard. We’re trying to upgrade to use the released version, RFC 9421. It would be great if Write Freely was part of this process! It means doing at least these things:

- Accept RFC 9421 signatures for GET requests (object, actor, collection)
- Accept RFC 9421 signatures for POST requests (inbox, sharedInbox)
- Send RFC 9421 signatures for GET requests
- Send RFC 9421 signatures for POST requests

This is a Fediverse interoperability effort; it will have only a small effect on user-visible features.

---

<div class="post-metadata">

**Author:** ![evanp](https://discuss.write.as/user_avatar/discuss.write.as/evanp/32/5982_2.png) [@evanp](https://discuss.write.as/u/evanp)\
**Post date:** [August 17, 2026, 3:04am UTC](https://discuss.write.as/t/rfc-9421/20843/2 "2026-08-17T03:04:47Z")

</div>

There’s a compatibility matrix here:

> **[RFC 9421 Adoption](https://swicg.github.io/activitypub-http-signature/RFC9421)**
>
> Repository for a SocialCG report on how HTTP Signature is used with ActivityPub