User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
polyproto 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
Core Specification https://polyproto.org/docs/protocols/core?source=Fedi
Webbed Site https://polyproto.org?source=Fedi
Community Forum https://polyphony.zulipchat.com
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
2w
@hypha I am not exactly sure what backblaze is smoking here :P
- @star
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
2w
@Cyborus i cannot tell you why firefox chooses to download this as .wav, but the link most definitely references a .webp
- @star
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
2w
There are now a bunch of cool 88x31's at the bottom of our homepage! verified_blobcat
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
2w
source

edit: changed from webp to png :)
This post has attachments, but this server's configuration prevents them from being displayed here.
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
2w
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 @polyphonychat instance, the shared media library, music server and fedi instance, without having to do anything extra! neocat_flag_polyam
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
3w
yuri
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
3w
Work on this has already started! neocat The OIDC-branch is being expanded with more information. The goal for now is to define all the rough outlines, and to fill in the rest later, through knowledge gained via feedback and an implementation.
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
3w
@Gnuxie @alexia As alexia already helpfully alluded to, if XMPPs XEPs are Lego-Bricks, then polyproto extensions are Duplos. Tech-standards integrate technologies into the protocol in a reusable way, while application standards define an application skeleton fit to federate with other implementation following the same standard.
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
3w
@Gnuxie @alexia I believe that one can do a lot of unifying through building a healthy community, great governance and extensible standards neobot_melt_happy
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
4w
Smiley added: "The question here is if it's all so great, why are the insurance underwriters going to great lengths to prohibit coverage for these things? They're generally pretty good at risk profiling."
From www.theregister.com/2026/03/17/ai_businesses_faking_it_reckoning_coming_codestrap/
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
4w
@link maybe there should be two of them! twinsies!
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
4w
you should know this:
This post has attachments, but this server's configuration prevents them from being displayed here.
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
1mo
This will then unblock work on adding working authentication to sonata, which will likely be up next in the task queue!
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
1mo
Next up on my list of tasks: Finishing the OIDC+SCIM PURR to introduce OIDC (OpenID Connect) as the common way of authenticating to one's own home server. This will kill polyproto-auth; it will not be missed neocat_blep

- @star
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
1mo
[ Merged ] ava merged 279 commits from indev into main 7 minutes ago

wowee neobot
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
1mo
@parrot Thank you!
- @star
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
1mo
After over 5 months of time spent refactoring and developing, sonata—our polyproto-core home server—has received so many internal updates and additions, that we could merge the code to actually generate and store/retrieve home server ID-Certs to the database, today! neobot_floof_cute ablobcatmusicneodog_melt_blep Even though not recommended at this stage of development, one could now already establish their home servers' identity by hosting their own instance of sonata.

While all of the code added and refactored over the last 5+ months has been necessary to implement this feature in a nice way (which doesn't need to be refactored again for a while), these additions and changes were so substantial, that they will enable a faster development pace for actual features going forward neobot
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
1mo
Version 1.6 of our Code of Conduct reaffirms the ban on AI-generated contributions and makes this policy even more clear. verified_blobcat verified_misskey
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
1mo
Over the weekend, lots of commits landed in the indev branch of sonata, our in-development polyproto-core home server. polyproto Code was introduced which uses the type system to verify, at compile time, that certificates being stored have actually been verified to be valid and well-formed before being allowed to get stored or passed to other parts of code. Encoding this information in the type system means being 100% sure that a certificate or key is valid in a given context, without having to resort to additional runtime checks. On top of that, CI was improved yet again neobot_happy
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
1mo
@mxremy You're very right in that there's no federation going on between most of the Discord alts. Getting this right takes a lot of time, because something like this has to be great the first time around. Changing things in backwards-incompatible ways later is always much harder. Development and documentation support would be much appreciated! Monetary support would help if it allowed me to hire freelancing critters to dedicate time on this project. Donating to me, personally, would not speed things up, even though the thought is very, very nice c: - @star