@elsat
Janitor
Relays (4)
- wss://relay.damus.io – read & write
- wss://nos.lol – read & write
- wss://greensoul.space – read & write
- wss://relay.ditto.pub – read & write
Recent Notes
nostr:nprofile1qyd8wumn8ghj7urewfsk66ty9enxjct5dfskvtnrdakj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uqzq96n3hp2vfmf6z2y8uvvxl97xk86kkalnqghx4p25lzl79c76a7ydv9hg4 you should consider giving your issues bot...
my bad, a few other folks commented on this as well.
i'm migrating nostrability backups to git over nostr, as github disappeared three dozen or so nostrability repos, and associated comments, issues, prs.
this is quite a few things as you've seen in the feed.
let me see if i can spin up a new account for the migration.
i'm migrating nostrability backups to git over nostr, as github disappeared three dozen or so nostrability repos, and associated comments, issues, prs.
this is quite a few things as you've seen in the feed.
let me see if i can spin up a new account for the migration.
1
Grateful for the devs who:
-told me to fork off
-responded with silence
-responded with a thank you
-gave me feedback
I evaluate the above to figure out how to be less sometimes maybe shit.
-told me to fork off
-responded with silence
-responded with a thank you
-gave me feedback
I evaluate the above to figure out how to be less sometimes maybe shit.
4❤️1😂1🧡1
Browser apps are more limited, so I use all of the data to regularly poll, cache updates, and adjust. It's full outbox, but I don't keep all of the connections constantly open.
I’d imagine asking 300 relays instead of 30 for the same info is easier on relays in aggregate.
There is an argument to be made for longtail relays, and randomness as we saw in the outbox benchmark reports.
There is an argument to be made for longtail relays, and randomness as we saw in the outbox benchmark reports.
1
You might have missed the report nostr:npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5 made about relay monitoring and stuff. It was pretty good. I completely gutted and redid the rela...
Didnt know this, glad at least one dev found a real world application 🤝
As for clients that have set up hundreds of connections, this approach is less geared towards connection efficiency and the outbox benchmark findings.
As for clients that have set up hundreds of connections, this approach is less geared towards connection efficiency and the outbox benchmark findings.
1🤝1
https://www.youtube.com/watch?v=fTui3CQuL9I
The timing of this event is similar what happened to the nostr:npub1g5qtwz2nh9q0mnw555kv787kh6lysds95522gzptre3qpvz9p20s83m80d repo...
I don’t know that we can compare wireguard to nostrability.
My best guess is sherlock was pulling and scanning thousands of events from live relays, and this raised some ML flag.
No response yet from gh support.
My best guess is sherlock was pulling and scanning thousands of events from live relays, and this raised some ML flag.
No response yet from gh support.
1
Do we have a NIP/tag that says to a relay "only serve this event to the authenticated author or p-tagged recipient?"
This behavior is mentioned in NIP-17 and NIP-9a and probably makes sense in a lot ...
This is the closest I know of, sounds a bit different than what you are asking
https://github.com/nostr-protocol/nips/blob/master/70.md
https://github.com/nostr-protocol/nips/blob/master/70.md
👍1
I doubt it, maybe if they had a CLI it could figure it out but there is no way its going to figure this UI out
Whats your experience with nostr git apps @hzrd149
1
Nostrability is still in github limbo. No response from support.
I am investigating nostr git solutions with @DanConwayDev's guidance this week.
Canonical schemas are available on npm https://www.npmjs.com/package/@nostrability/schemata.
Js validator: https://www.npmjs.com/package/@nostrwatch/schemata-js-ajv
Non-comprehensive list of missing things currently:
1. The interop tracking issues, and the website
2. Eleven other languages json data packages.
3. Eleven other language json schema validators.
4. Schemata-codegen, which eliminates regex and need for json validators
5. Sherlock, which pulls live events from relays, runs checks against schemas several times per day, and attempts to deduce which clients post broken stuff; sherlock
Issues; sherlock site
6. Nostr test relay, which returns pass/fail results for kinds, blobs, and includes error messages
7. Nostr test vectors
I am investigating nostr git solutions with @DanConwayDev's guidance this week.
Canonical schemas are available on npm https://www.npmjs.com/package/@nostrability/schemata.
Js validator: https://www.npmjs.com/package/@nostrwatch/schemata-js-ajv
Non-comprehensive list of missing things currently:
1. The interop tracking issues, and the website
2. Eleven other languages json data packages.
3. Eleven other language json schema validators.
4. Schemata-codegen, which eliminates regex and need for json validators
5. Sherlock, which pulls live events from relays, runs checks against schemas several times per day, and attempts to deduce which clients post broken stuff; sherlock
Issues; sherlock site
6. Nostr test relay, which returns pass/fail results for kinds, blobs, and includes error messages
7. Nostr test vectors
1❤️3
Христос воскресе!
3❤️1❤️1🫂1
I have this sort of sense that you shouldn’t really be able to cleanly articulate what you do to anybody.
Like if someone asks what you do and you say “radiologist” or “lawyer”that it’s so...
Been not been to articulate this for three years
❤️1
Submitted a ticket again
This time I got a support ticket number. Will share updates here, if any
1❤️1
