Tags give the ability to mark specific points in history as being important
-
1.33
protectedRelease: 1.333d635fd7 · ·- Fix the extension not working at all in Chrome before version 111, such as Chrome 109, the last version for Windows 7 and 8.1. Reading its own request rules used a form that only newer Chrome accepts, so starting up failed every time, and neither the key nor the stored search settings were sent with searches - Fix Chrome reporting an error when a tab closed while the extension was reloading the open tabs at browser start - Update dependencies
-
1.32
protectedRelease: 1.3251f60299 · ·- Fix anonymous tokens from versions before November 2024 not being carried over on update. Those versions stored them in a different format, and the migration that moves them to the current storage stopped with an error on each update, leaving them unused - Fix Chrome reporting an error each time the extension scheduled a token refill while no settings page was open. The extension tells an open settings page about the refill, and when none was open, the failed message was not caught
-
1.31
protectedRelease: 1.318a97bd48 · ·# 1.31 - Add support for MetaGer's onion service in Tor Browser. metager.de/tor offers to switch it on; only then does the extension ask for access to the onion address, so nobody else is shown a permission for a domain they have never heard of. Once granted, signing in, anonymous tokens, the key balance and stored search settings work on the onion as they do on metager.de - Fix a sign-in not being picked up in a browser that refuses cookies, such as Tor Browser by default. MetaGer then carries the key in the address instead of a cookie, and the extension only ever waited for the cookie. It now reads the key from the sign-in, key creation and account pages' responses - Fix the key cookie not being found or removed in private windows. Only the browser's normal cookie store was searched, and Tor Browser keeps every window private - Fix pages on the MetaGer website setting more than one cookie at once being missed in Firefox, which joins those cookies in a way the extension could not read - Report errors to MetaGer's error tracking (errors.metager.de), the same way every other MetaGer service does and as described on metager.de/datenschutz: the error, where in the extension it happened, the browser and the operating system. No IP address, no key, no search terms and nothing that ties a report to a person. In Firefox 140 and later this follows the choice in the add-on's permissions; older Firefox sends nothing - Update all dependencies
-
1.29
protectedRelease: 1.293925739d · ·- Fix the account, checkout, order lookup and campaign pages under anonymous tokens landing on the "what is an anonymous token" page instead of the account they were trying to reach. MetaGer moved the whole key process off the keyserver to its own `/konto`, `/preise`, `/anmelden`, `/schluessel-erstellen` and `/c`, and the rule attaching the real key still only watched the old `/keys` address — so all five pages saw only the temporary key and could not tell an existing member apart from a visitor who had never held one, offering to sign them in or start over instead of taking them straight to their account - Fix "Abmelden" on the account page itself not logging this extension out. It has its own logout link, separate from the one in the site menu that already worked, and this one was never on the list of logout links to catch — so it cleared nothing but a cookie this extension does not use, leaving the master key in storage and still attached to every request afterwards - Fix "Set up your MetaGer key" in the settings page going nowhere for a visitor who just logged out but still has an active anonymous token. It always linked to the startpage's `#how-it-works` anchor, which only renders for a visitor with no key at all — this one still looks signed in on the anonymous token, deliberately, so the button opened the ordinary signed-in startpage instead. It now opens `/anmelden` only for that visitor; everyone else still gets the explainer, which is the friendlier door in for someone who has never held a key at all
-
1.28
protectedRelease: 1.2808796850 · ·- Add the signed-in account to the toolbar button: a disc in that account's own colour on the icon, and its key code and balance in the tooltip - Add an account card to the settings page, showing the same mark that metager.de and the key management draw for the same key - Redesign the settings page: light and dark themes, the installed version, and switches that can be reached with the keyboard - Fix logging out from MetaGer's site menu leaving the key in the extension. - Add a logout to the settings page. With anonymous tokens switched on there was nowhere to log out at all: the site does not offer it, because the key it would be dropping is held by the extension and not by the browser's cookies - Open these settings from MetaGer's account pill as well, while it reads "signed in anonymously". It led to the key entry page, which is the one page that visitor cannot use: they have no key to type, and typing one there would hand the site the identity the anonymous token exists to withhold - Add a way from MetaGer's account block into these settings, for the case the site cannot answer itself: with anonymous tokens on it is handed a temporary key and genuinely does not know which account it belongs to - Fix a key picked up from the key cookie being addressed without a port. A cookie has a domain and no port, so a key stored from one on a local development instance was looked up on http://localhost — port 80, where nothing is listening — and every balance poll, token signature and temporary key silently failed to connect. Keys already stored that way are repaired when they are read Fix changing a search setting appearing to do nothing. MetaGer answers a change with the page to return to, which is the page you are already on with an anchor added, so the extension only scrolled to it: engine switches jumped to their heading and left the engine as it was, and the blacklist's Save did nothing visible at all Fix deleting the last entry of a search blacklist coming straight back. Emptying a setting left its old value attached to every request, because whether the request rule still matched the stored settings was decided by counting them — and the count does not change when a value is cleared Stop sending the MetaGer key to the search settings page. It carried the key because the page used to hold the account; the account is in the menu on every page now, so the settings are configured with an anonymous token like any other page Show six characters of a key rather than four, so the short form here is the one metager.de and the key management show Rename "Charge" to "Balance" in the key tables: it is a number, not a button
-
1.27
protectedRelease: 1.27ed1da527 · ·- Fix the MetaGer key staying behind as a browser cookie while anonymous token were active, which meant searches kept being charged to the key - Fix stored search settings getting lost when settings storage in the extension was switched back off - Fix the websocket for key balance updates connecting to a host chosen at build time rather than the MetaGer the search went to - Fix the key API being called on a host chosen at build time: a key's balance, its token signing and the keys created from those tokens now go to the MetaGer instance the key came from - Fix search settings cookies not being cleared on instances beyond metager.de and metager.org - Fix the MetaGer key being attached to searches whose query merely contained the word "keys" or "membership", which authorized those searches with the key instead of an anonymous token - Fix search settings not being taken over from existing browser cookies when the extension is installed - Fix a search setting whose value contains "%" or "=" being stored wrong, and one such setting discarding every other setting in the same response - Fix the MetaGer key being deleted when a token refill spent the last of its charge - Fix the logout link on the keyserver pages not being picked up on metager.de - Fix anonymous token being counted as unspent if the browser stopped the extension mid-request - Fix the request rules failing to install on a fresh Chromium profile ("Rule with id 3 does not have a unique ID."), which left searches without their settings, key or anonymous token headers - Prepare for further MetaGer instances: host permissions covering a whole subdomain no longer break the request rules - Add a test suite covering cookie handling in Chromium, Firefox and Firefox with First-Party Isolation - Update all dependencies, drop the unused uuid package, and move the build to nodejs 22 -
1.16
protectedRelease: 1.16c66dc862 · ·The previous use of anonymous tokens was error-prone and slow, as encryption was performed during usage. Additionally, new features required new processes to handle anonymous tokens on the server side. This update moves the cryptographic operations to background tasks. The extension now uses anonymous tokens to create temporary MetaGer keys with no connection to the main key. These keys are exchanged regularly and used for authorization. Anonymity is preserved, but performance is now significantly faster and more stable.