Avatar
Bitcoin For The Hood
6331f1d4b7665a8f452fd5a265c9c1a9c72e7afc0c21df4f0a6601be10d74f6e
Bringing Bitcoin To A Hood Near You 🇺🇸 #Bitcoin #Nostr Merch 🧢👕 Oakland ca. Podcast https://anchor.fm/kevin-lane9 https://anchor.fm/kevin-lane9 https://youtube.com/@BitcoinForTheHood #ReparationsOverEveryThing

🤷🏽‍♂️🤷🏽‍♂️🤷🏽‍♂️🤷🏽‍♂️🤷🏽‍♂️🤷🏽‍♂️

Do you accept #Bitcoin

Work must build upon a free open source software (FOSS) project based on JAM Systems as a fork or contribution to this repository: https://github.com/diamsa/jam

Depends on: [Nostr Live Audio Spaces: Nostr Notifications](https://nostrbounties.com/b/naddr1qq9rzdesxqen2d35xsmqygppksv3qtdgls96jpyy4mynf064k74u7a0wmvu3yn5dwhjfraq6tcpsgqqqw4rsnp5fp2)

Precursor: When a room is created, the server signing key should publish the Live Activity (kind 30311) per [NIP-53](https://github.com/nostr-protocol/nips/blob/master/53.md) per the dependency. The identifier should be saved in the room metadata.

Users should be presented with an option to view/close the room chat

Chat messages should be created using kind 1311 per [NIP-53](https://github.com/nostr-protocol/nips/blob/master/53.md) as live chat for the live activity. Use the NIP section here for the event to be published per chat message

https://github.com/nostr-protocol/nips/blob/master/53.md#live-chat-message

Chat messages should be created and signed by participants and their keys.

A tag "role" can be added to indicate if the user is a "moderator", "speaker", or "audience" at the time of the chat message for context.

When the message is displayed to the users, render the user's name, role, time, and the message.

Further bounties will be established in the future for extending chat (for replies, reactions, translations, export, publish transript)

When 🤷🏽‍♂️