The zap button has moved to the profile sheet that opens when you tap on someone, it was a bit difficult to tap either zap or profile before. I’ll check what’s going on with the crashes 🤔
There was another thread about it:
nostr:note10gxkn9mfrp8jesaxy7zahyynaks3uvjwkmmyqw2stpqnh89qqzysea9pp8
I like “Your Network” for the normal user interface. WoT is more technical term to me from back when it was an alternative to Public Key Infrastructure (PKI) which you would also never put in a user interface
I dont want to give the replyguy any ideas but it can be alot cheaper faster and worse than that, whats happening now is nothing and probably just 1 dude with some spare time…
What non-standard tags is it sending?
Blossom I’m not sure yet, I checked it a while back but then I got confused and switched to working on other things
It’s probably mostly streaming or video that needs some work, right now Nostur starts prefetching videos in your feed even when you might not watch them, which is not optimal. Will be fixed eventually
It’s probably useful to mute/block non-spam by nip05.
But for spam or attacks its a losing game, attackers can change nip05 very fast, and when you receive a post you have to first get the kind-0 profile, then check the domain, those are “expensive” checks and with spam you want to do as little work as possible.
With WoT you can discard a post almost immediately without even checking the signature. Proof of Work on the pubkey is also a very fast check but this has other problems.
So far I have not found other solutions that don’t require the defender to do more work than the attacker but thats the type of solutions I prefer to implement.
only has to happen once and can be done in background or when phone is charging overnight, updating also. When posts come in you just check against a set, its instant.
But its different for a mobile client vs when you are managing a server, I can see that
This is a bit tricky because it requires a separate request for each follow, so its not a problem when opening a single profile, but for a whole list it will hammer the relays a bit much.
There are some ways around this but then it will be less accurate but maybe still good enough, I’ll check if its doable.
Hey I'll try using your profile for a while in read-only mode to see whats going on because there shouldn’t be that much difference between alts. Where are you noticing it most?
nostr is censorship resistant because:
1. the follow list is decentralized
2. there are multiple relays
Normal users can resist censorship by switching relays, or ultimately run their own relay and they cannot be censored on follow lists because each follower owns their own follow list, it doesn't even need to exist on a relay, can exists primarily on everyones own device while syncing to relays.
Relays stopping spam doesn't mean nostr can be censored, it just means whatever was stopped was something no ones care about enough to either be followed or hosted on a different relay.
I don't do any tracking and I try to keep as much as possible only on your device.
What is saved where:
On your device:
- your accounts
- your follow list / feeds
- your posts
- DMs
- your bookmarks
- your settings
Synced on iCloud (if enabled):
- your accounts
- your follow list / feeds
- your bookmarks
- some settings
On other servers or relays:
- Media / Profile / Banner uploads
- Nests recordings
- Your posts or other nostr content you publish
- DMs (encrypted)
The relays you connect to could potentially track your nostr searches or know when you use nostr.
I have access to app installations, sessions, crashes that is tracked by Apple (this for all App Store apps) without user details. If you use the TestFlight version some more info is tracked to help with debugging.
any NWC wallet should have a info event on a relay that describes what commands they support, like pay invoice or get balance. I added the “Try to use anyway” because some wallets didn’t have it but still worked
do you have low data mode enabled? (the turtle icon top right) only then it will open images in the browser, I will change this soon so it will just load in the app after tap.
Taking the blacklist approach against spam is not that interesting, users can't be bothered to keep updating mute/whatever list, so you just become like an anti-virus company sending out definition updates every month just to stop spam.
its not that I'm refusing it forever, I'm just still skeptical that it would work and think it could even do the opposite, showing more spam because spammers are the only ones able to provide the PoW.
so its just very low on the list things I let spammers waste my time with
you may find something in Settings -> Relay stats, if you tap on a relay it will show last errors.
or if you want to see more details you need to use Console on macOS, but the logs will probably be partially redacted unless you are in debug mode with Xcode
what are the Nosflare relays? maybe I can try and see
I havent noticed any issues with sending events yet, but I do get a lot of “["NOTICE","Error fetching events: Too many subrequests."]” from relay.nosflare.com
I think there may be an issue with missing EOSEs. Nostur sends a CLOSE after receiving EOSE but for some REQs (not all) on nosflare there is never an EOSE and its probably kept open and hitting the limit of 50, Nostur normally never has that much subscriptions open at the same time.
Example REQ that didn’t receive EOSE:
["REQ", "A4CB2EF4-5DB8-4D74-BF6B-9B860DA44777", {"ids": ["5119271f7af3847dd2c655f6a5cfb1448bb3a70edf52acec4f39844346917cca"], "limit": 500}]
from what I've been able to measure so far most data is still coming from images and video. I guess it may become a problem for very popular accounts but for those it also might not be that interesting anymore to know about new random followers, I will probably limit that to new followers that you already follow (following back)
from the spammers perspective I would just make the content length like a normal reply and the created time also random between 20-120 seconds, its just cat and mouse and the spammer can adjust faster
How Nostur handles relays and the outbox/gossip model/autopilot currently:
- When logging in for the first time, Nostur imports your existing relay configuration, or bootstraps with a preconfigured set if none can be found
- Content is fetched using that configuration, which you can then find in Settings -> "Configure your relays..."
- Content is fetched from relays with the "Receive from this relay" toggle enabled
- If a post can't be found, for example if you have a post which quotes another post, Nostur will try to find the post on relays with the "Use relay for looking up posts" toggle enabled. It will also try to find the post using relay hints if included in the post and "Follow relay hints" is enabled
- When posting, the relays with "Publish to this relay" are used to publish your content.
- If you are using multiple accounts you can exclude specific accounts from publishing to a specific relays for privacy or other reasons
When you enable Relay Autopilot the following is also done (in addition to the above):
- All the relays sets from people you follow are fetched in order to figure out where their posts can be found
- A list of relays that multiple accounts you follow have in common is calculated
- Any misconfigured relay set (there are many) is ignored by Relay Autopilot. For example if someone has configured that their posts can be found on nostr.mutinywallet.com which is a well known relay only meant for writing not reading from, their entire relay set is considered garbage and ignored.
- In the remaining list of relays, the top 3 are ignored to avoid centralization
- Content is then fetched from the remaining relays list
Any relays that return too many errors or timeouts will no longer be used by Relay Autopilot until the app is restarted.
https://media.utxo.nl/wp-content/uploads/nostr/0/7/0774d3472bca683188362ad8c25e619b0126f39e530337769b6ea05ca17df6e4.webp
Oddbean new post about login | logout
Notes by Fabian | export
I think there may be an issue with missing EOSEs. Nostur sends a CLOSE after receiving EOSE but for some REQs (not all) on nosflare there is never an EOSE and its probably kept open and hitting the limit of 50, Nostur normally never has that much subscriptions open at the same time. Example REQ that didn’t receive EOSE: ["REQ", "A4CB2EF4-5DB8-4D74-BF6B-9B860DA44777", {"ids": ["5119271f7af3847dd2c655f6a5cfb1448bb3a70edf52acec4f39844346917cca"], "limit": 500}]