Awesome to see how fast feedback is being implemented/tested!
How about messaging priorities? I didn’t see that anywhere just curious if I missed it
Or these launcher and demo app fixes will allow test 6 to continue successfully to help with setting message priorities
wohooow - tuesday again Oo maaan i have way too little time these days -.-" …
someone can puts the link that shows the scheme of the network status with the progress and that stuff? Thanks
When I received the email notification earlier about this my heart skipped a beat. 
My only wish for the next update is some sort of stable testnet back online.
Doesn’t need all the newest features, just the basics so we can continue testing our new API uses.
Really didn’t expect the stable droplet network to go down
tcp 0 0 *:44546 *:* LISTEN 21/safe_vault
tcp 0 0 mainServer_A1:40878 ci.aim-rdv-display:5483 ESTABLISHED 21/safe_vault
tcp 0 0 mainServer_A1:60519 johnnytrumpet.plu:40995 ESTABLISHED 21/safe_vault
tcp 0 0 mainServer_A1:50324 139.59.178.79:43276 ESTABLISHED 21/safe_vault
tcp 0 0 mainServer_A1:51722 139.59.178.91:5483 ESTABLISHED 21/safe_vault
tcp 0 0 mainServer_A1:58689 84-245-28-177.dsl:46706 ESTABLISHED 21/safe_vault
tcp 0 0 mainServer_A1:55297 139.59.160.66:5483 ESTABLISHED 21/safe_vault
tcp 0 0 mainServer_A1:33398 188.166.159.235:5483 ESTABLISHED 21/safe_vault
tcp 0 0 mainServer_A1:40476 178.62.61.210:5483 ESTABLISHED 21/safe_vault
tcp 0 0 mainServer_A1:33269 139.59.178.65:5483 ESTABLISHED 21/safe_vault
tcp 0 0 mainServer_A1:57557 139.59.178.35:5483 ESTABLISHED 21/safe_vault
tcp 0 0 mainServer_A1:60308 5x19x247x38.stati:41463 ESTABLISHED 21/safe_vault
tcp 0 16 mainServer_A1:51453 139.59.178.135:5483 ESTABLISHED 21/safe_vault
tcp 0 16 mainServer_A1:44021 139.59.178.131:5483 ESTABLISHED 21/safe_vault
tcp 0 0 mainServer_A1:48048 xd9326519.dyn.tel:48667 ESTABLISHED 21/safe_vault
tcp 0 0 mainServer_A1:43606 rdcr:41483 ESTABLISHED 21/safe_vault
tcp 0 24 mainServer_A1:35400 139.59.178.63:5483 ESTABLISHED 21/safe_vault
tcp 0 136 mainServer_A1:35438 dhcp-169-229-198-:37766 ESTABLISHED 21/safe_vault
tcp 0 0 mainServer_A1:35914 pool-100-16-10-59:52418 ESTABLISHED 21/safe_vault
tcp 0 144 mainServer_A1:50609 139.59.178.93:5483 ESTABLISHED 21/safe_vault
tcp 0 0 mainServer_A1:49899 139.59.178.83:36379 ESTABLISHED 21/safe_vault
tcp 0 56 mainServer_A1:46342 139.59.188.114:5483 ESTABLISHED 21/safe_vault
tcp 0 16 mainServer_A1:54836 139.59.178.22:35409 ESTABLISHED 21/safe_vault
tcp 0 48 mainServer_A1:45583 139.59.178.84:5483 ESTABLISHED 21/safe_vault
tcp 0 56 mainServer_A1:50923 139.59.178.85:5483 ESTABLISHED 21/safe_vault
tcp 0 32 mainServer_A1:55585 139.59.178.126:35411 ESTABLISHED 21/safe_vault
udp 0 0 *:5484 *:* 21/safe_vault
My vault is 8 days on now … what was the problem ?? Nobody could connect to safesites or what ??
Exactly, for at least 3 of us. But I suppose it’s a more general problem, when I signaled the problem 2 days ago, nobody replied that the safe sites were working for him/her.
@whiteoutmashups if you are testing single user you can build Launcer with mock routing and you won’t need the developer testnet. I’ve been doing all my development with that, and as a bonus I can use the debugger to peek inside the Launcher if I need to find out why some API isn’t doing what I want 
Thats still plenty. I’m happy with 25.
Me too, I think it’s to see if uploads work better if we limit the amount that can be uploaded at once.
but … indefinitely? or by the moment?
These are tests. David has said that tests and alpha will have limited uploads but the live network will not
Summary
Change the definition of the term “close group”, and the corresponding routing table logic, such that all the network’s groups are disjoint and form a partition of the set of nodes. Each node will thus be a member of exactly one group. The group size, however, will not be fixed anymore.