actuallyalys
@actuallyalys
This post has content warnings for: transphobia, transphobia is below "read more".

actuallyalys
@actuallyalys

Nim v2 release candidate coincidentally just came out, and it seems to be a step forward in terms of stabilizing and maturing the language: https://nim-lang.org/blog/2022/12/21/version-20-rc.html. it makes more improvements than i was expecting, so that's cool.



one unfortunate thing about the CW system in conjunction with long posts is that it hides the whole post, including the headline. if i write a long post that touches on transphobia and i mark it as such (like my last post), that's all you can see, except for the tags, even though it's not really about transphobia, and a reader could skip over the section that discusses transphobia.

i could write an ad hoc CW hiding system with CSS, but i'm not confident it will work as reliably as the actual CW system. also, it wouldn't work with CW filtering. in this particular case i could arguably skip the CW, since it's not that explicit, but a similar problem could still happen for long posts with explicit bigotry. also, i'm not that familiar with cohost to know where people want the line to be drawn.

that being said, i appreciate cohost's CW system, and i think the filtering feature is a good idea. it just interacts badly with long posts sometimes, imo.