Now in #amethyst .. again testing international hashtags. Please ignore.
#ಕನ್ನಡ is in Kannada
#தமிழ் is in Tamil
#сообщество is in Russian
#漫画 is in Japanese
#समाज is in Hindi
My dinner today 🤩

Unfortunately i have no setup for iOS dev. Can anyone who has the setup take it?
Thanks for trying #zappedit
Your feedback makes me happy as a dev of this client ☺️
RTL languages is a new area for me. Let me do some research and get back to you :)
Hey nostr:npub1yaul8k059377u9lsu67de7y637w4jtgeuwcmh5n7788l6xnlnrgs3tvjmf
The following solution may possibly work. I am not an expert in iOS app development (in fact never done it). So, please take what I say with a pinch of salt :D
The call flow in damus goes like this from my preliminary analysis of the code on Github 👇
```
damus.c :: parse_hashtags ==>
cursor.h :: consume_until_boundary ==>
cursor.h :: is_boundary
```
I believe the fix is to change how the `is_boundary` function is implemented in damus.
When we look at the implementation of hashtags from the other clients, the regular expression based matching does not have any check for alphanumerics, but instead just a set of 'prohibited characters' (a black list)
Amethyst regex is this:
```java
"#([^\\s!@#\$%^&*()=+./,\\[{\\]};:'\"?><]+)(.*)"
```
Snort regex is this:
```js
/(#[^\s!@#$%^&*()=+.\/,\[{\]};:'"?><]+)/
```
Both of these regexes try to just write a blacklist of chars that can't be there in a hashtag, instead of whitelisting alphanumerics.
If, in c code, we can come up with a function that will check for blacklisted characters and return a boolean, we could use this to implement international hashtags in damus too.
Not sure if my theory is correct.
Retesting international hashtags in snort. Please ignore.
#ಕನ್ನಡ is in Kannada
#தமிழ் is in Tamil
#сообщество is in Russian
#漫画 is in Japanese
#समाज is in Hindi
Now in #amethyst .. Retesting international hashtags. Please ignore.
#ಕನ್ನಡ is in Kannada
#தமிழ் is in Tamil
#сообщество is in Russian
#漫画 is in Japanese
#समाज is in Hindi
📢 New Updates in #ZappedIt - Your reddit-style client for #nostr (https://zappedit.com)
1. Mobile users without NIP-07 extension can now use ZappedIt. Private key based sign-in has been enabled. However, NIP-07 extension login is the recommended and secure way to use ZappedIt.
https://void.cat/d/WsZMWPRVvHnsvsydsP9qCk.webp
2. Thanks to the pull request by nostr:npub1cz2ve34nk0ukn0ph4yq2qx3ud8rfy5e0ak4epx42dn8gha0sdgpsgra9kv we now have a list of followed people on #zappedit.
This is the first step to implement NSFW protection by loading pictures only from those you follow. (This is not yet implemented)
3. Visual overhauls (Bolder header, alignment fixes)
https://void.cat/d/RwYbp8d6mF1egp48sHdesj.webp
4. This is a funny one 😁 You can now 'Logout' from zappedit. We have been running without a 'Logout' system till now. So, if you are using shared computers or multiple accounts, this will help you.
5. A partial fix has been done to recognize and highlight international hashtags like #தமிழ். Previously these were not recognized correctly.
That's all for now!
Again a big thanks to my friend nostr:npub1cz2ve34nk0ukn0ph4yq2qx3ud8rfy5e0ak4epx42dn8gha0sdgpsgra9kv for his help in developling #zappedit
Thanks to the authors of #ndk again. nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft
Implementing login using private key was a breeze.
Thanks to nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 too whose work heavily inspired this. (I even copied some of his util method implementations)
Here we go 😊

However there may be some difficulties in searching for notes with international hashtags. This is because not all the clients set the 't' tag in their #nostr events using non-english hashtags.
I and nostr:npub1cz2ve34nk0ukn0ph4yq2qx3ud8rfy5e0ak4epx42dn8gha0sdgpsgra9kv will do some PRs to major clients to fix this gap.
📢 New Updates in #ZappedIt - Your reddit-style client for #nostr (https://zappedit.com)
1. Mobile users without NIP-07 extension can now use ZappedIt. Private key based sign-in has been enabled. However, NIP-07 extension login is the recommended and secure way to use ZappedIt.
https://void.cat/d/WsZMWPRVvHnsvsydsP9qCk.webp
2. Thanks to the pull request by nostr:npub1cz2ve34nk0ukn0ph4yq2qx3ud8rfy5e0ak4epx42dn8gha0sdgpsgra9kv we now have a list of followed people on #zappedit.
This is the first step to implement NSFW protection by loading pictures only from those you follow. (This is not yet implemented)
3. Visual overhauls (Bolder header, alignment fixes)
https://void.cat/d/RwYbp8d6mF1egp48sHdesj.webp
4. This is a funny one 😁 You can now 'Logout' from zappedit. We have been running without a 'Logout' system till now. So, if you are using shared computers or multiple accounts, this will help you.
5. A partial fix has been done to recognize and highlight international hashtags like #தமிழ். Previously these were not recognized correctly.
That's all for now!
Again a big thanks to my friend nostr:npub1cz2ve34nk0ukn0ph4yq2qx3ud8rfy5e0ak4epx42dn8gha0sdgpsgra9kv for his help in developling #zappedit
Now in #amethyst .. Testing international hashtags. Please ignore.
#ಕನ್ನಡ is in Kannada
#தமிழ் is in Tamil
#сообщество is in Russian
#漫画 is in Japanese
#समाज is in Hindi
Testing international hashtags. Please ignore.
#ಕನ್ನಡ is in Kannada
#தமிழ் is in Tamil
#сообщество is in Russian
#漫画 is in Japanese
#समाज is in Hindi
Hi... can you please give me some example international hashtags? i can use them to test if I have implemented this correctly.
I am aware of this bug. I need sometime to see what's causing this as I am using an open-source lib to detect hashtags.
I understand the goodness that comes with multi-lingual hashtags and am very much interested in fixing this. In fact I did a very similar fix to #amethyst recently to enable non-english hashtags.
The #zappedit project is just out of the "weekend POC" phase and getting adopters. I hope to fix the hashtags in a week or two max and give you a shoutout once I fix it?
PRs are welcome too. The source code is at https://GitHub.com/vivganes/zappedit