Lexicon Discovery Roadmap

[ngerakines]

With the Lexicon Discovery RFC moving forward and an early reference implementation of a lexicon discovery service live at https://lexidex.bsky.dev/, the next big step for Lexicon Community is to make our lexicons discoverable.

Currently, the @lexicon.community handle maps to did:plc:2uwoih2htodskvgocarwv5eq.

The next step is to create the following TXT DNS records:

• _lexicon.bookmarks.lexicon.community -> "did=did:plc:2uwoih2htodskvgocarwv5eq"
• _lexicon.calendar.lexicon.community -> "did=did:plc:2uwoih2htodskvgocarwv5eq"
• _lexicon.location.lexicon.community -> "did=did:plc:2uwoih2htodskvgocarwv5eq"

Then, the following records will be created:

• at://did:plc:2uwoih2htodskvgocarwv5eq/com.atproto.lexicon.schema/community.lexicon.bookmarks.bookmark
• at://did:plc:2uwoih2htodskvgocarwv5eq/com.atproto.lexicon.schema/community.lexicon.calendar.event
• at://did:plc:2uwoih2htodskvgocarwv5eq/com.atproto.lexicon.schema/community.lexicon.calendar.rsvp
• at://did:plc:2uwoih2htodskvgocarwv5eq/com.atproto.lexicon.schema/community.lexicon.location.address
• at://did:plc:2uwoih2htodskvgocarwv5eq/com.atproto.lexicon.schema/community.lexicon.location.fsq
• at://did:plc:2uwoih2htodskvgocarwv5eq/com.atproto.lexicon.schema/community.lexicon.location.geo
• at://did:plc:2uwoih2htodskvgocarwv5eq/com.atproto.lexicon.schema/community.lexicon.location.h3

The content of those records will correspond to the appropriate community/lexicon/... file.

The long-term goal is to automate this process through a tool that can both publish the lexicon records to the lexicon.community repository and also create DNS records.

References:

• RFC: Lexicon Resolution bluesky-social/atproto#3074

[tom-sherman]

also create DNS records

I need to re-read the RFC but is it not possible to add a *.lexicon.community record or something?

[tom-sherman]

Hmmm, it seems to still be an open question?

[tom-sherman]

Bryan confirmed that you need a DNS record for each group, so the plan you've outlined is correct.

[ebwinters]

you'd need to enable Github actions on the repo but I think it would be simple to add a script to our repo that signs in with an app key and creates a com.atproto.lexicon.schema record by reading the json file/file name that is passed into the action. Maybe we can tag PRs will NSIDs so the action knows which lexicons to create records for

[verdverm]

git diff, or the GHA field that scopes runs to changes based on file paths, would seem to be a better option than tagging or labelling PRs, imho

[ngerakines]

I think an early, and relatively inexpensive, solution would be to just evaluate all NSIDs from folder structures and create / update TXT records accordingly:

for each directory
    txt_record = ...
    continue if txt_record_exits(txt_record)
    create_txt_record(txt_record)

We can scale the process if and when we have enough lexicons or PR changes to warrant it.

[verdverm]

I was thinking more about actual publishing of the lexicon records themselves, when they get created or updated, to the PDS and repo.

signs in with an app key and creates a com.atproto.lexicon.schema record

what I understand @ebwinters to be asking about

How do we know what custom lexicon records need to be updated or published? (use diff instead of PR labels is what I am suggesting for this)

Shouldn't the DNS records remain stable, since they point to a DID? I could see your snippet being useful during first publish, but also seems like something that could be done by hand for a while with how infrequent it will be early on?

[snarfed]

also seems like something that could be done by hand for a while with how infrequent it will be early on?

Hell yes! These will be infrequent, so I'd be wary of automating too much, if at all. https://indieweb.org/manual_until_it_hurts

[ngerakines]

These changes have been applied with configuration and tooling published here: https://github.com/lexicon-community/infra

[verdverm]

The invalid h3 lexicon was published?

#40