User avatar
neobot_flag_trans Polyphony Cyberwitchery & Software asparklessparkles_pink @polyphonychat@amazonawaws.com
1w
December 12th is the targeted date for a v0.1.0 release of sonata, our @polyproto core home server implementation.
Planned for this initial proof-of-concept version are all features required to federate identities and verify messages sent from other people on any home server. Functionality/features above that are not likely to be included.
2
9
16
0
User avatar
Jessie (they/she) 🍓 🏳️‍⚧️ 🍉 @QueerMatters@mstdn.social
8h
@polyphonychat @polyproto i can’t tell you how fucking excited I am for this. Absolutely ROOTING for yall. I don’t think anyone realises it yet, but this protocol is gonna be seismic
1
0
2
0
User avatar
neocat_polyproto polyproto federation protocol @polyproto@amazonawaws.com
7h
@QueerMatters @polyphonychat Thank you for these amazingly kind words! neocat_floof_cute celeste_hearts_trans celeste_hearts_lesbian
0
0
1
0
User avatar
neobot_flag_trans Polyphony Cyberwitchery & Software asparklessparkles_pink @polyphonychat@amazonawaws.com
1w
Despite being a proof-of-concept release, writing qualitative code is important to me. A large reason for why development is taking a while is because throughout the project, I have set myself higher and better standards for what I find to be acceptable to push, as I have learned more about the language and software architecture overall. The home server implementation, as barebones as it might be, should have such a strong foundation to carry it throughout all the additional features that will land in it. Major, breaking rewrites should be minimized in the future. Time invested now is time saved later (to a point).
0
0
10
0