Lexicon Garden

at.mapped.post

A post representing either an activity or a travel experience

Repository @mapped.at did:plc:l5m5nuh5cvdatyn5fjxar2sh namespace authority
Details · record, key tid
Kindrecord
Record keytid
Authoritymapped.at
Indexed
Compare Edit in builder → Fork →

Record

record · key tid

Properties

activityType

ref

Reference to an activityType record. If present, this is an activity post; if absent, it's a travel post

Reference

basePost

ref

Reference to another post that this post is based on (e.g. a travel post based on an activity post)

Reference

location

ref

Reference to a location record

Reference

text

string

Caption or description text for the post

  • maxLength: 500

timestamp

requiredstring · datetime

When the post was created

title

string

Optional title for the post (especially useful for travel posts)

  • maxLength: 100

trail

ref

Reference to a trail record with route geometry

Reference

Similar lexicons

semantic match

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

  • at.mapped.trail

    record

    A trail

  • app.kalangitan.feed.post

    record not from the namespace authority

    A standard post. Location is a required part of every record in this app, not an optional tag. Belongs to exactly one persona via profileUri; the persona's location.visibility defaults govern how the location is stored and shared. For a gated persona this record lives inside the persona's Space. Spaces provide access control, not confidentiality. The space host and PDS operator can technically read this data.

  • at.mapped.activity

    record

    An activity like Hiking, Cycling, Kayaking

  • place.pollen.post.text

    record

    A text-only post. Thoughts, stories, musings.

  • cv.atmos.feed.post

    record

    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