That sounds to my ears like a pretty mashed up blend of English, Danish, Norwegian (I speak English and Swedish) and German.
They regressed from that to Estuary English? Or worse, received pronounciation…
That’s brilliant! As the guy says in the description, it’s not really correct, but I think it’s a great way of presenting the subject.
Quick update today - we’ve been fighting against a few last minute issues which are holding us back from releasing a testnet today.
Would you mind linking to these specific issues, if they’re on Github?
They are not on gh it’s running nodes behind NAT (igd) that is failed, not our crate, but seems a failure there. So investigating now with lots of us trying from lots of locations. It’s a PITA simple plain network issue, nothing worrying but a PITA for certain.
Is there any point in contiuing with profiling the sn_node performance?
These figures need to be taken with a huge pinch of salt anyway - its only one run on one machine.
If you feel there is any value then I would run the smaller tests say 5 times each and take an average.
|filesize||sn_node 0.48.1||sn_node 0.49.0||sn_node 0.49.2||sn_node 0.49.7|
Best bad news I’ve heard in a while, thought I was doing something wrong
Quick @Josh call it for tomorrow
You are a bad man, @scottefc86, a very bad man indeed
PITTA . . .
It’s just a Liverpudlian thing, or is Mancunian?
Not sure thers is a big difference
Careful or you will be a candidate for either a good kicking or remedial spelling lessons
NAT issues have caused so many bloody noses over the years for SAFE. Part of me wants to just bale on the whole thing and force node operators to learn how to forward a bloody port, just like so many other projects do. This would mean some sort of onboarding script that picks a random number, writes it into the config file, and then tells the user to open that port in their router, so we could still have unpredictable ports.
or use ipv6? just learned it doesnt have NAT
I’m still scared of IPV6. I now always disable it in my routers, after reading how so many devices have IPV6 vulnerabilities. I have a lot of random junk on my network, and don’t want to worry about what vulnerability each thing has.
Yikes! How big an issue is it?
But sounds like everything else is on track. Team flying high keep it going
Coming from you I’ll take that as a compliment
What are IPV6 vulnerabilities, can you explain in short why?
So tired of the IPV4 shortage of addresses an IP’s CGNAT.
My money is still on next week. And next week, I may have to cover that with money on the week after. But coming soon