Lady @Lady@cat.family

I’ve just switched over to using <https://git.ladys.computer/Shushe>="⛩️📰 书社" to build my main site, which formerly was handcoded. At present, this hasn’t offered me much aside from the chance to fix a few bugs, altho it has made including images as data u·r·i’s a bit easier. However, i’m planning on adding some more dataful areas to the site which would have been very cumbersome to manage manually. More on those once i finish developing them.

The process of setting it up was easy; it is designed to work well with git submodules and be easily callable from within another make·file. Check the `build´ target of <https://git.ladys.computer/WWW/blob/86942bda88e834ee9fd5129483d38be15fe5950f:/GNUmakefile>="the `GNUmakefile´ for the site" to see what little it entails.

Permalink: <https://status.ladys.computer/urn:uuid:018cdd6e-9aec-76ac-87ab-c66c46158998>

@kinluwi follower-only replies from people that people on your instance follow is the most subtle way for posts to unexpectedly federate to you; it's not easy to check for in masto

more like “grown men rue my calls”

@Satsuma i would get annoyed if the names of the days cycled that fast

i think the 6-day week is fucked but included it for good measure; i’ve historically leaned 10-day but i’m starting to feel like 8-day might be better

which is better?

1) a 10-day week which alternates 3 days of labour and 2 days of rest

2) a 10-day week with 6 straight days of labour and a 4-day weekend

3) an 8-day week with 5 days of labour and a 3-day weekend

4) a 6-day week with 4 days of labour and a 2-day weekend

reply) some other week configuration which evenly divides 40 or 30

i *really* need to make my calendar

My goals for 2024 are split between the creative and the curatorial.

On the curatorial side, I want to build a better online home for my fannish presence—including a place (or two) to host my fanworks, but also including homes for other activities like webshrines, meta, ⁊·c. I’ve been steadily trying to build the technological infrastructure for this, with the most recent attempt being <https://git.ladys.computer/Shushe>="⛩️📰 书社".

It’s very easy to get bogged down with technological aspirations (federated tagging, update tracking, linked data), but there is also low‐hanging fruit, and I have been pretty good about making slow, steady progress in this area. It is difficult going alone! I wish I knew more technically‐minded fans with similar inclinations, but in fact it feels like most of both the tech world and the fannish world are trying to solve very different problems from me right now.

On the creative side, I really would like to write more. I hardly wrote at all in the past year, partially because I moved across the country to live with my girlfriend and partially because I spent so much time on the above technical work. I have so many wips that I haven’t been able to devote the time to finish and I feel like my writing craft has somewhat fallen by the wayside of late.

#SnowflakeChallenge

Permalink: <https://status.ladys.computer/urn:uuid:018cd746-3903-797b-aae3-4cefdacf8388>

@noracodes if it’s a longer document, it might be worth putting a “links look like this:” somewhere visible near the start of the page

generally the concerns are (1) visual distinctiveness of links (you have that covered), (2) ability to intuit that a given style implies a link (not obvious without knowing to try hovering one’s mouse over it, but fixable by stating as much somewhere on the page), and (3) cognitive load of remembering what links look like on this page versus any other page (always in conflict with any customization; able to be mitigated on the user end with things like reader view)

semi-relatedly, double-escaped entities is the single most cursed aspect of X·M·L

it was indeed a bug: https://gitlab.gnome.org/GNOME/libxml2/-/issues/655