Hey man! I really like the idea ð
I think the best approach would be to make my Roadstr compatible with yours compact, while keeping the existing reporting system intact. That way, reports could travel both through regular relays and over meshcore, opening the door to proper interoperability the two projects without either of us having to redesign everything..
meshcore is definitely interesting and i like the idea of not being dependent by my isp to communicate with other people, but i'd want to make sure the same reports can still be published and received through standard relays. it's a nostr app after all. ideally, both would just be different ways of transporting the same signed events.
I'll look into adding support for your format on my side, keeping it optional and compatible with the existing architecture. this should also make it easier for other projects to integrate in the future..
And about the name I know yours came first, I actually came up with it when I read about the new kind 1315-1316 (maybe from Gigi, utxo or Derek, can't remember who) that I came up with it ð but honestly, combining "road" with the "-str" suffix while also getting something that sounds like roadster, is such a natural combination that we simply arrived at it independently, just at different times. Thanks for being so openly nice about it :) anyway, I'd much rather focus on making the two projects interoperable than worrying about the naming coincidence. I think that would be a win for everyone! â¡
LWB
npub1vjâŠ9hh7v
2026-10-11 17:42:11 UTC
in reply to nevent1qâŠ27ax
Author Public Key
npub1vjxq75czca0nswp2f5kgtfyzhynuccdjs29q098rd3kv09k7s6nq39hh7vSeen on
wss://nostr.momPublished at
2026-10-11 17:42:11 UTCEvent JSON
{
"id": "f0b7a75622734a28577803fbf73370b2dc95ddabb1ece4f578e2be0bc1f22225",
"pubkey": "648c0f5302c75f38382a4d2c85a482b927cc61b2828a0794e36c6cc796de86a6",
"created_at": 1791740531,
"kind": 1,
"tags": [
[
"e",
"7b37f599dafda58358e2463f460d14336fcec62c3fb51b5e93184f015ea722ff",
"",
"root"
],
[
"e",
"08c8cf6f489067ff850f045904eb5500c1fd76914e92ba9c2404f79f2393f520",
"",
"reply",
"dab6c6065c439b9bafb0b0f1ff5a0c68273bce5c1959a4158ad6a70851f507b6"
],
[
"p",
"dab6c6065c439b9bafb0b0f1ff5a0c68273bce5c1959a4158ad6a70851f507b6"
],
[
"p",
"c392b7b76b7510b75f7ca0d493a64173ff44bdfaca2074efeb6e232198d80e74"
],
[
"client",
"Nostrich"
]
],
"content": "Hey man! I really like the idea ð\n\nI think the best approach would be to make my Roadstr compatible with yours compact, while keeping the existing reporting system intact. That way, reports could travel both through regular relays and over meshcore, opening the door to proper interoperability the two projects without either of us having to redesign everything..\nmeshcore is definitely interesting and i like the idea of not being dependent by my isp to communicate with other people, but i'd want to make sure the same reports can still be published and received through standard relays. it's a nostr app after all. ideally, both would just be different ways of transporting the same signed events.\n\nI'll look into adding support for your format on my side, keeping it optional and compatible with the existing architecture. this should also make it easier for other projects to integrate in the future..\n\nAnd about the name I know yours came first, I actually came up with it when I read about the new kind 1315-1316 (maybe from Gigi, utxo or Derek, can't remember who) that I came up with it ð but honestly, combining \"road\" with the \"-str\" suffix while also getting something that sounds like roadster, is such a natural combination that we simply arrived at it independently, just at different times. Thanks for being so openly nice about it :) anyway, I'd much rather focus on making the two projects interoperable than worrying about the naming coincidence. I think that would be a win for everyone! â¡",
"sig": "59e1b2c2ec819932dad2df63f7cfe2bbb1ef630acb7e08e0d5ff56d5e472420f86701da6288f0dbe54d23f7f43cfcf87ec287827d0e9cbd7953e4568671665cc"
}