FIDO / FTN distributed voting system
I have the honor to be familiar with the guys from the project http://ru.gplvote.org/ . Its essence is as simple as a song and as necessary as air. The guys create a fully distributed open source voting system.
I hope everyone here understands that for the voting system it means “distribution” and “opensource”.
The guys have a whole concept of voice verification organization, on GnuPG, which does not require a single focal point. Read their website, it's interesting there.
I have a suspicion that if the elections to the Constitutional Court were made on this platform, then ... but, history does not tolerate subjunctions, except in books about the war ...
So, my humble contribution to this project was the idea to make distributed transport of voice delivery on the echoconference metaphor.
The beauty of the “ekhi” is that it is completely distributed, and each message sent to the conference on one node is pulled away by the system across all the other nodes that are signed to this conference.
That is, by accepting that for each “vote” an echo conference is started, voting can be carried out simply by sending a letter to “echo”. "Ekhi" can be local, global - as well as voting.
I see the advantages of such a system:
Actually, if you tighten up flexible routing there (when one node dies, the mail goes around) the thing that is not killed by DDOS is obtained ... And there are already dynamic routing protocols in FIDO:
')
FIDO operated at 40,000 nodes, without money, in the conditions of a paid long-distance connection. Accordingly, thoughts like “big traffic”, “will not sustain big traffic” give rise to one answer - RTFM. Information echo conferencing distributed in the network of nodes (nodes). At this level, the network is p2p. But now the data storage capacity quite allow you to keep the node and point on the same machine. Even according to the old standards, there can be 2 ^ 45 nodes = 32 trillion nodes in the network, so architecturally it is quite realizable ...
In order not to drive traffic from every home throughout the country, conferences should be organized similarly to administrative division: house, street, (micro) district, city (town), region, country.
Then the letter route for each node can be done like this:
There is a proposal not to pour from empty to empty, but to raise an FTN grid of 3-5 nodes on the same husky.sourceforge.net Husky and drive messages there.
If we rest in something, then I think you can write to the guys that did the Huskies, half the Russians are there, and ask us to fix our hands and / or configs. Or maybe they will be imbued with the idea and will add the necessary functionality.
Actually, who else wants toshake the old days and drive to make a normal e-democracy on FTN?
Threat I understand myself that the technology is not perfect, for example (for now) I do not know how to anonymize FTNN for secret voting. But it is necessary to begin with something.
ZZY (nebeybebno) In general, you can not bother FTN because of exotic, and make transport on the news groups NNTP (USENET). The architecture is the same as in FTN - groups are distributed on NNTP servers, see www.bog.pp.ru/work/usenet.html That is, each network member picks up an NNTP server and “subscribes” to interesting polls. Add. The advantage of this solution is that the NNTP protocol is supported by most modern mail clients (including Thunderbird) that support GnuPG digital signature.
ZZZY: Yes, in Husky there is not a GPL code. It is not clear what kind of file license there is, just license text ... EULA is shorter (((I looked at the NNTP servers — Apache James is under the Apache License (GPLv3 is compatible, respectively), and ISC is (do not be surprised!)) Under the ISC license (GPL is compatible and even CopyFree)
Formerly 5040 / 33.35
The guys have a whole concept of voice verification organization, on GnuPG, which does not require a single focal point. Read their website, it's interesting there.
I have a suspicion that if the elections to the Constitutional Court were made on this platform, then ... but, history does not tolerate subjunctions, except in books about the war ...
So, my humble contribution to this project was the idea to make distributed transport of voice delivery on the echoconference metaphor.
The beauty of the “ekhi” is that it is completely distributed, and each message sent to the conference on one node is pulled away by the system across all the other nodes that are signed to this conference.
That is, by accepting that for each “vote” an echo conference is started, voting can be carried out simply by sending a letter to “echo”. "Ekhi" can be local, global - as well as voting.
I see the advantages of such a system:
- ready, run-in, open software,
- advanced, intelligent policies to optimize the exchange of traffic between nodes, and one city-scale vote already has tens of thousands of letters,
- Dozens or even hundreds of people in each city who are familiar with FIDO technology (these are only former NODs, and thousands of them with points) who can simply pick up a network node from nostalgia ...
Actually, if you tighten up flexible routing there (when one node dies, the mail goes around) the thing that is not killed by DDOS is obtained ... And there are already dynamic routing protocols in FIDO:
')
FRIP ( Fidonet routing information protocol) , , «» — , ( , ). . , «» . , . .
Hubroute generator ( «» — , ; Husky Fidoroute). «» , ( — R50.ROU R50.TRU ) , . , .FIDO operated at 40,000 nodes, without money, in the conditions of a paid long-distance connection. Accordingly, thoughts like “big traffic”, “will not sustain big traffic” give rise to one answer - RTFM. Information echo conferencing distributed in the network of nodes (nodes). At this level, the network is p2p. But now the data storage capacity quite allow you to keep the node and point on the same machine. Even according to the old standards, there can be 2 ^ 45 nodes = 32 trillion nodes in the network, so architecturally it is quite realizable ...
In order not to drive traffic from every home throughout the country, conferences should be organized similarly to administrative division: house, street, (micro) district, city (town), region, country.
- The street is the “boss” of the houses,
- district - "boss" of the streets,
- the city is the “boss” of the districts
- the region is the “boss” of all the settlements,
- the country is the “boss” of the regions.
Then the letter route for each node can be done like this:
; ; // , ; ( ), { ;} There is a proposal not to pour from empty to empty, but to raise an FTN grid of 3-5 nodes on the same husky.sourceforge.net Husky and drive messages there.
If we rest in something, then I think you can write to the guys that did the Huskies, half the Russians are there, and ask us to fix our hands and / or configs. Or maybe they will be imbued with the idea and will add the necessary functionality.
Actually, who else wants to
Threat I understand myself that the technology is not perfect, for example (for now) I do not know how to anonymize FTNN for secret voting. But it is necessary to begin with something.
ZZY (nebeybebno) In general, you can not bother FTN because of exotic, and make transport on the news groups NNTP (USENET). The architecture is the same as in FTN - groups are distributed on NNTP servers, see www.bog.pp.ru/work/usenet.html That is, each network member picks up an NNTP server and “subscribes” to interesting polls. Add. The advantage of this solution is that the NNTP protocol is supported by most modern mail clients (including Thunderbird) that support GnuPG digital signature.
ZZZY: Yes, in Husky there is not a GPL code. It is not clear what kind of file license there is, just license text ... EULA is shorter (((I looked at the NNTP servers — Apache James is under the Apache License (GPLv3 is compatible, respectively), and ISC is (do not be surprised!)) Under the ISC license (GPL is compatible and even CopyFree)
Formerly 5040 / 33.35
Source: https://habr.com/ru/post/156097/
All Articles