I've written an #emacs init file to provide a clean interface for writing (typora-like) nostr posts using github.com/mattn/algia.
Reading and Writing don't have to be the same. And I don't like the way clients usually solve the writing part. I think that by moving away from the network while writing, we might be able to better elaborate our thoughts.
Since this is text-only I'll answer this note with a fullscreen screenshot of this very note while it is being written. Splitting reading and writing experiences this way is way is possible because this is a protocol.
We might actually be winning.
marcos
npub182…87tnk
2024-06-24 11:24:56
Author Public Key
npub1828ey4s37t3dlwjmgsa05zafvdlsfsa3lu5vlk5cdx0a3zppv7nq987tnkPublished at
2024-06-24 11:24:56Event JSON
{
"id": "6c7a85a25483aac41fcff7bcc5a3b40d6eb905dd0450c0ae4a3c3f48b3d07f59",
"pubkey": "3a8f925611f2e2dfba5b443afa0ba9637f04c3b1ff28cfda98699fd8882167a6",
"created_at": 1719221096,
"kind": 1,
"tags": [
[
"t",
"emacs"
]
],
"content": "I've written an #emacs init file to provide a clean interface for writing (typora-like) nostr posts using github.com/mattn/algia.\n\nReading and Writing don't have to be the same. And I don't like the way clients usually solve the writing part. I think that by moving away from the network while writing, we might be able to better elaborate our thoughts.\n\nSince this is text-only I'll answer this note with a fullscreen screenshot of this very note while it is being written. Splitting reading and writing experiences this way is way is possible because this is a protocol.\n\nWe might actually be winning.",
"sig": "ccfc392edd59d4821b3b42413d30e8fe84b24a68e366e8d5e0c50872309bf48fc5a6f7134f94b6bba3d802cc0b1b4426170a4fb01179d7417dad3389755bafeb"
}