Feed of "polyphony/polyproto-dot-org" https://codeberg.org/polyphony/polyproto-dot-org A dedicated website housing the polyproto specifications and everything polyproto related. Wed, 15 Apr 2026 03:01:54 +0200 cyrneko commented on issue polyphony/polyproto-dot-org#167 https://codeberg.org/polyphony/polyproto-dot-org/issues/167#issuecomment-13153194 Some kind of PURR-index <p dir="auto">hm, I think that&#39;s decent although I feel that &#34;PURR/Idea&#34; should be reserved to issues, and perhaps be in a separate section of the final site. Y&#39;know, to separate &#34;ideas someone had&#34; from &#34;things that are being worked on&#34;</p> hm, I think that's decent although I feel that "PURR/Idea" should be reserved to issues, and perhaps be in a separate section of the final site. Y'know, to separate "ideas someone had" from "things that are being worked on"

]]> cyrneko 123229869: https://codeberg.org/polyphony/polyproto-dot-org/issues/167#issuecomment-13153194 Wed, 15 Apr 2026 01:23:56 +0200 ava commented on issue polyphony/polyproto-dot-org#167 https://codeberg.org/polyphony/polyproto-dot-org/issues/167#issuecomment-13131963 Some kind of PURR-index <p dir="auto">Regarding clarifying the status of a PURR, I suggest we refactor the &#34;Type&#34; label in this repository:</p> Regarding clarifying the status of a PURR, I suggest we refactor the "Type" label in this repository:

]]> ava 123066045: https://codeberg.org/polyphony/polyproto-dot-org/issues/167#issuecomment-13131963 Tue, 14 Apr 2026 18:04:55 +0200 cyrneko commented on pull request polyphony/polyproto-dot-org#166 https://codeberg.org/polyphony/polyproto-dot-org/pulls/166#issuecomment-13131516 WIP: PURR-2026-0008: Capabilities <p dir="auto">Well, that is what the &#34;Motivation&#34; section is for.</p> Well, that is what the "Motivation" section is for.

]]> cyrneko 123059904: https://codeberg.org/polyphony/polyproto-dot-org/pulls/166#issuecomment-13131516 Tue, 14 Apr 2026 17:52:26 +0200 cyrneko commented on issue polyphony/polyproto-dot-org#167 https://codeberg.org/polyphony/polyproto-dot-org/issues/167#issuecomment-13131513 Some kind of PURR-index <p dir="auto">Oh right! that&#39;d be a great starting point I bet</p> Oh right! that'd be a great starting point I bet

]]> cyrneko 123059754: https://codeberg.org/polyphony/polyproto-dot-org/issues/167#issuecomment-13131513 Tue, 14 Apr 2026 17:51:44 +0200 ava commented on issue polyphony/polyproto-dot-org#167 https://codeberg.org/polyphony/polyproto-dot-org/issues/167#issuecomment-13122825 Some kind of PURR-index <p dir="auto">Just as an idea, but maybe we can clone and edit our &#34;Good First Issues&#34; project and deploy it to act as a website listing all the PURRs?</p> Just as an idea, but maybe we can clone and edit our "Good First Issues" project and deploy it to act as a website listing all the PURRs?

]]> ava 122919681: https://codeberg.org/polyphony/polyproto-dot-org/issues/167#issuecomment-13122825 Tue, 14 Apr 2026 11:45:37 +0200 ava commented on pull request polyphony/polyproto-dot-org#166 https://codeberg.org/polyphony/polyproto-dot-org/pulls/166#issuecomment-13122807 WIP: PURR-2026-0008: Capabilities <p dir="auto">As a sort of very direct question that should likely be answered in the PR body itself: Why would we need this?</p> As a sort of very direct question that should likely be answered in the PR body itself: Why would we need this?

]]> ava 122918793: https://codeberg.org/polyphony/polyproto-dot-org/pulls/166#issuecomment-13122807 Tue, 14 Apr 2026 11:44:00 +0200 cyrneko opened issue polyphony/polyproto-dot-org#167 https://codeberg.org/polyphony/polyproto-dot-org/issues/167 167#Some kind of PURR-index# Two issues with PURRs as of right now:

  • It's tideous to find what the latest PURR is
  • It's a bit confusing to find the state of a PURR at a glance

So, perhaps, we should have a kind of index that gives us these two pieces of information directly :)

One, what the latest PURR number is so that you can open a PR and just +1, and also just a list of PURRs and their status (we would probably need a label or two for this, or perhaps just display labels verbatim)

I know some of this can be done with Forgejo's built-in UI, but it makes sharing and working together easier IMO

]]> cyrneko 122777184: https://codeberg.org/polyphony/polyproto-dot-org/issues/167 Tue, 14 Apr 2026 01:42:12 +0200 cyrneko created pull request polyphony/polyproto-dot-org#166 https://codeberg.org/polyphony/polyproto-dot-org/pulls/166 166#WIP: PURR-2026-0008: Capabilities# This PR introduces Capabilities to polyproto, a system that intends to define how two implementations can negotiate their capabilities and act accordingly

Motivation

While APIs are versioned, and we could expose supported endpoints or extensions using a .well-known endpoint, that doesn't cover nearly as many cases as a capabilities system does, like:

  • Adjusting to scenarios based on API availability bidirectionally
  • Communicating support for features outside of p2 (i.e the availability of a Livekit SFU or a Tor Onion)
  • Could be used client-to-client, which is useful for p2p applications
  • More complex compatibility flows, like a hypothetical p2-chat that supports integration with p2-voice for voice+text channels, that can be expressed in a Capability/CAP

Other notes

This is heavily inspired by IRC's CAP system, and things like SSH kex/cipher-discovery.

API routes are to come soon™!

Please use this PR to discuss as I work on this PURR :)

]]> cyrneko 122776698: https://codeberg.org/polyphony/polyproto-dot-org/pulls/166 Tue, 14 Apr 2026 01:37:35 +0200 cyrneko pushed to cyrneko/p2-core-capabilities at polyphony/polyproto-dot-org https://codeberg.org/polyphony/polyproto-dot-org/commit/55c4a097f1d22d33012d4088cc02538918159df6 <a href="https://codeberg.org/polyphony/polyproto-dot-org/commit/55c4a097f1d22d33012d4088cc02538918159df6">55c4a097f1d22d33012d4088cc02538918159df6</a> caps: define general negotiation flow 55c4a097f1d22d33012d4088cc02538918159df6 caps: define general negotiation flow]]> cyrneko 122773500: https://codeberg.org/polyphony/polyproto-dot-org/commit/55c4a097f1d22d33012d4088cc02538918159df6 Tue, 14 Apr 2026 01:25:13 +0200 cyrneko pushed to cyrneko/p2-core-capabilities at polyphony/polyproto-dot-org https://codeberg.org/polyphony/polyproto-dot-org/commit/0f0558849d562ffc1ef228ea894c7500a5e35d80 <a href="https://codeberg.org/polyphony/polyproto-dot-org/commit/0f0558849d562ffc1ef228ea894c7500a5e35d80">0f0558849d562ffc1ef228ea894c7500a5e35d80</a> feat: First draft for Capabilities 0f0558849d562ffc1ef228ea894c7500a5e35d80 feat: First draft for Capabilities]]> cyrneko 122771760: https://codeberg.org/polyphony/polyproto-dot-org/commit/0f0558849d562ffc1ef228ea894c7500a5e35d80 Tue, 14 Apr 2026 01:15:26 +0200 cyrneko created branch cyrneko/p2-core-capabilities in polyphony/polyproto-dot-org https://codeberg.org/polyphony/polyproto-dot-org/src/branch/cyrneko/p2-core-capabilities cyrneko 122771736: https://codeberg.org/polyphony/polyproto-dot-org/src/branch/cyrneko/p2-core-capabilities Tue, 14 Apr 2026 01:15:26 +0200 ava deleted branch flori/document-paws from polyphony/polyproto-dot-org https://codeberg.org/polyphony/polyproto-dot-org ava 122699688: https://codeberg.org/polyphony/polyproto-dot-org Mon, 13 Apr 2026 21:35:16 +0200 ava merged pull request polyphony/polyproto-dot-org#165 https://codeberg.org/polyphony/polyproto-dot-org/pulls/165 Describe how PAWs work, and how they should be used ava 122699643: https://codeberg.org/polyphony/polyproto-dot-org/pulls/165 Mon, 13 Apr 2026 21:35:14 +0200 ava pushed to main at polyphony/polyproto-dot-org https://codeberg.org/polyphony/polyproto-dot-org/compare/cc1f03db1760ca73aa512163a43b998f3d67f6b1...466faae2859a2002fe45d81dcb22331e03b0052b <a href="https://codeberg.org/polyphony/polyproto-dot-org/commit/466faae2859a2002fe45d81dcb22331e03b0052b">466faae2859a2002fe45d81dcb22331e03b0052b</a> Merge pull request &#39;Describe how PAWs work, and how they should be used&#39; (#165) from flori/document-paws into main <a href="https://codeberg.org/polyphony/polyproto-dot-org/commit/0f8e4653b5f4cae8c2d55b1fbaf5100347f76897">0f8e4653b5f4cae8c2d55b1fbaf5100347f76897</a> feat: describe how PAWs work 466faae2859a2002fe45d81dcb22331e03b0052b Merge pull request 'Describe how PAWs work, and how they should be used' (#165) from flori/document-paws into main 0f8e4653b5f4cae8c2d55b1fbaf5100347f76897 feat: describe how PAWs work]]> ava 122699637: https://codeberg.org/polyphony/polyproto-dot-org/compare/cc1f03db1760ca73aa512163a43b998f3d67f6b1...466faae2859a2002fe45d81dcb22331e03b0052b Mon, 13 Apr 2026 21:35:14 +0200 ava commented on pull request polyphony/polyproto-dot-org#165 https://codeberg.org/polyphony/polyproto-dot-org/pulls/165#issuecomment-13085661 Describe how PAWs work, and how they should be used <p dir="auto">Thank you for your reviewwwww! :))</p> Thank you for your reviewwwww! :))

]]> ava 122699577: https://codeberg.org/polyphony/polyproto-dot-org/pulls/165#issuecomment-13085661 Mon, 13 Apr 2026 21:35:05 +0200 cyrneko approved polyphony/polyproto-dot-org#165 https://codeberg.org/polyphony/polyproto-dot-org/pulls/165#issuecomment-13085547 Describe how PAWs work, and how they should be used cyrneko 122696994: https://codeberg.org/polyphony/polyproto-dot-org/pulls/165#issuecomment-13085547 Mon, 13 Apr 2026 21:27:43 +0200 cyrneko commented on pull request polyphony/polyproto-dot-org#165 https://codeberg.org/polyphony/polyproto-dot-org/pulls/165#issuecomment-13085544 Describe how PAWs work, and how they should be used <p dir="auto">btw, this new change is good! :D</p> btw, this new change is good! :D

]]> cyrneko 122696964: https://codeberg.org/polyphony/polyproto-dot-org/pulls/165#issuecomment-13085544 Mon, 13 Apr 2026 21:27:41 +0200 cyrneko commented on pull request polyphony/polyproto-dot-org#165 https://codeberg.org/polyphony/polyproto-dot-org/pulls/165#issuecomment-13085487 Describe how PAWs work, and how they should be used <p dir="auto">Someone was working on it, by which I mean they slopped it...Got closed now for obvious reasons</p> Someone was working on it, by which I mean they slopped it...Got closed now for obvious reasons

]]> cyrneko 122695989: https://codeberg.org/polyphony/polyproto-dot-org/pulls/165#issuecomment-13085487 Mon, 13 Apr 2026 21:25:14 +0200 cyrneko commented on pull request polyphony/polyproto-dot-org#165 https://codeberg.org/polyphony/polyproto-dot-org/pulls/165#issuecomment-13085433 Describe how PAWs work, and how they should be used <p dir="auto">Yeah sub-issues are a rare github W....I should check whether there is an open issue for Forgejo</p> Yeah sub-issues are a rare github W....I should check whether there is an open issue for Forgejo

]]> cyrneko 122695530: https://codeberg.org/polyphony/polyproto-dot-org/pulls/165#issuecomment-13085433 Mon, 13 Apr 2026 21:23:01 +0200 ava commented on issue polyphony/polyproto-dot-org#54 https://codeberg.org/polyphony/polyproto-dot-org/issues/54#issuecomment-13084704 Homeserver key rotation: does it invalidate all id-certs signed by this one? <p dir="auto">Ah, I think I understand a bit better now</p> Ah, I think I understand a bit better now

]]> ava 122692605: https://codeberg.org/polyphony/polyproto-dot-org/issues/54#issuecomment-13084704 Mon, 13 Apr 2026 21:11:22 +0200 ava pushed to flori/document-paws at polyphony/polyproto-dot-org https://codeberg.org/polyphony/polyproto-dot-org/commit/0f8e4653b5f4cae8c2d55b1fbaf5100347f76897 <a href="https://codeberg.org/polyphony/polyproto-dot-org/commit/0f8e4653b5f4cae8c2d55b1fbaf5100347f76897">0f8e4653b5f4cae8c2d55b1fbaf5100347f76897</a> feat: describe how PAWs work 0f8e4653b5f4cae8c2d55b1fbaf5100347f76897 feat: describe how PAWs work]]> ava 122689752: https://codeberg.org/polyphony/polyproto-dot-org/commit/0f8e4653b5f4cae8c2d55b1fbaf5100347f76897 Mon, 13 Apr 2026 21:05:23 +0200 ava commented on pull request polyphony/polyproto-dot-org#165 https://codeberg.org/polyphony/polyproto-dot-org/pulls/165#issuecomment-13084368 Describe how PAWs work, and how they should be used <p dir="auto">Oh, right, true; I forgot about that, because I use them daily on GitHub for professional<span class="emoji" aria-label="trade mark" data-alias="tm">™️</span> work there! I hope Forgejo gets them at some point, as they are really neat</p> Oh, right, true; I forgot about that, because I use them daily on GitHub for professional™️ work there! I hope Forgejo gets them at some point, as they are really neat

]]> ava 122687259: https://codeberg.org/polyphony/polyproto-dot-org/pulls/165#issuecomment-13084368 Mon, 13 Apr 2026 21:01:05 +0200 cyrneko commented on pull request polyphony/polyproto-dot-org#165 https://codeberg.org/polyphony/polyproto-dot-org/pulls/165#issuecomment-13075695 Describe how PAWs work, and how they should be used <p dir="auto">In addition to this below comment, I am wondering if the creation of these boards and such could be automated...</p> In addition to this below comment, I am wondering if the creation of these boards and such could be automated...

]]> cyrneko 122634048: https://codeberg.org/polyphony/polyproto-dot-org/pulls/165#issuecomment-13075695 Mon, 13 Apr 2026 18:44:50 +0200 cyrneko commented on pull request polyphony/polyproto-dot-org#165 https://codeberg.org/polyphony/polyproto-dot-org/pulls/165#issuecomment-13075635 Describe how PAWs work, and how they should be used <p dir="auto">Well...codeberg doesn&#39;t do sub-issues!</p> Well...codeberg doesn't do sub-issues!

]]> cyrneko 122634018: https://codeberg.org/polyphony/polyproto-dot-org/pulls/165#issuecomment-13075635 Mon, 13 Apr 2026 18:44:48 +0200 cyrneko commented on issue polyphony/polyproto-dot-org#54 https://codeberg.org/polyphony/polyproto-dot-org/issues/54#issuecomment-13075557 Homeserver key rotation: does it invalidate all id-certs signed by this one? <p dir="auto">Well yes! For compromises. But not for ID-Cert renewals.</p> Well yes! For compromises. But not for ID-Cert renewals.

]]> cyrneko 122631660: https://codeberg.org/polyphony/polyproto-dot-org/issues/54#issuecomment-13075557 Mon, 13 Apr 2026 18:38:00 +0200 ava created pull request polyphony/polyproto-dot-org#165 https://codeberg.org/polyphony/polyproto-dot-org/pulls/165 165#Describe how PAWs work, and how they should be used# I found it useful to finally write down how polyproto amendment workflows (PAWs) work. This includes info about how and when they are to be created, what they are used for and how we should interact with them.

]]> ava 122610525: https://codeberg.org/polyphony/polyproto-dot-org/pulls/165 Mon, 13 Apr 2026 17:58:20 +0200 ava pushed to flori/document-paws at polyphony/polyproto-dot-org https://codeberg.org/polyphony/polyproto-dot-org/commit/c5e397b91e044dd04f0ca1e6a5f2083091db9f1e <a href="https://codeberg.org/polyphony/polyproto-dot-org/commit/c5e397b91e044dd04f0ca1e6a5f2083091db9f1e">c5e397b91e044dd04f0ca1e6a5f2083091db9f1e</a> feat: describe how PAWs work c5e397b91e044dd04f0ca1e6a5f2083091db9f1e feat: describe how PAWs work]]> ava 122603649: https://codeberg.org/polyphony/polyproto-dot-org/commit/c5e397b91e044dd04f0ca1e6a5f2083091db9f1e Mon, 13 Apr 2026 17:40:18 +0200 ava created branch flori/document-paws in polyphony/polyproto-dot-org https://codeberg.org/polyphony/polyproto-dot-org/src/branch/flori/document-paws ava 122603577: https://codeberg.org/polyphony/polyproto-dot-org/src/branch/flori/document-paws Mon, 13 Apr 2026 17:40:18 +0200 ava deleted branch cyrneko/namespace-naming-guidelines from polyphony/polyproto-dot-org https://codeberg.org/polyphony/polyproto-dot-org ava 122541585: https://codeberg.org/polyphony/polyproto-dot-org Mon, 13 Apr 2026 15:17:50 +0200 ava pushed to main at polyphony/polyproto-dot-org https://codeberg.org/polyphony/polyproto-dot-org/compare/287c8e1414631d8ad4ff394655b8f3d1716d2636...cc1f03db1760ca73aa512163a43b998f3d67f6b1 <a href="https://codeberg.org/polyphony/polyproto-dot-org/commit/cc1f03db1760ca73aa512163a43b998f3d67f6b1">cc1f03db1760ca73aa512163a43b998f3d67f6b1</a> Merge pull request &#39;PURR-2026-0006: Namespacing guidelines&#39; (#162) from cyrneko/namespace-naming-guidelines into main <a href="https://codeberg.org/polyphony/polyproto-dot-org/commit/fea433deffab0eda8c40e52899316423b18334ff">fea433deffab0eda8c40e52899316423b18334ff</a> chore: <code class="inline-code-block">nix fmt</code> <a href="https://codeberg.org/polyphony/polyproto-dot-org/commit/353d3e75a66499bec1e9bc572d6126c638310f5f">353d3e75a66499bec1e9bc572d6126c638310f5f</a> feat(PURR-2026-0006): URI-based namespacing cc1f03db1760ca73aa512163a43b998f3d67f6b1 Merge pull request 'PURR-2026-0006: Namespacing guidelines' (#162) from cyrneko/namespace-naming-guidelines into main fea433deffab0eda8c40e52899316423b18334ff chore: nix fmt 353d3e75a66499bec1e9bc572d6126c638310f5f feat(PURR-2026-0006): URI-based namespacing]]> ava 122541561: https://codeberg.org/polyphony/polyproto-dot-org/compare/287c8e1414631d8ad4ff394655b8f3d1716d2636...cc1f03db1760ca73aa512163a43b998f3d67f6b1 Mon, 13 Apr 2026 15:17:49 +0200