Pre-Dev-Update Thread! Yay! :D

That was one of the reasons for introducing delete for SDs to free up resources. I gather that SDs require more from the nodes than immutable data.

2 Likes

Disjoint group implementation almost finish…

13 Likes

Not pulled yet, but on it’s way:

4 Likes

I hope I’m not spoiling anything :grin:

3 Likes

I try to remain calm on Dev Update Day but seeing all the activity on Github gets my heart raising. :wink:

9 Likes

The SAFE Launcher arrived at version 0.9.1


SAFE Core at version 0.22.0


SAFE Vault at version 0.12.1

7 Likes

Wasn’t this the one being used the last week or two? It’s the one that’s being recommended in the email tutorial, however long ago that was released

1 Like

It actually was a typo in the changelog. Should be corrected now to 0.9.2. Sorry about that.

2 Likes

Safe core arrived at version 0.22.1

SAFE Launcher updated to version 0.9.3

11 Likes

Quite some routing PR’s ready to be pulled:

11 Likes

I’m gonna be the first one to like today’s dev update!

EDIT: FAIL.

2 Likes

This got merged today:

This will be next according to the dev-update:

10 Likes

I’m reading through these github updates posted on the pre dev update and updates here and thinking do we have a list of all these features and what they do in plain English? A lot of them are just weird titles that don’t make sense. So really to understand the implications of each of these new additions of code we need to understand the function in plain English. Then how can that code be taken and turned into something the user can manipulate using an app or something in practical terms?

2 Likes

Yeah the big thing it looks like I’m (along with anyone else interested in making apps) waiting on is the new switch from SAFE Launcher to SAFE Authenticator.

This will completely change how apps interact with the SAFE Network. So we need this to be finished, in order to make apps.

I hope this doesn’t take a very long time, and is a quick change (ie. not as big as the rust change), so anyone wanting to work with SAFE can get going again soon.

I’m also working on a website that teaches people everything you need to make a SAFE app in the easiest way, but this will need to be updated once the Authenticator changes are ready

Any estimates on this :clock3:? @frabrunelle ?

4 Likes

Yeah, I want to make apps, I’m constantly coming up with ideas and seeing the implications of the SAFE network but wrapping my brain around the code is the hard part.

hmhmmmm - do you think this will change the systematics of how apps can run via safenet …?

because i’m a little bit confused … if it only changes the way apps sent their commands/data … this rework would only mean that the safeAPI-wrapper would have to be reworked too and nothing else would have to be changed in terms of app-code …? ( @frabrunelle )

1 Like

Well I’m wondering if they strip down the launcher where are all the features the launcher currently serves going to go? Will we need a seperate app to run all those features or will they be intergrated into the demo app?

They will go in the trash and be handled by a new “language binding,” (see update) since the authenticator will only be handling authentication. It’s a great change, will simplify things a huge amount for the end user and most importantly allow SAFE apps, browsers, sites etc to start working on everyone’s mobile devices, so I’m all for it, but apps will need to use a new language binding instead of the current API through launcher.

1 Like

It depends. Their idea is to do all permissions check within the network itself and change the launcher for a simple authenticator instead. Apps would then talk directly to the network and no longer through the launcher. Their goal with these changes is to be able to support mobile platform which wasn’t practical with the launcher concept.

For web apps that runs within the Safe browser it should not change a lot. The browser should continue to provide an API for web apps to use. For native apps it’s different, their idea is to provide safe_core libraries in a variety of programming languages and require native apps to use them instead of the REST API. It isn’t clear if they are going to still provide a REST API within the new authenticator or through some other apps.

You can see the discussion in the dev forum.

5 Likes

I’m glad to hear the launcher is getting an update, but am honestly a bit disappointed that vaults have not been the primary push. A new launcher/authenticator is great news but doesn’t do much good if the vaults are not in order.

I know there are a lot of users waiting to see if proof of concept for vaults that can work outside of the droplets on a larger scale…

5 Likes