Pre-Dev-Update Thread! Yay! :D


#1999

This looks pretty interesting for todays update! :slight_smile:


#2000

Love this thread :heart:

Hope for anything nice!


#2001

3 more sleeps.
252dd612c8ab75c50f5b79a823196a6fb9879768_hq
@starsmick I know you feel it :wink:


#2002

yes its 3 nights still thats alot…, but good to know that Im not alone counting until next update:wink:


#2003

looks like there is will be some info in todays update about the scalibility , as in github there is a new commit with details


#2004

Tomorrow we will see the first testnet? :smiley:


#2005

sorry but no chance… still alot of tasks to be done according to jira, not sure why those are still on hold tho.


#2006

I think those tasks are not up to date …:sunglasses:


#2007

I wish that was true but I dont believe it, even the task mentioned in the last update is paused- https://maidsafe.atlassian.net/browse/MAID-3282


#2008

Just a bit of context for why this task is on hold: this task had been picked up by Qi as the task he was working on (MAID-3870) was blocked by a PR from Adam (PR 232) that introduced some significant changes to the code. Currently, our main focus in the PARSEC subteam is on performance and since MAID-3870 is tackling a performance issue, Qi picked it up again as soon as he could. We still have a certain amount of work to do before we can call PARSEC ready; mainly on improving the performance as progress still can and should be made until it is completely usable for routing. (Then of course, there is also a number of malice related tasks + documentation and tests) but there isn’t a lot of uncertainty about it: it’s just about keeping going one day at a time and tackling the issues that there are. Of course, our velocity there isn’t what it used to be as we went from 7 pairs of eyeballs to 2 to 3 pairs of eyeballs at any given time as we are ramping up our effort towards the other aspects of Fleming.
Patience is key.


#2009

Last year you guys gave us the taste of victory when Parsec was achieved. The taste of victory is kind of addictive, I cheer for you grand master rock star wizards :slight_smile: and looking forward to when the taste of victory stays with us for eternity. Keep up the amazing work like you guys allways do and we will get there, relative soon!


#2010

I might have missed it mentioned earlier but why is this?


#2011

i think half the routing team is implementing PARSEC and the other half is trying to improve performance/speed of PARSEC


#2012

Actually it’s not exactly what BambooGarden is saying: half the team is working on Parsec with a focus on performance. The other half is having a holistic look at the routing design, focusing on some “big questions” to make sure we go into Fleming with a design that is proven to cope with various situations. We’ll communicate a bit more on this soon with some forum articles. Stay tuned :smile:


#2013

Great thanks for that guys, looking forward


#2014



SAFE Network Dev Update - January 31, 2019
#2015

any update today? 20char


#2016

Late ones are usually good :pray:t2:


#2017

Getting ready for app stores :thinking::crossed_fingers:


#2018

Hi @Nigel, there’s nothing firm yet but basically, yes.

As you’ll already know, the mobile authenticator is currently a P.O.C. and it’s sitting on GitHub. When it’s in a more polished state then we’d hopefully be looking at getting it on to the Google Play Store for Android, and for iOS we’d probably be looking at TestFlight (initially at least). That being said though, we might look at other options as well.

#dontholdmetoallthis #dontaskmefordates

Is that too much of a politician’s answer?

David.