Replying to Avatar DanConwayDev

This happened because it was trying to send the event to the old set of relays (the pubkey) plus some fallback relays that are no longer active. I have made a 2 changes to address this:

1) It backs up the new event first (with the relays you want to restore) and send updates these relays instead of the ones you wanted to replace

2) I have replaced the fallback relays with relay.nostr.band, nos.lol and relay.damus.io which I think are accepting events from any pubkeys. events also get sent to blaster.mutinywallet.com as they are profile related.
Avatar
DanConwayDev 1y ago

nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 I'm not convinced the changes on the master branch are being deployed to metadata.nostr.com. In your capacity of CEO of nostr can you check please?

Reply to this note

Please Login to reply.

Discussion

Avatar
fiatjaf 1y ago

Of course not, it's a manual process.

Also I've forked your repo because you never gave me write access to yours, so there are a bunch of changes there now: https://github.com/fiatjaf/nostr-profile-manager

How can we merge both?

Avatar
DanConwayDev 1y ago

You had access but branch protection was on, forcing everything to go through a PR. I turned that off now. There seems to be a few linting issues and test failures on your master branch.

We should probably start from your tip, as that's whats in production.

Avatar
Laeserin 1y ago

Just the tip. Promise.

Avatar
Laeserin 1y ago

Sorry. 😂

Avatar
fiatjaf 1y ago

Oh, so I could have merged my own PRs? I didn't realize that. I remember you saying "branch protection" and assumed it was bureaucracy. Sorry.

Avatar
DanConwayDev 1y ago

Yes. I guess it still is the bad sort of bureaucracy as every change doesn't need to be peer reviewed in this sort of project.