I think using org.atmosphereconf.profile as a type is a great idea.
An example could look something like this:
at://did:plc:cbkjy5n7bk3ax2wplmtjofq2/org.atmosphereconf.profile/self
With content that looks like this:
{
"$type": "org.atmosphereconf.profile",
"avatar": {
"$type": "blob",
"mimeType": "image/png",
"ref": {
"$link": "bafkreiarfc33ygmvwuwfhkdg4sm4n6ua46bg4s63moajb6xrkdimvnzcyq"
},
"size": 466197
},
"displayName": "Nick Gerakines",
"homeTown": {
"$type": "community.lexicon.location#h3",
"h3": "852a9067fffffff",
"name": "Kettering"
},
"interests": [
"ATProtocol",
"Software Development"
]
}
A few call-outs:
- The “homeTown” field is set to one of the location types for indexing.
- The “avatar” is a user-provided profile picture.
- The “interests” field is user-provided tags for conference topics and social activities
RSVPs
When someone purchases a ticket or RSVPs to the conference event ( Smoke Signal ) then the atprotocol.dev identity can create an attestation record with organizer-provided proof.
For example, my RSVP would be updated to include a signature reference:
{
"$type": "community.lexicon.calendar.rsvp",
"createdAt": "2025-09-19T17:33:18.908Z",
"status": "community.lexicon.calendar.rsvp#going",
"subject": {
"cid": "bafyreia66bgnwqxxiq74c6w27xr3gwtiqeuklfs4a6jwulcaxbwb3rowiu",
"uri": "at://did:plc:lehcqqkwzcwvjvw66uthu5oq/community.lexicon.calendar.event/3lte3c7x43l2e"
},
"signatures": [
{
"$type": "com.atproto.repo.strongRef",
"cid": "bafyreigqcfmzvvnxnvx5iafituqtnshg33dt23rqp2x5ome7hmiow3op3q",
"uri": "at://did:plc:lehcqqkwzcwvjvw66uthu5oq/org.atmosphereconf.rsvpEndorsement/3m3fqaop4tyng"
}
]
}
And in the atprotocol.dev (did:plc:lehcqqkwzcwvjvw66uthu5oq) repository, the following record would be created:
{
"$type": "org.atmosphereconf.rsvpEndorsement",
"cid": "bafyreidqi6gk7rzddy2kxgglejntukvnpkppdlwzgg7ds2hax4n4fow32m",
"role": "organizer"
}
Because it’s just a record, no additional or confidential signing data would be needed.
AppView
Lastly, with the three record types (profile, RSVP, and RSVP endorsement), an app view that subscribes to Jetstream to watch for record events would render an interactive map, interest pages, attendee profiles, etc. Just throwing some ideas out there.
https://going.atmosphereconf.org/2026 - the base URL
GET /2026/ - Displays recent activity leading up to and on the day of.
GET /2026/map - Displays a map of where attendees are coming from
GET /2026/u/[handle] - Attendee profile pages
GET /2026/i and GET /2026/i/[interest] - Interest tag cloud and directory
GET /2026/e and GET /2026/e/[handle]/[record_key] - Official and unofficial event directory and information
because it’s hip rn and uses Slices for indexing/auth.