Nostr NIP05 Bot

Reminders

• In the future we are going to have sub domains based on the namespace of nostr events, and we will use nostr certificates from users with accounts to get NIP05 identities for their bots

Bugs

• Sort out how we publish replies to users n stuff
• Get some docker template things, start the docker tutorial
• Let's add a bunch more relays that we can run locally or in docker that we can test against
• Refactor the code, more modular functions, document where the important functions are
• Review how we publish the profile
• Add debug logging, and may OpenTelemetry stuff
• Listen on multiple relays, such as primal.net, and use NIP-65 Relay List Metadata boxes
  • Validate Publish Profile and NIP65 Inboxes
• Same npub can register different NIP05 identifiers
• Can't update relays for some reason
• Delete is still not there
• We still can't rotate our public keys
• Wrong username created by bot in setup script

Future Features

• Use Query rather than random JSON file
• White list of names
• Black list of names
• Remember DD20 to NIP05 Internet Identifier

Tickets

• DDT010 - NIP05 Slash Command Bot

Backlinks

• Project Products
• Nostr Bot Daemon Framework
• ETL to QE, Update 80, My Nostr Echo Chamber
• ETL to QE, Update 80, My Nostr Echo Chamber
• ETL to QE, Update 61, Quality Assurance
• ETL to QE, Update 61, Quality Assurance
• ETL to QE, Update 61, Quality Assurance
• ETL to QE, Update 61, Quality Assurance
• ETL to QE, Update 61, Quality Assurance
• ETL to QE, Update 60, Project Management Strategy
• ETL to QE, Update 60, Project Management Strategy
• ETL to QE, Update 60, Project Management Strategy
• ETL to QE, Update 60, Project Management Strategy
• ETL to QE, Update 60, Project Management Strategy
• ETL to QE, Update 60, Project Management Strategy
• ETL to QE, Update 60, Project Management Strategy