MaidSafe Dev Update - May 25, 2017

Just take it slow - its actually very well written, clear and concise with fairly simple vocabulary.
I’m not going to kid on its dead easy but mostly what it is is new and different from the problems network engineers/architects normally have to deal with. It’s not mind-blowingly complex, it just requires a little patience and logic and constantly reminding yourself “These are the ONLY rules/actions that this node is capable of following/performing to accomplish the task.”

Dunno if that helped or if I made myself sufficiently clear but I’m knackered, its hot, I have a cold beer and a seat in the garden beckons - That’s yer lot for now :slight_smile:

EDIT: Oh and +1 for clean slate between testnets

2 Likes

Indeed a second read has helped and I am sure after 2 more I’ll be in a better place. I think it was the amount of information that caused an initial overload. Needed to unplug and reboot.

Is the thought process not to encourage more development?
Been said (somewhere) that folks are reluctant due to wipes… catch-22?

1 Like

Not really. One could easy re-upload it as long API is not changed. If it is breaking changes, then yes, it needs to be modify. But for now, there will be a lot of breaking changes. Once we hit Beta, that’s when code becomes more stable, and leading to less repetitive development changes.

0.0.0

First digit version is major update breaking changes
Second digit version is major changes with no breaking changes.
Third digit version is minor changes with no breaking changes.

I think we should follow this suit to keep us inform if there are breaking changes or not.

4 Likes

I get that but what do you think the motivation behind the idea is then, surely it’s not simply to save everyone from re-uploading their stuff. There must be more substance to the thought no?

1 Like

I don’t care about data until beta. Between now to Beta, all data will be lost period. Datachain that is being implemented, will have faulty issues too. In the end, we still have to re-upload it until datachain becomes stable.

3 Likes

:grin: ok well I’ll be the lone ranger that’s thinks it’s a good idea and may attract more users to the tests.

4 Likes

Not denying that. I agree that implementing it right now would attract more users, and more testing. That’s a good thing, but I’m just stating the facts, it will fail in the next several or more testings.

4 Likes

so we will have to rip it up and start again

3 Likes

So a Blockchain, huh :slight_smile:

Pity we wont be able to call it chainless anymore. I liked the sound of it.

Anyways, great update! I appreiate them even if I get lost every now and then. Data chains I havent spent much time on yet, guess now is the time to catch up. Nomnom :fork_and_knife:

2 Likes

This makes me wonder if individual data chains will grow to some huge size like the blockchain Bitcoin has or will they reset at some point?

2 Likes

Aren’t they decentralized / spread out?

1 Like

David responded on another question HERE about Data Chains and it looks like option B might squash my question. :slight_smile:

5 Likes

Data chains are very different to blockchain, for example only about 20 steps (blocks) will need to be retained by most vaults.

8 Likes