> no utter dread > no engagement farming > no manipulation > no advertisement tactics THIS IS HOW IT WAS SUPPOSED TO BE nostr:nevent1qqszlckyd5cr5f5l43tekwets6dgh2dzlyaednlw8sxd24yca6j8scqpzpmhxue69uhkummnw3ezuamfdejsygxy8wa43chxhsheg4t4sftldwjn9yg8h48gyaqx3s5nd35anxqt05psgqqqqqqsdd6c9s
@Vitor Pamplona I'm sure you're aware, but the markdown parsing of kind 1 notes messes up all kinds of things. The quoted note above is not embedded, and gifs also render weird once the markdown parser kicks in. > like this Adding "plz fix" because one day I'll go over these notes and create issues and PRs and by "I" I mean someone else 😂 https://media.tenor.com/uj4Cnt7RVE0AAAAM/fatdog-dog.gif
> like this https://media.tenor.com/_4xCiEhhoZsAAAAM/dog-smile.gif
Yep, the main problem is that to "fix" it, we need to break compliance with real markdown... If the follow it to the letter, it is supposed to break. 🤔
1. In a world where the data producers and consumers are different software, the consumer will end up handling all sorts of formats because they different producers will just do their own special thing. 2. We should just use a non-replaceable version of 30023 for markdowns and merge it with kind-1 feeds.