yes as a workaround you can tap on the unread count at the top and choose Mark all as read
#Nostur update (TestFlight)
- Removed delay from marking notifications as read when opening tab
- When opening main notifications tab, automatically open one of the subtabs with unread
- Improved performance by not parsing duplicate events from relays
- Fixed loading of unread DMs at startup
TestFlight: https://nostur.com/testflight
Source code: https://nostur.com/source
This great, thank you! I was looking for something like this
Haven’t seen this yet, do you know if its a display issue or if it actually didn’t send? Maybe you could check from another app to see if it sent if it happens again
nostr:npub1n0sturny6w9zn2wwexju3m6asu7zh7jnv2jt2kx6tlmfhs7thq0qnflahe Great write-up on MISSION.md "We don’t need to store our data on random relays, and hope our contact list doesn’t get lost, or leak metadata to the public. We can store everything on our device". This is EXACTLY what I was thiking for my app. Have a small database like SQLite on the device and load that first. Them query relays for updates. Have a standard import/export format for Nostr that different clients can use. Have this format be an official NIP . This format could be as simple as a linear array of EVENTS in JSON format. This is what I use in my dev database, as you can see a "database" can be as simple as 100 lines of code, with functions to read(), save(), append() and request(), (from relays) nostr:npub1melv683fw6n2mvhl5h6dhqd8mqfv3wmxnz4qph83ua4dk4006ezsrt5c24 nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m https://github.com/pedro-vicente/nostr_client_relay/blob/main/src/database.cc
yep I’m using sqlite too now, through CoreData. Seems nostrdb will be great too when ready but for me the database is not the performance bottleneck right now
#Nostur updates (TestFlight)
- Added 'Share link' to post menu to share a nostr.com/
- Low battery mode improvements: Pauses animated GIFs, Imposter checking, and fetching post stats
- Added Rescan followers button to fix some notification issues
- Fixed blocking with reposts
- Fixed GIF searching not working with spaces
- Fixed compatibility with Intel Mac (macOS 13.0+)
TestFlight: https://nostur.com/testflight
Source code: https://nostur.com/source
It is a silent follow, you follow them but they don’t show up in your published following list
I had a bug in Nostur where it would lose track of who is already following you and then it appears someone is following you again when they update their contact list, or you open their follows tab.
Unfortunately the only way to fix it is to do a full rescan, which I will have a button for in the next release.
My iOS client is built with a C++ GUI library, but the result is not that good. So going iOS native. The only reason to use Swift is that I can use my C++ backend code and #nostr API . So using Swift just for the UI part https://github.com/pedro-vicente/nostr_client_relay
It’s easy to make nice UIs with SwiftUI but I found it difficult to get smooth scrolling performance, for that it’s probably better to use UIKit. I’m now using a mix of SwiftUI and UIKit but and I’m not really happy with it, maybe it will get better with iOS 17+
nostr:npub1n0sturny6w9zn2wwexju3m6asu7zh7jnv2jt2kx6tlmfhs7thq0qnflahe Nostur is a neat client on Mac desktop. I find it easier to find things like replies in threads, compared to nostr:npub1fjtdwclt9lspjy8huu3qklr7eklp5uq90u6yh8mec290pqxraccqlufnas where it’s confusing to do that (maybe just me ) . Did you use native Swift?. My holiday project is to learn swift New iOS interface (iPad) 🙃 
Yes native Swift, I was learning Swift/SwiftUI as well while building it, the source code is here: https://github.com/nostur-com/nostur-ios-public
There is now another tab on TestFlight for macOS, could you check if this one works on Intel?
I think when nsecBunker crashes and auto restarts I still can’t use it to sign events until after I login and unlock the key, is there any solution for this?
#drinkstr
I’ll check if I can release a new non app store version tonight. Does the newest one still give that Intel compatibility message?
That might be a different issue then, is that non-app store 1.4.0? It may have already been fixed in the TestFlight versions. I will release a new non app store version when 1.5.0 is ready. As a workaround you could run the TestFlight version, wait 1 minute and see if it doesn’t crash, this will load new things in the database, then close and start the non-app store version again.
There is an issue with the imposter checker, I will have an update soon, until then you can revert to build 147
nostr:note1khcfu6hsc5ma9j3wfd399hdz8f0m2u7f3s38tq5pkwznyhn42ynqx8aq0z
Nostur stores your follows on device so you can’t lose them. Mismatch of relays between clients can make it go out of sync but Nostur will offer to restore on startup
I’ve removed the last 2 builds from TestFlight because of some crashes related to the imposter checker, will have a fix out later
#[0]
cant use nostur, crashes right after opening the app nostr:npub1n0sturny6w9zn2wwexju3m6asu7zh7jnv2jt2kx6tlmfhs7thq0qnflahe
Probably related to the imposter checker, I will put an update out later
it adds the label if both the following is true:
- you are not following the contact
- it has a 80% similar name and profile picture as someone you already follow
#Nostur update (TestFlight)
Imposter check improvements:
- Show label on all feeds instead of only profile
- Also catches if name is 80% similar
- Cache the result of the imposter check
Fixed: Undo send missing on replies
Fixed: Duplicate follower notifications
