@star Not him, but I enjoyed the whimsical humor. The talk itself was too basic for me, I would have wanted more on replication and state resolution/consistency. (You know, the hard networking problems.) There was some of that in the Q&A, but as it was the talk was more of an “introduction to asymmetric cryptography” and less about Polyproto as a network.
I also got click-baited into this by misreading “homeserver” (software for self-hosting) so as “home server” (“old phone kept hostage in the closet” as the talk would call it ). I also was able to name almost all neomojis as they appeared. @brettm
I am very glad to hear that! I threw that in on purpose, but it was hard to judge what the live audience thought of it, because I couldn't really see them with the stage lights and all. c:
The talk itself was too basic for me [...] but as it was the talk was more of an “introduction to asymmetric cryptography” and less about Polyproto as a network
I understand the sentiment. And to be honest, as I said at the end of the talk: Finding things to talk about wasn't hard at all, but packaging them was. Ultimately, I made the deliberate decision to have this talk be as beginner-friendly as I could reasonably make it. A lot Chaos talks are these hyper-specialized pieces of media suited to individuals whom already have a firm amount of knowledge surrounding the presented topic.
A sentiment I have received a lot in the past was something along the lines of "I do not understand how any of this works, but I think your idea is very neat", mostly by non-techy individuals. And this is precisely what I had in mind when structuring and writing this talk. I really wanted to have something that I can easily throw out to basically anyone, no matter their technical background, and—assuming they are willing and have the attention span and energy available to follow—can understand the foundations of how it all works. Accessibility is extremely important to me, and I believe making knowledge accessible is an important thing. That does not mean that I think every talk should do this, or anything like that; and, were I to hold another talk about polyproto, I would NOT cover the basics again. There, I'd say "if you'd like a refresher on the basics, feel free to watch this talk". But for this talk, that has been my goal.
And at the same time, I can understand that it leaves individuals like yourself wanting more, or perhaps rolling their eyes at me explaining what likely feels like "1+1". But yeah. You have to make such a decision, and I hope that you can understand why I did what I did. c:
I would have wanted more on replication and state resolution/consistency. (You know, the hard networking problems.)
You see; that's the thing! polyproto does not do replication or state resolution. If an extension writer/publisher wants to add this, they are very free to, but polyproto does not do it, and polyproto-chat will also not do state-resolution and things like these, because I believe them to not be at all necessary for (and perhaps even working against) an actually good experience in federated chat.
If you now have even more questions, do feel free to ask them c: And thank you very much for watching the talk and then also providing feedback! That is very kind of you
yea I was gonna reply the same thing about replication; this isn't IPFS, IRC Server-Server or Matrix, and we believe that for chat doing a whole thing with replication and eventual consistency and state resolution and algorithms over the network is needlessly complex for what should be "do federated auth to the remote server, send it a signed message" (which is exactly what p2-core + p2-chat will be!)
You see; that's the thing! polyproto does not do replication or state resolution.
So in other words, messages are per-real-server (not Discord “server”/space, lol) and when the server goes down I keep my account but the messages on that server are gone? So basically ActivityPub with transparent account migration for chat rooms, that correct? @brettm
re: Long, polyproto talk yappings@curiousicae@brettm Mostly! A real server can host any amount of spaces (guilds, whateveryouwannacallit). And yes, any server going down only affects functionality of that server (even with your own home server). And as it stands currently, you mostly directly perform actions and access resources on a server, such as getting or sending messages, by sending that request to that server, and not usually by sending it to your home server
I am very glad to hear that! I threw that in on purpose, but it was hard to judge what the live audience thought of it, because I couldn't really see them with the stage lights and all. c:
Gixen were you where, I’d guess: 1/3 Yeah! 1/3 This is fine 1/3 Could do without 0/3 GTFO the stage!
Not that I’ve been to any Chaos events in the last half-decade. @brettm
re: Long, polyproto talk yappings@star Finding things to talk about wasn't hard at all, but packaging them was. Ultimately, I made the deliberate decision to have this talk be as beginner-friendly as I could reasonably make it.
I wasn’t criticizing that you do a beginner-friendly talk per se, it was mostly about it being introduced as an all-around talk (“The PolyProto protocol”), when really it was more like “Foundations for the PolyProto protocol”. I think the audience questions at the end also pointed to people having expected a more advanced talk, but I’m only infering ofc.
@star looks good to me! I did have one or two questions, you mentioned you're aiming to have some example by december, i'm just curious what language you're using? and will it use sqlite or what for storing the chats?
I never held a talk before today, but I am glad I did, and I am happy I did it here! 
Thanks to the amazing VOC, you can watch my talk here, if you'd like: media.ccc.de/v/ds26-627-how-to-outlive-your-home-server-the-polyproto-federation-protocol 
@star@amazonawaws.com
1
1
1
1❤️1💜1
