Thank you for the heavy work team MaidSafe! I add the translations in the first post
Privacy. Security. Freedom
Thank you for the heavy work team MaidSafe! I add the translations in the first post
Privacy. Security. Freedom
If cross platform issues are genuinely slowing development and testing, I don’t think anyone would resent targeting one platform initially. If Linux can be that target docket containers or VMs could be used to give broader access on other OS.
My thoughts previously were that this wasn’t a huge issue at this stage. From the comments above, it sounds like it may be more of a thorn in the side.
My thoughts previously were that this wasn’t a huge issue at this stage. From the comments above, it sounds like it may be more of a thorn in the side.
It’s not impeding us as much as it seems. The underlying libs like quinn and tokio take most of that away, but now all of it. It’s not a worry too much though.
Careful Traktion, dangerous territory. I suggested this very thing as one of my first few posts in 2017 and was shouted down by the forum community.
I’m new to this community, so I fully acknowledge that this rant is likely based on a lack of knowledge or understanding about how the code operates. However, I was taking the alpha 2 browser for a test drive and noticed the following comment that gave me pause: " Sorry! Breaker auto-updates are only supported on the production build for MacOS and Windows. " Religious wars aside, what could be the reason for natively supporting windows and mac at such in the alpha stage, or ever? I could s…
None taken. I would not know how to answer that though. Features in place ~99% (we need to work out farming with a privacy currency), features in code ~99%, features integrated into Safe 95%. How many bugs left, who knows?
I am not even sure what the question means to be fair, what would the actual difference in time to launch. The phrase 90% of effort in the last 10% is close to true.
There’s the answer and we know as much as we did before the question
Seems from the outside that the main feature work is on the token - farming, spending, etc. It was one thing to say lets have a token and do this & that, but more work to implement it. To make it really anon, farming rewards fairly, spending it, and make it so its not sluggish.
Needs to be done though and important to get workable.
Well done on the progress, it sounds like you feel you can see more daylight now.
It’s getting there @joshuef last night did a thing! that cut messages down from circa 35,000 to 500 and indications on some runs we can get from 60,000 messages to approx 32, that allows cleaner logs, more efficiency and seeing more light. The guys have really pushed hard at this one and it’s paying off.
Would that be the AE back off?
Whatever it was, that’s a helluva optimization! Great work being done.
It’s a mix, but a big part is using a backoff mechanism when nodes are busy, so resend but with exponential delays (like CSMACD in ethernet). Mixing with Ae updates and we are giving nodes a chance. A nice thing though to see we could send so many messages so quickly although we shouldn’t do that.
I’m guessing this could reduce memory utilisation which was one of the puzzling features of the public testnets. An amazing optimisation regardless.
It is why blockchain cant solve the problem!
Thanks team!