Add Abbot to Public Channel

[aidadiaz9]

Due date = 10/20/23

Add Abbot to your nostr public chat channel.

[bnonni]

The NIP-28 spec doesn't mention "adding" someone to a chat. I think a user must opt into a public chat channel by simply creating a note of 42 - channel message and broadcasting it. Browsing and joining public chat channels or adding someone to a public chat channel would be something a client would implement (i.e. a frontend to show users the list of chats, buttons for joining or adding someone and leaving). Looking at nostrchat.io, you can see when you click the + sign next to Channels, it shows "create" and "join" but no "add."

I created an ATL BitLab public chat channel to see if the chat channel interface has an "add" button, but it doesn't .

Solution

• Add nostr buttons to atlbitlab.com/abbot
• DM button will open nostrchat.io/dm/
• Channel Add button shows an input box and ask them to input the channel id (e.g. 3cc312d9cd7e45bbd254dd541caf7bb24b45becd6b22435ef616ea3047ffbe2a)
  • on submit, we make a request to the telegram API (see #3) and put a command in the text (e.g. /nchannel 3cc312d9cd7e45bbd254dd541caf7bb24b45becd6b22435ef616ea3047ffbe2a)
  • on the backend, code logic to handle this command and parse the channel id arg
  • construct a note kind 40 or 42 (need to figure this out), sign with Abbot seckey and send to Relay-Abbot (see #3) to broadcast to relays
• Example of buttons

The nostr code for this issue will be complete in #6 This issue should handle the frontend changes and the requests

[bnonni]

@w3irdrobot your pieces

Frontend Nostr

• Input box on click Nostr Channel
• Define and add note kind (channel invite)
• Construct event with new note Kind and broadcast including tags with Abbot pubkey
• Sign and send event with ATL BitLab pub/sec keys

Backend (AbbotNostr)

• Be able to store note with new kind (deps on DB)
• Add filter to relay manager by new kind and filter by ATL BitLab pub key to make sure Abbot listens for authorized notes to join channels
• Construct response event kind 42 including tags for channel id (parse chan id from incoming note w/ new kind)
• Insert hard coded response from Abbot into event kind 42 (intro text)

  
      "Hey! The name's Abbot but you can think of me as your go-to guide for all things Bitcoin. 
       "AKA the virtual Bitcoin whisperer. 😉\n\n"
      "Here's the lowdown on how to get my attention: \n\n"
      "1. Slap an @ before your message in the group chat - I'll come running to answer. \n"
      "2. Feel more comfortable replying directly to my messages? Go ahead! I'm all ears.. err.. code. \n"
      "3. Fancy a one-on-one chat? Slide into my DMs. \n\n"
      "Now, enough with the rules! Let's dive into the world of Bitcoin together! \n\n"
      "Ready. Set. Stack Sats! 🚀"

[w3irdrobot]

i'm gonna go with a custom kind of 21021 for abbot to be looking for invites to a channel. this is what is called an "ephemeral event", defined by nip01. essentially relays don't have to store it. so they pass it on to anyone listening for them at the time but anyone that shows up after will not get it.

i can understand the reason for using a replaceable event in the range of 10000 <= n < 20000 as well.

thoughts on using 21021?

[w3irdrobot]

the expected message will have an empty content, a kind of 21021, and a tag e set to the id of the channel to join.

[w3irdrobot]

also, using a similar method as dms do, let's put a p tag in there to reference abbot's pubkey

[saucy-tech]

opened a pr in the dev website repo. added buttons for nostr dm and nostr channel with styling. added form with validation for channel id

[w3irdrobot]

@bnonni i don't think i have access to this frontend site at all

[bnonni]

Yeah, no one does because its our atlbitlab.com website and it isn't public. I'm working on a solution to make it so

1. the front end code can live in this repo
2. @saucy-tech can get hacktoberfest credit for his code

[bnonni]

Due date = 10/20/23

Add Abbot to your nostr public chat channel.

Due date:

• 10/26/23 or 10/27/23 (ideal)
• 10/28/23 (latest)

[saucy-tech]

On Saturday I can work on adding the Telegram front end UI to follow the nostr flow (Telegram DM and Telegram Channel buttons).

[bnonni]

Sounds great! Thanks!