Indeed and perhaps an apology is due from me for not making that point MUCH clearer up at the top of the thread. We all concentrate far too much on the negatives.
9 Likes
Yes.
And just because he happened to be the only one from the team here, he probably got a bit of anger, that’s actually directed towards the decision to not change anything in emissions.
If the folks responsible for that decision would raise their heads, then maybe others could have a bit more peaceful time. But now it easily seems like the technical team would be responsible too. Though I must say I understand very well if they’re not willing to do that.
Just imagine reading in the update, that “On the emissions front, Bob and Alice have decided to not change a thing”. On the other hand, now it seems that no one in particular is responsible for that, which means anyone on the team gets the blame.
But whenever a dev has been talking technical dev things here, I think they have been treated well. Maybe not always, but in general.
2 Likes
Critical? Definitely. Hostile? I don’t see it. I guess it’s impossible to see it from both sides. Maybe the damage is done (both sides), I hope not 
I think that’s what people are missing. Rather than just “it’s in the white paper”. I’ve heard many valid reasons why emissions should be stopped but nothing why they shouldn’t while the network is not functioning.
Are those comments from the same
worried about the functionality of the network?
6 Likes
Can’t wait for any of them to be released and to get a network where I can test them 
10 Likes
Well, I think that be a question to other folks on the team, however, without any emissions and uploads not working well at the moment, we won’t have such a large network size as the operators on the cloud won’t put up with the continuous instance costs at such scale (assuming a decent amount are on the cloud to begin with). We also wouldn’t have faced other challenging issues, which were discovered at scale. i.e Certain assumptions about the network were proven right and others were proven wrong as well at this scale to our surprise.
I don’t recall at the moment. I have been too absorbed with uploader and downloader services (multiple flavors) and monitoring solutions for them internally, which get us more visibility with the help from other members off the team. These services would be auto deployed for dev, staging, and production once the PRs are done, and give the team a more consistent real-time view off some of the data that lives on any given target testnet including production (i.e. random and non random sampling via downloads off previously uploaded data etc (time series)), and tracking a slew of overall metrics associated with uploader and downloader activities.
In addition, team is working on integrating the full suite of different simulated node types on DO (every increasing coverage and simulation for what an environment may be like for an end home user behind a router, granted we are not limiting or throttling bandwidth here (not yet at least 
):
- full cone nat node
- port restricted cone nat node
- random symmetric nat node
- upnp node
- public node (no nat)
Some of the environments above have already been implemented, while for the rest of them, the research phase aka POC is already complete, and just requires the final end to end integration in the orchestration process of the infrastructure pipeline (mostly to be implemented by Chris and Roland).
There is also on-going work on migrating away from ELK7 to ELK8 as well (recently started).
As you can see, this is just from one team member’s perspective, and there is a ton of other action items being looked at by everyone else simultaneously. 
14 Likes
You are getting to the heart of the matter here. I really don’t want to repeat myself yet again but WTF can’t we change emission rates that would appear to do more harm than good?
And this was why I had hoped we would have a proper (official) ticketing system where each “complaint” was logged and its root cause assigned.
The negative comments about not earning - is this due to a misconfiguration of nodes or just someone moaning that their tickets do not come up in the lottery as often as they would like?
Is this tech or just moaning?
And BTW a proper ticketing system - which I was assured was going to happen - would have simplified and codified the troubleshooting process for LaunchPad, antctl and likely Formicaio and anm as well - possibly even to the extent that in many cases just filling out the ticket form would have revealed the solution before human eyes needed to look at it.
1 Like
When there is a little more time can someone expand on what was proved right and was wasn’t?
4 Likes
I’m guessing this will help shrink the differences between test environments and real world environments?
3 Likes
Yes, it should in theory, though it can’t meet all edge cases (not possible). However, these types of network connectivity methods are the high level category off the type off network found at folks’ homes for vast majority of folks out there.
It will also help simplify the ultimate end solution (as team drifts closer to its final specifications) on the bootstrap sequence off antnode. Team should be able to test that out under all these conditions and see how it performs as well, which will be a huge benefit in validating the PRs around it.
In addition, it helps us test out even nodes that require relay assistance in these different environments, and whether connectivity has succeeded or not via a proxy relayer etc, and if PUTs or GETs are working against that relay node and payments are being received or not etc.
8 Likes
But it they are waiting it out like the rest of us, why dump ANT?
4 Likes
The only issue I have right now is a working network. After that folk can scream and shout about emissions all day every day for infinity.
A working network really should be 100% focus right now. That and only that will get us what we need to have a whole capable team of engineers and the business teams able to get moving on all fronts.
If we don’t get a working network asap then the games over. Simple as that
Turning emissions up to max or stopping them completely won’t fix this. We have to keep those emissions screams out of at least one single shaggin thread so the engineers can get some feedback that’s not a constant drone about something that won’t fix the routing tavlea api or dead nodes.
Just one single thread without all this constant persistent singular obsession would be wonderful and helpful.
It’s Chinese torture now and it’s just a total waste to have it in every single thread in every single place every single day to every single team member who shows up at any location.
Can we just stop it for a while and get the basics working at scale here please
19 Likes
@dirvine I think the issue is that people in this forum don’t know what to do right now to bring this project forward… So what they do is trying to help out where they think they see an issue …
- Marketing is in slow mode because of the network issues - no point in pushing hard here on other communication channels while we have upload issues
- It doesn’t make sense to interact with the network that we have right now and just waste eth on fees…
- Setting up your nodes as a hobby is done within 5 minutes and there’s no point in trying to get rich with node running if you don’t have your own data center with spare capacity you can put to work here …
… I don’t think it’s hostility at all… It’s the annoying crowd that eagerly tries to help …
People have been told “it’s happening” a year ago and since then there’s not much to do in this forum anymore… The team is busy fixing stuff and we have limited toys to play with…
11 Likes
You are spot on and the team also has that pressure but they have nobody to slaughter to the gods if emissions 
9 Likes
Have @neo assign each team member an anonymous, unbannable account to troll forum members with?
8 Likes
noooooooooooooo please no 
9 Likes
I honestly believe the emissions screams from everyone here are with the best intent to get us to a working network but it I hear you 
9 Likes
Or just one single thread where the personnel who are responsible for the emissions debate about it with the community. Then everyone else can focus on other things.
Note that I personally don’t have very strong opinions about the emissions.
4 Likes
If someone makes me Moderator I can program a bot utilising a local llm to decide if new posts are about emissions and just move all posts about emissions in one large topic
(I just hope this is a temporary issue and therefore I’m not sure it’s worth the hassle =D but then again… It’s most certainly a pretty simple task… )
5 Likes
Wow been out all day just settled down to read the update and I can see you have all been busy
@Shu thanks for sharing really enjoy reading your posts.
@dirvine I promise never to mention emissions again 
Well done to all the team and thanks for all the hard work
11 Likes
Codeword: lollipops 
going forward
9 Likes