Hey, I just wanted to chime in here a bit. I understand the frustration. We ourselves want all of this too.
However, in the last release we made some clumsy mistakes because things were rushed. We were encouraged by lots of people here in the community to take more time to ensure better quality releases, and that’s what we’re doing now.
So please just try and bear with us here! 
Does this have an impact on decentralization of the network? I feel like this network needs to keep nodes that are not performing well, but still contribute to the overall goal. I don’t believe we should be aiming in the direction of only using nodes that perform well. Just my two cents.
The idea is to avoid mis-configured nodes from even joining the network and then not behaving as one would expect regardless off their actual hardware specifications.
There are a series off PRs in the works to rely on connection information than identify, including 180 second dial backs, and eventually automatically reach a conclusion on the type of node/network topology you are on so flags such as --no-upnp, --relay, --ip etc would not be required.
The process would be super streamlined including auto-detecting which network adapter is transmitting and receiving traffic for antnodes running within the OS as well etc.
All of the above needs to be rolled out in phases with majority off the code base for node operators to be on the latest versions to have maximum impact towards a healthier network.
Well if ant does not come through I can retire on that comment alone 
Thank you @happybeing 
The bears have got you from the other thread 
awe man i’m going to have to pull up Saturday Night at the movies (The drifters) and have a sing to myself , thanks so much to autonomi/maidsafe and everyone on the forum, i’m stoked. Looking forward to checking out Atlas in the morning. These are the days,i’m happy as happy!
The road to success is always under construction… 
I recommend this is a very informative text and I think it answers your question
So large uploads do work everytime now?
With the not yet released new client - yes - the new client only gets quotes for one batch of chunks at a time, then uploads that batch and repeats until all data is in the network
Edit: and ofc if you simply build yourself from main you can have that client already and test it out
Great update and great to hear this!
Thx 4 the update Maidsafe devs and your hard work
Come on you never dissapoint, everything just takes it code/testing/time before it’s reality 
@Josh @aatonnomicc @happybeing @riddim @traktion @safemedia 
When my home nodes go offline, sometimes, it can take 600s before I restart my OS and restart the nodes (sometimes I even have to remove autonomi’s folder, restart my computer and extract it again, restart and add my arbitrum address before the nodes run again). So is 180s enough time, then again there can/will probably be a retry after 180s…
Although not data payments, I wonder if there are also batch payments, to prevent normal txs but with high txcosts and low value tx? Although it can/will be useful if i can start rewarding ai’s 1 attos @ the moment… 
Not to criticize, but I do get @Lisa_Brown point, unless we all become Data from StarTrek and can all memorize 99e3b8df52814b379e216caf797426071000905a2cd93a9f5e90eef2b32517a9ec1ef0bfe27d79360014fd97639ac612 and repeat the address without missing a character within 180s, it will be hard to trek these stars 
, but probably not for ai’s…
Super update btw 
Keep hacking super ants
I wondered about that too. I worry that there’s an unconscious drift from the original vision of a network for everyone, because of the need to prioritise ‘big’ participants to get uploads over the blockchain-wall.
Will native token solve that?
Not necessarily. We need to shed blockchain which might or might not be achieved with native, but the longer we wait the less likely that will be.
By then the mindset here and outside will also be more set, the participants and applications directed away from everyon etc. So it becomes hard to get to the destination of a network for everyone the further we have drifted from that route.
Since last September we’ve been off course and creating a lot of difficulties in this respect, and spending resources on creating that distance which could have been spent solving the problems related to native and other things that support the original vision.
I’ve just seen someone arrive wanting to connect the project via OTC with VCs. Some will welcome that for obvious reasons, but I see that and any positive responses to that as part of the inevitable drift (or worse) resulting from the blockchain wall that has been built around the project.
This is fully working browser launcher app for windows( It should work on Linux and Mac too, but I never tested that). You will need just to download 1 file, install it, run and this is what you will see. It auto detects your browsers, you pick which one you want and it will create a custom profile for that browser and configure it to work with autonomi. It will not break your existing browser behavior, just create separate environment for it. So it is just click and play solution. It is ready, fully functional. I will release it officially in max 2 weeks.
have you got AntTp built into it already or is it using a separate end point for AntTp hosted elsewhere?
Thats very welcome news…confronting the upload issue with a whole of team approach has payed off.
Again a tauri app if I’m not mistaken 
very nice
The 180 second thing was actually very close to the long time thing of nodes not responding for a length of time (around 5 minutes or so) would be shunned, ignored, or whatever you want to call it. This was actually removed recently when they started ignoring the connection error due to no response.
Also nodes were supposed to get a new peerID every time they restarted. Maybe its time they did this and it would solve any problem since you would effectively have nodes at new addresses and the existing chunks would be offered up to the network.
At this time though, if its going to be longer than the 180 seconds then you’d be better to remove all your nodes and just start new ones. Maybe this could be baked into launch pad
I plannet to use AntTp as a library, but it had conflicts in cryptographic libraries with Tor module dependenices. So I had to build AntTp as a separate app, its binary is included directly in this launcher app, but it runs as internal execution. So it is external app, but bundled inside. From user perspective there is no difference, it works like charm, one app only. The offers combination
2 &3 are setting to browser a socks5 proxy, which detects a domain. if the domain has *.ant pattern, it routes to AntTp. Everything else goes to regular internet. A plan to add there some domain resolution logic, where *.ant domain will automatically resolve to some landing page file…
