nostr:nprofile1qqs9val6td43edk4hmnct5yg4yzv6zqgy4ft7awl8eps9n4qzkja8cgpremhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet59uq3wamnwvaz7tmwdaehgu3wdah8xct5wvhx7un89uq36amnwvaz7tmwdaehgu3dwfjkccte9emkcann9eehqctrv5hsj3pt3x 

 Hungarian language makes an error :) but finally it’s working for me, thx!
 https://cdn.satellite.earth/8e5be4d6a8bdaebc41b6dd254be0bb9c1449581ddac0787ec74abcadee4b6e57.jpg 

 omg, will fix it. 

 When I want to log in. IOS 18.1 https://cdn.satellite.earth/1701c66ac5d606abc92e9f764fb862e3c17c5000f957ec3f768130743712fa3d.jpg 
 

 There is an issue with Hungarian language.

You need to change the default language first, or wait for the next update. 

 Yes, that works. Thx. 

 Nice. 

 I wish 0xChat would start respecting our relay configurations. If I go into 0xChat, it doesn't adhere to the outbox model, and just has a list of general relays, in addition to DM Inbox Relays. As soon as you accept the 0xChat relay config, your main relay config is totally trashed. If you go back into Amethyst, you'll see it has dumped all the general relays you setup in 0xChat into your public inbox and outbox relay categories. It means you have to fix all your relays in Amethyst everytime you use 0xChat. It's disrespectful.  

 @DagnyT DAFUQ your name show up for @Dan YALL CAN fix above or what 

 Sorry for the misunderstanding. Actually, the general relay list configuration in 0xChat is the public outbox/inbox module. In Amethyst and some other Nostr clients, general relays are placed in the kind3 event, which is likely a historical legacy issue rather than part of the standard NIP. 

 So you're saying the problem is with Amethyst?  

 It’s hard to say; it’s likely just a legacy issue. Before the outbox/inbox module NIP was introduced, most Nostr clients stored relay configs in kind3, but this isn’t the standard approach. 

 I see. If the only relays that are defined in 0xChat are public outbox/Inbox, and seperately DM Inbox, how are you pulling in notes from other users? In Amethyst, that function is served by the general relays, which 0xChat doesn't have.  

 Currently, it simply uses your outbox/inbox relays and the note’s hint relays. Later, it will use the contacts’ or follows’ outbox relays.  

 Given that people typically only have 2-3 relays set for their inbox and outbox, isn't that strategy a bit limiting in what content your feed is based on? On the other hand, general relays typically have 5+ defined, and many of them are the high-volume, wide reaching relays that deliver a ton of content. Maybe it would be a good idea to import users' general relays as a foundation for the feed? Just a thought. In any case, I appreciate you taking the time to talk to me about this.  

 Thanks for the suggestion; I really appreciate the thought you’ve put into this. 

In fact, the most suitable approach would be to use a user’s outbox relays rather than general relays to fetch their notes. Our current outbox model isn’t fully implemented yet, planning improvements in this in the near future. 

 I will change “general relay” to “outbox/inbox relay” to prevent any misunderstanding. 

 That would be helpful, although it doesn't solve the practical problem of 0xChat's relay config overwriting a user's established relay metadata. That's really the issue that needs to be resolved.  

 Hi, I have a problem with reedeming cashu tokens from chats. I think that was a problem with the mint being unresponsive, but the ux in 0xchat wasnt great. It started an "infinite loading" without telling me whats was wrong. Also, I wasnt able to copy the raw cashu token in my clipboard, so to verify what was the problem. 

 Thanks for your valuable feedback! I’ll work on improving this in future updates.

By the way, could you let me know which mint you’re using? I’d like to replicate the issue on my end. 

 I'm trying to update on nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgzqtdq0 and it gives me this error. Has the apk signer changed or something?

https://image.nostr.build/2f11f57256cd6649217539cbd83dc5f359b0a5bbb63554faf59c9be9afb9358d.jpg 

 Can you try using the GitHub link to see whether it works? 

https://github.com/0xchat-app/0xchat-app-main/releases/download/v1.4.0-release/v1.4.0-release.apk   

 The direct download from GitHub does work, it has updated with no issues. Thank you! 

 🙏🙏 

 Getting this when checking signatures:

❯ apksigner verify --print-certs Desktop/v1.4.0-release.apk
DOES NOT VERIFY
ERROR: Target SDK version 34 requires a minimum of signature scheme v2; the APK is not signed with this or a later signature scheme
WARNING: APK Signature Scheme v3 signer #1: Unknown additional attribute: ID 0x559f8b02
WARNING: SourceStamp: Unknown stamp attribute: ID 0xe43c5946 

 Try to upgrade your build tools version, we are using v4 signer. 

 Using build-tools 35.0.0, apksigner 0.9, when verifying your APK:

INFO: SourceStamp: No digests available in the source stamp for signature scheme: 31

Are you getting a different result? Which build tools version? 

 Using --verbose is now showing the certificate information.

However, it gives false for Verified using v4 scheme (it's true for v3.1 scheme) 

 Don't worry, your signatures are in the event you published. Need to fix something in the app and it will be okay 

 Nice, thank you 

 Hey, is anyone else having this issue on Android? For me the layout is inverted to RTL direction https://image.nostr.build/e4e622ebad5bb12e10c696a797608e23f14277431537c1d95e2ff8329b47225b.jpg 

 Any more infos? i can’t reproduce this issue on my end 🤔 

 Okay, I figured it out - after I added English to the system languages, it started displaying correctly. 

 Thank you for a great release!