Meaning fork resolution / blocks calculation occurs only through WS2P ?
BMA seems to accept POST requests though!
Why would the DUBP not use various networking utilities?
Because you dont like REST no one should be allowed to use it ? comon …
This confirms my suspicions! Where are the maths showing it? I mean, if you consider its fine that anyone knows how to cheat but not others, it becomes seriously difficult to trust anyone in here. Especially when most participants here spend there time correcting each other vocabulary. perhaps would be nice to cleanup our own backyard first !
We seriously disagree on the method here. I dont shoot first ask question later… I think a clear spec written out might impulse the changes!
You’re suggesting, only @cgeek can impact the development of the Protocol ? be serious please
You’re suggesting, we have to binarize documents and fix it all. At the same time we make it all unreadable for humans. What a bad long term idea! think twice friend, think twice!
Propose, Yes propose but really… binarizing a protocol, that is proven to be broken and having a single implementation? It would persists errors without the need for it yet (1 tx every 10 blocks avg, 1250 members stagnating).
- I said “I will draft”, wasn’t asking you to do it.
- It doesnt suit me to install a node I cant read. nor does it suit me to work using a forum held by people so proud they threaten to kick anyone who disagree with them ? DO I HAVE A CHOICE THOUGH!?
- You are totally missing the point! I’ll explain it in a later post but in short: the grammar is there to specify formally the protocol changes
- again with your binary format… dude… like the binarization happens magically, without parser and lexers. Let me make it simple: if you send a message, the receiver will have to read it, and therefore know the set of rules required to do so… you may melt the parsing in your tools and programming stuff the way you want, it doesnt change the FACT that if your node intend to communicate, it’ll need to specify a language others can read and write. unless of course, your plan is a pure and simple technological take over.
If I am to participate further in this project, it will not be by waiting for a hero to save us all with a 3 years plan. I mean seriously, you are about to work for years on a piece of code but taking couple hours on specifications is too much? This is so inconsistent with your public presentations that I can’t help but to question your intentions.
I dont have any use for RFCs telling me “HOW I DID IT”, just write a blog post for it.
What I need is a basic consensus on how will nodes communicate, sync. How will the protocol change (unless the Version tag is just a joke) And I need this answer AGNOSTIC to any implementation: the MINIMUM to allow multiple implentations. Just as humans developped languages hundreds thousand years ago, Duniter’s ecosystem will do the same if it is meant to evolve. else its just a brotherhood of nodes talking to each others, like brothers and sisters having incestuous relations, one missing coma somewhere and the whole network is threaten.
Im not on a political quest here, Im on a literate one, those takes more time and are based on knowledge transfer rather than tough assertions “My node is just as fast as bitcoin YOUHA. Wait, why nobody uses it ?”
Exponentials takes a lot of time to become visible, but once they do, they reduce time! right ? Then, lets take our time! solve the missing pieces rather than rush the one true and godly implementation.