@polyproto - Awawazon Woof Services

polyproto federation protocol @polyproto@amazonawaws.com

2mo

We are fucking queer to our polyproto-core. Don't like it? Fuck off!

To everyone else: The happiest of pride months to you!

1

1

1

1

1

1❤️1

0

24

41

7

polyproto federation protocol @polyproto@amazonawaws.com

4mo

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

<a href="https://polyproto.org">
    <img loading="lazy" src="https://88x31.polyproto.org" alt="The polyproto federation protocol" style="image-rendering: pixelated"></img>
</a>

1❤️1⭐1

1

6

19

3

polyproto federation protocol @polyproto@amazonawaws.com

7mo

In the footer of our website, one can now find a bonus fops for when times are tough!

1

1

4

9

2

polyproto federation protocol @polyproto@amazonawaws.com

8h

@laru The beauty of having an open protocol is that it allows for many interpretations of it. I can certainly imagine that there'll, at some point, be clients that match exactly what you want

0

1

0

polyproto federation protocol @polyproto@amazonawaws.com

1d

@laru Not at all! Our primary motivation is to build the best possible, easiest to use federated Discord-like that we can

1

0

1

0

polyproto federation protocol @polyproto@amazonawaws.com

1d

@laru soon..

1

0

1

0

polyproto federation protocol @polyproto@amazonawaws.com

1w

@16af93 NUH UH

1

0

polyproto federation protocol @polyproto@amazonawaws.com

1w

Stickers!

1❤️3

1

3

17

4

polyproto federation protocol @polyproto@amazonawaws.com

1w

Due to stress, this is a little late now, but you can access the meeting minutes of the first polyproto-chat working group meeting here: https://write.polyproto.org/s/XLPL74svfB

The meeting has been very pleasant and fruitful, and I am very much looking forward to the next one! Once ready, a poll to pick a date/time for the next meeting will be published here as well. 💜

0

2

9

0

polyproto federation protocol @polyproto@amazonawaws.com

1w

@parrot Sadly not; this is about a group that has the goal of specifying a chat standard

0

1

0

polyproto federation protocol @polyproto@amazonawaws.com

1w

@lumi @CinnamonCatYurilover It is quite clear that a protocol aiming to be an actual alternative to proprietary services such as Discord must offer at least a similar set of functionality. As such, we consider voice- and videocalling to be in scope for our overall project.

0

1

2

0

polyproto federation protocol @polyproto@amazonawaws.com

2w

polyproto-chat working group! just 2 days away! it got here so fast!!

1

3

11

0

polyproto federation protocol @polyproto@amazonawaws.com

2w

@16af93 noted.

1

0

polyproto federation protocol @polyproto@amazonawaws.com

2w

ordered 2000 stickers (4cm*1.6cm) with this motif because why not

1

9

0

polyproto federation protocol @polyproto@amazonawaws.com

2w

A visualization of the polyproto-rs repository, made with Gource. Thought it'd be neat to share this

❤️1

2

6

12

1

polyproto federation protocol @polyproto@amazonawaws.com

3w

@lypsilonx Oh, sweet! In that case, I can very much encourage you to join our Zulip! I'd love to collaborate :) - @star

0

2

0

polyproto federation protocol @polyproto@amazonawaws.com

3w

The meeting is set to happen on July 22nd, 6:00pm (Europe/Berlin)! Be there or be

Calendar subscription | Calendar event download (.ics) | Proton Meet Link

1

0

16

11

1

polyproto federation protocol @polyproto@amazonawaws.com

4w

@Nyan Hi! I believe you'll be able to find answers to this on our website (polyproto.org) and specifically also the following blog post: polyproto.org/blog/2026/01/02/prior-art/

0

polyproto federation protocol @polyproto@amazonawaws.com

4w

We are forming a working group to design the best possible federated alternative to Discord, Matrix and co.! And we'd love for you to be a part of it!

For this, we will have regularly scheduled online meetings and asynchronous communication in between meeting dates.
Our first meeting is about figuring out how we'd like to work together. How often do we meet? How do we want to make decisions? How will results get communicated to the broader public?
Sound interesting to you? Read the full agenda and detailed description, help us with choosing a date and time for the first meeting by entering your availability here and/or join the Zulip to stay informed!

- No advanced technical knowledge required for this meeting
- Date/time will be chosen and announced after Sunday, July 12th 2026, 3pm (Europe/Berlin)
- Meeting will be held online, link will be published after date/time is fixed

1

1

1

1

2

1❤️4

5

43

38

12

polyproto federation protocol @polyproto@amazonawaws.com

1mo

We are extremely thankful and happy for your feedback thus far!

More working group-related information soon.

0

1

4

0

polyproto federation protocol @polyproto@amazonawaws.com

1mo

@hsza @Venefilyn

does it all use https under the hood?

yes. The X.509 from polyproto is purely a layer on top of existing infrastructure, and doesn't commingle with it.

then you're still importing the issue of CA centralization from that

That's true. But you cannot decentralize everything without creating a huge, complex, unimplementable mess of a specification. Tech extensions could be used to replace HTTPS and the fact that the infrastructure behind it is sort of centralized with an alternative transport layer.

With decentralization, you can always go a level deeper. We are focusing on creating a decentralized federated network, not a decentralized IP transport layer. And even if that were solved, you could go deeper again and say "still, the internet itself is very centralized because of ISPs, server providers etc." and demand polyproto-over-meshcore or something like that. But then you could still say "well, semiconductor production used for meshcore radios is quite centralized too, so we should provide a specification to build your own radio from sticks and stones and then do polyproto over that". And, sure, those aren't invalid points, but that'd all take well over a decade to do, so I defer that to other individuals/for later.

1

0

1

0

polyproto federation protocol @polyproto@amazonawaws.com

1mo

@hsza @Venefilyn Intermediary certificates being forbidden also means: It isn't (at least easily; everything is doable if you ignore the rules) possible for someone like Google to offer something like LetsEncrypt for polyproto, which would centralize trust, and thus power, around them.

0

2

0

polyproto federation protocol @polyproto@amazonawaws.com

1mo

@hsza @Venefilyn Unlike CAs used for HTTPS and such, polyproto does not have trust roots. Trust roots are trusted certificates by big companies, which essentially sign the certificates of other companies acting as certificate authorities "downstream". These trust roots make CAs very centralized in practice. If you tried to host a website using a completely self signed SSL cert, your browser would refuse to load it and display a big fat warning about the SSL cert being untrustworthy. That warning is because there is no valid path from the self-signed certificate to any of the trust roots installed on your device.

In polyproto, intermediary certificates are forbidden. There's only the home server certificate and client certificates. Picking up the "self-signed certificate for your website" example again: If you deploy your own home server, you do that with a self-signed certificate which the server generates and signs. Unlike the website, there is no warning and no refusal from your browser. This is what makes it much more decentralized.

Why this even works from a security perspective is, because we are only building in top of established infrastructure. To make your home server reachable over HTTPS, you still have to get an SSL certificate somewhere, be it from LetsEncrypt or some other service. We use the security guarantees that the infrastructure the entire world runs on give us, and build something less restrictive on top of that. Perhaps this makes sense, perhaps this is too wordy; let me know if there are any questions you still have! :)

2

0

1

0