ordered 2000 stickers (4cm*1.6cm) with this motif because why not
Remote
polyproto federation protocol
@polyproto@fed.amazonawaws.com
iceshrimp.net 2026.1.2-beta+5d980642fb
A refreshingly simple, decentralised, federated protocol. No more losing friends, followers or messages if your old homeserver sunsets. Feel free to migrate to another homeserver at any time, even if your old homeserver has shut down ages ago.
Posting here:
🫶
A refreshingly simple, decentralised, federated protocol. No more losing friends, followers or messages if your old homeserver sunsets. Feel free to migrate to another homeserver at any time, even if your old homeserver has shut down ages ago.🏳️⚧️ Trans rights are human rights. Be gay, do crime!Posting here:
-ava: @star@fed.amazonawaws.com
0 Followers
0 Following
17 Posts
Core Specification:
Webbed Site:
Community Forum:
We have our own 88x31 now, too! It's not the most beautiful one out there, but I did make it myself! Embed it wherever you want :)
Link to image
Link to image
yuri
Sorely missing update post for what has been done since April 2nd:
- Labels have been revamped for PRs and Issues on our repos. I felt they were much too hard to visually distinguish at a glance. The new system solves this 
- Add a page on our website describing PAWs, as per one of our last posts on this account
- Merged PURR-2026-0006: Namespacing Guidelines, a set of guidelines for naming polyproto extensions in collision-resistant ways, by @alexia@shrimp.starlightnet.work
- Opened PURR-2026-0008: Capabilities, describing optional extensions and how client and server negotiate a set of common features automatically (such as a chat server not also offering voicechats)
- Made substantial progress on PURR-2026-0001: OIDC+SCIM in polyproto, describing a concrete flow for how to register a polyproto actor through an OIDC+SCIM IdP (with diagrams)
- Progressed further in PURR-2026-0001 by researching how to best replace the concept of a "Sensitive Solution" we previously introduced with OIDC/OAuth2 mechanics. Sensitive Solutions are basically just a "confirm this action with your password" for certain actions requiring elevated trust
- Created a repository for "altmaid", a tool to automatically parse mermaid diagrams in markdown documents and auto-generate accurate, descriptive and helpful alt text for them
As you can see, lots and lots of work has been done, and the month isn't even over yet, and the list isn't even exhaustive! 
- Labels have been revamped for PRs and Issues on our repos. I felt they were much too hard to visually distinguish at a glance. The new system solves this
- Add a page on our website describing PAWs, as per one of our last posts on this account
- Merged PURR-2026-0006: Namespacing Guidelines, a set of guidelines for naming polyproto extensions in collision-resistant ways, by @alexia@shrimp.starlightnet.work
- Opened PURR-2026-0008: Capabilities, describing optional extensions and how client and server negotiate a set of common features automatically (such as a chat server not also offering voicechats)
- Made substantial progress on PURR-2026-0001: OIDC+SCIM in polyproto, describing a concrete flow for how to register a polyproto actor through an OIDC+SCIM IdP (with diagrams)
- Progressed further in PURR-2026-0001 by researching how to best replace the concept of a "Sensitive Solution" we previously introduced with OIDC/OAuth2 mechanics. Sensitive Solutions are basically just a "confirm this action with your password" for certain actions requiring elevated trust
- Created a repository for "altmaid", a tool to automatically parse mermaid diagrams in markdown documents and auto-generate accurate, descriptive and helpful alt text for them
As you can see, lots and lots of work has been done, and the month isn't even over yet, and the list isn't even exhaustive!
It took 3 months, but the first major parts for OIDC in polyproto have landed: codeberg.org/polyphony/polyproto-dot-org/pulls/104
ballin'
Over the last 24h, a lot of additions have landed in the PURR for OIDC+SCIM in polyproto, with each commit bringing us closer to unblocking work on all home server parts which require user authentication—which, as you might have guessed—that's a lot of parts! :neodog_book_owo:
While OIDC essentially makes sure that we aren't rolling our own auth solution, making things like passkey support, 2FA and permission scoping super easy, SCIM allows for polycu- uh, I mean organizations cough to automatically provision polyproto identities for critters!
To explain why SCIM is cool: imagine being invited to your polycul-organizations' self-hosted services network, and immediately having just one account and sign-in with which you can use their @agzentv676w2y3gx@fed.amazonawaws.com instance, the shared media library, music server and fedi instance, without having to do anything extra! :neocat_flag_polyam:
While OIDC essentially makes sure that we aren't rolling our own auth solution, making things like passkey support, 2FA and permission scoping super easy, SCIM allows for polycu- uh, I mean organizations cough to automatically provision polyproto identities for critters!
To explain why SCIM is cool: imagine being invited to your polycul-organizations' self-hosted services network, and immediately having just one account and sign-in with which you can use their @agzentv676w2y3gx@fed.amazonawaws.com instance, the shared media library, music server and fedi instance, without having to do anything extra! :neocat_flag_polyam:
Replying to
@hsza@social.tudbut.de @algernon@come-from.mad-scientist.club Why are we being mentioned? What's the request here?
Replying to
ready.chair6.net/?url=https://polyproto.org thingimajig says so :neobot_fingerguns:
polyproto-rs currently has 325 tests. Who ( 
←) would do something like this 
In preparation of this working group, we'd really looooooove to hear your thoughts, wishes, fears and general knowledge that you'd like to share with us, regarding the working group and the chat protocol itself. write.polyproto.org/aolvLTdsS7GzEOHtoVU04g?both
RE: fed.amazonawaws.com/notes/ao3fi60n8fbhjgpn
polyproto-chat working group! just 2 days away! it got here so fast!!
"How to outlive your home server: The polyproto federation protocol" can now be streamed from here, for those interested: media.ccc.de/v/ds26-627-how-to-outlive-your-home-server-the-polyproto-federation-protocol