Profile: 22e2e20f...
Blindly believing tools can fix humanity as a sort of magic wand is childish.
Back to your dream I can remember you nobody prevents to donate with cash to the most trusted person in need you know nearby. Direct transaction, immediate possibility to assess results.
The more layers the more opaque and ultimately uncontrollable the process. Helping becomes just another way to tap and forget.
Something curious happening. Message A posted from device D1 was not visible from D1 itself. “Looking up for message” message. Message B posted from device D2 was visible from D1. Then reloaded web page. Now message A is visible from D1 again. And message B was not visible from D1 at first. And then there it is again.
Search with Id on the second device returns "looking up message" and never appears. It does on the device I originally posted from. Strange thing my previous answer to you is visible from the second device. It appears messages are picked up sometimes.
For DM another strange thing: on the second device I can see my DMs but not the answer to them!
Using iris web on both sides.
#[5] Id of missing note. And pict of it below. I am logged in with private key on both devices and connected.
#[0] why what I am posting from one device is not always visible from others? As example my recent answer to https://iris.to/post/note1l9945vz40sw4atkz8d4m2r3kjcw06rt3e76rjv6ed9y73c0p9kksy3wsd0
#[2] if you still see the above iris web has a problem with deleted messages. Reloaded page multiple times.
In a hub and spoke arrangement nostr is designed as an airport. But if makes sense for airlines to share runways and for passengers to pool together departure location, I don’t see the same benefits here.
Operating on your own messages requires the same amount of connections if relays are reserved or not. Looking up on followed’s is not instead because reserved relays introduce a latency shared don’t expose. Latency made visible in the “looking up message” boxes that litter the federated feed channel on iris web. But with parallel connections (and http3) this delay should not escalate much. Also promote reserved relays progressive scaling. Relays pooling would also restrict lookups mostly to LANs. I envision automatic orchestration already.
Where’s the bottleneck nostr is trying to manage here? Someone modeled extreme cases already I am sure.
#[0] why is nostr doc stating p2p does not work? Maybe a silly question. I see only upsides: with your own relay and optional replicas you never have to worry about losing access to your own messages. Plus you don' have to ingest followers messages. Plus you can start nano and push your relay(s) on increasingly capable servers. What I am missing? Scalability?
I saved pub key as username on iCloud Keychain. Auto-fill expects a second field to appear for password. Why is even possible to "log-in" with just the pub key? Another issue now I can see my private messages but not the answer to them.