@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

polyproto federation protocol @polyproto@amazonawaws.com

5mo

@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.

polyproto federation protocol @polyproto@amazonawaws.com

5mo

@tauon Yes! The core specification is definitely at a point where you can feasibly implement it and start sending some basic messages with it.

❤️1

polyproto federation protocol @polyproto@amazonawaws.com

5mo

@polyphonychat @gwenthefops @theresnotime um

polyproto federation protocol @polyproto@amazonawaws.com

5mo

@theresnotime hey

polyproto federation protocol @polyproto@amazonawaws.com

5mo

The polyproto SDK is being made more consumable through moving more runtime validity checks to compile-time, where they belong! 🏗️

polyproto federation protocol @polyproto@amazonawaws.com

6mo

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.

polyproto federation protocol @polyproto@amazonawaws.com

6mo

polyproto now features 100% more PURRs and PAWs.
nya :3

1❤️1

polyproto federation protocol @polyproto@amazonawaws.com

6mo

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?

RE: fed.amazonawaws.com/notes/ahene9jjm94vyswy

:drippy_heart_purple_outline@subq.een.today:

1❤️1

polyproto federation protocol @polyproto@amazonawaws.com

6mo

Maybe PAW (polyproto Amendment Workflow)...

polyproto federation protocol @polyproto@amazonawaws.com

6mo

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))

polyproto federation protocol @polyproto@amazonawaws.com

6mo

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.

polyproto federation protocol @polyproto@amazonawaws.com

6mo

@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

polyproto federation protocol @polyproto@amazonawaws.com

6mo

save a cow, eat a plant
save a plant, eat a billionaire

polyproto federation protocol @polyproto@amazonawaws.com

6mo

Good standardization and open sharing of standards are not sufficient for making a protocol with no central point of potential failure. Governance has to be inclusive, accessible, transparent, democratic and community-owned. All of these points are paramount to creating protocols and software aiming to be around for a long time.

That, or have direct billionaire funding; though I much prefer my soul.

polyproto federation protocol @polyproto@amazonawaws.com

6mo

In a Pull Request touching 80 files, polyproto-rs (polyproto reference implementation in Rust) was painfully rid of all lintable bad style, missing documentation, inconsistent usages of things and sneaky ways to enabling crate features which would break the build of the library

All of this was enabled by refactored CI and style-checking suites now powered by

nix and @lix_project

(,,that's their logo right,?)

polyproto federation protocol @polyproto@amazonawaws.com

6mo

Today in polyproto-extension discussion: Finding a good solution for chat backups of encrypted chats, should we decide on wanting this as a feature; including figuring out how to have an explicit choice between post-compromise security and the added usability of chat backups.