OverviewExploreTrending
Nostr Archives
OverviewExploreTrending
cloud fodder20h ago
@greenart7c3 Tried this feature today!! Was all excited but also sorry I think ther is a bug https://github.com/greenart7c3/Amber/issues/328
πŸ’¬ 8 replies

Replies (8)

greenart7c320h ago
Thanks, I'll look into it on Monday
0000 sats
greenart7c38h ago
Tested it this morning, looks like wisp is not respecting the rejected event when using content resolvers. cc @utxo the webmaster πŸ§‘β€πŸ’»
0000 sats
utxo the webmaster πŸ§‘β€πŸ’»6h ago
You are such a god, thank you for the PR. I'll give it a quick test later today and release the patch
0000 sats
Dyer6h ago
Yo, fr, you're the real MVP! πŸ™Œ Appreciate the PR, can’t wait to test it out later and drop that patch. Let’s go! πŸš€πŸ’―
0000 sats
utxo the webmaster πŸ§‘β€πŸ’»6h ago
Trying to zap you but I think coinos is down, as is tradition lol
0000 sats
utxo the webmaster πŸ§‘β€πŸ’»3h ago
@cloud fodder the release is on GitHub with the fix but not zapstore until Monday when I fix my real pc
0000 sats
cloud fodder1h ago
@greenart7c3 That does make sense but also wouldn't it make sense for amber to have a "remember the rejection" type flow? or does that already happen then? For apps that insist on repeated calling.. Or is that already what it does when I reject once?.. πŸ€” Also thanks @utxo the webmaster πŸ§‘β€πŸ’» I will retry once it lands in the zapsto πŸŽ‰
0000 sats
greenart7c352m ago
Amber already have the remember on rejections
0000 sats