I’m Ruby。 I’m roughly 20 apples tall
ルビーです。背がりんごを20つぐらいです。

I drew my profile pic and banner. The gameplay in the banner is from dragon quest 1 for game boy that I recorded myself.


staff
@staff

a day early! or just on time? depends on if you view Wednesday or Thursday as the true patch notes day. (unless you’re an oldhead, in which case we’re a day late (ed. note: patch notes used to be on tuesday))

we’re still working on asks and the public API but we’re dropping patch notes early/late/on time today because we wanted to provide a very clear cutoff time for one change today which fixes some unintuitive behavior in markdown: single line breaks are now preserved! here’s some details on what that means.

previously, if you wanted a post to have line breaks matching what you’d see on most other platforms, you’d need to do some arcane bullshit. options included:

  • adding two spaces to the end of a line (impossible on mobile since that gets collapsed into a period)
  • adding an html line break (<br />, impossible in comments since those don’t take html)
  • adding a backslash escape to an end of a line (like this\). this is Secret Behavior that we’re pretty sure colin and jae are the only people who use. markdown is fun like that

these all obviously suck if you aren’t familiar with markdown (and also suck if you are) so now you can add a line break and it’ll Just Work.

since this change could change the rendering of old posts if we applied it site-wide, we’re bringing in a NEW AGE OF POSTING. these changes will only take effect on posts and comments made after 3pm EDT / noon PDT / @833 today (May 10, 2023).

if you want to keep using the arcane bullshit listed above, you can! they will still work as expected! this change just adds a new way of doing line breaks.

that’s all for this week! thanks, as always, for using cohost!


You must log in to comment.

in reply to @staff's post:

a day early! or just on time? depends on if you view Wednesday or Thursday as the true patch notes day. (unless you’re an oldhead, in which case we’re a day late (ed. note: patch notes used to be on tuesday))

someone should graph the precession of patch notes day over time to watch the drift.

oops

EDIT: so doing some investigation, this is complicated to trigger and has an easy workaround. not sure exactly what causes the specific behavior (i mean i can see the AST but don't know how it gets there).

this will include a <br/> in the final output:

<em>here's a test post
hey what's up</em>

this won't:

<em>
here's a test post
hey what's up
</em>

this also won't:

<em>
here's a test post hey what's up
</em>

so workarounds are either:

  • include your opening tag on a separate line
  • don't include random line breaks in the middle of your text

yeah my thought here is that this improves the experience for Most People. anyone writing html was already operating in Extended Mode and any idiosyncrasies there are just gonna happen. this is part of why we introduced a new age

this is Secret Behavior that we’re pretty sure colin and jae are the only people who use.

nah this is how i always did it too, other ppl using cohost is actually how i learned about space-space at the end instead of backslash. maybe you can tell ive been blogging for awhile from that hahahahaha. i kept using backslash because its actually possible to see it in the editor.

the preview should be showing behavior based on what will be actually rendered so that part's a bug. editing old posts and having them maintain old behavior is expected tho.

I do write them in markdown. And then every time I cross-post to another site I have to specially edit it for each site's particular flavor of nonstandard markdown support, and each one is a little bit different. One of the nice things about this site is that it was Just Normal about markdown (at least as far as I noticed).

i think that the cohost markdown cheatsheet is now wrong then -- it says:

to separate text into paragraphs, leave an empty line between two blocks of text. if you do not leave an empty line between them, pressing enter once will still cause both blocks to be combined onto one line.

specifically, the second sentence about "both blocks being combined into a second line" seems incorrect.

(separately, i have a strong suspicion this may not be the most feasible, but it'd be nice to have a toggle for this, for those of us who like being able to hard wrap as we're typing / paste in from other places like text editors and such)