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
2mo
In the last 7 days, about 30 commits have been made to polyproto-rs, the software development kit for polyproto. Once merged, the changes made will make integrating polyproto into your application much easier and safer than before.

Finishing this large piece of work will unblock work on
sonata, the in-development polyproto home server, which will be ready for sending the first ever federated test message over polyproto not too long after that, I hope.

Even though it's mostly just me working on this, things
are happening, fueled by spite, stubbornness, lesbianism and the desire to do something about the absolute state of non-centralized communications.
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
2mo
@lea @illyBytes @polyphonychat neodog_angel_pleading
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
2mo
A pretty big PR is coming to polyproto-rsโ€”the polyproto Rust SDK, aiming to improve developer ergonomics by a ton and addressing a good amount of technical debt! codeberg codeberg.org/polyphony/polyproto-rs/pulls/95
This marks the crates' biggest refactoring to date and is particularly important and directly helpful for building sonata, our polyproto-core home server
neobot_happy neobot_salute
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
2mo
poWLWyproto
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
2mo
Also now found on the top left of the website! I only wanted to update the favicon, because the old favicon had no contrast on light backgrounds, whereas this one does; but that also changed the logo on that part of the actual site. I'm keeping it this way now >3_transgender verified_trans
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
2mo
@specificprotagonist @Cyborus @theresnotime d'awwwwwww -ava
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
2mo
3_transgender
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
2mo
@tauon yes!
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
2mo
@snugglybun I think that to replace Discord, the UX of the competing application must be not good, but great. Luckily, this is our number one goal with this protocol, and the reason which makes me very optimistic about people actually flocking to it, once it becomes ready.
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
2mo
@tauon Yes! The core specification is definitely at a point where you can feasibly implement it and start sending some basic messages with it.
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
2mo
@polyphonychat @gwenthefops @theresnotime um
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
2mo
@theresnotime hey 3_lesbian
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
2mo
The polyproto SDK is being made more consumable through moving more runtime validity checks to compile-time, where they belong! ๐Ÿ—๏ธ
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
3mo
The README for the "polyproto-dot-org" repository was majorly updated today. It now explains the terms "PURR" and "PAW" and elaborates on how spec change requests are best submitted.
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
3mo
cat_is_blob_and_lesbian polyproto now features 100% more PURRs and PAWs.
nya :3
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
3mo
boost_requested Matrix has MSCs (Matrix Spec Changes), XMPP has XEPs (XMPP Extension Protocols)... We'd also like a fun acronym to describe change proposals to the polyproto specification and polyproto.org-managed polyproto extensions! Which of the options below would you like most? โ€‹espeon_loveโ€‹ โ€‹neocat_flop_blepโ€‹

RE:
fed.amazonawaws.com/notes/ahene9jjm94vyswy
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
3mo
Maybe PAW (polyproto Amendment Workflow)... neocat_boop_blep
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
3mo
A standard term for polyproto spec change proposals is needed. I was thinking PURR (Polyproto Update & Revision Request) or CAT (Change & Architecture Track(er/ing)) blobcat
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
3mo
We are finally starting to produce a draft for OpenID Connect as an auth-standard for user->own home server authentication. This might also pull in SCIM, but everything about that is still very blurry. Please feel free to leave thoughts, questions and opinions here, or on our Zulip.
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
3mo
@5225225 An argument is perhaps to be made, that
- A service being down is something that users begrudgingly accept, but do not take massive issue with
- The much reduced complexity through "a room is on a server" making for less engineering challenges, which, in turn, may actually contribute to the real-world uptime being higher on these services, compared to ones using more complicated distribution logic