Are.na
Coming soonAre.na is a creative-research platform where people collect blocks (images, links, text) into channels and connect them across channels over time. Pairing it lets ~Alter recognise the shape of how you gather and relate ideas: how many channels you keep, how often you recombine a block into a new context, and the mix of subjects your recent channels cover.
Coming soon
Pairing Are.na isn't live yet. This page documents what ~Alter will read once it is, published ahead of launch so you can see exactly what it will and won't touch before you ever pair it. The pairing button stays disabled until this connector goes live.
What pairing does not authorise
Pairing this connector is a read commitment, not delegation. Specifically, ~Alter cannot use this pairing to:
- •Post, edit, or delete blocks or channels on your behalf.
- •Follow, connect to, or message other Are.na users.
- •Join, leave, or change membership on any channel.
- •Change your profile, avatar, or account settings.
- •Surface your Are.na pairing to any third party without a separate consent row scoped to that recipient.
The OAuth or attestation scope we request is the minimum required to recognise the pattern described in What we read. Anything beyond that is structurally refused at the connector boundary, not promised by trust. How pairing works.
What we read
- Your Are.na account id, username (slug), and profile URL.
- Your first and last name, if set on your Are.na profile.
- Your total channel count.
- Your connection count, the block-recombination activity Are.na aggregates across your channels.
- The titles of up to 20 of your most recent channels, read to characterise the mix of what you collect, not the blocks inside them.
What we don't read
~Alter explicitly refuses these fields even when the OAuth scope or API permits them. Every refusal is enforced at the connector boundary, not by trust.
- The contents of any block: the images, text, links, or files you've saved.
- Comments or any social activity beyond the channel titles themselves.
- Other users' channels, blocks, or profiles, even ones you've connected to.
- Your email address or any Are.na account credential.
Where it lives
Evidence is stored in ~alter's pairing ledger keyed to your ~handle. The channel count and connection count are read and kept, but neither maps to a trait in your identity vector yet: both wait on a bias-validator four-fifths clearance before they activate. Until that clears, pairing establishes provenance only. Once active, the derived pattern feeds your identity vector only after a separate consent row is granted.
How to revoke
Nothing to revoke yet, since Are.na cannot be paired. This is the revocation you will get when it goes live, published now so you can see the way out before you ever choose the way in. Revocation will be immediate. You will ask the AI client you paired through to revoke this connector, or revoke it from your consent surface over the same connection. Either path revokes the provider token, stops all further reads, and purges the derived signals this connector fed into your identity vector. An audit row records the revocation.
One thing is kept on purpose. The connector retains a record that this account was paired and when it was disconnected, so the same account cannot be unpaired and re-paired in quick succession to churn your identity vector. That cooldown record holds the raw profile snapshot until the window passes. It is never read into a new signal while disconnected, and it is not shared with anyone.
Prefer the command line? The CLI is the optional deeper path and revokes the same connector:
CLI (optional)
alter unpair are-naPairing this connector does not enrol you in any matching, ranking, or matching surface. Every downstream use requires its own consent row. See the consent model.