no, I just didn't update the header, but it's on 0.0.9
markdown renders well in the asciidoc renderer, so it's backwards compatible
Discussion
Do we have test pages for both?
Actually, Markdown pages don't render correctly, I need to convert them. I just looked at my own wiki pages.
Can you give me an example?
Here's another example, the first one of my articles I've checked
I wonder how many of my 273+ entries would actually show up correctly
Oh yes, that looks totally broken.
Please don't convert. Others should instead join me in ignoring this bullshit and waiting for clients to get good at displaying articles
We need much more NIP-54 wiki clients all abiding to *one* standard.
What I also have recommended on Github, keeping event kind 30818 Markdown and creating a new event kind for Asciidoc. But... well, we see the result now.
This is perfect. There could be another event kind for wikitext too if nobody gets around to finding another conversion method first. Everyone would be happy. nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 please consider
Also, NIP-54 isn't even changed yet. Why do we even have NIPs if people are doing what they want anyway?
Merging PRs into the NIPs requires implementations.
There’s a PR with the switch that’s been waiting for two months for implementations to be able to merge
The NIPs repo is DESCRIPTIVE.
I thought the point of the post you're replying to was that if the first devs on the standard just do whatever they want instead of adhering to the standard then that's not good for decentralization which requires growth with more devs being able to join in freely