Now that we have a clean slate on the Network I wanted to propose this thread as a central location for websites, email IDs and the wealth of exciting things that will no doubt populate the Network in the coming days and weeks. I am hoping that this will act as a shop window for anyone new to the SAFE Network but also a great resource for anyone who wants to show it off to their mates.
safe://jams.demo is back but the Easter egg isn’t present in this version. That can be accessed at safe://jams.jammed and once in the player, click on the JAMS logo at the middle top, controls are Z, X, and left/right arrows.
It’s also worth noting that JAMS does not work with the newest versions of Peruse so SAFE Browser is recommended for now.
‘to-do’ works only on the Peruse >= v0.6.0 (which uses a newer/future Safe API), so it is normal that it doesn’t work on the Safe Browser.
I’m pretty sure it will work again in Peruse if you restart you computer or stop eventual Peruse instances which didn’t stop properly.
That’s an error relative to not being logged in. Login is not persistent between sessions. Go back to safe-auth://home/#/login and login and try again… should work but didn’t for me too… but a restart of persue; logging in; and then trying again does work - and shows previous item noted.
Safe Browser seems to through errors but then, looking quickly at it, I can’t see that it’s really affecting the noting of items.
Hey, testing out the new network. Everything looks really good. But even though I’ve authorized the web hosting manager and the email manager, they still say waiting for authorization. Is there any way to get around this? Also, is it possible to redeem a code for the same account even if our IP changes between sessions?
I don’t have time myself atm, but maybe somebody can split the lists into two showing min/max SAFE Browser / Peruse version for each list. The change comes in with Peruse v0.6 I think, not sure about SAFE Browser.
Purge legacy?.. I don’t understand why those are being retained. Expecting the latest browser and removing or noting those that fail on a browser upgrade - for then those to be fixed and un-noted as normal list item. So, I’d expect one to-do item above…
What’s the recommended way to create public names, upload - presumably not with the WHM PoC as that is creating structures that is not compatible with other apps which are doing this directly, and is quite likely to change?
Can you give us a list of SAFE Browser + Peruse versions that are compatible with each other, and the corresponding WHM versions, including links to the downloads? Also, what is different between them? I’m now quite confused as to what to use to create stuff on alpha2:
for things I uploaded previously. Should that all still work with SB 0.10.2 and if so which WHM to use?
for the latest stuff I’m working on now with Peruse >= 0.6, which WHM should I use?
BTW, I suggest this could be turned into a useful resource here:
The main incompatibility lies between the POC apps and the previous range of versions of SAFE apps. Not sure about the exact incompatibility issues though.
Peruse v0.6 introduced the NodeJS based DOM API, so apps made for that will not be compatible with any SAFE Browser (and vice versa). The latest version of the SAFE Browser still contains the Beaker plugin API.
Looking into the future: I assume MaidSafe will not focus on the older applications anymore, except for some bug fixes perhaps. I just noticed MaidSafe moved the Web Hosting Manager into a separate repo recently, so everything might become more structured soon.
Thanks @bzee, I was aware of this but want something official because we aren’t privy to Maidsafe’s plans. I would have assumed we should be using Peruse 0.6+ and whatever the compatible WHM is for new stuff and updating old apps to that new API so they to can use those, but @joshuef was just suggesting digipl should use the WebID PoC WHM so I’m unsure. If I understand it, that will produce public names in a different format than any old app including the older WHM. I may be wrong though as I’ve not looked at the PoC code. So best if Maidsafe clarify I think.
In the mean time I will probably use the older apps to create public names and upload, but build my code for then new API.