website.strange.ephemera

Short note published on henry.codes/micro. Canonical and contains syndication information.

Repository @strange.website did:plc:pbr2nzfsr6bcqjeqlvohmh5y not from the namespace authority
Details · record, key tid
Kindrecord
Record keytid
Authoritystrange.website
Indexed

Record

record · key tid

Properties

content

requiredstring

Post body, in Markdown format.

  • maxLength: 100000

createdAt

requiredstring · datetime

embed

union
One of
Reference
itemsref
Reference

tags

array
  • maxLength: 8
itemsstring
  • maxLength: 640
  • maxGraphemes: 64

updatedAt

string · datetime

#replyRef

object

Threading information, mirrors app.bsky.feed.post#replyRef.

Properties

parent

requiredref

root

requiredref

#syndication

object

Properties

cid

string · cid

Needed to reply to this post when threading.

network

requiredstring
  • knownValues: bluesky | mastodon

syndicatedAt

requiredstring · datetime

text

string

Exactly what was posted to this network.

uri

string · at-uri

url

string · uri

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • A post that lives on Atmos and is not shown on Bluesky. It sits in the author's own repo and is public like every record there: any AT Protocol app can read it, but apps that do not know this type do not show it, so it does not appear on Bluesky. When the author shares it to Bluesky, an app.bsky.feed.post is written at the same record key and crosspost names it; the two records are one post. Treat crosspost as the link between them, never the shared record key alone, and only when crosspost.uri

  • An embedded Bluesky post.

  • A quoted record, optionally narrowed to a passage of it.

  • Record containing a GainForest feed post. A faithful port of app.bsky.feed.post into the app.gainforest.feed namespace. A reply (i.e. a 'comment') is a post that carries a `reply` ref; because that ref uses com.atproto.repo.strongRef, the GainForest appview can honour replies whose parent/root is ANY record in the commons (an observation, project, cert, organization, or donation), not only another post. Deprecated `entities`/`textSlice` fields from the Bluesky source were omitted in favour of `f

  • town.delve.feed.post

    record not from the namespace authority

    Record containing a Bluesky post.