Pre-Dev-Update Thread! Yay! :D

[KafkaLee]

I am so so excited! and eager to use testnet David!

[Josh]

@dirvine

I wonder what happens in 2022 when this thing lives?

Was that there a release date

@dirvine

we have not been as focussed on data and stable data under a churning network.

I wonder is it better that a community test is not built always-joinable to have less churn.

[dirvine]

@Josh

Was that there a release date

more a relief date

@Josh

I wonder is it better that a community test is not built always-joinable to have less churn.

I think it makes sense to use default here and not have always-joinable set as then it’s more real-world like. Also would reduce churn I imagine. So I would say yea, don’t set always joinable.

[bridge]

Hat off the team.

[Nigel]

@dirvine

formally correct

very niiice

@dirvine

CRDT memeberhip via simple Set’s using a supermajority over supermajority vote to allow nodes to join or restart. That will solve a lot of silly inconsistencies we have and also allow onboarding of new nodes to be simpler (merging set’s is a trivial thing to do and as they are sets of trusted signatures then they are already self validating).

This is new and sounds neato. CRDT everything.

[Guybrows]

@dirvine

2022, I wonder what happens in 2022 when this thing lives?

Is that a promise?

[Guybrows]

@dirvine

The guys have really pulled it all together with amazing speed and done that with a 4 day week, hardly any management and in the last 3-4 months almost zero direction from me, they have worked with each other and just got shit done. to every single person in the team and on this forum. It’s been tough, it’s not over but I hope we can all see it more clearly now. With @JPL making the docs simpler, much more descriptive and digestible I hope we can onboard many projects and apps in the very near future.

A factory I do some work in kept only production staff onsite during lockdowns. The productivity and output hit record highs. Go figure.

Well done team Maidsafe.

[Zoki]

@dirvine

more a relief date

[aatonnomicc]

Safe Network v0.50.0

What a beautiful release number

[MrKeepingItSafe]

This is it.

We are going to see all the hard work pay off this week

[nos]

@dirvine

focussed on entropy instead of time and strict order.

COOL_COOL

[Southside]

The agogometer is carefully extracted from its silk-lined case, polished reverently with a swans neck dipped in Bruichladdich, licked clean and precisely positioned on my desk.
It quivers gently under my touch, thrumming with an inner power and passion…

[Zoki]

BREAKING

LIVE, from MAIDSAFE HQ.

It’s looking like it’s going to be a great Christmas holiday!!

[happybeing]

I like this…

feat(client): add a Chunks cache on client API to prevent retrieving an already retrieved Chunk

[Sascha]

I’m puzzled by the fact that the latest release of “safe_network” is called “Safe API v0.46.0”. I’m probably just being ignorant.

Releases · maidsafe/safe_network

[joshuef]

Ha, we’re puzzled as to why that’s still latest release. there’s like 4 after it . Github is being odd…

(if you do know why it’s doing that, do please shout!)

[upstate]

@joshuef

Github is being odd…

Everything running off AWS is acting odd and sporadically today it seems.

[joshuef]

does github use aws? I’d have thought they were on azure

[cryptonewsday]

Might apps use AWS?

Our till (working from an app on an ipad) at work reverted to a different version today, we had to delete it and reinstall to get the right version. Yesterday another app I use had a very different design for a few hours or so, then switched back.

I also read recently that a vulnerability had been discovered and published which could affect a very large number of websites and apps, and I think it was related to the hosting architecture, so part of me wonders if there’s some connection.

[upstate]

I shouldn’t have said “running off” as I doubt it is completely on one service, but with everything so interconnected I bet it’s playing some part in the issue. Just so many damn strange issues today and nothings consistent.