Am Sonntag, 18. November 2012, 21:01:02 schrieb Matthew Toseland:
On Sunday 18 Nov 2012 02:58:55 you wrote:
Wait, we're not going to maintain backward compatibility with SSKs? That
doesn't seem wise...
Current proposal in a nutshell:
- Support existing SSKs for back compatibility.
- New
I have merged Robert's original patch (compile fixed) for depth-first
announcement onto a branch, opennet-changes.
It will need to be tested thoroughly:
- Do new nodes announce with new seeds?
- Do new nodes announce with old seeds?
- Do old nodes announce with new seeds?
(Note that Update Over
Idea for automated seednode collection:
Could official seednodes pass a list of second tier seednodes that newbies
can try to connect to when official nodes are overloaded?
Implementation:
When an official seednode accepts a newbie node for announcement it checks
if that node has its be a
Sent from my wireless phone.
On Nov 19, 2012 10:24 AM, Juiceman juicema...@gmail.com wrote:
Idea for automated seednode collection:
Could official seednodes pass a list of second tier seednodes that
newbies can try to connect to when official nodes are overloaded?
Implementation:
When an
On 2012/11/19 (Nov), at 6:42 AM, Matthew Toseland wrote:
I have merged Robert's original patch (compile fixed) for depth-first
announcement onto a branch, opennet-changes.
Yeah! (commence happy dance)
It will need to be tested thoroughly:
- Do new nodes announce with new seeds?
- Do new
What will actually change for SSKs apart from the way they work internally?
Will the SSK-Generator just spit out new keys with another new ending like the
last time SSKs were changed internally, but everything will keep working the
same as usual, so same FCP-commands for retrieval and inserts
