<3 <3 <3 my patch for whitelisting some #dex protocols is getting a lot of love <3 <3 <3
Thanks a lot for spreading it around @dietrich and @andrestaltzhttps://twitter.com/dietrich/status/950811946432872450 …
-
-
Replying to @soapdog @andrestaltz
Thanks for patching! Now we need to write some example WebExtensions that take advantage of it...
1 reply 0 retweets 1 like -
Replying to @dietrich @andrestaltz
Already building them, this thread is before the patch was accepted: https://viewer.scuttlebot.io/%25csKtp9VmxTjJoKy17O7GA6%2F3S8ou9Y9XLi8pZ%2FQgwKs%3D.sha256 … (I believe you'd love scuttlebutt my friend! join us! :D)
1 reply 0 retweets 1 like -
Replying to @soapdog @andrestaltz
I will! What we need to make are example starter extensions for each protocol, so that p2p web experimentation is zerobarrier.
2 replies 0 retweets 2 likes -
Ok, I’m scuttling. Such a sadness each time I have to download an Electron app and give it the keys to fucking kingdom, instead of having web-level security.
2 replies 0 retweets 1 like -
Full open source though ;)
1 reply 0 retweets 0 likes -
-
Replying to @dietrich @andrestaltz
Everything is open source, including the electron based apps. There are non-electron solutions where you run a local nodejs-based server and open the interface on your browser of choice as well.
1 reply 0 retweets 1 like
I’m talking about Electron apps generally. The “sure, whatever” permissions UI of Electron apps is worse model even than mobile apps, where at least constraint-based permissions systems are used, and enumerated on install.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.