not sure what i did different, but over the last few days i have been condensing all my stuff relating to #nostr #relay #dev
https://realy.lol
just now took the code i had reworked to use my codecs and much of my protocol helpers and lo and behold, here's the fails in the M. Dilger (nprofile…4luh) relay test:
```
Supports EOSE: FAIL (Timed out without EOSE)
Keeps open incomplete subscriptions after EOSE: FAIL (Timed out without EOSE)
Keeps open incomplete subscriptions after EOSE: FAIL (Timed out without EOSE)
```
i will fix these errors shortly, they are probably very simple, it should be sending eose after it finds everything but probably it's because i made the filter API synchronous per websocket instead of the way fiatjaf did it, with a messy concurrent channel API
this is working with fiatjaf's new `relayer`, as it is from the base it uses almost exclusively my own original codec for everything, and including the filter matching functions, which i debugged with the help of Mikes testing tool previously, currently except for the nip-11 relay information document
i'm calling it `realy` because i keep on making that typo from the word relay, and i think it's kinda funny, probably many won't even get it... and just to point out that `strfry` means a C function that makes a random anagram out of a string (string fry)
it also has some other tools, a vanity npub miner and a reverse proxy tool but tbh i'm not sure if they are working as it is right now, but they are useful and related tools to the main relay and the library
i will be further polishing this up but it can be used as is
the main planned improvements are related to configuration of the database, and after that, a CLI interface that works over DM that enables potentially paying for relay subscriptions, and managing adding and removing access for npubs, removing them, probably adding advanced filtering controls for access so that paid users can have all of their chats and discussions posted to the relay without any additional configuration while preventing spammy replies from getting on the relay
#thoon
mleku / mleku™️
npub1fj…mleku
2024-09-16 20:51:06
Author Public Key
npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmlekuPublished at
2024-09-16 20:51:06Event JSON
{
"id": "fc0e0fe5ea766b427f31740f9efc44e0d68118eebb4f9703e3f050adb7dc4305",
"pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"created_at": 1726512666,
"kind": 1,
"tags": [
[
"t",
"nostr"
],
[
"t",
"relay"
],
[
"t",
"dev"
],
[
"p",
"ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49",
"wss://nos.lol/",
"M. Dilger"
],
[
"t",
"thoon"
]
],
"content": "not sure what i did different, but over the last few days i have been condensing all my stuff relating to #nostr #relay #dev \n\nhttps://realy.lol\n\njust now took the code i had reworked to use my codecs and much of my protocol helpers and lo and behold, here's the fails in the nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3xamnwvaz7tm0venxx6rpd9hzuur4vghszgrhwden5te0dehhxarj9ejkjmn4dej85ampdeaxjeewwdcxzcm99uq3yamnwvaz7tmwdaehgun4v5hxxmmd9uqzpms35h0lgrqe542lg8ly9dy0qrnp3jgjy43z4cmmds4mv7mkcnjf8w4luh relay test:\n\n```\nSupports EOSE: FAIL (Timed out without EOSE)\nKeeps open incomplete subscriptions after EOSE: FAIL (Timed out without EOSE)\nKeeps open incomplete subscriptions after EOSE: FAIL (Timed out without EOSE)\n```\n\ni will fix these errors shortly, they are probably very simple, it should be sending eose after it finds everything but probably it's because i made the filter API synchronous per websocket instead of the way fiatjaf did it, with a messy concurrent channel API\n\nthis is working with fiatjaf's new `relayer`, as it is from the base it uses almost exclusively my own original codec for everything, and including the filter matching functions, which i debugged with the help of Mikes testing tool previously, currently except for the nip-11 relay information document\n\ni'm calling it `realy` because i keep on making that typo from the word relay, and i think it's kinda funny, probably many won't even get it... and just to point out that `strfry` means a C function that makes a random anagram out of a string (string fry)\n\nit also has some other tools, a vanity npub miner and a reverse proxy tool but tbh i'm not sure if they are working as it is right now, but they are useful and related tools to the main relay and the library\n\ni will be further polishing this up but it can be used as is\n\nthe main planned improvements are related to configuration of the database, and after that, a CLI interface that works over DM that enables potentially paying for relay subscriptions, and managing adding and removing access for npubs, removing them, probably adding advanced filtering controls for access so that paid users can have all of their chats and discussions posted to the relay without any additional configuration while preventing spammy replies from getting on the relay\n\n#thoon",
"sig": "8eb6c87e669fab78925fa18532d62e562339e81b4075033b584c93b96dd1d12e52b7f1a2b115443d06b6ffbcdd65cccc53090702ce9ba157aecb9935992a829e"
}