Just want to take the opportunity to the importance of listing features when large releases are made.
For example as of last week safenetwork.tech did not show node aging complete. Before reddit took down the posts about baby Fleming one person commented something like “Fleming sounds interesting but what does it do?”. It would be good if we can shout as loud as possible about what features large release have, on twitter and so on. Just a simple list of what features baby Fleming and other large releases contains. We need the world outside this forum to know more and more about SAFE. I understand that the pace have been high lately and focus have been to just get the baby crawling, but it would be good if we could also shout to the world that the baby is crawling.
@happybeing I tag you as this post might be of interest.
Definitely. It’s not within the scope of what the company does now though. But it’s what @Sotros25, @andyypants, @TylerAbeoJordan et. al. are working on. They’ve got some really good things going on on that front.
Updates like these are of lower priority than before, but I think that maybe @frabrunelle or @StephenC, might be able to squeeze in more of that. It’s up to them to prioritize though.
The guy seriously said that people saying “great progress” is FUD… in bold. I usually read people’s posts for the full argument when up for possible interpretation, but I am physically incapable of reading past such a completely incorrect on all possible levels statement. My body won’t let me do it. It’s so absurd that I can say I’ve never come across something so ludicrous as to disable me from reading something from a particular somebody ever again.
Yeah that’s what I mean… This guy is in a fragile state, he’s not even getting that right. It’s not much to see here.
But this is just a single case. There’s going to be a lot more of real trolling, and competent trolling… It will be proportional to the awareness of the project. So, this is really nothing.
Please be encourage to flag inappropriate posts as inappropriate, as that will cause the post to be hidden when 2 or 3 people flag it and alert the moderators to the need for potential moderation.
Please flag a post as inappropriate rather than responding as that doesn’t feed a troll or a narcissist who both do not see the criticism as valid. They will never see criticism as applying to them and thus you can get hundreds of posts/replies when trying to correct these people’s bad approaches to expressing their entitlement.
While this post to encourage using the flag feature, it will be seen as applying to recent posters, but it is only a general reminder to encourage people to flag rather than feed.
Am I the only one that finds gouda’s weekly pre-update and update comments vaguely amusing? I can never tell what exactly he’lll come up with next. There’s a certain inventivity to the gloom and doom, and then the way it’s surrounded by praise for the wonderdul maidsafe team, and encourgement and respectful polite questions, the contrast is a little teeny bit hilarious to me
you got me wrong I hope that this is right and the node aging part is finished, but from updates and github It doesnt seem to be the case, hopefully someone can clarify this.
Then do not ATTACK first then backpeddle when called out. Until then people will understand your attacks as attacks. Pretty simple, the ball is in your court, stop attacking
Ask for understanding why rather than attacking is what i am saying. Typically the team is not lying and the answer is usually a slow updating or misunderstanding on the reader’s part
We were slow updating a roadmap/timeline on the website. That probably did not help really. However the non stop negative perspective by that account is quite something. None of our code will ever be complete to the point of never being updated, but that account seems to live in a parallel universe where new innovative systems are created by following a flowchart and ticking boxes. It will never be like that, much to the chagrin of that account and some others to be honest. I have seen the “explain it in a sentence”, “you must know what’s left”, “it’s terrible management to not have definitive launch dates” and sometimes breaking it down to “Ok not full launch, what about beta/alpha/X/YZ” with the intention to extrapolate to a launch date and so on.
It’s a lot of uncertainty doing this job (problem/solve/repeat) and many don’t get it, the only way to succeed is grit and determination, the best way to fail, is negativity. I think it is really that simple.
8 - eight - packages updated in the last 24 hours on MaidSafe · GitHub
Now some of these updates may be more meaty than others but it all shows a project moving forward in an organised, purposeful manner.
You can help by testing whats been released, reading the docs, correcting typos or even tackling some issues that are flagged. If you feel thats too difficult for you, ignore your apprehensions, have a go anyway and call for help on the forum when you get stuck. Its an excellent way to learn AND help.
the github routing repo includes some open tasks from last year labeled node aging, apart from that wouldnt any update include information about node aging beeing completed? thats quite a news isnt it?
