Get in touch

Roadmap & release notes

Current version 1.0.10 · page updated 2026-10-14

What the annotator can do, by the version that added it, and what we’re building next.

Latest release
v1.0.10, Nov 1, 2026.
Releases so far
19 since Jul 16, 2026.

What’s next

Planned work, from committed to still being explored.

Next#

Committed, not yet started.

  • AI second opinion for custom schemas

    The model's verdict follows the built-in antisemitism taxonomy, so a team using its own schema gets the plain-language explanation but not the pre-annotation. Fixing this means deriving the verdict from the team's own schema, which changes the model contract rather than the wiring, so it was left out of the parity pass.

  • Peer comparison on custom schemas

    Three things the built-in panel has and a custom schema's editor lacks: the compare carousel, the inline marks showing what other annotators said on the same post, and the guided keyboard flow.

  • Contribution tracking

    What each annotator, team and organization has produced. The usage page already reports the headline figure, how many annotations each has stored. Still missing: output over time, how much of it has passed review, and coverage of a project rather than a running total.

Exploring#

Wanted, with an open question to settle first.

  • The other hate types in the same panel

    The extension already ships the label spaces for anti-Black, anti-Latino and anti-queer hate, but the annotation panel is locked to antisemitism. Unlocking it is a small code change; the larger decision is how to keep a corpus annotated against four taxonomies coherent.

  • Structured flagged-source measurement

    Today the extension marks a citation to a watchlisted outlet only when an annotator happens to come across one. A deliberate, repeatable set of prompts would turn that into a rate that can be compared across assistants and over time.

A roadmap, not a schedule: nothing here has a delivery date. The only dates on this page belong to releases that have shipped.

Release history

Every version and what it added.

A version marked “in development” is built and being tested, and reaches annotators as the next update. Select a release to see what it added.

v1.0.10

Nov 1, 202614 changes
Items say more about where work was filed, Codebooks and the team pages are easier to scan, and walkthroughs use everyday examples.
Items and projects
  • The annotation drawer says when a post's filing changed, and asks before saving an annotation with no project.
  • Annotated rows name the project they were filed under.
  • The project you picked stays picked after you sign out and back in.
  • Select rows in the item list to approve, re-annotate or delete their annotations together.
  • Every count on the Items page says what it is counting.
Codebooks
  • The Codebooks list shows one line per codebook.
  • New codebook asks for a name and previews the template you pick.
  • The codebook editor has a cleaner layout and a Tutorial button.
Org, Conflicts, Sources and Usage
  • Conflicts compares annotators in one table.
  • The Org page's Domains dialog and Past decisions table are easier to read.
  • Sources shows what was decided in two columns, and the left menu can be dragged wider or narrower.
  • Usage shows capped figures as a share of the cap, with the numbers on hover or click.
Walkthroughs
  • Walkthroughs on Items, annotating and Codebooks use general examples, and practice annotating happens on a sample codebook.
  • Walkthroughs no longer dim the page.

v1.0.9

Oct 22, 20269 changes
Exports open in their own window with two new formats, long lists page instead of stopping short, and annotating works again on the newest LinkedIn and Mastodon pages.
Annotating on a page
  • LinkedIn and Mastodon redesigned their pages, which hid the Annotate button. Both the new and the old pages work now.
  • On Truth Social, the original post and the comment a reply answers can be annotated and picked as context, and a reply carries the conversation above it.
  • A generated picture in ChatGPT or Claude that changes after it first appears can still be annotated.
  • Pre-annotate works on every codebook, including written answers and highlighted passages.
Items and projects
  • Export opens a window listing the file formats. Parquet and pandas join Excel, CSV, JSON and JSON Lines, and the window remembers your last choice. Leads can schedule the export from the same window.
  • Long item lists show 200 rows a page, with arrows and a page number below the table. The Annotated tab counts every annotation and loads older ones with Load more.
  • Search and Filters are two separate buttons. Filters opens one menu with a section for each filter, and every filter that is on shows as a chip under the tabs.
  • The tables show each platform as its logo and no longer have a Categories column; an annotation's answers are in its record.
Walkthroughs
  • The walkthroughs follow the new Export window, paging and filters, and a lead's walkthrough goes page by page.

v1.0.8

Oct 20, 202614 changes
The extension takes on AddressHate's own look, large item lists open much faster, and Settings is split into tabs.
Look
  • The popup, the annotation panel and the workspace now use AddressHate's colors and typefaces, matching the AddressHate Dashboard. The Annotate and Flag buttons on a page stay blue and red.
  • The annotation panel looks the same on every site instead of taking on each platform's color.
  • On the Items page and in every project, the tabs that choose which items you see, the search box and the filters sit directly above the list, and each active filter is shown so you can remove it in one click. Adding items is one button, with Import in its menu.
Annotating on a page
  • The window that lists a post's annotations works with every codebook and shows each team's own questions. A question another annotator answered differently is marked on the question itself instead of in a separate agreement box.
  • Only leads and senior annotators see the Approve and Request changes buttons there; everyone else can read the annotations but not change them.
  • Reopening your own annotation fills in your earlier answers on any codebook, and its button says it will overwrite them.
  • Bulk labelling (the Select several button and Alt+B) is switched off for now and will return in a later update.
Speed
  • Large item lists and projects open much faster, and the page stays responsive while they load. Rows appear as you scroll, and a project you have opened before, or are hovering over in the sidebar, opens almost at once.
Settings
  • Settings is organized into tabs (Profile, Annotating, Usage, Privacy & legal) with larger text. Each setting sits on its own row with its control on the right.
Review
  • Clicking an annotation in Review opens it in a window with everything on one screen: the post on the left, every answer and the feedback on the right, and Request changes and Approve at the bottom. The left and right arrow keys move to the previous or next annotation, and approving one moves on to the next automatically.
  • The Review table works the same for every codebook. It shows the post, who annotated it and its status; the filters open from a button in the table's header; and the number waiting sits beside the table's heading.
  • Approving a single annotation no longer asks for confirmation.
Usage
  • The Usage tab on the Organizations page is easier to read. The teams-and-people table shows one figure per cell, with a switch between this month and all time, and only the resources in use get a column. A limit is shown only where it is set or nearly reached, and clicking a figure changes its limit.
  • A line above the resources table explains how limits work, and a feature an organization's plan doesn't include is labelled that way instead of showing as a refused limit.

v1.0.7

Oct 16, 20268 changes
If a sign-up confirmation email never arrives, you can ask for a new link; an annotation made while an organization is still being set up is kept until it can be sent; and each role gets its own first-day tour.
Signing up
  • After you sign up, the confirmation notice says the email can take a few minutes, and a “Send a new link” button appears after five minutes in the popup, on the page and on the join screen.
  • The organization question in the first-day questionnaire can be left empty.
Getting started
  • Each role has its own first-day tour, so someone who is promoted, or who joins an organization in a new role, sees that role's tour once.
  • The walkthroughs are more forgiving of how you type an answer, show clearly what to enter, and say what is still missing.
  • You can choose a new project's schema while creating it.
Organization setup
  • An annotation made while your organization is still being set up is kept and sent once setup is fixed, instead of being abandoned, and the message says so plainly.
  • Admins can check an organization's setup from the Organization page and fix what can be fixed with one button.
  • Admins can open an organization's view on a deployment that has only one organization, and are told when an organization isn't ready to be viewed.

v1.0.6

Oct 15, 20267 changes
Every email from the extension shares one design, the first-day walkthroughs can no longer send or change anything real, and a new lead's first screen no longer requests data it can't have yet.
Email
  • Invitations, sign-up confirmations, password resets, join requests and security notices now share one design, with a plain-text copy, one sender address, a clear headline, one action and a line on what to do if it wasn't you.
Getting started
  • The Teams walkthrough has you practice an invitation with a made-up address and refuses a real one while it is open, so a rehearsal never emails anyone.
  • The Organization walkthrough now tells you when a change would be real, instead of appearing to save it and then not saving it.
  • A walkthrough's sample data can no longer tick off a Getting started step you haven't done yourself.
  • A walkthrough step that opens over a dialog can be clicked and read inside it.
  • A new lead's first screen no longer requests the review and conflicts counts before the terms and questionnaire are done.
  • Signing in to a new account from the popup no longer shows the previous account's team name over the welcome screen.

v1.0.5

Oct 13, 202610 changes
The annotation drawer tucks to the side with one click, the extension's own keys no longer reach the site you are on, and leads can see how far each person has progressed, from installing to their latest annotation.
Annotating
  • A small tab on the edge of the annotation drawer slides it out of the way and back, so you can read the post or watch the video underneath without closing a half-filled form. Picking context still works while it is tucked away.
  • The extension's own keys stay with the extension: Alt+C no longer turns on TikTok's captions, Escape ends picking or bulk labelling without also acting on the page, and Space or Enter on the Annotate button opens the drawer instead of pausing the video.
  • Typing with Option or Alt in the drawer (an accented letter, or Option+Delete to remove a word on a Mac) works normally instead of triggering a shortcut.
  • If you click on the page while an AI explanation is running, the drawer no longer takes back the keyboard when it finishes.
  • On TikTok, a comment that is only a picture, a sticker or a GIF has its Annotate button beside the commenter's name instead of far below the picture.
Getting started
  • The AddressHate website can email you the install link.
  • A welcome page with three steps to get started opens after you install. Removing the extension opens a page with one optional question asking why.
For leads and admins
  • The Users page shows each person's progress: installed, signed in, terms accepted, how much of the first-day tour they finished or whether they skipped it, and their first and latest annotation.
  • A “Registered, not installed” list shows who asked for the install link but hasn't installed yet, with a button to send the link again.
  • An export, a deletion or another recorded action no longer fails once with “try again” after the service restarts.

v1.0.4

Oct 11, 202619 changes
Leads can delete or remove many items at once and undo it, you can edit your own annotation from History, links open at the exact comment, and Brandwatch searches are checked as you type.
Annotating
  • Edit your own annotation from the popup's History (✎ Edit) or from the Annotated drawer. The workspace opens it with your answers filled in, ready to overwrite.
  • A link to an annotated comment opens the page at that comment. On TikTok, the comment panel opens and scrolls to it.
  • A “Select several” button at the top of the page starts labelling many posts at once, and the progress message explains when a large batch is being delivered in steps.
  • On YouTube and Rumble, the video itself (title, description and channel) can be added as context for a comment, from the drawer or by clicking it on the page.
  • Typing in the annotation drawer no longer triggers the site's own keyboard shortcuts (on TikTok, “c” turned on captions).
  • A reply is annotated as the reply, not as the comment it answers, on Instagram, Facebook, LinkedIn, TikTok, Reddit and Rumble.
  • An AI-chat row in History opens the saved record, since the chat itself is private. Only its annotator sees “Open your chat”.
Projects and items
  • Leads can tick items, or select every item a search or filter matches, and delete them or remove them from the project in one step, with Undo in the message that follows. Deleting 50 or more asks you to type the number first.
  • Where two organizations have a team with the same name, the team is shown with its organization beside it, and a lab's first team takes the lab's name instead of “General”.
Signing in and joining
  • A new account confirms its email address before its first sign-in.
  • After a few wrong passwords, signing in requires a short automatic check of the browser. An account with many wrong passwords in a row is locked for a while; its owner gets an email, and resetting the password unlocks it.
  • Someone a lead added who signs in with Google or Microsoft is asked to accept the organization before joining it.
  • The privacy policy now also describes what is sent when you annotate a response in an AI-assistant conversation and who in your organization sees the prompt with it, and everyone is asked to accept the updated terms once.
  • A flagger can leave the first-day tour at any time with “Skip the tour” or Escape, and it stays closed.
Importing from Brandwatch
  • The Import wizard reads your search terms back in plain English as you type (“Finds posts with the phrase ‘blood libel’, but not ‘satire’”), so you know what a query will find before you preview it.
  • A query that can't run, such as one with an open quote or bracket, is flagged under the box before you continue, and a lowercase “or” or “not” gets a warning, since Brandwatch treats it as a word.
  • Search terms can be much longer and are never cut off silently: the box counts as you type and says when a query is too long. Preview checks the query with Brandwatch first and says where any problem is.
  • Running the same import again brings in posts that are not yet in the queue, instead of the same newest posts, and posts already annotated are not imported twice.
  • A large import that takes a while says it may still be running, instead of saying the service is unreachable.

v1.0.3

Oct 6, 20269 changes
Comments that are only a picture can be annotated, flaggers join a project by invitation, and exports come in the format you need.
Annotating
  • A comment that is only a picture, a GIF or a video (a photo reply, a sticker) can now be annotated on every platform that shows one, and lists label it “Image — no text” instead of leaving it blank.
  • The annotation drawer moves out of the way: it opens on the left when the post you are annotating is under it, can be switched to either side, and steps aside while you pick comments for context.
Flagging and joining
  • Anyone can install the extension and flag posts right away. Their flags go to AddressHate, and the popup says where your flags go.
  • A lead can invite people to a project from its Add people window, by email address or with a shareable link that can be turned off or replaced. The people invited flag for that project.
  • An organization's invite code and its requests to join are now for university and organization email addresses, which can annotate. A personal address joins a project by invitation instead.
Exports
  • The arrow beside Export downloads the same list as a CSV, JSON or JSON Lines file, and a scheduled export can be delivered in any of these formats.
  • The Excel workbook is easier to read (a filterable header row, real dates, clickable links, wrapped text) and ends with a Codebook sheet explaining every column and its answers.
Fixes
  • Signing out, or switching account or organization, starts the next session with a fresh copy of its own schemas and projects.
  • A new icon: a note with a folded corner.

v1.0.2

Oct 3, 202614 changes
Imports carry the text of every post, people who already have an account can be invited, and a pass over every surface fixed controls that could act twice and screens that lost your place.
Imports and exports
  • A Brandwatch import files every post with its text, from Brandwatch's full text, else the platform's official API, else the public page. A post that takes a while to read is filed within the hour, and one that can't be read is skipped and counted, so the import reports what it left out.
  • An exported project now includes its sub-projects and annotations made before a post was added to the queue, and the workbook gains a Posts Annotated column.
  • A scheduled or API export no longer skips an annotation that reached the service late, after the export's last run.
Organizations and people
  • A lead can invite someone who already has an account. They get an email with a link to accept.
  • Each organization can have an invite code. Anyone who signs up with it appears in Requests to join on the Users page, and their permission group is chosen when they are approved.
Annotating
  • A Facebook comment keeps its badge and its annotations when Facebook changes the story's link between visits.
  • An image generated by an AI assistant can be annotated even when the chat has no text around it.
  • On a conflict, the annotations that weren't chosen read “Not chosen”, and each tag shows where the annotators differed.
Fixes
  • A double click no longer acts twice on flagging (a second click used to remove the flag), review verdicts and feedback, conflict notes, new items, organization settings, new teams, schemas or file imports.
  • A “required” message clears as soon as the question is answered, and a single-choice question asks for an answer rather than “at least one option”.
  • Questions in the schema builder can be reordered with the keyboard, and keyboard focus stays in place after an action on the Usage, Platforms and Schemas pages and in the walkthroughs.
  • The Schemas page shows which schema is an organization's default and its columns line up. The Platforms page no longer scrolls sideways in a mid-sized window.
  • Signing in no longer leaves the form unusable when the service's reply can't be read, and Settings says “Sign out” like everywhere else.
  • Deleting your account also removes your name from import batches, posts waiting to be imported and the flagged-source watchlist.

v1.0.1

Sep 29, 202623 changes
Every role now gets a walkthrough of its first job and every page a walkthrough on sample data, organizations and teams are easier to run, and a production pass over every surface fixed problems 1.0 had left unnoticed.
Your first day
  • Every role gets a walkthrough of its own first job. The first time you open the workspace, it guides you through the work your role does (a lead sets up a schema, a team and a project; an annotator annotates; a reviewer reviews) in short chapters you can stop and resume.
  • Each page has its own walkthrough on sample data, so you can try every control without changing anything real. It starts on your first visit and can be replayed at any time.
  • Getting started lists your walkthroughs and your progress through each, and you can start any part of one from there.
  • Brandwatch importing in depth: a button on Schedules → Imports teaches Brandwatch's query language in a practice lab, then walks through the Import wizard, scheduling, and adding a saved batch or a file, all on sample posts with nothing sent to Brandwatch.
  • Exporting in depth: a button on Schedules → Exports shows what an export contains, sheet by sheet and column by column, then covers the Export button, delivering an export on a schedule, and API tokens.
  • Importing from a file has a downloadable template with the columns it reads and an example of each kind of row.
Organizations, teams and people
  • Several labs can now share one university domain, each as its own organization, and every organization has a display name instead of an internal id.
  • A lead can approve a request to join straight from the email that tells them about it.
  • Adding a member is a short step-by-step window on the Users page (address, permission group, team, confirm), and adding a teammate on the Teams page works the same way.
  • An organization's team rows expand to show who is on each team, what they may do and when they last signed in.
  • Annotators and flaggers see their own usage on Settings: what they have used this month and what is left.
  • API access (the tokens a lead creates for their own script or scheduler) moved from Settings to Schedules → Exports, in its own section below the schedules the service runs.
Schemas, conflicts and sources
  • A schema is now chosen per project, and an organization's first schema is its default. Teams no longer have a schema of their own, so the questions a post gets are decided in one place.
  • A conflict now shows the annotations side by side, one column per annotator, so the disagreement is easy to see. On a conflict you are part of, one click adopts a colleague's answers in place of yours while keeping your comment.
  • Every organization's flagged-source watchlist now starts empty and holds only the outlets that organization chose. A lead can add an outlet (its names and web addresses) directly from the Sources page.
Fixes
  • A short highlighted passage written in capitals can be annotated. It was mistaken for a page heading and removed, so the highlight recorded nothing and no message said why.
  • On a Reddit feed, annotating a post files that post, not the first post on the page. On LinkedIn, each post in the feed has its own link, so flagging one no longer marks every post on the page as flagged.
  • An image generated by an AI assistant keeps the prompt that asked for it, including on ChatGPT's new page layout.
  • A Facebook comment's link leads to the comment, not to the profile of the person who wrote it.
  • The extension no longer occasionally thinks you are signed out until the browser restarts, and signing in again while an old session is expiring no longer loses the new sign-in.
  • A question hidden by another answer is no longer submitted or required, however many conditions deep it is.
  • The workspace no longer shows an older answer over a newer one when you switch team or page quickly, and Escape closes a picker or pop-up before anything behind it.
  • The on-page windows (the flag consent, the Explain confirmation, the annotation viewer, the sign-in card and the bulk-labelling bar) fit a narrow window, keep keyboard focus inside while open and return it when they close.

v1.0.0

Sep 27, 202637 changes
The first stable release, and the first with a public store listing, so researchers can find the extension instead of being sent a link. Using it still requires an account, as it always has. 1.0 was held for this release: a pass over every surface the tool already supported, finishing what was nearly right and fixing hidden problems. It also adds a practice page inside the extension that behaves like a real platform.
Somewhere to practice
  • The extension has a practice page that looks and behaves like a real platform, with the real Annotate button, the real panel and your team's own questions. Nothing you submit there is kept, so you no longer have to learn the tool on real posts.
Signing up
  • Under the terms, the setup screen now offers an optional checkbox to join the AddressHate mailing list for occasional news about the project and the tool. It shows the address it would add, which is the one you signed in with. It is unticked by default, is never a condition of using the extension or any part of it, and sends nothing about your annotations. Every message has an unsubscribe link, and leaving the list is separate from deleting your account.
  • The Terms of Use are clearer and narrower, so you will be asked to accept them again. The project may now say publicly that your organization uses the extension, and no longer names you. Your name, annotations and judgments are never used without your explicit consent in a separate agreement. The terms also state that the tool is for academic and organizational research only and that you must be located in the United States.
Articles and other web pages
  • Only an article's own text is now stored. Navigation, ad markers, the share row, photo credits, the newsletter pitch, the tag list and related-story blurbs are removed, and stray citation marks and broken characters from a mis-encoded page are repaired. The text is the same whether you annotated the page in place or pasted its link into a project; before, the two could differ, making one article two documents in a corpus.
Images and video from AI assistants
  • An image generated by an assistant can now be viewed again after it is annotated: in review, in conflicts and in your own history. The saved copy had been stored but never shown, so reviewers judging a picture saw only the text around it.
  • A picture that finishes loading after you start reading now gets its Annotate button. Late images, common on slow connections, had no button until the page was reloaded.
  • A photo you attached to your own prompt is no longer offered for annotation; the button belongs on what the assistant produced.
Reviewing and conflicts
  • Settling a conflict works again. Since the current storage backend became authoritative, the service had refused every attempt the page offered. Settling now marks the chosen annotation as the one that counts and the others as excluded in one step, and clearing the decision returns all of them to unreviewed. Nobody is asked to redo anything, and a lead who annotated the post cannot settle it.
  • The coaching note a lead leaves on a conflict is shown to the annotator again.
  • Every control in a review or conflict row (the checkbox, the verdict buttons, the per-row actions) can be reached by keyboard and is announced by screen readers. Each row had been one large button that hid them.
  • An administrator's review inbox is limited to the organization they are working in, so every row is work they can place. The page already said so; now the inbox matches.
Usage and limits
  • Daily and weekly figures are now shown. They were recorded but never displayed, so a team hitting a daily limit saw only a monthly total with room to spare and no reason for the refusals.
  • Refusals are counted. When a limit turns work away it is recorded, and when a limit is only being measured, the page shows what it would have refused, so you can judge the effect before turning enforcement on.
  • A change to a limit records who made it and when.
  • Deleting an account removes its figures from the page instead of leaving a row for someone who no longer exists.
  • The per-person monthly AI allowance is raised so that the organization's own pool is what limits use. It had been so low that no plan's pool could ever be reached.
Managing people
  • An account whose permission group no longer exists now gets the least access the product has (flag only) instead of the default role. It used to get full annotator access, so a flag-only volunteer could silently end up with the team's whole workload. Administrators keep their access, and affected accounts are listed so a lead can fix them.
  • The Platforms page marks a platform added after a team's list was saved, with one click to allow it. Such platforms used to be denied without explanation, which happened twice with 8kun before anyone noticed.
  • The roster shows which extension build each person is running, so you can tell whether they have a fix yet.
Settings, Sources and Getting started
  • Settings had a production pass: text and links are correct, an administrator viewing another organization sees that organization's settings, and a failed control now says so instead of appearing to work.
  • The Sources page names the organization whose watchlist it shows and lists the AI assistants your organization is cleared for, the only places a flagged-source warning can appear. An organization cleared for none of them no longer has the page.
  • Getting started was checked line by line against what each role and permission can do. Steps shown to people who couldn't take them, or that described the product as it used to be, were removed.
  • API access on Settings had the same pass. A token says when it is close to expiring, the page says how many tokens you may hold instead of refusing the one that goes over, and an out-of-date or briefly unreachable service says which, with a way to retry, instead of showing an error code. A script can check its own token: asking who it is returns the token's name, what it can access, how many days it has left and how much of its monthly call allowance remains, so a scheduled export can warn you before it starts failing.
  • API calls are now metered like every other resource. Usage & limits shows how much each person, team and organization pulls through scripts, and an administrator can set an allowance there. The default is deliberately high, far above a nightly or even hourly export, so it only catches a job looping without a pause.
Your own codebook
  • Every organization now has the antisemitism panel and can build its own questions beside it, so a new tenant no longer starts with nothing to annotate with.
  • An organization sees and uses only the schemas it created, plus the bundled panel. Another customer's codebook is not listed, readable or assignable.
  • Each row on the Schemas page says why your organization can use that schema: everyone has it, you built it, or it belongs to one of your own teams or projects.
  • In the schema editor, the question palette and the question's Details panel are now full-height columns on either side of the canvas, each scrolling on its own, so the questions stay in view while you work through a long list of settings.
  • The editor now explains itself: every section and nearly every control has a sentence on what it is for, such as what a field id is and why it can't change, what a taxonomy does and what a condition hides. Help is on by default the first time you open the editor, and one Hide help button puts it away.
  • Building a schema works in a narrow window: the template shelves fold into a row instead of pushing the templates a screen down.
Fixes
  • The article shortcut (Alt+Shift+A) now says when it can't open, instead of silently doing nothing as if it weren't set up.
  • A team's export and its queue no longer disagree about which items belong to a project.
  • Annotating works again on ChatGPT. ChatGPT rebuilt its conversation page in September, leaving responses with no Annotate button, already-annotated mark or flag icon, and nothing on screen explaining why. Conversations from before the change keep their annotations.
  • When a sign-in has expired, the page now says so. You still need to sign in again, but “sign in to annotate” made it look as if the extension had forgotten you.
  • The annotator-agreement panel no longer reports agreement it can't see. For teams on their own codebook it showed a green “Unanimous” on every post, because it looked for the built-in question set's answers, found none, and treated “nobody answered” as “everybody agreed”. It now compares the answers actually given, shows nothing when there is nothing to compare, and never counts an annotator it couldn't read as agreeing.
  • Review, Conflicts and the local outbox now label questions with your own codebook's names. They used the built-in question set's labels, so a team whose first question is “Severity” saw those answers under someone else's heading, and the outbox column was empty.
  • Adding someone to a project no longer offers accounts from other organizations. Choosing one used to be refused only afterwards, with a message that couldn't say why without revealing who else exists. The picker now offers only names that can be added.

v0.7.0

Sep 23, 202680 changes
Articles and other web pages can now be annotated (the whole piece, a highlighted passage or any reader comment) by calling the extension onto the page from the toolbar popup or a keyboard shortcut. Mastodon and Truth Social join the platforms, and a corpus can be imported from a file. Items can be annotated from the workspace without opening the platform, and opening one assigns it to you. You can also sign in with a Microsoft work or school account, alongside Google and username and password, so partners on Microsoft 365 no longer need a separate password issued to them.

Can be annotated after this release: 20 surfaces: X, YouTube, Rumble, TikTok, Reddit, Instagram, Facebook, LinkedIn, Bluesky, Mastodon, Truth Social, 4chan (including its 4plebs archive), 8kun, ChatGPT, Claude, Grok, Gemini, DeepSeek and Qwen, plus any article or other web page on demand.

Signing up
  • Anyone can create an account with their email address. The account is held until you confirm the address from the email we send; the link asks whether it was you, and “This wasn’t me” removes an account someone made in your name. Once confirmed, a university address (or one your organization has claimed) chooses its organization and waits for a lead, as before, or sets the organization up if it isn't here yet. Any other address can flag posts right away, and a lead or admin can promote it from the roster. The shared invite code still works but is no longer required. The form first asks whether you are using a university or another address and holds the email field to that answer, so you see where your kind of address leads before you type it.
  • Leads are emailed when someone asks to join their organization, and the person is emailed when the request is decided. A request can't be approved until its address is confirmed.
Articles and other web pages
  • Any web page can now be annotated: a news story, an op-ed, a blog post. Press Annotate this page in the toolbar popup, or press Alt+Shift+A, and the headline gets the usual Annotate button. Nothing runs on the page until you ask; the extension has no standing access to any site beyond the platforms it has always run on.
  • Highlight a passage to annotate just that: only the highlighted text is stored, and its link reopens the page at the quote. The Annotate button on the headline annotates the whole piece, storing its text (up to 12,000 characters) with the comment section as context.
  • Reader comments can be annotated like a thread on a social platform. Each has its own Annotate button and is stored under the commenter's name, not the publication's, with its posting time and likes where the page shows them. A reply keeps the comments it answers and the article's headline as context, and a passage highlighted inside a comment is filed as the commenter's.
  • Comments are found on the systems news sites and blogs actually use (WordPress, Drupal, Hacker News, forum software and many more) and on sites with no recognizable markup. If none of that finds them, annotating one highlighted comment teaches the page where its comments are, and every comment beside it gets a button.
  • Disqus comments, used by many news sites, can be annotated once you allow it. Disqus shows them in a frame the extension can't otherwise reach, so Chrome asks for permission the first time, and declining changes nothing. Comments a site loads from other services are not read, and the record notes they were there rather than reporting none.
  • A pasted article link is filed as an article, and the service reads the page's headline, byline and text so it can be annotated from the workspace. Brandwatch imports can request news pages the same way when a lead ticks Articles.
  • Administrators can allow or restrict articles per organization and team on the Platforms page. An organization that had narrowed its platform list must tick Articles before its annotators see the option.
Mastodon and Truth Social
  • Posts and replies on mastodon.social and truthsocial.com have the Annotate button, with a reply's thread kept as context. An organization or team with a restricted platform list must tick the new platform on the Platforms page first.
A corpus from a file
  • The Import window has a third source: upload a CSV or JSON file of posts (links, or just their text) and add them to a project. A row with text and no link becomes an imported text, annotated from the workspace with no live post to open.
Looking closer at a post
  • The annotation panel's ⋯ menu holds the tools for studying a post: the plain-language explanation, how far it spread (likes, replies and shares as the platform shows them), whether the account behind it looks like a person, the AI pre-annotation and what other annotators said. Flag sits in the panel's title row.
  • Explaining a post from the page (the magnifier beside a flagger's flag button) now asks first and shows how many AI explanations you have left this month, so a stray click doesn't use one. When none are left, the sheet says so instead of offering a button, and an explanation that fails to load no longer counts against the allowance.
  • If a post's picture is gone from the platform (an imageboard deleted the thread's files, or the image links expired), an annotation reopened from the workspace shows the copy saved when it was annotated, marked as the saved copy. If no copy was kept, it says so and offers the post instead of an empty box.
Images and video from AI assistants
  • An image or video generated by an AI assistant on ChatGPT, Claude, Grok, Gemini, DeepSeek or Qwen has its own Annotate button underneath, so the picture can be judged apart from the rest of the response. A response that is only a picture, which had no button, can now be annotated.
  • A picture is judged with the prompts written before it as context, but not the assistant's surrounding text, even when the same response also contains text.
  • A picture wrapped in a link to its full-size file keeps its Annotate button, and the chat's source check no longer offers to report the assistant's own image host as a cited outlet.
  • The file itself is saved with the annotation: the extension reads it from the page when you annotate (its address only works in your browser) and archives it once, in your organization's own archive. If it can't be read, the annotation is still saved, noting which image it was about.
Annotating
  • You can now annotate an item from the workspace. Open an item on the Items page or in any project or sub-project, and each of its links has an Annotate button that opens the usual editor (the project's schema, the same answers, the same review) without visiting the platform.
  • Opening an item for annotation assigns it to you, so the queue shows who is working on what as they work, not once the annotation arrives.
  • The editor shows the post's text and author wherever they are known. Where they aren't, it says which is missing and puts the post one click away instead of an empty card. There is always a link to the original, since only the platform has the images and the conversation around a post.
  • An item you have already annotated reopens your own answer instead of a blank one, as editing from the Conflicts page already did.
  • Several comments can be labelled at once: press Alt+B, click the comments you mean (or take everything on screen), and apply one label. It is meant for long threads where almost nothing applies. It only answers the first question in your team's schema, skips anything you have already annotated instead of overwriting it, and a label that needs more than that one answer stays greyed out with the reason shown.
  • The “annotated on this page” button now shows how much of the thread each annotator has done, on hover and in a line above the list it opens, so two people working the same video or thread can see each other's coverage without leaving the page. You always see your own, and what you can see of others' work is unchanged.
  • Posts imported from a social-listening source now keep their text and author, so they can be worked entirely from the workspace. Any post someone has already annotated shows its text and author too, however it was collected.
  • For a post nobody holds yet, such as a pasted link, opening it reads what the platform publishes: the post's text and author on X, YouTube, TikTok, Reddit, 4chan and 8kun, and the link preview on any other site. Nothing private or behind a login is read, and only for the post you are about to work on.
  • A post with pictures or video now says how many there are, with a link to view them on the platform, instead of showing the text alone as if it were the whole post.
4chan's archive
  • Posts 4chan has deleted can be annotated on archive.4plebs.org, which keeps them; every post in an archived thread has the usual Annotate button.
  • An archived post keeps its original board and number, so an annotation made on the archive ticks off a queue item added from a boards.4chan.org link, and the same post annotated in either place is one piece of work. An organization cleared for 4chan is cleared for the archive too.
Fixes
  • When a platform redesign removes posts' Annotate buttons, an administrator can enter a replacement on the Platforms page, and every installed copy picks it up within hours, without a store update.
  • The toolbar popup has one button for the page behind it: Add this page on a platform, Annotate this page on an article. Pasting a list of links is done from the workspace.
  • The “✓ You annotated” mark no longer flickers. On sites that redraw posts as you scroll, Reddit especially, the mark was removed and only restored a third of a second later; it is now restored immediately.
  • A site your organization isn't cleared for now says so: the annotate shortcut or the toolbar popup tells you the site is turned off for your organization and that an administrator can turn it on, instead of the extension seeming broken.
  • An annotation held up by a service outage is no longer abandoned after about an hour, which used to need a manual retry. It now keeps trying for up to a week, and the message says the problem is on our side and nothing is lost.
Signing in
  • “Continue with Microsoft” sits beside “Continue with Google” on the sign-in panel and the in-page sign-in card, wherever your organization has been set up for it. Nothing changes for anyone who signs in another way.
  • The extension asks Microsoft only for your email address and name. It can't read your mail, files or calendar and never receives your password. A Microsoft sign-in lasts as long as any other, and signing out ends it everywhere.
  • If a sign-in needs your IT department's approval, the extension shows Microsoft's own message instead of a generic failure, so you know who to ask.
Accounts
  • Administrators and team leads can now send a Microsoft invitation as well as a Google one. The account is created with its role and team already set, the person claims it by signing in, and the roster shows which provider a seat is waiting on.
  • Invitations, password resets and the “no password on this account” notice now come from the extension's own mailbox, an address people can reply to, and a forgotten password can be recovered without an administrator issuing a link by hand.
  • An invitation can now go to any email address. A Google or Microsoft invite used to be limited to a short list of organization domains, and anyone else (a collaborator on a personal address, a partner on their own institution's domain) had to be added to the service's configuration by hand. People still need an invitation from an administrator or lead before they can sign in.
Projects
  • Putting people on a project now opens a share window like those in document tools: type a name in the box at the top, with everyone who already has the project listed below it, one row each.
  • Names picked in the box are added together, so staffing three people is one action, and each row has its own remove control.
  • Anyone can open it to see who is on a project; only a lead can change it.
Exporting
  • Export now works on the item list as well as the Annotated list, so a project's collected posts can be downloaded whether or not anyone has annotated them. A spreadsheet used to hold only finished annotations, so material still waiting to be worked on couldn't leave the tool.
  • The button is on the Items page and on every project and sub-project, and exports what you are looking at: the open project, the current slice, and your search and filters.
  • One download covers both halves of the page: a first sheet of items (each post with its project, assignee and how many people have annotated it so far), then the annotations, one sheet per schema, laid out as the Annotated export always has.
Scripted access
  • Leads can now create an API token on the Settings page and use it from a script or scheduler to download the same workbooks as the Export button, so a nightly export to a data warehouse needs no browser and no password stored in a job.
  • A token can only export. It sees exactly what its owner sees, can't change anything, and stops working once revoked by its owner on Settings or by an administrator on the Users page. It is shown once, at creation, with a ready-to-run command beside it.
  • Both exports can be fetched as JSON or CSV as well as Excel, with the same sheets and columns, so a data pipeline needs no spreadsheet parser. Large exports can be read a page at a time.
  • Leads can also schedule an export: choose the project, the format and how often, and the service delivers the workbook daily or weekly by email or to a storage bucket, without anyone opening the extension. Each schedule shows its last run and what happened, and can be paused, edited, run on demand or deleted from the new Scheduled exports page.
  • A schedule can start from the list you are viewing: the Export button's arrow offers “Schedule this export”, which opens a schedule with that list's project, slice, platforms, people and search carried over and shown, so a recurring delivery is never broader than the list it came from. You only choose how often and where it goes.
  • A schedule can be narrowed to particular people (whose annotations and whose items), chosen from your roster or taken from the list you started from. Left empty, it covers everyone you can see, as before. The form now reads down the page, each question beside its answer.
  • Scheduled exports and imports now share one “Schedules” page with a tab for each, replacing two entries with nearly identical names. Anyone who could only see exports still sees only that tab.
Sources
  • Each organization now has its own watchlist, whichever database stores its work. Outlets a lead approves, removes or edits apply only to their organization, and only its annotators are warned when an AI answer cites one. Organizations sharing a database used to share one list, so a lead in one could add an outlet the other's annotators were then warned about, or remove one they relied on.
  • An organization new to the watchlist starts with an empty list and builds it from its own annotators' reports.
  • The page is now called Sources. Reported outlets, the watchlist and past decisions are more clearly separated, and the explanations run the full width of the page.
Finding your way around
  • The workspace sidebar is now three headings (Work, Managing and General) that open in place, instead of one long list of every page. Daily work is under Work; the pages for setting things up are under Managing.
  • Items moved into Work beside Review and Conflicts, the two pages that watch the queue.
  • Projects are listed alphabetically and can be narrowed to one team, a switch that used to be in the toolbar popup. Hovering over a project shows who is on it, beside the row.
  • Every page shows its title and a short description in the top bar, so a page opened from a link says what it is.
Getting started
  • The Getting started page was rebuilt around what a new account does first: a short checklist that ticks itself off as you go (pin the extension, annotate a post, see where it landed), with the reference material below it.
  • Small diagrams show the annotating loop, the panel, flagging, reviewing and how switching teams changes what you see.
  • Every line is tailored to the reader's role, what their team may do and which platforms their organization is cleared for, so it no longer describes pages you don't have or sites where the extension is deliberately inactive.
Settings
  • Settings is now three panels (your profile, your annotating preferences and API access), with the legal documents along the bottom of the page.
  • Leads and administrators see how many posts their organization has looked at, alongside their own count.
Reviewing
  • The Conflicts page is one table with two views: open disagreements and those you have filed away share the same columns, and each row has both actions (settle it, or file it away), so you no longer scroll past everything already handled.
  • Filing a conflict away changes no annotation. It only affects the list, applies to your organization alone and can always be undone.
  • The Review page now says when it couldn't load instead of showing an empty inbox. A refused or unavailable queue used to read as “nothing to review”, the one message that makes a reviewer stop looking.
  • Ticking a row on the Review page no longer redraws the page, and the sidebar's Review and Conflicts counts are fetched as counts instead of loading both pages in full on every page you open.
  • Agreement between annotators is now measured with the statistics research reports (Cohen's and Fleiss' κ and Krippendorff's α), in the on-page viewer for a post several people annotated and for a whole project on the Conflicts page. A figure that can't be computed says so instead of showing zero.
  • Annotators who choose different “other ideologies” for the same post now raise a conflict. A post everyone agreed was antisemitic but disagreed about otherwise used to be filed as agreement and never surfaced. The row says which of the three answers differs and shows each annotator's choices side by side, and the agreement statistics score this question too.
Managing people
  • Someone at a university address, or at a domain an organization has claimed, can create their own account and ask to join; a lead of that organization must approve them before they can do anything. Organizations can list the email domains that are theirs.
  • Adding someone uses one form everywhere. Leave the password blank and the service emails them a one-time link to choose their own username and password, so nobody has to send anyone a password.
  • The Users page can be narrowed to one organization, and the team list follows it, so a lead picks from their own people instead of everyone.
  • Teams and Organizations are now proper tables, each with its own “new” control in the header, and an organization's schemas are a single list.
Usage
  • Usage can be viewed over a range of months instead of one at a time, and narrowed to a single organization.
For reviewers and ethics boards
  • A public “What we collect” page explains what the extension can see, when anything is sent and what never is, where it goes, what the AI features do, how long data is kept, and how to set up an institutional annotator account. The privacy policy, the options page and the Getting started guide link to it.
Throughout
  • A design pass over the whole workspace: one color for the navigation icons instead of eleven, tables instead of tile grids, real controls instead of rows of text, and explanations built into the page instead of stacked above it. No information was removed.
  • Checkboxes, dropdown menus and scrollbars are dark throughout, including in the annotation panel on the platforms, where they had been light against the dark panel.
  • Every field in the import window now has a screen-reader name, including the search-terms box, which decides what an import collects and previously had none.

v0.6.1

Aug 30, 20269 changes
A lead can create and run a team in their organization: its creator seats and unseats everyone on it and is the only person besides an administrator who can delete it. Admins can send someone a one-time link to set their own password, and the queue's row buttons now announce what they do to screen readers.

Can be annotated after this release: 17 surfaces: X, YouTube, Rumble, TikTok, Reddit, Instagram, Facebook, LinkedIn, Bluesky, 4chan, 8kun, and ChatGPT, Claude, Grok, Gemini, DeepSeek, Qwen.

Teams
  • A lead can create a team inside their own organization, and the creator owns it. An owner can seat and unseat anyone in the organization on that team, other leads included, without asking an administrator.
  • Only the owner or an administrator can delete a team, and deleting it releases the owner's own seat. A team that still has other people on it or still owns projects is not deleted, and the message says which.
  • A team made before this release has no recorded owner, so only an administrator can delete it; nobody inherits a team they did not create.
  • Administrators can send anyone a one-time link to set their own password, instead of making up a starter password for them. Opening the link doesn't use it up, and it works once.
Privacy
  • Where two organizations share a flagged-source watchlist, the outlets are shared but the people are not: who reported or approved an outlet is now shown only to their own organization. The list itself is unchanged.
Projects
  • A project now belongs to the people on it. Everyone, leads included, sees the projects they were added to or created, not every project in their team or organization.
  • Creating a project puts you on it, and you can add leads and annotators by name from its page. They see it in their workspace and in the drawer's “filing this under” picker, and a lead added to it can edit it.
  • A project nobody has been added to stays visible to its team's leads, so nothing made before this release disappears and every project can still be staffed. Administrators still see every project.
Getting around
  • The two buttons on a queue row (assign to me, and remove) now announce what they do to screen readers, which used to read out only the bare symbol on each.

v0.6.0

Aug 27, 202631 changes
8kun joins the imageboards, bringing the annotator to seventeen surfaces. Disagreements can be settled from the Conflicts page, Instagram posts opened from a link can be annotated, and team leads can invite colleagues by email. The page under a teammate's annotation and the Multimodal button under the pointer no longer move unexpectedly.

Can be annotated after this release: 17 surfaces: X, YouTube, Rumble, TikTok, Reddit, Instagram, Facebook, LinkedIn, Bluesky, 4chan, 8kun, and ChatGPT, Claude, Grok, Gemini, DeepSeek, Qwen.

8kun
  • The annotator now runs on 8kun, its seventeenth surface. Threads and replies are annotated in place, on a thread's own page or a board's index.
  • It works like 4chan, since the two sites are built the same way: a post is identified by its board and post number, and a reply carries the posts it quotes as context, so a reviewer reads it within the thread.
  • 8kun work is filed under the same name as the site's earlier addresses, so a thread annotated today lines up with what was collected from it before.
  • It follows the same per-team platform settings as every other surface; an organization that hasn't enabled it sees no change.
Annotating
  • Disagreements can be settled where you see them. On the Conflicts page, your own row has “Edit my annotation”, which reopens the editor on exactly what you submitted (the post, its thread, its media and your labels). Resubmitting overwrites that annotation, as re-annotating in place does, so you don't have to find the comment again to change one answer.
  • The Multimodal button no longer jumps. Clicking it after picking an ideation used to collapse the ideation grid to one line, moving the button up under the pointer (and on a reel, where Multimodal starts on, moving the whole Flags row). A click now leaves the layout alone; sections still fold when you move through them with ↵ and ⇧↵.
  • Instagram posts and reels opened from a link can be annotated. Only posts opened from the feed or a profile were recognized; a reel opened directly lays out its comments differently, so nothing could be annotated and Alt+click found no post. All three layouts and every form of Instagram post URL now work.
  • Work you annotate while browsing now appears in the project you filed it under. A project's Annotated tab used to list only posts first added to it as items, so a post you found yourself appeared in your History but not on the project's page. It now appears in both, and in the project's spreadsheet export.
  • Answering “No” to a required yes/no question now works. No was shown on screen but left out of what was sent, so the service refused the annotation as unanswered and the extension retried it in the background indefinitely, with nothing on screen saying why; only Yes could be recorded. A required question now shows both answers with neither preselected, so an untouched question still reads as untouched, and No is sent as an answer.
Assigning work
  • Who can be put on a project now follows the project tree: a project offers the people on its team, and a sub-project offers the people on the project above it, so a study's batches are staffed from the study. Taking someone off a project also takes them off its sub-projects, and the page says which ones.
  • A sub-project whose parent has nobody on it offers nobody and says so: add people to the project first, then to its parts.
  • The item assignee picker follows the same rule. It had offered everyone the account could see, and work assigned outside its team never reached that person's queue; such names are now neither offered nor accepted. Claiming work for yourself is unaffected.
Exporting
  • The spreadsheet export now has one sheet per schema. The antisemitism panel's sheet keeps its Ideation and Categories columns; a team on its own schema gets one column per question, headed by the question, with answers as the labels the annotator chose and highlighted passages as quoted text. Every sheet has the post, the picked context and the review state. Custom schemas' answers used to be missing, because everything was exported into the antisemitism columns.
Reading a teammate's annotation
  • Opening a post's annotations from its ✓ pill no longer scrolls the page to the top, which on YouTube meant scrolling all the way back down to the comment. The page stays where it was, and closing the viewer returns you to the pill you opened it from.
Teams
  • Team leads can now invite colleagues by email. The admin console's Google invite (a passwordless account claimed by signing in with Google) is also on the lead's Team page, beside the username-and-password form, with the same limits: only addresses in a domain the deployment has approved, only onto the lead's own team, and only with a teammate's role. Until the person signs in, the roster shows the seat as waiting to be claimed.
  • Leads can now arrange everyone in their organization across its teams. A new People section on the Team page lists each person with a chip per team: switch it on to add them, off to remove them, and choose their primary team, where new work is filed. It includes the lead's own memberships, so moving between your organization's teams no longer needs an admin. Other leads' teams are still set by an admin, and nobody can be removed from their last team here.
  • A team member who is a lead now shows as one on a lead's roster; the row used to fall back to the first group, so a cross-team lead looked like an annotator. Leads can set a teammate's level up to senior annotator (making or unmaking a team lead), but only an admin can change a cross-team lead's or an admin's level. Adding someone already on a sibling team keeps their level unless a new one is chosen.
  • A lead's new project is always filed under one of their teams. If the lead had no team, it used to go into the shared pool, which an organization with its own database can't see, so the project vanished as soon as it was made. Now a lead with no team is told to ask an admin, the “no team (shared)” option appears only where the pool belongs to the organization, and a refused create shows the reason instead of “try again”.
  • Each organization now has a list of the schemas its teams may use. An admin grants library schemas to an organization on the Orgs page, and a team lead can only choose from that list. The bundled antisemitism panel is granted the same way, so an organization annotating with its own instruments never sees it, and a schema a team built for itself stays available within its organization. A schema a team uses can't be removed from the organization until that team is switched to another.
  • A project now sets which schema its work uses. A lead chooses it on the project's page; sub-projects inherit it unless they choose their own, the editor switches as you change project, and a team's schema is the default for posts annotated outside any project.
  • Admins can send anyone a one-time link to set their own password, for a starter password that never arrived or an invited account whose Google identity can't be used.
  • The lead who creates a team runs it: they can add or remove anyone in their organization on that team, other leads included, and are the only lead who can delete it.
  • Switching teams now changes what an admin or cross-team lead sees, not just where their work is filed. Picking a team in the toolbar popup narrows the queue, the Items page and the file-under picker to that team's projects, as it already did for everyone else. A new “All teams” option, the default, keeps the full cross-team view.
  • Flagged sources are now kept per organization. Outlets a lead approves, removes or edits on the Flagged sources page apply only to their organization, and only its annotators are warned when an AI answer cites one. A new organization starts with an empty list built from its own annotators' reports.
  • “Flagged for annotation” now shows only flags raised in your own organization, whichever account you use, so a flag and the evidence captured with it stay with the organization that raised it. Nothing else you can see has changed.
  • Importing from a social-listening source is now limited to administrators. One import draws on a request budget shared across the whole deployment and turns one topic judgment into hundreds of entries a team must work through, so it stays at one level until curation is settled. Team leads keep every other way of filling a project.
  • Switching teams now shows the projects you were added to on that team. The annotation panel's project picker used to list every project the team had; it now lists the ones a lead has put you on, and says so when there are none yet. Leads still see their whole team.
Getting started
  • The Terms of Use are now shown and accepted on your first sign-in, before the extension opens, instead of appearing as small print beside the setup form saying that continuing meant agreeing. The screen sets out the key points, links to the full terms and the privacy policy, and has a box to tick. The version you accepted, and when, is recorded with your account and shown in Settings under Privacy & legal.
  • One of those points is new and is why the screen exists: by accepting, you allow the project to say publicly, in presentations, funding reports, papers and press, that your organization uses the extension and that you are one of its authorized annotators. This does not cover your individual work: your annotations are not published under your name, you are not quoted, and nothing implies that you endorse a finding. You can ask us to stop naming you at any time.
  • When the terms change materially, the extension asks again rather than treating your continued use as agreement. It asks only for the acceptance, not the questionnaire, and queued work stays queued in the meantime.
  • The one-time sign-up questionnaire accepts any organization. Its Organization field was a list with one entry (ours), and the service refused any other answer. It is now a text field with suggestions, starting with the organization your account already belongs to.

v0.5.0

Aug 18, 202626 changes
Bluesky, LinkedIn and Facebook join the platforms, the Conflicts page works, and the figures say what they mean: annotation counts come from the annotations themselves, and every oversight page says whose work it shows.
Bluesky, LinkedIn and Facebook
  • The annotator now runs on Bluesky, LinkedIn and Facebook, bringing it to 16 surfaces. Bluesky posts and replies, and LinkedIn and Facebook posts and comments, are annotated in place like everywhere else.
  • Each is its own piece of work. A Bluesky post keeps one identity whether its link names the author by handle or by DID, and a LinkedIn or Facebook comment is separate from its post, so flagging one comment doesn't mark the rest.
  • LinkedIn is partway through rebuilding its feed, and the annotator reads both layouts. The new one gives posts and comments no link of their own, so work captured there is stored with the post rather than a URL nobody else could open.
  • Flagging a LinkedIn or Facebook post that only its group can see attaches what was captured, as flagging an AI conversation does, because the link alone would show a join wall to whoever picks up the flag. Public posts are still flagged by link.
  • All three follow the same per-team platform settings as other surfaces; an organization that hasn't enabled them sees no change.
The work queue
  • Annotators can assign work to themselves. The button and the unassigned items were always shown, but the request was refused as lead-only, so the click silently did nothing. Taking work off your own list works the same way.
  • Assigning work to others is still a lead's decision, so an annotator now sees only the controls for their own list.
  • A failed queue change now says why instead of silently leaving the row as it was.
Annotating
  • On 4chan the Annotate button is no longer cut off. It sits in the post's header line, level with the name and date, in the same place on every post, and that line now reserves room for it; posts are drawn in boxes sized to their widest content, which clipped anything past the edge. Two smaller causes were fixed too: the reserved space was dropped moments after each post was drawn, and the button's label could open wider than the post.
  • Wherever the label still doesn't fit, on any site, the button stays an icon instead of opening partly off the edge.
Flagging
  • A comment you have typed now stays with a flag. The editor used to warn that flagging would discard the annotation, and it did, comment included, so writing a note (say, about a post the extension read wrongly) and then flagging cancelled each other out. The note now becomes the flagged item's first comment, so whoever picks up the flag can read why.
  • The warning before flagging now appears only when there are labels to lose, and says what happens to the comment. With only a comment typed, flagging just works.
  • Flagging a post someone on your team already flagged adds your note to the existing item instead of creating a second one.
Review & conflicts
  • The Conflicts page works again. Since the annotation platform moved to its current storage on August 5, it had shown nothing while stating “Every post labeled by 2+ annotators has matching labels”, although it wasn't reading your data. Disagreements were recorded correctly throughout, which is why the side-by-side view on the post itself kept showing them.
  • Conflicts is now a comparison rather than a decision. Every annotation is kept and agreement is scored across them, so the page shows who chose what instead of offering to pick a winner; coaching happens through Review.
  • The Review page now names the teams its inbox covers. Some reviewers oversee every team in the organization and others only their own, but the page described them all the same way, so two reviewers comparing inboxes couldn't tell a difference in scope from a fault.
  • It also explains two other reasons reviewers see different lists: approving a row removes it from everyone's inbox, and an annotation is auto-approved if its author already held a reviewing role when submitting it, so a colleague's older work can appear while their recent work doesn't.
  • Annotations by someone not on a team are now reported instead of disappearing, since no team's reviewer could approve them. The page shows how many there are and that an admin needs to add the annotator to a team.
  • A reviewer who oversees several teams no longer sees the names of annotators from other organizations.
Usage & limits
  • “Stored annotations” now counts what each person has actually stored, read from the records themselves. A revised post counts once, a re-sent submission counts once, one the service refused doesn't count, and an annotation a lead deletes stops counting.
  • The figure used to count accepted submissions, which could run far ahead of the work done, most visibly for anyone annotating during the August 11 service interruption, whose submissions were re-sent many times before they could be stored. Those numbers correct themselves, since the figure is recounted on every page load.
  • The old count remains under its own name, “Submission attempts”, on the metered resources card. Monthly limits apply to it, and it reflects load on the service rather than work produced.
  • If an organization's records can't be read, the page names it and says the figures are incomplete instead of silently showing a smaller number.
  • The page now opens with what needs attention: every person and team at or near a monthly limit, by name, and whether anything is actually being refused. It appears only when there is something in it.
  • Every column sorts, long lists of people can be filtered by name, and the whole month can be exported as a spreadsheet.
  • The page shows a loading message instead of an empty rectangle while figures are fetched, and a second click can no longer send the request to turn on enforcement twice.

v0.4.0

Aug 12, 202640 changes
The antisemitism taxonomy is now the Decoding Antisemitism Lexicon itself, unaltered. Multi-team tenancy arrives too: a team owns its annotation schema and its set of surfaces, and every page that reaches across organizations is admin-only.
Annotation taxonomy
  • The categories in the annotation drawer are now the Decoding Antisemitism Lexicon's own: all 40, under the Lexicon's names and in its order, grouped into its six parts. AddressHate's own revisions are gone, so the extension can be read alongside the book it comes from.
  • Each category shows its concept number, so you can look it up in the Lexicon directly.
  • Three earlier categories were merged back into the Lexicon concepts they had been split from, and Evil/The Devil and Immorality, which the Lexicon covers in two places, are separate categories again instead of one heading.
  • Work annotated before this change keeps its categories. Nothing was relabelled retroactively; a past annotation still records the category the annotator was shown.
Platform access
  • Which sites and AI chats a team may annotate on is now a setting: an admin ticks the 13 surfaces per organization and per team, so a team limited to one research question, or an agreement that excludes AI-chat transcripts, is enforced rather than explained.
  • An organization's list is a ceiling its teams can narrow but never widen, and a surface the organization has turned off shows as unavailable on the team's row instead of as a box that does nothing.
  • A team without its own list inherits its organization's. Enforcement happens in the page (no Annotate button on a surface the team doesn't hold) and again when the submission arrives, since the first check runs on the annotator's machine.
  • Nothing is restricted by default: the shipped policy is empty, so every team keeps all 13 surfaces until an admin unticks one.
Teams and organizations
  • Each team assigns its own annotation schema, resolved from the team, then the organization, then the default, so changing one team leaves its siblings alone.
  • An acting-team switcher: the team you are annotating for decides the schema, the destination and the meters, while what you can see still spans every team you belong to.
  • Pages that reach across tenants are admin-only. A lead's oversight covers every team in their own organization, not other organizations' names, rosters or totals.
  • The organizations page is one collapsible table of organizations and their teams, with drag-and-drop between them using the same confirmed move as the buttons.
  • Every move confirms against a dry run that names the people it re-files, and makes clear that existing annotations stay where they are and only future work moves.
  • A person belongs to teams in one organization only, as many as you like within it; no account, admins included, can hold seats in two organizations.
  • Moving someone to another organization releases their teams in the old one, named in the confirmation first. When a team moves, anyone it leaves behind or carries along is likewise named and released, never left in two organizations.
  • Moves now warn first if a member is missing from the target organization or a team schema isn't published there, instead of failing submissions later.
  • The teams page shows every team in your organization; teams you're not on are read-only instead of a form that would be refused on save.
  • A platforms page sets which sites and AI chats each organization and team may annotate on. A team can narrow what its organization allows but never widen it, so an organization-level limit is a real ceiling.
  • Platforms a team isn't cleared for don't show the annotation tools, and the service also refuses submissions from them, so the policy holds whatever the browser does.
  • The toolbar popup now files work under the team selected in its header. It used to file queue changes under your primary team, and its queue could show a different team's list than the full page.
Annotating
  • The annotation panel shows who the work is for: a line under the post names the team and, if you have chosen one, the project, and both can be changed there instead of in the toolbar. Switching teams reopens the editor with that team's schema, warning first if you have already started.
  • The project you pick is a standing choice: it stays selected for everything you annotate next, across posts and sessions, until you change it in the panel.
  • Flagging follows it: a post flagged while working through a project goes into that project instead of a shared pile to be sorted later. The confirmation names where it went, and your list of flags shows it on each row. With no project selected, a flag still goes to the team's flagged queue.
  • The panel shows the platform's logo instead of a two-letter code, matching the queue and history rows.
  • The post and the thread it replies to now share one space at the top of the drawer, so a long comment on a long post no longer fills most of the panel before the annotation controls.
  • A “Show less” control shrinks that area further and stays set across posts and sessions, in both the antisemitism panel and custom schema forms. It appears only when there is something to shrink.
  • Every reply in a Reddit thread has its own Annotate button. Nested replies were skipped and could only be annotated by holding Alt and clicking, if you knew to.
  • On 4chan the Annotate button is no longer clipped by a narrow post: its label opens in whichever direction the post has room for, instead of always to the right and off the edge of a short reply.
  • Custom schemas now match the built-in panel: reopening an annotation pre-fills your answers. Resubmitting overwrites the previous annotation, so an editor that opened blank was silently replacing finished work; this was the release's most important fix.
  • The flag pill, the thread-context box (on a chat, the opening request and the prompt that produced the response) and the AI explanation now work with custom schemas, so teams on their own schema see the question when judging a response.
  • Annotation schemas are versioned, so an answer is always shown against the definition it was given under, however often the schema changes.
Syncing your work
  • Finished annotations are now sent several at a time instead of one after another, so an offline backlog clears in about the time of the slowest one rather than the sum of all of them.
  • A waiting queue is retried when the extension starts, when your connection returns and when you sign in, the moments when whatever blocked delivery has usually just cleared.
  • Each submission retries on its own schedule, so a new annotation no longer resets the timing for everything waiting, and a submission the service just refused isn't re-sent every few seconds.
  • When the service itself is failing, the queue stops after the first refusal instead of trying every annotation. Delivery used to spend its whole retry allowance within minutes of an outage; it now lasts through it.
  • Two ways an annotation could sit on “syncing” forever are fixed: a submission filed for a team you have left now says so instead of retrying silently, and the queue can no longer end up with no delivery scheduled.
  • “Retry now” retries immediately; it used to report success without doing anything if the queue was busy.
  • The popup counts retrying work separately from work in progress, so a stuck queue no longer looks nearly done.
Settings
  • The settings page has four cards instead of seven: signing out and deleting your account share a line, the panel and post-counting toggles share a card, and the privacy, terms, support and roadmap links moved to a full-width footer with the version.
  • The extension now reaches the service at a permanent address, so the service can move between machines without anyone updating anything. The address is no longer an editable setting; the text box could have sent an annotator's credentials to another server and served no other purpose. The page shows which service it is connected to.

v0.3.0

Aug 8, 202620 changes
The platform set nearly doubled, and the annotation panel became configurable per organization instead of fixed in code.

Can be annotated after this release: 13 surfaces: X, YouTube, Rumble, TikTok, Reddit, Instagram, 4chan, and ChatGPT, Claude, Grok, Gemini, DeepSeek, Qwen.

New surfaces
  • Rumble and TikTok, both the video and its comments.
  • Three more assistants: Gemini, DeepSeek and Qwen.
  • Reddit submissions themselves became annotatable, with the submission carried as context for its comments.
Annotating
  • Flag and Annotate moved into the chat's own action row, beside every other control for that response, instead of landing in the middle of a long answer.
  • A highlighted passage now anchors to that passage instead of to the whole response, so precise evidence stays precise.
  • On extension pages the editor opens as a centered modal, since there is no post behind it for a side drawer to keep visible.
  • On Qwen, Annotate and Flag join the platform's own selection menu instead of competing with it for the same corner of the screen.
Flagged sources
  • Citations to watchlisted outlets are marked inline in an assistant's response, with the reason one click away.
  • Anyone can report an unlisted outlet; leads triage reports into the watchlist every annotator's extension fetches, with no rebuild.
  • Detection only: a flagged citation is never an automatic hate label.
Per-organization annotation schemas
  • A schema builder with visual, JSON and layout tabs, and a live preview that uses the same renderer as the annotators.
  • Custom HTML and CSS layouts with field placeholders, validated the same way on the client and the server, so a layout can't pass one and fail the other.
  • Starting-point presets, so a new schema begins from a working example.
AI budget
  • AI use is metered per organization, team and person, with monthly limits and a Usage & limits page.
  • Every account starts with 5 pre-annotations and 5 explanations a month, a default allowance rather than an unlimited one.
Reliability and safety
  • A security review: hardened sign-in and queue authorization, HTTPS-only ingest, rate and cost limits, and baseline security headers on every response.
  • The normalized annotation database became the authoritative store for every submission.
  • Every network call has a timeout. An accepted connection that never answered used to hang forever and could make the extension look dead on the page.
Workspace
  • Platform brand logos on every queue and history row.
  • One shared set of design tokens behind the whole interface, so the popup, the panel and the workspace stay consistent.

v0.2.0

Aug 4, 20268 changes
Five more surfaces, and adding a colleague no longer requires a shared password or a redeploy.

Can be annotated after this release: 8 surfaces: X, YouTube, Reddit, Instagram, 4chan, and ChatGPT, Claude, Grok.

New surfaces
  • Grok conversations.
  • Reddit and Instagram comments.
  • 4chan threads.
Accounts
  • An admin can invite a colleague from the console: a passwordless account with its permission group, team and organization already set, claimed by signing in with Google.
  • The accounts roster groups by team, permission group or role, collapses and searches; a flat list stopped working past about thirty accounts.
Fixes
  • Post identity is stable on YouTube, so the badge on an already-annotated comment (and the flag pill beside it) no longer disappears and reappears as the page redraws.
  • A flag placed on a permalink is recognized wherever that post appears.
Permissions
  • The extension requests no site access beyond the ingest service itself, the only place it sends requests, so the platform permissions it used to ask for were never needed.

v0.1.0

Jul 16, 202618 changes
The first release: annotate in place on the platform itself, with a lead's approval required before a submission enters the corpus.

Can be annotated after this release: 3 surfaces: X, YouTube, and ChatGPT and Claude conversations.

Annotating in place
  • Hover over any post or comment, click Annotate (or press Alt+A), and classify it against the AddressHate label space in a drawer beside the post, without copying it into a separate tool or losing sight of it.
  • The thread comes with it: reply chains, quoted posts, the parent comment, the video or conversation the post sits in, and its media.
  • Keyboard navigation between posts, picking the co-text comments that make a post understandable, and a five-second undo after every submit.
  • ChatGPT and Claude conversations can be annotated too: an assistant turn, or a selected excerpt of one, with the prompt that produced it captured as context.
Sync that doesn't lose work
  • Submissions are queued locally and delivered with retries, so work done through a dropped connection, a sleeping laptop or a browser restart is kept.
  • The editor stays on screen until a submission is acknowledged, instead of closing and hoping it arrived.
The review gate
  • An annotation is archived immediately but stays pending until a lead approves it. Approval commits it to the database and runs the AI second opinion.
  • Leads get an approval inbox with the captured evidence, a conflicts view for posts where annotators disagree, and coaching feedback that annotators see on their own history rows.
Evidence flags
  • Flag a post for someone else to annotate, with the passage that prompted the flag highlighted.
  • Flagging inside a private conversation requires consent, and the evidence can only be read in the workspace; nobody else can open someone's chat from its URL.
Accounts and roles
  • Username and password or Google sign-in, with capabilities from permission groups (admin, lead, senior annotator, annotator, flagger) resolved live, so a change to a group applies immediately.
  • Teams are the isolation unit: two teams don't see each other's flags or annotations.
  • A one-time onboarding agreement before first use.
The workspace
  • A full-page Items dashboard over the shared work queue: directories, creating items by pasting a list, assignment and filtering.
  • History with review status on each row, date and project filters, and export to .xlsx.
AI second opinion
  • An optional model pre-annotation and plain-language explanation beside the annotator's own answer, scored for agreement: a second opinion, never a substitute for the annotator's.
Hosting
  • The ingest service on Cloud Run, with a durable archive of every submission envelope.
  • These public pages: privacy, data deletion, terms and support.

How versions are numbered

What the version numbers mean.

Versions are numbered major.minor.patch. On the 0.x line, the middle number moved for each release and the last number for a fix shipped on its own. 1.0 marked the point the tool was stable across every surface it supports, not a date; releases since then move the last number. The version shown above is the one in the extension’s manifest, which is also what Chrome shows on its extensions page, so you can compare it with the version you have installed.

Questions about a release: extension@addresshate.org. Setup and troubleshooting help is on Support.