Zap button for tweets in x.com

[saiy2k]

A chrome/firefox extension, that add the zap button for each tweet:

• The author of tweet should have x handle and npub connected and verified in https://nostr.directory/
• This needs to be resolved first: Issue: Zap fetch / count for a single URL #56

So, the extension can render the zap button for users who have their npub verified in nostr.directory.

Update 1:
Same can done in youtube and any other social media platforms

[ayushk687]

@saiy2k please assign this issue to me

[1amKhush]

@saiy2k Working on this. Will consult for any doubts or issues. Thanks!

[saiy2k]

Thanks for pitching in @ayushk687 and @1amKhush.
There is more to do this issue that described here. It's all in SoB proposal.

Let's discuss this in TG.

[krishvsoni]

Hey @saiy2k, I went through the SoB proposal and the codebase. The proposal lists 3 deliverables beyond orientation:

• PR 1: Nostr directory clone frontend (handle ↔ pubkey browsing/verification UI)
• PR 2: Nostr directory clone backend (Next.js + Firebase/Firestore, schema optimized for extension queries)
  Browser extension injecting Like/Zap buttons into x.com/YouTube

I see @ayushk687 and @1amKhush are working on the extension side.

The nostr directory clone (PR 1 + PR 2) has zero code in the repo no Firestore, no Next.js, no handle ↔ pubkey mapping logic.

I'd like to take that on:

• Frontend: UI to browse and verify X handle ↔ npub mappings
• Backend: Firestore schema designed so the extension can query directly without a separate API layer
• Pubkey crawling strategy: approach for discovering npubs from X bios, filtering Bitcoin/Nostr users
• This would unblock the extension work since it needs a data source for handle → npub lookups.

Can we have chat on this?

[1amKhush]

Hey @saiy2k, I went through the SoB proposal and the codebase. The proposal lists 3 deliverables beyond orientation:

• PR 1: Nostr directory clone frontend (handle ↔ pubkey browsing/verification UI)
• PR 2: Nostr directory clone backend (Next.js + Firebase/Firestore, schema optimized for extension queries)
  Browser extension injecting Like/Zap buttons into x.com/YouTube

I see @ayushk687 and @1amKhush are working on the extension side.

The nostr directory clone (PR 1 + PR 2) has zero code in the repo no Firestore, no Next.js, no handle ↔ pubkey mapping logic.

I'd like to take that on:

• Frontend: UI to browse and verify X handle ↔ npub mappings
• Backend: Firestore schema designed so the extension can query directly without a separate API layer
• Pubkey crawling strategy: approach for discovering npubs from X bios, filtering Bitcoin/Nostr users
• This would unblock the extension work since it needs a data source for handle → npub lookups.

Can we have chat on this?

@krishvsoni Actually i have already worked on the things you have mentioned. @saiy2k has mentioned he will start reviewing stuff 10 April onward so will be making the corresponding PR then (if possible i would like to avoid duplicate work, sorry for not informing earlier). Thanks!

[krishvsoni]

Thanks @1amKhush for the heads up! Good to know the directory clone is already in progress.

I also looked through the rest of the codebase and noticed a few open gaps. Would any of these be useful to pick up?

• Re-enabling nostr-comment, nostr-dm, nostr-live-chat disabled since v0.4.3 due to asset resolution issues in React apps. The code is all there, just needs the React compatibility fix.
  CHANGELOG.md line 90

• NIP-45 COUNT support both the like and zap specs flag the 1000-event cap as a limitation and hint at NIP-45 as the solution.
  src/nostr-like-button/spec/spec.md line 47-48
  src/nostr-zap-button/spec/spec.md line 47-48

• Zap receipt validation: currently commented out in utils.ts, zap counts on posts are hardcoded to 0.
  src/common/utils.ts lines 115-150

@saiy2k happy to take on any of these if they're useful. Or if there's something else from the SoB proposal that still needs hands, let me know.

[1amKhush]

@krishvsoni No worries! Btw even i am not too sure about the protocol for the SOB project PR's, why dont you join the telegram channel - all the dev related stuff is discussed there imo. Also as this particular issue seems a large one, do you mind collaborating in this one?

[krishvsoni]

@krishvsoni No worries! Btw even i am not too sure about the protocol for the SOB project PR's, why dont you join the telegram channel - all the dev related stuff is discussed there imo. Also as this particular issue seems a large one, do you mind collaborating in this one?

Sure @1amKhush , happy to collaborate also I haved joined the TG channel.