About and methodology

This site is built from the exported X archive for Stoke Newington History. It publishes public post history only and excludes private archive material.

Public archive boundary

This standalone site begins with the first archived post published after the account-transition note from 2 October 2013.

Preceding post: "I moved from the Common a while ago and have been focusing mainly on local history so this account has a new name and avatar. Still me."

What is included

Public posts from data/tweets.js, account metadata needed for context, media files from data/tweets_media when present, and derived analytics generated from those files.

What is excluded

  • data/direct-messages.js: Private direct messages are not public archive content.
  • data/direct-messages-group.js: Private group messages are excluded.
  • data/direct-message-headers.js: DM metadata is private and unnecessary.
  • data/contact.js: Contacts/address-book data is private.
  • data/ad-impressions.js: Advertising data is irrelevant to the public tweet archive.
  • data/ad-engagements.js: Advertising engagement data is excluded.
  • data/account-creation-ip.js: Security-sensitive account metadata is private.
  • data/device-token.js: Device tokens are private and security-sensitive.
  • data/ip-audit.js: Account access/IP audit history is private.
  • data/phone-number.js: Personal account data is excluded.
  • data/email-address-change.js: Internal account history is private.
  • data/deleted-tweets.js: Excluded by default until explicitly chosen for publication.

Known limitations

  • The export contains no usable geo or place fields for posts, so location-aware analysis depends on text matching rather than geotags.
  • Conversation IDs and quote-post context are not present in this export, so thread recovery is limited to reply chains between posts in the archive.
  • Some uploaded media is missing. In this archive, 607 referenced media items are unavailable and are shown with placeholders.
  • Deleted posts are present in the export but excluded from the public site unless intentionally enabled later.

Thematic analysis pipeline

Thematic pages use a practical short-text pipeline: URL removal, token cleaning, stop-word removal, keyword and phrase frequency, manual place matching, and editable rule-based theme labels tuned for local-history topics such as archives, buildings, ghost signs, talks, memorials, and heritage campaigns.

Privacy choices

Direct messages, contact/address-book data, ad datasets, security-related files, IP history, device tokens, and similar account-internal records are intentionally ignored and never copied into the public build.