Could just be a reposter, this is why we need to start using `i` tags from nostr:nprofile1qqs99d9qw67th0wr5xh05de4s9k0wjvnkxudkgptq8yg83vtulad30gpz4mhxue69uhks6tnwshxummnw3ezumrpdejqzxrhwden5te0wfjkccte9ehx7umhdpjhyefwvdhk6qgdwaehxw309ahx7uewd3hkcd5u7te 's NIP (forget the number of the NIP 😅)
NIP-01
shoutout hypertuna 😂
they're useful .... until you do something you're not supposed to.
Would be a new NIP, completely different t criteria and ttest vector. Could reference NIP-66 though.
nostr:nprofile1qqswwud0pvzu362lehm0av6sq4zd97cue5uy0z8f7jgtk0hz368dvmcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxmhwden5te0wa5x2ct59e5xzurs096xzan9wfhzucm09uqsuamnwvaz7tmwdaejumr0dshsdms043 nostr.watch wen blossom server discovery? 🫡
Someone else can do it, I'll aggregate it 😂
And yes, many problems with NIP-11s, it's one of many reasons why I wrote @nostrwatch/schemata; not on npm yet, need to fix NPM publishing in my CI.
I used my personal relay, many relays ignore empty filters.
Submitted PR.
here is the code:
https://github.com/dezh-tech/mangostr/pull/12/files
in src/lib/components/latestnotes.svelte im trying to fetch some events. im not sure if this is the correct/recomeneded way. but it doesn't work...
Forget to commit that component?
Yes. Let me know if you have any questions.
BTW the link to the banner broke on jellyfish, it was the only relay that I could test banners against 😂
oh, nice. can we implement nip-66 monitors as a part of our nostr server stack at nostr:nprofile1qqst4k7a55r4w2ee0pfqfr48fuh08tvjkx4vqlpafcw7c96w3nwfv2spz4mhxue69uhk5etvd3ukv6tndqhxcctwvshst6rvu4?
are they working like that?
> our server stack contains any daemon or server side code used in nostr.
Yeah, its totally possible. I've refrained from doing it myself because I like the separation of concerns.
...my agents are separate processes and they publish to relays.
(testing a wiki implementation)
You can aggregate NIP-66 events from relaypag.es and relay.nostr.watch instead.
like this post if you like tacos.