• 0 Posts
  • 6 Comments
Joined 1 year ago
cake
Cake day: July 29th, 2023

help-circle
  • It’s a long read, but a good one (though not a nice one).

    • learn about how all the people who actually make decisions in c++ world are complete assholes!
    • liking go (the programming language) correlated with brain damage!
    • in c++ world, it is ok to throw an arbitrary number of highly competent non-bros out of the window in order to keep a bro on board, even if said bro drugged and raped a minor!
    • the c++ module system is like a gunshot wound to the ass!
    • c++ leadership is delusional about memory safety!
    • even more assholes!

    Someone on mastodon (can’t remember who right now) joked that they were expecting the c++ committee to publicly support trump, in the hopes he would retract the usg memory safety requirements. I can now believe that they might have considered that, and are probably hoping he’ll come down in their favour now that he’s coming in.


  • Just take the same approach that mathstodon does with their latex formatting, to wit: just barf the probably-human-unreadable format strings out over activity pub, and shrug when people complain because what else are you gonna do?

    It isn’t like inline images work any better over activitypub in general (and even markdown/html is tricky, in the face of various mediocre mastodon client apps, some of which I use) and doing server-side conversion of latex (or whatever)to mathml is a nonstarter because of it will just be filtered out by clients anyway as unsupported and possibly malicious.

    The least bad option might be something like asciimath (which can be prettyprinted via mathjax client javascript in the web view of the site) as its raw form is less awful to read than latex, and so would be more suited to viewing via activitypub or in a lemmy app.

    I wonder what proportion of awful.systems users view it via the web interface.


  • Everyone and their dog uses mathjax or katex to render math client-side these days. I’m not gonna say that it would be trivial, but it also shouldn’t require you to get elbow-deep in lemmy’s own post-formatting code.

    Unfortunately, there’s no obvious prior art that can be stolen here, and there’s only one slightly confused feature request in the lemmy-ui repo, so someone is going to have to nail all the bits together themselves.