Yeah, works great. Gonna try to self-host the websockets proxy.
t is for Tag
Yeah. For tor it works if you add armv7 in the filter release titles. Brave releases are a big mess, no luck trying to filter it out.
Search for Mutiny wallet, should narrow down a bit
Appreciate you developing it :) 🫂
You're missing the Polish Zloty (PLN) ;)
Yeah. I just like to live on the edge ;)
Nostr clients that mess with your relays list without asking for permission should be publicly shamed and then shoot in the face. £@&%%*!
Thanks for giving it a test. Will fix it tomorrow. How does feed scrolling responsiveness compares with Amethyst? ( which phone?)
If you check it when adding the app then yes...
This is how app stores should be, direct from the dev tits, no middle man.
One of the most incredible places to free fly, the Dolomites...
Now imagine how big a smile when something nice happens 🫂
Yeah!!!
Freedom from gravity ❤️
Yes. I now see old zaps receipts signed by my privKey on the list, but not on the SummaryBar/chart.
It's self-hosted nostdress, so I didn't think would be a problem. Are you aware of any other reason you shouldn't sign your own zap receipts??
Ok finally I found out what was wrong. I'm using nostdress connected to my LND node to generate the invoices and publish the zap receipts (9735). And I was using my own private key to sign the receipts. I didn't pay attention to nostdress config doc which said to not use your own. I quickly checked nip-57 and didn't see anywhere mention to not use your own privKey to sign the receipt. Since Amethyst's NotificationFeedFilter has a filter condition to exclude events which author is the loggedInUser it explains the behaviour I was getting. After changing to a new generated privKey to sign the receipts everythingd seems to be working. Do you know the reason it shouldn't use its own privKey to sign the receipt?