nostr.build URLs with # are breaking Yana it seems.
Discussion
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z why are you adding it to the URL? πΆπΎπ«‘
I think they break Amethyst too.
Amethyst is breaking itself it seems πΆπΎπ€·ββοΈ
It's a Christmas miracle.
Nostr.bulid is quite spotty lately. Maybe something to do with the new NIP-96 interface.
I am just questioning whenever i could disable NIP-96.
NIP-96 is the new API for generic image/media servers. We shouldn't go back to hardcoding several different API just because of hiccups here and there.
Nostr.build doesnβt add # to the URL for sure πΆπΎπ«‘
Of course not. But that isn't the problem. The problem is that the server is replying with 403 here and there. I still don't know why. It feels quite random. Most images work fine.
Do you have specific URL that returns this so I can check πΆπΎπ«‘
It usually doesn't repeat. The app calls it, gets a 403 and if it calls again the image comes. I am not really sure why. But since the hash is also frequently not matching, it could be something on your caching system.
You mean calling image url or api? πΆπΎπ«‘
This is easy to see in gossip logs when image loading is turned on. Many 403s, but when you open the url manually it's fine. I think it might be some kind of rate limiting where clients are trying to simultaneously do a lot of calls and something in the stack is deciding that's too many..
Do you mean calling the image URL? I need more info to be able to look into it πΆπΎπ«‘
Yeah the image url
I haven't had any problems in amethyst though since I actually upgraded, so, apologies for any mis-filed bugs on that one haha. Google broke side loading and I was on an old version.. π
I just checked all the rules and the only thing that is blocked on the image serving end, is favicon for different devices. If that is what you see for favicon under that domain, that is expected πΆπΎπ«‘
Fix already in master. Will release soon.
using primal, yeah
Primal android seems also to not handle it.
any other clients for a meantime?
What do you miss in Yana?
Just tested logged as you and it seems to work.
Can you confirm after restart app? Maybe websockets entered strange state....
Still happening, it kept happening every time I saw these notifications today.
Other things I want to see in Yana:
- not include myself when calculating inbox relays when replying to a thread that includes me
- don't mention myself in my own notes
- nostr.wine-compatible translations service integration
- do you mean don't broadcast to your write relays? Or just don't show them on the popup for choosing which relays to broadcast your replies, and assume it will always broadcast to your write relays?
- fix in master
- added to roadmap
I mean when I am replying to a thread that includes myself my own read relays are used, but I think only read relays of others should.
Don't always broadcast to my write relays, no! I like to have all the things there sometimes.
Give it a spin https://github.com/frnandu/yana/releases/tag/v0.14.0
