Sven Slootweg @joepie91@pixie.town

A thought. Here’s the thing about sharing pronouns on profiles, even if you think it’s obvious or think it’s not for you because you’re cis/straight.

Sharing your pronouns is using your privilege to normalize the practice of doing so. If more of us share our pronouns, it becomes a WE thing instead of a THEY thing.

This reduces the othering people who aren’t cis/straight experience every day.

1/2

#LGBTQ #Pronouns #Allyship #Unity #Humanity #Empathy #Othering

#FediBlock cloudflare.social

because fuck crimeflare, also: didn't people suggest to fediblock all wildebeest instances on sight? now it's got a public release...

So much of tech discourse asks us to be excited about the nexus, never wary of the torment.

(The Torment Nexus meme is honestly one of my favorite Internet Darmoks, right up there with Milkshake Duck.)

Looking for anti-Elsevier propaganda, logos etc; I can’t find any on the web!

So I and the other folks at mastodon.mit.edu were offline for a couple of days because (so I’ve heard) a pipe froze and burst in the MIT student center, knocking out the server of the student group managing this until just now.

Which on the one hand, sure, that didn’t happen with the birdsite. But I had forgotten how strangely comforting it is to know exactly where your data is and who is managing it.

PSA For Anyone On Meds:

Baja Blast contains grapefruit! Do not drink it! Grapefruit de-activates a wide variety of medications!

When people misuse the words concrete, asphalt and gravel, it's just cementics.

JFC, I'll take a slew of half baked 2000s era Under Construction 🚧​ websites any day to this utterly barren internet wasteland of search results that are machine generated copies of other sites that are machine generated copies of other sites that are machine generated to only appear in my search in order to attempt to sell me something.

🤔

I get so tired of academic publishing. I am trying to get something peer reviewed ( https://www.biorxiv.org/content/10.1101/807693v2 ) that I spent a huge amount of time writing and typesetting to make readable and accessible without all the dogshit we do to papers, like hiding away all the detail in supplements that you have to flip back and forth from to understand anyway. That means that the document ends up being like 45 pages, but that's because the text is 2/3 width with 1/3 for margin figures and margin notes, lots of whitespace, about 100 diagrams, figures, pictures, etc. interwoven with the text to support the reader!

If I render it in the typical reader-hostile way, remove all the parts where I'm trying to make it accessible to nonprogrammers, remove all context that informs the state of prior art and the motivation for the work, and remove all the figures except the ones plotting data it is normal paper length.

I can't get it reviewed! It's "too long" and it's a "user guide, not a paper." So now I have to chop it back up, shoehorn it into typical paper format, make it worse to read and harder to understand. That, or I guess I could do the usual perfunctory 5 page code paper that just says "we made a package to do experiments, here it is doing experiments" without any effort to contextualize it or describe how and why it works that way.

Is this really how we want it to work? Only things that hew exactly to the traditional style are allowed to exist, if you try and experiment with new document forms you're just wasting your time, the only thing that matters is that it "looks like science."

Is there a place where people developing third party tools and clients for Mastodon are hanging out?