chris on Nostr: relays should implement some sort of algorithm chosen by the relay runner rather than ...
relays should implement some sort of algorithm chosen by the relay runner rather than just spewing the most recent events or making the client come up with some sort of hacky global/main filter.
It would be cool to see different feeds from the perspective of a programmer, designer, baker, gardener etc… rather than some algo that has overfit what it thinks i want to see.
Once you get stuck with a bad algo on twitter/x for example you’re kinda stuck with it and you have to artificially interact with posts that are similar to the kind of content you want to see again even tho you’re not necessarily interested in that post.
Published at
2025-03-26 03:51:22Event JSON
{
"id": "69536726aea45cb6d5a2359c3b59df3776b771e20fcb6030136a6dd3c7192995",
"pubkey": "220522c2c32b3bf29006b275e224b285d64bb19f79bda906991bcb3861e18cb4",
"created_at": 1742961082,
"kind": 1,
"tags": [],
"content": "relays should implement some sort of algorithm chosen by the relay runner rather than just spewing the most recent events or making the client come up with some sort of hacky global/main filter.\n\nIt would be cool to see different feeds from the perspective of a programmer, designer, baker, gardener etc… rather than some algo that has overfit what it thinks i want to see.\n\nOnce you get stuck with a bad algo on twitter/x for example you’re kinda stuck with it and you have to artificially interact with posts that are similar to the kind of content you want to see again even tho you’re not necessarily interested in that post.",
"sig": "d4f3b7a69efd192f8222e9ab5a6e70682564bd0ba48d6c9d637790c0368bfc2b48a393064f5d45720cbd0d4374f455e4d2309e7fbe390a26339419bbe587b7a4"
}
