I just noticed as I was perusing via the new SAFE Beaker Browser builds, discourse is currently parsing/removing safe: protocol links. such that when you add:
Iām on Chrome on OSX 10.9.5 , I have the blue link href but obviously in Chrome this protocol string isnāt executed , only proxy works with http:// and .safenet ending , I wonder what keeps Beaker from executing the hyperlink , they work in the address field but not inside the safenetforum page ā¦ must be a small detail .
Further Beaker is the only Browser that renders my page correctly , that is fully animated
Iām on chrome on mobile now, and itās showing the link as clickable.
@frabrunelle said discourse is updating their servers (which this forum is hosted on) which may be why itās giving you errors on older versions of chrome (for example, I just had to update my Chrome just to even be able to connect to this forum page).
EDIT: he just corrected me on this. Looks like we actually donāt know why itās doing this. Hopefully he can chime in
Yeh, it appears clickable, but the link is removed by discourse, as @frabrunelle notes below. (on which, awesome if they have a whitelist, @frabrunelle )
As for the animation question @000, @hdastwb had a likely explanation for this here .
not currently, but it should be possible SAFE Browser / Beaker just needs to register itself as a protocol handler for safe://
the way to do this is a bit different depending on the operating system. I think it might be useful to look at the source code of webtorrent-desktop (itās an Electron app, just like Beaker) to see an example of how to implement this.
Hereās the code that registers a protocol handler for magnet and stream-magnet (it works on Windows, macOS and Linux):
Have anyone managed to set safe:// protocol to be open with Beaker in GNOME? @frabrunelle or @joshuef?
I added an entry to the mimeapps.list and created the corresponding .desktop file, and when I click on a safe:// link it triggers the Beaker browser but it doesnāt open the URL.
This is an important thing to get working, and I hope we do. I love how magnet: links open automatically in your BitTorrent client when clicked, and hope we get this functionality built into the browser for safe:// links.
Programs usually ask if you want to set it as the default for certain types of files / links, and in my opinion a finished SAFE Browser should definitely be expected to do this.
Clicking a safe:// link on this forum or anywhere should automatically open it in SAFE Browser, ultimately
From what I researched so far, the .desktop file it generates is fine (this file is used by GNOME to launch it), but for some reason the URL passed as parameter to the Exec command (which correctly contains the %U at the end) is not taken by the browser when it opens. Iāll keep researching.