MaidSafe Dev Update :safe: 15th December 2015

Getting place, mitic thread! Thanks for all!

7 Likes

Keep up the great work :smile:

6 Likes

step by step
keep slayin+

4 Likes

Oh mama! Perfectionism at its finest! I love to watch the manifestation of clean high quality products. Send the bar into orbit. With the leadership of SAFE, so many other projects will scramble to achieve a similar level of refinement. These are interesting times indeed.:smile:

7 Likes

Great work! Congrats for the working routing example!

5 Likes

Thank you! I’m cheering for you all.

5 Likes

Patience is a virtue guys.

2 Likes

I’d just like to know who these “guys” are that have been questioning the team’s commitment and putting pressure on them to speed up. I think all the opposite has been repeatedly stated by those calling for rough timescales. Most of those asking have already expressed that they were “satisfied” early in the previous thread with answers received from team.
Patience may be a virtue, but constructing straw men isn’t. There was a communication issue, not an impatient, hurrying up, pressurizing issue as far as I can see…not virtuous at all :smiley:

4 Likes

You will gain patience when you see the vision.

The dev team will gain inspiration and fresh resolve when they see the yum-yums.

YOU can make this happen…
https://www.greggs.co.uk/greggs-gifts/

4 Likes

I want to highlight this so it is not misinterpreted (e.g as “launch”). This is an indication that the Rust-5 deliverables are currently weeks away - that’s a first public test network. I think this means something like what we played with earlier but with everyone participating in one public network rather than in isolated local networks.

@al_kafir I think you are overlooking the reasoning I gave about pressure - that calling for timescales can itself create pressure, particularly when it becomes a chorus, and in some cases more than just asking. Also, that providing timescales certainly does create pressure, especially when, as currently, it is very difficult to estimate reliably.

I hope you and everyone can see from this update that some of the team do currently feel under great pressure because of this overrun. We’ve already seen how this can be unhealthy for the project because it seems to have been a factor in what caused this delay, and obviously can be unhealthy for the team.

To All At MaidSafe

I’d like to say to the team that I know you are likely to work extra hard in this situation, but my experience that is not in your or the project’s interests if it goes on too long. So be willing to take a pause when needed, and carry on doing the great work on this amazing project. And thank you all for all your work and good humor.

6 Likes

No, I saw it… :smiley: The thing is, lots of things can create pressure for devs …every step of the way has been pretty pressured. Your posts on the other thread were also well after things had been resolved to mine and others satisfaction I think.
I’d say your “reasoning” seems not so much reasoning, as opinion really…Do you mean the devs have conveyed to you that they feel this is an extra needless pressure some members of the community are unreasonably putting on them - or is it just opinion, I mean?
If just opinion, then I could just as easily “reason” that directly requesting that the lead dev comment on various other projects etc is a distraction from the project and pressures devs to answer.(I don’t think that) - I don’t see any difference…it is just opinion. I’d choose not to make an issue of my opinion though…especially as I have no clue in all reality how pressured this makes devs feel. I would trust that the devs would PM or make their discomfort known themselves if this were the case.[quote=“happybeing, post:14, topic:6360”]
Also, that providing timescales certainly does create pressure
[/quote]
It would appear the implication/inference/basic premise is that this pressure is either created for no reason or for specious reasons. Some aspects of creating a new internet thingy, create pressure, some un-avoidable and necessary - timescales is one of them I think.
Your reasoning appears flawed to me in any case:… :smiley:
To continue not addressing the issue would have caused the issue to fester and for FUD to proliferate - I believe we were close to that point - trolling had started. The people who raised the issue, brought it into the light to be thrashed out and the issue was pretty well resolved quite early on in the thread. Where would we be now, by not asking questions?..I shudder to think…lol… :smiley:
Edit:

The fundamental issue to me mainly boils down to the Natives getting restless due to feeling uninformed. As I mentioned previously, the communication issue appears to be much less of a problem for “coder” Natives. I don’t think this is very surprising as coders have a good grasp af what is involved and understand progress being made.
I say I don’t find it surprising, because if I were to invent a similar “Decorating tech thingy”, I would be surrounded by decorators all talking about and understanding decorating; the tendency would be to inadvertently neglect to clearly explain things to the other non-decorating users
It may be all about devs presently, but if Safe Network becomes widely used, then the proportion of devs to non-techie users will be miniscule. It’s going to be all about the non-techie users eventually. At this point, the non-techie investors need to feel informed too – by simpler means that following Github etc. Hopefully, the new roadmap will be clear and include layman’s terms and rough timescales. :smile:

1 Like

@al_kafir I’m going to respond to you by PM because I don’t think we need to continue this debate here and doubt anyone else is interested in continuing it. I’d rather leave it too, but I want to explain to you why I disagree with what you’ve posted here. If anyone is interested, we can always invite them to the PM.

EDIT: In response to @iJRN’s request below I’ve resonded in public here: Developer Update Timescales Discussion

3 Likes

I am interested, please keep the conversation public. @happybeing @Al_Kafir

3 Likes

I don’t debate by PM anyway. :smiley:

4 Likes

4 posts were merged into an existing topic: Developer Update Timescales Discussion

chorus

Agreed. I’ll also add, it seems to me that @Al_Kafir is talking about those (new?) users whom I suspect have freshly invested in some Maidsafecoin. Then this hypothetical speculator creates an account here to ask “When is this going live?”, mostly from a speculation/forecast launch perspective for profit, less so from a buy-in to the whole project/vision perspective, that is until one of us inevitably replies with a patient even toned comment, letting them know that revolutionary software takes time to build, test and launch successfully.

3 Likes

Good evening people,
Another great update.
I started investing in the coin march this year and my analysis at polo shows I would break even selling at 7380 and with nearly one million coins I could be looking at more than 50% loss at the moment. Now I don’t assume I am an investor in maidsafe as I didn’t buy them in the crowdsale, but I offer my moral support and wish devs the very best. sofa.

5 Likes
2 Likes
4 Likes