{
"$type": "site.standard.document",
"content": {
"$type": "at.markpub.markdown",
"flavor": "GFM",
"text": "\nThis is where the data lives that is used by apps like [bluesky](https://bsky.app), [leaflet](https://leaflet.pub), etc.\n\nThese notes are synced to [my PDS](https://pdsls.dev/at://did:plc:s7xw6pqvc72ha73bogjqp4m3/site.standard.publication/3ml5obpcbda2o#backlinks:site.standard.document) via the [obsidian-standard-site](https://github.com/SootyOwl/obsidian-standard-site) plugin. Since they exist as AT Records, they should be able to pick up backlinks via [constellation](https://constellation.microcosm.blue).\n\n[Digital Gardening](/digital-gardening) is able to pick up a backlink from [this leaflet post](https://writing.drewmca.net/3ml5wpyblw226), but only because I directly copied in the at:// URI. If I just link directly to `https://notes.drewmca.net/Digital-Gardening`, the records don't reference eachother. If I try to link to `at://did:plc:...`, clicking the link in the web browser doesn't work.\n\nI think what's missing here is some `http url -> at uri` resolution. I'd like to be able to, within a leaflet or bsky post, just copy in the URL to this note. Then, through the existing `<link rel=`, another client could recognize that the URL to this note is really an ATproto record and reference it appropriately.\n\nIf you inspect the HTML of this page, you'll see in the `<head>`,\n\n```html\n<link\n rel=\"site.standard.document\"\n href=\"at://did:plc:s7xw6pqvc72ha73bogjqp4m3/site.standard.document/3ml6ypek4wi2s\"\n/>\n<link\n rel=\"alternate\"\n type=\"application/atproto\"\n href=\"at://did:plc:s7xw6pqvc72ha73bogjqp4m3/site.standard.document/3ml6ypek4wi2s\"\n/>\n```\n\nAnd if you were to just look at the response headers, you'd see... well, in theory at least:\n\n```HTTP\nAtproto-Uri: at://did:plc:s7xw6pqvc72ha73bogjqp4m3/site.standard.document/3ml6ypek4wi2s\n```\n\nThen, the remainder is just getting applications like [leaflet.pub](https://leaflet.pub) and [bsky.social](https://bsky.social) to recognize when a URL like `notes.drewmca.net/the-ATmosphere` has an associated AT URI and include that reference in the record they're creating. Then, backlinks will show up here for free!\n\n#### References\n\n- https://atproto.com\n- https://atprotocol.dev\n- https://atmosphereaccount.com\n"
},
"path": "/the-atmosphere",
"publishedAt": "2026-05-06T15:17:48.833Z",
"references": [
{
"uri": "at://did:plc:s7xw6pqvc72ha73bogjqp4m3/site.standard.document/3ml5ofekxhq2z"
}
],
"site": "at://did:plc:s7xw6pqvc72ha73bogjqp4m3/site.standard.publication/3ml5obpcbda2o",
"textContent": "This is where the data lives that is used by apps like bluesky, leaflet, etc.\n\nThese notes are synced to my PDS via the obsidian-standard-site plugin. Since they exist as AT Records, they should be able to pick up backlinks via constellation.\n\nDigital Gardening is able to pick up a backlink from this leaflet post, but only because I directly copied in the at:// URI. If I just link directly to https://notes.drewmca.net/Digital-Gardening, the records don't reference eachother. If I try to link to at://did:plc:..., clicking the link in the web browser doesn't work.\n\nI think what's missing here is some http url -> at uri resolution. I'd like to be able to, within a leaflet or bsky post, just copy in the URL to this note. Then, through the existing ,\n\nAnd if you were to just look at the response headers, you'd see... well, in theory at least:\n\nAtproto-Uri: at://did:plc:s7xw6pqvc72ha73bogjqp4m3/site.standard.document/3ml6ypek4wi2s\n\nThen, the remainder is just getting applications like leaflet.pub and bsky.social to recognize when a URL like notes.drewmca.net/the-ATmosphere has an associated AT URI and include that reference in the record they're creating. Then, backlinks will show up here for free!\n\nReferences\nhttps://atproto.com\nhttps://atprotocol.dev\nhttps://atmosphereaccount.com",
"title": "the ATmosphere",
"updatedAt": "2026-05-17T06:17:30.592Z"
}