I've removed google tracking from my website.

Firefox 69.0 :firefox: available:

mozilla.org/en-US/firefox/69.0

– Enhanced Tracking Protection will be turned on by default; default standard setting for this feature now blocks third-party tracking cookies and cryptominers
– support for the Web Authentication HmacSecret extension via Windows Hello
– various security fixes

#firefox #mozilla #firefox69 #tracking #etp #webauthn #infosec #security #cybersecurity

Fixed the sandboxing issues that dat-webext had on Mac and Linux. Now it works everywhere :). Looking forward to pushing dat support out to a larger audience soon!

@da That sounds like what coil (coil.com/) are doing. They also proposed a web monetisation API (github.com/interledger/rfcs/bl).

Didn't hear much about Flattr since the Eyeo acquisition, wonder how they're doing with the increased competition...

Just tested to see if I can put a dat:// URL into my Firefox RSS Feed reader extension. It works!

"You’ve to enable third-party cookies in your browser for Scroll to do its thing." ctrl.blog/entry/scroll.com-fir from @da

Interestingly, Scroll contacted us at Ghostery during their beta phase as our cookie blocking was preventing the subscription detection. I suggested a few ways they could implement the service without having to track all non-scroll users too, including a per-site login button, but unfortunately they didn't take up the offer...

First, [Google]’s continuing to argue that third-party cookies are actually fine, and companies like Apple and Mozilla who would restrict trackers’ access to user data will end up harming user privacy. This argument is absurd. But unfortunately, as long as Chrome remains the most popular browser in the world, Google will be able to single-handedly dictate whether cookies remain a viable option for tracking most users.

eff.org/deeplinks/2019/08/dont

The less time I have to follow hourly updates of things, the more I appreciate newsletters and RSS.

My colleague chrmod's fixes to tab and webNavigation extension APIs for GeckoView now landed in nightly! That means a load more extension use-cases will now be possible in GeckoView :)

A very nice writeup and retrospective from Feross about his open source project maintainer funding experiment. (The one with ads the in cli that caused a big stink.) For anyone involved in building, maintaining, or using open source projects it's worth a read.

feross.org/funding-experiment-

I reimplemented the libdweb TCPSocket API moving the actual networking to the parent process.
This should fix the issues with Linux and Mac process sandboxes blocking socket creation. Now to do UDPSocket too!

WIP branch: github.com/sammacbeth/libdweb/
Sandbox issue: github.com/cliqz-oss/dat-webex

Seems some of the issues dat-webext has with connecting to peers may be due to a lack of UTP. It is apparently the source of hole-punching magic in discovery-swarm and the new hyperswarm: github.com/hyperswarm/network/

Oh god...

All Chrome extensions can execute remote code in their own context:
bugs.chromium.org/p/chromium/i

Included in the bug report is a proof-of-concept web extension by gorhill, author of uBlock Origin.

@da we install a webextension already for adblocking. Webrequest api is already working properly.

A colleague of mine is working to flesh out some of the other extension APIs that are still missing. Once that patch lands maybe I'll write up the current state of extension support.

@da interesting. I didn't have an problems on my device with 3gig. Did you try Firefox preview and get similar issues? Would be good to narrow down if it's a dat or Geckoview issue.

I added apk download links to the Cliqz Concept Browser readme. Get yourself an android browser that can load dat:// URLs.
github.com/cliqz/cliqz-concept

@da You can either go through the standard support page (cliqz.com/en/support), or you can email it directly to me (sam[at]cliqz.com) and I'll forward to the right person.

@da Yes, there is a general privacy issue with extension capabilities, and that is not solved by these changes. The webRequest will still be available for observation.

The Chrome team claim that the Manifest V3 changes to webRequest fix privacy issues. The article I linked shows why this is not the case.

Show more
Mastodon

macbeth.cc is one server in the network