Sometimes I fear that nostr is going to suffer death by a thousand cuts, self imposed, due to ...
- inconsistent data in relays
- improper handling of replaceable events
- ridiculously long lived caching that ignores replaceable events
- inefficient bandwidth utilization
- rush to partial implementations
We can fix this. But to do so requires staying focused on projects and features, vs abandoning them when they get 20-30% of the way there.
If someone could work on the following projects I'd appreciate it: Flockstr, NJump, Coracle.
#dev
Vic
npub1yx…p7kza
2024-03-13 21:37:05
Author Public Key
npub1yx6pjypd4r7qh2gysjhvjd9l2km6hnm4amdnjyjw3467fy05rf0qfp7kzaPublished at
2024-03-13 21:37:05Event JSON
{
"id": "5c28ad0455b263d3473ab8a18c42e8eb33e5721ec8b53ff7daba5407f8cb3778",
"pubkey": "21b419102da8fc0ba90484aec934bf55b7abcf75eedb39124e8d75e491f41a5e",
"created_at": 1710365825,
"kind": 1,
"tags": [
[
"t",
"dev"
]
],
"content": "Sometimes I fear that nostr is going to suffer death by a thousand cuts, self imposed, due to ...\n\n- inconsistent data in relays\n- improper handling of replaceable events\n- ridiculously long lived caching that ignores replaceable events\n- inefficient bandwidth utilization\n- rush to partial implementations\n\nWe can fix this. But to do so requires staying focused on projects and features, vs abandoning them when they get 20-30% of the way there. \n\nIf someone could work on the following projects I'd appreciate it: Flockstr, NJump, Coracle.\n\n#dev",
"sig": "1bcbf28ee0465e6ec18f4ca651c714a7ad927944c288517a228ef4e33c729f6d0ad9b5cf9c2d27ad826d93e4f516b7d541387c04547750f580210325b559b529"
}