CHANGED IN THIS VERSION: the time anchor is now ON by default, and — see
"Fixed" below — it can actually run for the first time in this package. In
earlier builds the file implementing it was missing from the package, so the
feature silently did nothing. PRIVACY.md has been updated: it previously said
the extension makes no network requests at all, which was true only while the
feature was off by default.

Feature : "Time anchor" — no longer a setting, it is always on
Endpoints: three, tried in order until one answers — the network is
decentralised and a single host would defeat the purpose:
https://api.drand.sh/<chain>/public/latest
https://drand.cloudflare.com/<chain>/public/latest
https://api2.drand.sh/<chain>/public/latest
<chain> is the fixed quicknet hash
52db9ba70e0cc0f6eaf7803dd07447a1f5477735fd3f661792ba94600c84e971
(hard-coded in zeitanker.js, not user-supplied). Each attempt has
an AbortController timeout.
Purpose : Fetches a public random value from the drand network (League of
Entropy) and writes it into the capture. Since nobody could know
that value in advance, it shows the capture is not older than that
round — without relying on the device clock, which the user can
set freely.
Sent : nothing. Plain GET, no headers identifying the user, no page data,
no URL of the captured page. The response is a random value, a
round number and a timestamp, identical for everyone asking in
that round.
Failure : the capture is saved without an anchor. No error, no retry loop.

No other network path exists. Two further fetch() calls appear in the source
and are local by construction: result.js reads back a blob: URL it created
itself, and background.js converts a data: URL from captureVisibleTab into a
blob. Neither leaves the machine.

CHANGED

• The filename now includes the title. The default was
{site}{date}{time}{n} — website, date, time, running number. Anyone
finding a capture a year later could not tell what it was about. It is now
{title}{site}{date}{time}.

• That title comes from the page's publisher metadata rather than the window
title, which almost always carries suffixes ("… - PubMed") that merely
consume space. The length limit rises from 40 to 60 characters; at 40 the
title broke mid-word.

• Existing installations follow on update, but only where the template and
length were never changed. A pattern you chose yourself is a decision and
is left alone.

CHANGED

• The filename now includes the title. The default was
{site}{date}{time}{n} — website, date, time, running number. Anyone
finding a capture a year later could not tell what it was about. It is now
{title}{site}{date}{time}.

• That title comes from the page's publisher metadata rather than the window
title, which almost always carries suffixes ("… - PubMed") that merely
consume space. The length limit rises from 40 to 60 characters; at 40 the
title broke mid-word.

• Existing installations follow on update, but only where the template and
length were never changed. A pattern you chose yourself is a decision and
is left alone.

FIXED

• The context menu appeared in German regardless of language. Translations were
present in all nine languages but never used. This affected every build so
far. The same applied to two notifications and three places in the settings.

• On pages with a fixed menu column on the left, that column was missing from
the PDF and left an empty area behind. The cause was not the detection but
its parent container: when that was classified as an intrusive overlay and
hidden, the column went with it.

• In multi-page mode, captures in black and white or greyscale came out
almost empty: a few lines of noise at the top and nothing below. The chosen
colour depth was not carried over when the PDF was assembled, so the file
header announced colour while the viewer found a fraction of the expected
data. Short pages were affected the same way. On long single-page captures
it was never visible.

• Fixed menu columns on either side are kept in the PDF. On app-style
interfaces the capture is clipped to the area that scrolls the content — the
menu column sits beside it and was falling outside. The clip now extends to
include it. Where a column is taller than the window, it is captured as far
as it fits.

• Pages with endless loading (timelines, search results, forums) produced an
error and no PDF at all, even though the capture had already got a long way.
The page footer is now recognised as the end and the capture finishes there.
Where there is no footer, the state at the start of the capture applies. In
both cases a PDF is produced, and a note says that it is shorter than the
page has since become.

FIXED

• The context menu appeared in German regardless of language. Translations were
present in all nine languages but never used. This affected every build so
far. The same applied to two notifications and three places in the settings.

• On pages with a fixed menu column on the left, that column was missing from
the PDF and left an empty area behind. The cause was not the detection but
its parent container: when that was classified as an intrusive overlay and
hidden, the column went with it.

• In multi-page mode, captures in black and white or greyscale came out
almost empty: a few lines of noise at the top and nothing below. The chosen
colour depth was not carried over when the PDF was assembled, so the file
header announced colour while the viewer found a fraction of the expected
data. Short pages were affected the same way. On long single-page captures
it was never visible.

• Fixed menu columns on either side are kept in the PDF. On app-style
interfaces the capture is clipped to the area that scrolls the content — the
menu column sits beside it and was falling outside. The clip now extends to
include it. Where a column is taller than the window, it is captured as far
as it fits.

• Pages with endless loading (timelines, search results, forums) produced an
error and no PDF at all, even though the capture had already got a long way.
The page footer is now recognised as the end and the capture finishes there.
Where there is no footer, the state at the start of the capture applies. In
both cases a PDF is produced, and a note says that it is shorter than the
page has since become.

FIXED

• The context menu appeared in German regardless of language. Translations were
present in all nine languages but never used. This affected every build so
far. The same applied to two notifications and three places in the settings.

• On pages with a fixed menu column on the left, that column was missing from
the PDF and left an empty area behind. The cause was not the detection but
its parent container: when that was classified as an intrusive overlay and
hidden, the column went with it.

• In multi-page mode, captures in black and white or greyscale came out
almost empty: a few lines of noise at the top and nothing below. The chosen
colour depth was not carried over when the PDF was assembled, so the file
header announced colour while the viewer found a fraction of the expected
data. Short pages were affected the same way. On long single-page captures
it was never visible.

• Fixed menu columns on either side are kept in the PDF. On app-style
interfaces the capture is clipped to the area that scrolls the content — the
menu column sits beside it and was falling outside. The clip now extends to
include it. Where a column is taller than the window, it is captured as far
as it fits.

• Pages with endless loading (timelines, search results, forums) produced an
error and no PDF at all, even though the capture had already got a long way.
The page footer is now recognised as the end and the capture finishes there.
Where there is no footer, the state at the start of the capture applies. In
both cases a PDF is produced, and a note says that it is shorter than the
page has since become.