jimbocoin 🃏 @jimbocoin - 21d
First problem hosting my own #strfry: VPS not powerful enough to compile it. 🤦♀️ Trying to compile from my laptop and then rsync the whole dir. 🤞
It should not be this hard. Strange that #strfry binaries aren’t already in a package manager. At least a PPA if not the big ones.
The thing I like about strfry is that it doesn’t require a database. Is haven easy to install?
I’ll give it a shot. I like that it has nginx and systemd instructions right in the README. Looks like it has more functionality than I need. Does it support NIP-13 PoW enforcement?
Oh, then maybe this isn’t what I need. I’m trying to run a special-purpose public relay.
mleku ✝Ⓐ☯︎ @mleku - 21d
i could add this feature to #realy very easily... i've not looked at doing such things because i simply think it's a silly thing, and my relay https://realy.lol has SIMD SHA256 hashing on it so it's pretty fast, i think it's under 500ns to hash a message, and the canonical message format derivation is also zero allocation
it's written in go, same as haven, and it's based off relayer instead of khatru, which i think does stupid things with the concurrency, way too much of it in eventstore libraries i completely rewrote the entire go-nostr library as well, everything is way faster, you can see here: https://github.com/mleku/nostrbench it's got the fastest JSON and binary encoder you can get... i have no idea what strfry's data encoding performance is like but i doubt it could be much faster than this
also, it already has a simple access control system based on the follow and mute lists of designated npubs, called "owners" all muted npubs their events can't be stored on the relay and only the follows of the owners are allowed to access and must use auth
