search

zem / qtc-net

A short telegram sytem for Amateur Radio
Other
5 stars 0 forks source link

Think about checksums in a decentralized network #33

Closed zem closed 10 years ago

zem commented 10 years ago

OK here the idea:

"the signed content contains "type", "call" and the alphabetically sorted fields of the message, packed together like they would be in the data file."

A client reduces the quality of a timestamp. Figure out what the hell you are doing with the call and voilla you may get qtc messages from various sources with the same checksum.

For example: If a message appears in a realtime network like APRS, you may consider building some sort of hour specific checksum which means that you can't send a message two times within one hour even if all the publishers do not know each other.

I have to think about this.....

zem commented 10 years ago

Add on: define a checksum type enumeration like signature type.

zem commented 10 years ago

dont forget do define a message delevery timeout for example 1 hour 24 hours 1 month

zem commented 10 years ago

provide optional parameters with a defaults data structure.

zem commented 10 years ago

implementation done