I forgot this convention when I first setup my instances (though I'm also not sure of the reach on a single user instance).
I develop privacy features for Cliqz and Ghostery browser extensions and Apps, and helped to build the whotracks.me transparency tool.
I'm also interested in the p2p web, specifically DAT, where I'm pushing for dat:// protocol support in Firefox via the dat-fox and dat-webext browser extensions!
Fun find today: we were getting errors from our code only in Firefox dev edition and up, and also only when the devtools were opened. So obviously I had to make a page that detects when the devtools are opened or closed!
(open in FF dev edition or nightly)
Bugzilla ticket is open: https://bugzilla.mozilla.org/show_bug.cgi?id=1545400#c2
Nice writeup by @darius about Dat, SSB, and ActivityPub and how they can learn from each other: https://blog.datproject.org/2019/03/22/three-protocols-and-a-future-of-the-decentralized-internet/
Indeed, my post-standardization of ActivityPub work (on Spritely) has largely been about exploring similar thoughts! See also the @librelounge episode with @joeyh where we talk about Secure Scuttlebutt (esp in relation to ActivityPub) https://librelounge.org/episodes/episode-14-secure-scuttlebutt-with-joey-hess.html
And yes, Firefox is still fighting a huge uphill battle against Chrome interop, and I have no idea how they're even able to keep their heads above water. They need all the help they can get, because they're battling stupid bugs like this every single day.
WebKit (Safari) is no less amazing for the comeback they've pulled off in the past few years, although they have fewer interop pressures. Web devs make sure their sites work in Safari, because the CEO has an iPhone.
Had a very interesting chat today with Sebastian from Mozilla who's working on their android components project: https://github.com/mozilla-mobile/android-components
If you want to make a browser for android, this is the place to look. Well written, well-tested, modular and composeable components covering all of the different parts of the browser. This will make making browsers and browser-like apps much easier!
"Why should I use a Reverse Proxy if Node.js is Production-Ready?" by Thomas Hunter https://medium.com/intrinsic/why-should-i-use-a-reverse-proxy-if-node-js-is-production-ready-5a079408b2ca
Really well-written and interesting post. I appreciate it has a benchmark to back up the performance argument.
Thank god the entire industry hasn't decided to revolve around Blink/Chromium for 95% of the web's browser traffic, or else Google would have an unlimited ability to push forward whatever bullshit standard they wanted.
Wait hold on, my producer is telling me something [places finger on my ear piece]
Been writing up how basic Dat support is implemented in Firefox with dat-fox:
Next post will be how dat-webext fixes all the shortcomings that dat-fox has!
“These companies are unavoidable because they control internet infrastructure, online commerce, and information flows. Many of them specialize in tracking you around the web, whether you use their products or not. These companies started out selling books, offering search results, or showcasing college hotties, but they have expanded enormously and now touch almost every online interaction. These companies look a lot like modern monopolies.”
BTW, you can now browse `dat://` archives using Datmobile on Android.
The performance has been shown not to hold for adblocking extensions (https://whotracks.me/blog/adblockers_performance_study.html), and there are many other problematic webextension APIs w.r.t. privacy.
The solution to these issues should be institutional, not technical. Google should impose performance constraints on extensions, and audit what data extensions are sending home. However, looking at the rampant malware on all their stores, this is something they're unlikely to do, so instead they'll nerf extension's capabilities.
Disagree with this article's thesis that the Webextension webrequest API should be removed.
By moving to a declarative blocking API you are limiting the possible ways for extension to function to blocking and redirecting. This is a very narrow use-case, based on the current prevalence of blocking extensions.
But this is not the only way to solve problems such as blocking ads and improve privacy, as shown by privacy badger and Cliqz' tracking protection.