The primary difference between these two for our purposes is that NoScript lets you select scripts to run on a page on a case-by-case basis, whereas uBlock Origin delegates those choices to a group of motivated volunteers who maintain whitelists and blacklists to control all of this; you can then override UBO’s stock rules as needed.
There are several studies that have directly measured the web audience to answer this question:
There is no tracking or other snooping technology in Fossil other than that necessary for basic security, such as IP address logging on check-ins. (This is in part why we have no comprehensive user statistics!)
Fossil attempts to set two cookies on all web clients: a login session cookie and a display preferences cookie. These cookies are restricted to the Fossil instance, so even this limited data cannot leak between Fossil instances or into other web sites.
timeline simply collapses to zero width. All of the information you can
get from the timeline can be retrieved from Fossil in other ways not
fossil timeline” command, the “
command, by clicking around within the web UI, etc.
Potential Workaround: The timeline could be enhanced with
tags that replace the graph with a column of checkboxes that control
what a series of form submit buttons do when clicked, replicating the
current JS-based features of the graph using client-server round-trips.
For example, you could click two of those checkboxes and then a button
labeled “Diff Selected” to replicate the current “click two nodes to
diff them” feature.
Graceful Fallback: Edit your wiki documents in the default plain text wiki editor. Fossil’s wiki and Markdown language processors were designed to be edited that way.
Workaround: Edit the URL to give the “
ln” query parameter per the
/file docs, or provide a patch to reload the page
with this parameter included/excluded to implement the toggle via a
The default “diff” view is a side-by-side mode. If either of the boxes of output — the “from” and “to” versions of the repo contents for that check-in — requires a horizontal scroll bar given the box content, font size, browser window width, etc., both boxes will usually end up needing to scroll since they should contain roughly similar content. Fossil therefore scrolls both boxes when you drag the scroll bar on one because if you want to examine part of a line scrolled out of the HTML element in one box, you probably want to examine the same point on that line in the other box.
Graceful Fallback: Manually scroll both boxes to sync their views.
On pages showing a data table, the column headers may be clickable to do a client-side sort of the data on that column.
Potential Workaround: This feature could be enhanced to do the sort on the server side using a page re-load.
In several places where the Fossil web UI shows a check-in hash or similar, hovering over that check-in shows a tooltip with details about the type of artifact the hash refers to and allows you to click to copy the hash to the clipboard.
don’t appear. You can then select and copy the hash using your browser,
fossil info” queries on those hashes, etc.
Graceful Fallback: You can use Fossil’s anonymous login feature to convince the remote Fossil instance that you are not a bot. Coupled with the Fossil user capability system, you can restore all functionality that Fossil’s anti-bot defenses deny to random web clients by default.
disabled will take you to the
/sitemap page instead of showing a
simplified version of that page’s content in a drop-down.
Workaround: You can remove this button by editing the skin header.