Hopefully not.
I don't know. I was just doing it for debugging. As a normal user I would just not care and wait until it fixed itself.
I think the medium.com replacement is the best strategy moving forward. Preferably keep the two ecosystems slightly separate, with separate clients, unless a client deliberately wants to support both.
I am (kinda) working on something like that, #[3] is too, but we must come up with a nice standard.
One this this "long-form" standard should have is the ability to edit the content.
If someone starts posting bloated URLs I will unfollow and mute.
You may have the beginnings of a good idea there, but I personally would be opposed to it too.
It looks like Markdown was added to Damus just so links could be made clickable (the same reason I've stupidly added a Markdown parser to branle an year ago and it bubbled up to Astral), and someone there is working on removing it: https://github.com/damus-io/damus/pull/301
#[2] has also said he is going to remove Markdown support from Astral.
Nice one.
I am using a client that doesn't render images inline and like to see the URLs I'm clicking.
Yes. I've suggested that too in the past. Someone should do it.
It is very hard to comment about what John Carvalho says, because I can't ever understand what is his core point.
Overall I think the Slashtags idea of WOT is interesting, but you don't need a fully peer-to-peer thing for it, and I think fully peer-to-peer things will work at scale, plus they're too complex. Their stuff would work better on top of Nostr.
What clients implement Markdown? We should ask them to remove Markdown support. Or just leave the bold/italic stuff in place and remove the weird stuff like []() and ## === ![]()
Like this: https://github.com/styppo/hamstr/pull/12
So you're going to request them to _not_ implement Markdown now? :)
Yes, on https://stacker.news or https://lnmarkets.com.
That only work when there is a central place with a central codebase. Nostr is too open for that to work.
At least while Nostr is still in this phase, if any client gets sufficiently big they can start bloating the protocol by doing these kinds of moves and there is nothing any benevolent dictator can do about it, so we should all be mindful.
This is relevant to the Markdown case: #[1]
I am pretty sure it was this. Have you ever seen a social network be successful with Markdown?
Because tons of people come to us asking "why Nostr uses this weird thing and not ed25519?"
It was a joke, sorry.
Because we're on team secp256k1/bip340.