@joshuef Here is that “stretch rewards” after about 5 hours (started nodes about 20 minutes after OP) For the nodes started with the launcher
Also I have to note that the error rate (on the device started with the launcher - starlink) at the beginning was very high compared to previous betanet using --home-network. Like 20 times higher than beta net after only 10 minutes in the many thousands. After 5 hours it seems to have improved with it being 17,000 to 30,000 on the 30 nodes on starlink
Nodes working now. How do I get rid of inactive ‘added’ nodes from the display? Ctl-X doesn’t do anything and ps aux | grep safenode doesn’t find any services named safenode1 or safenode2.
…but tbh it’s not 100% intuitive yet … tried to set my discord name with [capital] D … didn’t work … wanted to set resources with [capital] O … didn’t work either … i did recognize it’s non-capital letters … but for starting nodes it’s correctly shown … (and yes nano does this too … but i think it’s misleading there too …)
i don’t see how i can remove single nodes again (because my internet speed is a bit limited … just wanted to test adding a couple and now they’re there …)
same here - per 5gb it’s possible to add one node?
This is a good question for the launcher, how does the launcher decide which mode to use for connection and how can we find out @joshuef
I want to use port forwarding and not uPnP, but cannot see how to make the launcher use port forwarding and the ports to use.
@Dimitar I am guessing that the launcher tries uPnP and if that doesn’t work then home-network. I doubt it will do port forwarding since that is more a expert user who is likely to use node-manager or run the nodes directly and will port forward that way. So there is no point in adding port forwarding to the router if using the launcher
If you run safenode-manager then good to start with port 12000 or start above that
I’ll try it shortly but another point is that Ctrl- is not intuitive either. Dare I point to vdash?
If this is for ordinary folk it needs to avoid Ctrl or other combinations, and not set traps. Those menus in JPL’s screen shot cry out for people to try clicking them, and will confuse the hell out of users who don’t use the terminal. (At first I thought they were part of the launchpad UI because I don’t have that in my terminals.)
Testing it on us is also not a great way to find out how useable this is for non technicals so I hope ordinary folk are being included to weed out less obvious barriers.
How do I get rid of inactive ‘added’ nodes from the display? Ctl-X doesn’t do anything and 
…)