Probably. Someone should PR NIP-11, would propagate changes faster than a note
for all you vibers out there I'm putting together context files you can easily attach to any llm and they should give you the magic ability to one-shot a working nostr app
https://github.com/nostr-net/llms/
I've tested the python version on chatgpt and claude and it worked beautifully.
obviously next step is to create mcp agents from this.
#vibecoding
nostr:nprofile1qqsypwwgtll74lqu4huvxzjwtjyxvrlkujt35rw8y026ke6ttesmg5gpzemhxue69uhkummnw3ex2mrfw3jhxtn0wfnj7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7wzpxlr
Every single web client will have these errors from time to time (if not always), unless they route every connection through a proxy.
These terms are acceptable.
Opened a PR for an alternative AxeOS OC interface with named presets. https://github.com/bitaxeorg/ESP-Miner/pull/840#issue-2990399888
There's a 99% chance those relay stats are very inaccurate.
What do you mean by "relay overlap" ?
And to be clear, they are complimentary and so is relevant. Just wanted to clarify the functionality.
They are conceptually much different π
Both useful on different ways. Randomness is great in fuzz testing and finding edge cases that are difficult to find without randomness, the auditor I wrote is better for unit testing known vectors to validate expected behaviors.
The tests I have aren't random because then its difficult to meaningfully communicate the outcome. Instead it each NIP had a test suite, and then each test in the suite attempts to obtain samples from relays and then uses the uses those samples to construct filters than satisfy the respective test.
Yeah my resolver is also struggling with it https://npub1nadarndr8f0fra505suk85xhvgksqer2vnuqsjkvt2tfm7d0wakqhwlpf5.nsite.cloud
Will have to take a look during the weekend βοΈ
What is the challenge resolvers face when attempting to resolve the most recent hash?
I used coracle I think.
Yes, completely rewritten from scratch. There's a link to the original in the GUI.
Cool Kid Citadel Chronicles
The state is constantly changing, to publish events NIP-66 style would be burdensome in its own way. When I considered publishing events for a similar purpose, I backtracked and landed at a DVM as well.
Also, I think this is using the legacy API, and since I cannot find a git, I cannot patch it, and thus, it will soon die.
No, and I don't plan on adding it.
Happens
My mind immediately went to using timers to hotfix race condtions. I should probably go outside.
One step at a time...
Recommend to use relay.nostr.watch or relaypag.es instead or in addition to
hotfix will be deployed in roughly ~10 minutes. It's possible the error caused you to have breaking state. lmk if the error persists.
Despite not being particularly invested in US politics, other than taxation and foreign policy, I will say this is the most entertaining show I've ever witnessed. Nothing short of hilarious with a perceptible dose of catharsis.