Tags

Tags give the ability to mark specific points in history as being important
  • 1.29

    protected Release: 1.29
    - 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

    protected Release: 1.28
    - 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

    protected Release: 1.27
    - 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.26

    protected Release: 1.26
    Fix IS_CHROMIUM returning false in a recent chromium update
  • 1.24

    protected Release: 1.24
    - Compatibility with First-Party Isolation: All cookie operations (get, getAll, set, remove) now set the firstPartyDomain attribute to avoid errors in browsers like Mullvad.
  • 1.23

    protected Release: 1.23
    - Add action icon update functionality and warning icons for extension status
    - Fix: Correct property access for cookie name in TokenManager
    - Refactor Cookie class documentation and improve constructor comments for clarity
  • 1.22

    protected Release: 1.22
    - Improved error handling for key creation and charging: now handles HTTP 422 (invalid/expired tokens) in addition to 401
    - Update KeyServer.js to provide clearer error messages for token issues
  • 1.21

    protected Release: 1.21
    - Fix: Error Handling in Settings Manager initialization
    - Update Translations
  • 1.20

    protected
    3a4d38f7 · update changelog ·
    Release: 1.20
    * Fix: Calculating decitoken count failed for numbers between 0 and 1
    * Fix: Rescheduling duplicate alarms for key charge and refill
  • 1.19

    protected
    a5d51c93 · RC 1.19 ·
    Release: 1.19
    * Bugfix: DeclarativeNetRequestRules sometimes not updated on settings change
  • 1.18

    protected Release: 1.18
    * Fix: Let serverside key discharges not affect the extensions usage statistics
  • 1.17

    protected
    7689949f · fix changelog ·
    Release: 1.17
    * Fix: Add Key Api Server to the list of paths where no key is submitted with the requests
    * Fix: retrieving decitoken was not working properly
    * Fix: properly handle failed charges because of expired tokens
    * Modify some german translations
  • 1.16

    protected Release: 1.16
    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.
  • 1.15

    protected
    f0fa4668 · v1.15 RC ·
    Release: 1.15
    * Submit currently used key for membership applications
  • 1.14

    protected
    dbaa5834 · fix license slug ·
    Release: 1.14
    * Fix: Permission requests on settings page failed for Firefox
    * Update: Add suggestion URL to Opensearchdescription
    * Upgrade Dependencies
  • 1.13

    protected
    8815f43f · RC 1.13 ·
    Release: 1.13
    * Optimize key charge checking and remove unnecessary requests
  • 1.12

    protected
    8e9b4f2d · RC 1.12 ·
    Release: 1.12
    * Fix: NetRequest Rules only applied for intiatorDomains of MetaGer
  • 1.2

    protected
    da0d61fe · fix some race conditions ·
    Release: 1.2
    * Add hint to show if settings are applied in inkognito mode
    * Allow fraction Token payments
    * Update Anonymous Token payment to be synchronious
    * Fix: Interface on permission updates
    * Fix: NetRequestRules not getting applied to Chrome startpages
  • 1.1

    protected
    5c3b6d6d · RC 1.1 ·
    Release: 1.1
    Fix: key wasn't properly removed on logout
    Fix: Token refill when extension storage was corrupted
    Fix: properly import key on installation