How the Bluesky map works
Atlasemoji turns a public Bluesky thread into a map. Paste a Bluesky post URL, and the mapper reads the public conversation, detects location signals, geocodes recognized places, and places them on the map as either topic locations or poster locations.
What data we read
The mapper uses public Bluesky / AT Protocol data. It does not ask for your Bluesky password, does not log into your account, and does not read private messages. It reads the public post thread you paste and public profile fields for accounts that appear in that thread.
- Post text from the pasted thread.
- Reply text from public replies in the thread.
- Public embedded link titles and descriptions when available.
- Public author handles, display names, avatars, and profile bios.
Where the data comes from
Bluesky is built on AT Protocol. Atlasemoji calls public Bluesky API endpoints to retrieve the thread and public profile summaries.
Retrieves the public conversation tree for the post URL you pasted, including replies returned by the Bluesky API.
Retrieves public profile summaries for authors in the thread. Atlasemoji uses these public profile fields to look for declared locations such as “London,” “Seattle,” “based in Berlin,” or “📍 New York.”
Topic vs poster locations
These are places mentioned by the conversation itself. For example, if a post says “London,” “Belarus,” “Maine,” or “Rock Island,” Atlasemoji treats that as a topic location.
These are locations declared by people participating in the thread, usually from public profile bios. Poster locations use the account avatar on the map when available.
How places become map points
- Atlasemoji scans the public thread text, embedded link text, and public profile bios for location phrases.
- It classifies each detected place as either a topic location or a poster location.
- It geocodes recognized places into latitude, longitude, and geohash values.
- It builds a reusable Atlasemoji manifest and GeoJSON feature collection.
- It sends those mapped rows into the main Atlasemoji map so the result appears visually instead of only as JSON.
Why some maps are sparse
Not every thread contains mappable locations. Some people do not put locations in their profiles, and many posts do not mention places. A thread about “London,” “Belarus,” or “Maine” should produce topic markers. A thread with participants who publicly say “📍 London” or “based in Seattle” should produce poster markers.
Sharing notes
The safest share format is a plain Atlasemoji map link plus a short explanation. Bluesky does not render arbitrary iframe HTML inside a post composer, so iframe embed code is mainly for websites that allow iframe embeds. A shared Atlasemoji link also needs to point to a deployed environment where the saved manifest exists.
“Mapped this Bluesky thread with Atlasemoji: [map link]”
Privacy boundary
Atlasemoji does not infer a private home address. The mapper only uses public text and public profile fields. If a profile says “London,” the marker represents that declared public place, not a precise personal address.