Event JSON
{
"id": "39800232f46a7a83509bc8c24931d9cc78455ba4a17756210f5126c3431a682d",
"pubkey": "098bfa86b83e88e6164c52db13acbf1091d82db85989a1ba98dbcc296ea01c29",
"created_at": 1712660369,
"kind": 1,
"tags": [
[
"e",
"119789564fc9507e630e770ad831322c8d7856037bcb30c9b4f7b4578ed50aae",
"",
"mention"
],
[
"p",
"70122128273bdc07af9be7725fa5c4bc0fc146866bec38d44360dc4bc6cc18b9",
"",
"mention"
],
[
"q",
"119789564fc9507e630e770ad831322c8d7856037bcb30c9b4f7b4578ed50aae"
],
[
"t",
"markdown"
],
[
"t",
"pkm"
],
[
"t",
"vimwiki"
],
[
"t",
"obsidian"
],
[
"t",
"logseq"
]
],
"content": "Best idea I've heard in a long time. I can hardly think about an argument against having a default #markdown note type for Nostr. That'd single handedly put an end to the incosistent rendering issues across clients to begin with!\n\nBut why stop there? Just think how easy it'd be to implement closer integrations with #markdown based #pkm [^1] systems like #vimwiki #obsidian #logseq etc.\n\nnostr:nevent1qqspr9uf2e8uj5r7vv88wzkcxyezertc2cphhjesex600dzh3m2s4tspr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgs8qy3p9qnnhhq847d7wujl5hztcr7pg6rxhmpc63pkphztcmxp3wgrqsqqqqqppd9dj3\n\n[^1]: Personal Knowledge Management",
"sig": "40cf2cdc70cc3a1179f2caa8101c6dba873754bfed561fb224905ebbd7109d58cf5ca1d058ff17bc36a0f0b4f8590f7dd2dbf898189d37d7226bd73a5bfabfa6"
}