it's crazy how people can talk about Bitcoin all day.
i have held crypto on numerous occasions. but i always need the money for something else, so it doesn't stay crypto for long.
Nostr indexer seems to be running smoothly now https://void.cat/d/5gytpj7fXCfgYiPh4e3wxJ.webp
i was wondering why you'd bother with selling the bot access if it's good, but then again, if you do share access, this will give you more funds so you can amplify your bot's trades.
and you know you've got a working model when it handles any scenario you can throw at it. just gotta run lots of simulations.
of course they will. what you need to do is gather as many large datasets as you can and train your model on that.
only sheer laziness prevents me from developing a crypto trade bot based on machine learning. that, and a lack of actual funds to invest with it...
only a tiny fraction of the npubs i see in the relay pool on my indexer have any relay lists (kind 10002). plenty have the non-standard relay list that most clients stuff in the metadata (kind 0) though.
the program i wrote performs two duties right now. in addition to indexing, it's also broadcasting stuff from mostr.pub since it's hardly visible anywhere. but it has to be smart about it. mostr.pub will occasionally do a big dump of metadata and i can't send that directly to the relay pool because that triggers the rate limiters
too, just like with the queries, so what i do instead is i hold back events that i cache locally (which includes metadata) and when there is actual user activity, it includes my cached metadata with it. it generates much less traffic that way.
i think i finally figured out how to handle queries in my Nostr indexer. i run queries on the relay pool when i encounter new pubkeys, and i've been running them on individual pubkeys to get info about them, and it was triggering the rate limiters, so what i do instead is toss any key i come across in a set that i then query the pool for and empty in batches.
#[0] apparently, your new client uses event kind 6, which snort.social doesn't support, and the source for mostr.pub says it's deprecated
#[0] this bot thing keeps creating new users:
filter.nostr.wine: Connected
filter.nostr.wine: Inserted metadata for [6b83..6e96] cyber-cat-ad3cb1a53c802099ed96967b4997ae29 (npub1dwpn6wqmxh5atqk7ghxpt3430j80te53zn3mdcsw0uylru7td6tq406lpy@nost.vip)
findOnAll: Queried 0 results in 93 ms
nostr.milou.lol: Query timeout
puravida.nostr.land: Query timeout
filter.nostr.wine: Inserted metadata for [b666..bfbc] cyber-cat-bbe52cd60bce860ba91a456db55ad2 (npub1kendyc4g4yxfp0m90kvkwm0ekshsgj0n47f6cy7x0e4xtq2ah77qkmcsdz@nost.vip)
this would explain why Coracle always seems to destroy my relay list when i try to use it...
based on trying to capture NIP-65 in my Nostr indexer: there are clients that do it, but it's nowhere near as common as stuffing relay lists in the "content" field of a NIP-02 record
"shared" as in published, not "in common with you", i mean
i mean, i suppose it could. some clients let you view people's shared relays. snort.social lets you do it, for example
they *should* be using a NIP-65 relay list metadata event but since it has such a high number, i'm assuming it was introduced relatively late, so hardly anyone clients use it.
they stuff it as JSON in the "content" field of a NIP-02 contact list message, mostly
this place is so small but the spam bots are already here. my indexer sees them. there's one that creates a new account every few seconds. just filling up everyone's databases with junk.