Sorry for my ignorance, but how can we get a notification like this for SAFE Network sites, when someone tries to get to a safe:// site with a different browser? Basically a popup saying a newb to download SAFE Browser with a link to it, like so: http://blockjack.io/
A little instruction vid how to set up SAFE Browser + SAFE App Node.js would help.
Alright thanks, got further, now I’m getting this:
npm ERR! Failed at the safe-app@0.0.1 build-safe-lib script ‘cd native/safe_app && cargo build --features “use-mock-routing testing” && cd …/…/ && cp -f native/target/debug/safe_app ./src/native’.
and
Tell the author that this fails on your system:
npm ERR! cd native/safe_app && cargo build --features “use-mock-routing testing” && cd …/…/ && cp -f native/target/debug/safe_app ./src/native
Rustup on ubuntu. Ill try 1.14 later tonight. Thanks for the help.
EDIT:
@hunterlester I installed rust 1.14.0 and still get this:
npm ERR! Tell the author that this fails on your system:
npm ERR! cd native/safe_app && cargo build --features “use-mock-routing testing” && cd …/…/ && cp -f native/target/debug/safe_app ./src/native
Good catch, I was still running version 1.15. Now I successfully ran the mocha test, thanks.
I tried the create_public_name example but the browser doesn’t seem to be aware of the request. Maybe I didn’t install it correctly. I can’t access its login page by entering the safe-auth:… url in the address bar for example.
I’m getting this error when running the create_public_name example:
What’s needed is apps need to register with the operating system as a URI Handler to handle the safe: uri.Since this is different across various operating systems and apps, a web search is the quickest way to solving this.
Ideally clicking a safe: link should cause the operating system to show a dialog asking which app to use to handle the action (including safe browser if it’s installed).
A similar example is mailto: links prompt to open your email client, bitcoin: links prompt to open your bitcoin wallet, etc.
Working on getting safe_browser up and running. If I install it according to the readme, upon running it appears to still be waiting for the external launcher and does not recognize safe-auth://home/#login.
I build beaker-plugin-safe-authenticator and place the contents of dist in safe_browser/app/node_modules
Now safe_browser is looking to import a module from beaker-plugin-safe-authenticator in app/node_modules but I think it’s looking for an index.js, which is not output by any of the three webpack scripts in beaker-plugin-safe-authenticator
bundle.js looks like react/redux code
api.js handles auth and ffi loader
protocols.js seems like it may need to be what’s imported but it requires modules that exist in beaker-plugin-safe-authenticator but not safe_browser
I’ll continue to tinker until I figure it out but I’d love help finding the way, just in case I’ve veered way off course.
[EDIT: removed dev username references so as to save precious reading time. I just switched to the commit that integrated beaker-plugin-safe-authenticator. I was unnecessarily complicating things. Thank you @DavidMtl ]
OK, I’ve managed to build SAFE Browser and SAFE App Nodejs now but safe-auth://home just brings up a message: This site would like to open a URL in another program
Clicking on Allow doesn’t seem to do anything, certainly nothing like the screenshot at the top of this thread.
How do I integrate the authenticator with the SAFE browser build, or am I barking up the wrong tree?
Sorry for the slow response. The intention is that any new CEPs would be posted in Request For Proposal within the Development category of the forum, however, it is likely that this would be discussed in a main forum thread first prior to posting. Just in case you hadn’t seen it yet, the CEP process is detailed in this thread.
EDIT TO ADD:
I do like the idea of the mentorship program, we get approached regularly about internships, unfortunately we don’t have the resources to deliver this just yet, but as we are constantly working on recruitment I hope that this will change in the near future. Thanks for your ongoing involvement and continued interest!
Sorry for the spam, if any of you still have the log files from test-12b, can you please check this thread and see if you get a match please. Just to help debug one of the issues from test-12b