# PLEASE STOP USING MARKDOWN
If you put stuff on the internet it is public now. If you say something it is public now too.
At least with signed messages they cannot misrepresent what you're saying -- with tags they can't even take those out of context.
I used to like the unseen notification count on Twitter. Now I got much more followers than what I was used too, such that they have become utterly and completely useless. There is always some notification, because Twitter thinks I want to be notified when someone liked a post that replies to some other post that replied to mine or something like that. And often there are so many notifications that they become "read" much before I can scroll through them all, so I kinda have to remember what was the last one I saw the last time I scrolled.
I wish my notifications were just text replies and mentions. I wanna read the replies, but I often miss many since everything is so garbled with nonsense "likes".
None.
# What about
* [markdown-esque](/) content like [](urls) or 
# ASK YOUR CLIENT TO REMOVE MARKDOWN SUPPORT
[please stop using markdown links, just paste the URL directly](/hello)
They should have chosen a single way, then.
One of the biggest problems of Markdown is that they have two ways of expressing italic and bold, and they both make no sense.
Why not a single _ for italic and a single * for bold?
But you can also serve clients locally from a browser extension!
You must sleep.
Use a custodial keypair (C) for each. If it happens that at any point they decide to create their standalone keypair (S) outside of TIDAL, you allow them to "adopt" the custodial key from the standalone key using NIP-26 delegation.
If someone is following C, their client that supports NIP-26 should be able to recognize that S->C, so they should automatically associate both and also follow S.
After some time, the user should be able to exit TIDAL completely and just use S (although TIDAL could also let them export C just in case).
I am not sure there aren't problems with this approach, but sounds like it could work.
What do you think of this? #[6]
I have built a web client with blogging https://flycat-web.vercel.app/ not sure if it is causing problem, it uses one replaceable event as a table for storing a list of articles, and one user might got multiple tables if he blogging more
I just tried to use it but didn't see any relay connections happening.
What is the practical difference for a relay between a client sending a query like ["REQ", "_", {"authors": ["dead", "beef"]}] or a query like ["REQ", "_", {"authors": ["dead"]}, {"authors": ["beef"]}]? #[1] #[0] #[2]
Where is the source code?
I was thinking of using something like kind 10 for the article "root", this would be basically empty, then multiple kinds like 30010 with the parameter thing with the actual text content, so the newest version of the content would always replace the previous.
My problem with it is how can someone refer to a specific version -- without requiring relays to store everything.
I think we might need some specialized relay to allow for pinning specific versions at user request (and perhaps payment). But this could come later.
And markdown for the text!
What do you think?
Welcome to email.