I have been banned from submitting issues at the Steemit Condenser Github Repo. So here is my report:
First I will republish in full the report here:
Bug in condenser markdown renderer with pull-left class divs
To fix the problem, it is necessary to put two break tags and a linebreak, see here without, and with the linebreaks.
It probably won't affect many people, but in addition to this, to account for anyone who has used this workaround in their code, it would make sense to collapse both markdown linebreaks/paragraph endings and these tags, so they don't thten create a secondary problem.
Also, I just now noticed the Steem editor looks a lot like the one used to create issues. Its upload function is better, however, in that it places a textual placeholder where you drop the image. Perhaps merge the fork for this?
Exhibit A shows my composition with the preview including my screenshots, Exhibit B shows what happens when I try to submit an issue. The interface does not make this explicit, but this means that I have been prohibited from submitting issues, because I am a nuisance, in their opinion.
Exhibit A
Exhibit B
So I figure, this is a perfect way to provoke, pester, and make a lot of fuss, by calmly, and clearly showing that their opinions on my bug reports are clearly not the same as what others will think, and I would even be able to show the issue and the conversation I had with at WITNESS who seems to have wormed his way into the development team's list of acceptable contributors, even spokespersons, responding to issues as though it is in his authority to close and reject without other Steemit employees vetting it.
My previous article about alcohol detox and the role of sugar in the lethal symptoms of Delerium Tremens I have extensively had to apply the very fixes in my code that I describe in the bug. I am a skilled HTML markup coder, from a very long way back, in fact I first started working with hypertext on the amiga with the early pre-HTML system called 'AmigaGuide', which was designed for making help documents.
Note to Steemit, Inc.:
You are hereby on notice to justify your actions to the community, and I will continue to investigate, analyse, and publish every issue that I find as I more deeply engage with your shitty, poorly written software, until you fix the problems, clear out the rot in your organisation, and fulfill your duty of care as guardians of the platform the community depends upon.
This is just the beginning.
Imagine if someone as clever as Dan Larimer were instead very good at psychological analysis, military theory, document layout and design, as well as being talented in systems architecture, and moderately skilled at crafting high quality algorithms and protocols, was out for your blood. Would you be so complacent then?
certainly not the only bug in that editor...
I was aware of the pull left / pull right div bug, and was using that same workaround of adding linebreaks to my code to work around it. Its a minor bug, but should be fixed. :)
The proper solution would be to devise a custom markup element, such as for example: `|> pull right content |> and <| pull left content <| and the collapsing of sequential line breaks is already present in the markdown parser, it need only add the <br /> token.
Needing to use the html entity < to cause < - it seems to me there should be an escape character in the language same as is used in regex and commandline parsers. Nobody uses backslashes for anything, except Micro$oft, and if you use it as escape, just \\ and note, I had to type 3 backslashes to get 1, so there is already a tokenising identifier for that.
If the quality of code in
steemd's username sanitiser is any indication, the whole parser is gonna be a study in overly complex, insanely kludgy code, that resembles how I would have written it when I was 9 years old on my TRS-80 CoCo in MS Basic.