Lady of Misrule @Lady@cat.family

(the short version is that the cgi service runs as a different user than owns the repository, which git doesn’t allow anymore unless you specifically opt in via a global .gitconfig)

apparently at some point my git updated to break https fetching from my gitweb server; i’d apologize but 0 people have noticed and sent me an email about it so

anyway ⛩️📰 书社 <https://git.ladys.computer/Shushe> is BASICALLY 1.0.0, pending me actually putting together documentation for it, which will take a while because that means coming up with my own custom documentation language, because DocBook wasn’t good enough for me, and my website has been Wanting an update for some time so i might go take it for a pre·emptive spin

the distinction between emoji style and text style is like the distinction between upright and italic, the existence of variation selectors for some of the set NOTWITHSTANDING

give me the means to choose at the font level!!

the entire POINT is that whether a character has text or emoji presentation should be a quality of higher‐level markup and not encoded at the character level. variation selectors are a begrudging concession for use in limited scenarios where a plaintext distinction may never·the·less be argued for. but that whole conceptual framework doesn’t WORK when your higher‐level markup is just doing “implicitly insert characters into the text stream and then render as plaintext like normal”

of COURSE this would mean doing additional work, work which may right now be difficult or even impossible, to do font selection to ensure that only fonts which display emoji characters with text presentation are used, and not fonts which display emoji characters with emoji presentation. this is maybe impossible because i am not sure fonts STILL have a good understanding of what “emoji presentation” means nor operating systems fallback mechanisms for properly selecting the correct font for a given presentation. NEVER·THE·LESS

the current definition of `font-variant-emoji´ simply implicitly adds a V·S·15 or V·S·16 after emoji characters which can take them. this is definitely the least useful possible interpretation of `font-variant-emoji´. if i `font-variant-emoji: text´, i would like NO emoji characters to be given emoji presentation, not “only emoji characters which were not {already encoded codepoints at time of encoding and thus prone to possible awkward re·presentations in pre·existing encoded texts}”

“people” in this case being C·S·S·W·G

thinking of redesigning my website; got distracted by people possibly misunderstanding and at least being really awkward about unicode

i will consider paying money to servo once i can right‐click and copy a link in their browser

« As browsers have become more powerful, plugins have become less useful. » is that why

🆖

the new york times editorial board, home of the world’s most lukewarm and tepid takes, is now calling on biden to drop out of the race for the sake of the country, if you were wondering how things are going

(please don’t put “i filed a bug report on GNOME GitLab” on your resume; save that for the interview)

if i were hiring for a position i would rank someone with an account on GNOME GitLab who only submitted a couple of issues above someone with a GitHub account with 2000 commits and 30 pull requests merged

i do not care about your github stats

in fact i care substantially more about how many repositories you have contributed to that are NOT on github

i gotta say, even with microsoft and all, nothing has turned me off of github more than techbros treating it like a linkedin

any day the N·F·L is ordered to pay as much as $14 billion is a good day

hell yea https://www.nytimes.com/2024/06/27/business/media/nfl-sunday-ticket-lawsuit-billions-damage.html