nostr:npub1dlfezkj445xzatnyu2up3t9m46wxk0vmtmjyuxd2qs8mp8cd8nws8mcdx0 how is it works nip-05 with GitHub pages?
auto-translate ruined the art

you can even sign your post, send it to Twitter, add sign and what, you will own your data with Twitter? I don't think so
relay does not exist to propagate copies.
Bitcoin node with p2p network does. and this is a strict rule to have copy of all transactions (which means all utxos, which means all bitcoins).
This allows me to transfer my coins. if there were no this rule - since nodes removed knowledge about my coins - I list them.
tbh, I don't think you own anything in Nostr except your npub.
I don't think your client stores all your notes. If no - all these things are stored by relays, do they own all this shit.
заходите, давайте обсуждать
Twitter’s ‘new’ Tweetdeck lives behind a verified paywall
https://www.theverge.com/2023/7/3/23783092/twitter-tweetdeck-new-preview-force-legacy-apis
The problem is that new tweetdeck have different functionality.
So you can't just build the same dashboard that you had in the old tweetdeck.
I have 2 more accounts for testing purposes
Amethyst 0.49.2: BugFixes
- Fixes emoji rendering on chat handles
- BugFix for incorrect caching of NIP95 images
- Adjustments to Markdown detection and rendering
- Avoids color-filtering the emoji
- Adds a brighter shade for Pins
Download:
- Play Edition with Push Notifications & Translations: https://github.com/vitorpamplona/amethyst/releases/download/v0.49.2/amethyst-googleplay-universal-v0.49.2.apk
- F-Droid Edition without Translations: https://github.com/vitorpamplona/amethyst/releases/download/v0.49.2/amethyst-fdroid-universal-v0.49.2.apk
thanks for quick fix!
tried to zap from my own node with Zeus wallet from the amethyst client and this is fucking amazing
not 1 tap, but I'm really surprised
hmm, maybe I created nip-94 by a mistake. one more try
["REQ","da07",{"kinds":[1,30023,7,6,1984,9735,9734,6969,9802,31337,33888],"#e":["854a1dcdbc9fc3c28f92fa09d257077c811533c653d7fd85619747c211e1cafe"],"since":1684234618},{"kinds":[1,30023,7,6,1984,9735,9734,6969,9802,31337,33888],"#e":["fb685de440ed96893f4979cd61a34f621edfb3c070b737a88a7d83047377ab71"],"since":1684234618},{"kinds":[1,30023,7,6,1984,9735,9734,6969,9802,31337,33888],"#e":["d25981a7dee3bb75f341fc7c4be29342e805b114fefb718838f54b87967e18a8"],"since":1684234618}]
this a request from your client when you are trying to open an event. why it's not asking for a 1064 and 1065 events?
IDK why, but amethyst correctly processing kind 1 and kind 1065 (even if you are not asking for it, idk why you are asking many different events - but not 1064 and 1065)
but 1064 it can't process
nostr:npub1xdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wscmntxy should your relay normally serve small nip-95 objects?
because I tried to debug what Amethyst is sending to the relay - and your relay responding with 1, 1064 and ,1065 kind correctly
