Daniel Aleksandersen

You can detect Brave (with Shields/ad-blocking enabled) using a [specially crafted GET request](https://www.ctrl.blog/entry/brave-user-agent-detection.html). (Detection method just updated.) This request must be sent to the same origin and not to an...

As of April 2020, you can test for `(navigator.brave && await navigator.brave.isBrave() || false)`.

The time zone, screen resolution, pixel density, and accept header is indeed part of the fingerprints. This may have been introduced since you open the bug, of course. — however,...

This seems to be a timing issue. Scripts created or modified **during** a background sync may end up with a modification time that conflicts with the deletion detection logic. The...

An alternative approach is to explicitly mark deleted files as deleted; essentially leave the synced file as a tombstone. This could be achieved by turning deleted files into empty 0-byte...

A second problem is the lack of remote locking. With unfortunate timing, two devices syncing at nearly the same time could manifest as both what I and @cunlem describes. (Although...

In conclusion, the simplest change is to remove the timestamp-based guesswork in the sync base and introduce tombstones for deleted files. The second biggest impact is remote locking followed by...

> I didn't modify any scripts during sync either. Restoring them from trash marks them as modified. What goes wrong is clearly the if-modified-since then delete logic. It’s unclear on...

Version 3 addresses are the recommended address format now. https://www.torproject.org/docs/onion-services.html.en

You don’t need to specify tab id here.