News for hackers. Stuff that matters.
Re:Extensions in Firefox 59 by fenwick67 on Friday January 26, 2018 @04:35PM (#16243090)
Maybe I'm reading this wrong, but it sounds like they've made it so you can develop a webextension that handles DAT:// or IPFS:// URLs. They didn't make IPFS:// URLs redirect to http://ipfs.io/ipfs/$hash.
Re:Extensions in Firefox 59 by classichasclass on Friday January 26, 2018 @04:57PM (#16243221)
Sort of. I think this is based on the `registerProtocolHandler()` means, and if so, you can redirect this to an internal page in your extension. See https://addons.mozilla.org/en-US/firefox/addon/overbitewx/ (disclaimer: authored by yours truly).

The more pressing concern is how you would speak these protocols because there's still no direct socket support. In my case, the addon just acts as a history and redirect shim and my server does the actual server access and translation. I'm actually thinking of cobbling together a native messaging-based extension as a stopgap since obviously this is suboptimal.

Re:Extensions in Firefox 59 by soapdog on Friday January 26, 2018 @05:50PM (#16243541)
Hi, I did just like you said using Native Messaging API[1] to communicate with a local companion app using standard input/output shell calls, this app can handle the socket communication, that is how I am handling it for the scuttlebutt experiments I am doing (I mentioned them above with some URLs if you want to check), I hope to start a conversation soon on the add-ons list about the needs of having UDP and TCP available for WebExtensions. It is suboptimal but it works today...
Re:Extensions in Firefox 59 by classichasclass on Friday January 26, 2018 @07:41PM (#16244127)
Is this bug 1247628?
Re:Extensions in Firefox 59 by soapdog on Friday January 26, 2018 @08:05PM (#16244221)
oh! I was not aware of that bug! thanks a lot for pointing it to me, I will add myself to the CC list there and join the talk.
Re:Extensions in Firefox 59 by soapdog on Friday January 26, 2018 @05:54PM (#16243554)
They made that before that protocol was on the whitelist, now they could ship a native app that has a webextension bundled with it to handle all of it without using that redirect.