Avatar
Sascha-Oliver Prolić
3b8c97ae9286f01253c4f88d42d16e858c7c92513abf2f38251aff713514bce6
Christian, Working on futr nostr client, Junior Haskell developer for life

Apparently I'm the only one finding that funny. Or maybe it's just I have no followers on nostr.

Working on resolving some issue with relay connections, will be much more stable now. I'll submit commits tomorrow and then let's go NIP 17 ! #futr #nostr

Sure, but what do we gain for not reinventing the wheel? 🤣 Best quote from our guy

Replying to Avatar jimmysong

Sketch of a protocol I discussed with nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s for proving storage of a file.

before uploading, select 32 random bytes from the file, store their indices and the sha256 hash. do this 1000 more times (select 32 different random byes, calc sha256).

upload the file to the server. every day, ask for the hash of the 32 bytes at the indices stored from the server. if it matches transfer some sats. if not the server no longer has the file. you can check for 1000 days.

Who are these invalid people? 🤣

[WARN] "Could not decode server response: Error in $.tags[119]: Invalid PubKeyXO: a6f436a59fdb5e23c757b1e30478742996c54413df777843e0a731af56a96eea"

[WARN] "Could not decode server response: Error in $.tags[153]: Invalid PubKeyXO: 0ac62fe0c6b537b8e419793336e7ceeb21040bfdd7e0b8845d5272a2406fc236"

Replying to Avatar brugeman

Full dump of nostr events collected by nostr.band crawler for you to play with (550Gb): https://media.nostr.band/events.jsonl.gz

If you wanted to do research, data analytics, calculate stats, etc - that's your chance.

Contents:

- 550Gb of nostr events in jsonl format, gzipped

- no data about source relay

- some event kinds are absent (DMs, other encrypted stuff, ephemeral)

- some duplicates are possible

Will publish regular updates on this data set if someone makes anything useful out of it.

Thanks nostr:npub1mygerccwqpzyh9pvp6pv44rskv40zutkfs38t0hqhkvnwlhagp6s3psn5p for the push.

Nice, thanks. I'll run this through my event parser and see if it breaks somewhere. I already found that some people follow invalid pub keys.

Replying to Avatar Nostr-PHP

Just rolled out some small updates on https://nostr-php.dev/

- added a favicon

- added Matomo for analytics which can be viewed by anyone at https://matomo.sebastix.nl/

- added a new reference: Craft CMS Nostr Kit plugin made by nostr:npub102alxpn4xmrtwrau3tqevhjgth8xaweatsf94tpy30q0ayrvdqvq6xnsm5

Nice to see good old PHP serving #nostr now.

nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75sprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0y8qdrm why is your 8th follow broken? Event id 044612271036e504b6c81c5c39ae5a320978a89c3c6c65cae275e4fcbec2d83e. Follow has pub key a6f436a59fdb5e23c757b1e30478742996c54413df777843e0a731af56a96eea, but I cannot import this pub key, because it's invalid. Or maybe it's by design you mess up your follow list so other clients may break? 😂