GM ☕ Another day in the stream
It's not finished yet, but it is working. Thanks for the quick turn! What was it?
No joy. As before (this is a new screenshot), the fetching part works and downloads a database file, but broadcasting results in many errors with relays. I used this a day ago and it was fine.
I just close and reloaded my browser, kicked off a new deep sync, we'll see how it goes.
The fetching part works, it's the broadcasting that fails.
Any chance of getting some sort of additional info besides "Error" on failed relay contacts? I'm getting a bunch of them when trying to sync, though until today it's been working fine. See my last post for a screenshot.
Hmm, I use #nostrsync.live to sync between relays, and it usually works great, but this time it throws errors on most relays. Is this running locally in my browser, or on the nostrsync.live website?
self-dribbling basketballs
Same as it ever was.
"Now there's no more oak oppression
For they passed a noble law
And the trees are all kept equal
By hatchet, axe, and saw"
Oh wait, wrong thing 😆
I've only read Lopp's high-level overview but it does seem worth keeping track of progress.
GM ☕
It could be. I'm still learning the basics of #nostr communication protocol. I'm not sure how the clients select that--don't they just contact the relays listed in each followed accounts profile?
So far my #nostr experience is limited to #Coracle on PC and #Damus on an iPad. The Coracle UI is really nice, and I especially like the web-of-trust filtering capability.
However, in comparing my follow feed side by side between the two, there definitely seems to be some missing notes on the Coracle side that Damus is displaying. I can't make out a pattern yet but there are several that remain missing even after refreshing Coracle and even logging out/in to repopulate the local database. 🤔
GM ☕☕
Weww, 29 mile bike ride today through three trail systems in San Jose.
And after reading the series, watch the Tencent adaptation of the first book.
