stereosteve / is on Nostr

"b8fc6829c79e75719ca08852b47116ffc4d60ae35a5db20c63a133977c5e1988d326f490f90d724fba14c0a73a8e79e775df621ee57650522a7472b420ba6d7d"

Last Notes

2023-04-01 00:32:45

- reply

Honestly they might not want to be seen holding and getting rich on a pile of drug money they stole even if it could go up.

2023-04-01 00:32:45

- reply

Honestly they might not want to be seen holding and getting rich on a pile of drug money they stole even if it could go up.

2023-02-14 01:53:48

- reply

I've been working on adding an ElasticSearch storage backend to the basic relayer.
ATM the indexing is very basic and it just sorts by most recent first.
But my plan is to add some better indexing for different Kinds and add some additional ranking signals. See note here:
https://github.com/stereosteve/relayer/blob/elasticsearch/storage/elasticsearch/elasticsearch.go#L140-L150
My initial use case is for a private or hobby style relay... less worried about the "aggregate all of nostr"... nostr.band is doing a pretty good job with that.
But I also think ElasticSearch is a good backend for the read heavy workload of most relays what with the roaring bitset and document compression and all that. It'd be nice if all relays had decent search and we didn't have to punt to closed source things.

2023-02-14 01:53:48

- reply

2023-02-13 16:27:56

- reply

Do you use strfry for this with the custom merkle tree database thing? Or is this a separate component. I’m intrigued by strfry and wonder if you are using it to sync with any other nodes?

2023-02-13 16:27:56

- reply

Do you use strfry for this with the custom merkle tree database thing? Or is this a separate component. I’m intrigued by strfry and wonder if you are using it to sync with any other nodes?

2023-02-02 00:11:29

- reply

Hey isaac

2023-02-02 00:11:29

- reply

Hey isaac