I posted something. Then I noticed that it was formatted wrong! I went back to fix it in edit mode. It seemed fine in edit mode. I saved it again. It was still wrong.
The thing that was wrong: In source / edit, my sentences are separated with the charcters "period space space". This is a typing standard that improves legibility, which is extra important in effortposts. However, in the displayed mode, one of every double space had been eaten! Every post, every comment, mangled! Sentences are separated with "period space" instead of "period space space" and the text is slightly less legible for it. I noticed it for questionmark space space and exclamationmark space space as well. There's some secret life form eating spaces.
Testing behavior: Period Space: Sentence 1. Sentence 2.
Period Space Space: Sentence 1. Sentence 2.
Period Space Space Space: Sentence 1. Sentence 2.
Yep, saw it in preview, all the spaces are getting eaten. This is a crime against good style. I won't go so far as to say this is a hate crime against anyone who struggles with reading and visual processing... yet. But the site is editing my comment in order to enforce an objectively worse typographical standard (period singlespace). Literally 
. 
on Communist Bear Site they automatically censor out your punctuation marks in order to make your writing conform to a worse standard, calling double spaces a bourgeois decadent waste of space.
Please help
(Also, should this go in /c/technology or in /c/hexbear? It's about both)
(Should I be submitting this as a bug report on github instead?)
at the risk of enabling you there is probably a somewhat reasonable way to set up a macro to automatically do the forced whitespace character when you double on the spacebar.
I might try to set one up. For now I'm manually adding
when I want it because I think if I want to be extra like and write in a way that annoys others, I should have to put in some effort to do so. What is victory without struggle? What is performance art without effort?I'm trying to figure out ways to do it on the client side so I can just read it my way, but it's proving harder than I expected to get something running that is thorough, covers all edge cases, and isn't abysmally slow :(