Great news
And no one saw the mobile binaries coming.
And a fixed (alpha 2) release date whoa whats in that juice you’ve been drinking
Great news
And no one saw the mobile binaries coming.
And a fixed (alpha 2) release date whoa whats in that juice you’ve been drinking
You’re not alone, Savage. I’m running stock 6.0.1 and I’m having the same issue. I can install and when I attempt to open the Authenticator, it hangs for a few seconds and I get the “Unfortunately the SafeAuthenticator has stopped” message.
Yes, that’s what I get. I wonder if it’s because my phone has been ready for retirement (for a while now) Note 4. This may motivate an upgrade if that’s the case
Holy guacamole!!
I’ve had a long hard day, and check up on SAFE while on the train home.
I’m ecstatic! It’s amazing how the thing on everyone’s mind is alpha 2, and Maidsafe comes out of left field with binaries for mobile! What an awesome surprise. And alpha 2 next week!
Makes me so proud to be witnessing the birth of this uncensorable, fully distributed, autonomous supernetwork, from the (more or less) front row
Wow… I am having goose pimple reading all the updates and responses from the communities.
It’s so amazing and such wonderful surprise on the mobile binaries and ALPHA 2!!
Thanks maidsafe team for the hard work. Have a good rest!!
Very exciting and sensible, but also a minefield!!
edit: a nice list of difficulties to consider when using unicode: normalization forms, case mappings, derived properties, regular expressions, collating algorithms, segmentation rules, script property inheritance, pluralization and calendar data from CLDR, the confusables list, han unification criteria, the punycode nameprep algorithm…
Now that is unexpected. A mobile update.
Nice job, team!
this is shaking news !!! so you had an army of people working on it in a secret basement
Army of ants to be precise!
Am I correct in thinking that with the release of Alpha-2 next week that the forum user level -1 requirement goes away?
I doubt it, it would open up the network to miscreants, too soon, when not everything is tested.
They were not allowed their phones till it was working And not allowed to leave till it was done.
interesting, I can connect fine from Android ( 7.1.2 , lineage 14.1 ) , but only if I use the wifi network.
If I use the 4G mobile network, it says it is unable to connect to safenetwork.
EDIT : I forgot I needed to update my IP - it works nicely on the mobile network too
The invite code will stay for the time being, still an effective way of preventing spam pre safecoin.
Phone SafeAuthenticator status:
Andriod 7 - Installs fine and when I run it either from WiFi [2 differents ones] OR LTE it errors out with this:
That sounds like you haven’t got your IP address whitelisted. Did you visit the invite site and register your new IP address?
Also people need to remember that some mobile networks change you allocated IP address often. Some don’t.
My WiFi would have the same IP my Windows machines have.
But the LTE would have a different one, you’re right.
EDIT: However now I can’t get connected with the SAFE browser either, but earlier I could…same IP address since I registered.
Sorry I don’t know then, but maybe someone from @maidsafe can answer. Try reregistering your IP again anyhow. And force stop SAFE App on the phone before trying the phone again
Thanks for all the hard work to everyone in MaidSafe. Great job and really excited for the next Alpha.
Will it still have a limit of 500 POSTS?
Will it still be restricted to only forum users with a certain level?