As a thin veil of excuse, the DCRI incident involved what they considered military secrets rather than defamation charges. Still dumb to do that extrajudicially, of course.

The article on the lawsuit is blocked, which is standard procedure for participants of an ongoing lawsuit: Talk to your lawyer about it, and nobody else, because anything you say without your lawyer’s counsel might jeopardise your legal position. Even if it’s just people editing that article, the foundation will want to protect itself until the matter is settled.

Don’t forget that non-profits, too, are beholden to laws. If they want to continue offering their services in India, they don’t really want to be charged for contempt on top of the other case.

People here prefer the federation of Mastodon

I browse all a lot to look for interesting new communities. Every now and then I come across a new community from ani.social, the NSFW instance or something, and on Voyager I can’t seem to block entire instances. I also don’t know if there’s a way to filter only the communities without blocking the users too, but as it stands, I may have to look for another app to block the instances entirely.

Shouldn’t, definitely. But for a while, it will keep running, because that’s how a lot of speculative investment works.

It can! For a while. Isn’t that the nature of speculation and speculative bubbles? Sure, they may pop some day, because we don’t know for sure what’s a bubble and what is a promising market disruption. But a bunch of people make a bunch of money until then, and that’s all that matters.

Oh believe me, I would change some things about that database if I could. Alas, I’m just the analyst building data models from it.

(To be fair, it’s otherwise easy to work with and for most use-cases, it doesn’t matter since they’re aggregated per month anyway, so I just load the last month’s data on the 2nd of each month. I definitely have worse patients to operate on.)

Unrelated to the topic, but I deal with a database storing timestamps.

In local time.

For systems all around the world.

You’ll see current entries timestamped 12:28 from eastern Europe followed by ones 6:28 from America and then another 11:28 from central Europe.

Without offset.

In my classes on analytics, we were taught to prefer using normalised axes starting at 0 to more accurately put changes into perspective.

I wasn’t strictly meaning to correct so much as point out a reason why it’s more concise. I value the inclusive motivation too, if that was hard to tell; I just think there is another reason even if you don’t care about inclusion.

It seems a lot of people are actively opposed to it though, not sure why. I’m just asking questions, you know?

😉

When it’s built around lage aggregators, running which privately is rather hard, there’s a bias in favour of centralised, large operators thereof, which mitigates some of the advantages.

“their” is shorter than “his or her”

(Even if you don’t care about gender inclusiveness, they is just more convenient)

That’s the other option, of course: If your employees are happy, they don’t need to form a union to press complaints.

Maybe they just forgot to brainwash them with anti-union propaganda

For the right jobs, it’s a good tool.

This isn’t the right job.

Sounds like they did the lookups by hand actually

cries in data analyst

Did you know our company is over a thousand years old, possibly even two? Recent dives into our digital archives have unearthed invoice records dated to the year 1021, though we’re also investigating the validity of one dated to 215.

Whoever decided to make dates a manual entry text field without validation should be forced to write SQL by hand, without syntax highlighting, autocompletion, syntax checks, reference or looking up stuff, querying a database with no schema or data dictionary.

Well, it’s ““This””, not “This”, so I’d say it’s fine.

I share your hope. I’m just offering the caveat that it might not go as quickly and smoothly as you expect (unless I’m reading your comments wrong - do correct me!)

It’s my perpetual gripe with many of those open tools that I love ideologically, but practically find lacking in some respects, typically UI/UX (including the pre-experience of the decision whether to use them). I don’t have all the skills or knowledge to fix the issues that bother me, as it’s often far eaiser to know what’s wrong than how to fix it.

I understand and endorse the philosophy that it’s unfair to demand things of volunteers already donating their time and skills to the public, but it creates some interdisciplinary problems. Even if capable UX designers were to tackle the issue and propose solutions or improvements, they might not all have the skills to actually implement them, so they’d have to rely on developers to indulge their requests.
And from my own experience, devs tend to prioritise function over form, because techy people are often adept enough at navigating less-polished interfaces. Creating a pretty frontend takes away time from creating stuff I’d find useful.

I don’t know if there’s an easy solution. The intersection between “People that can approach software from the perspective of a non-tech user”, “People that are willing to approach techy Software” and “People that are tech-savy enough to be able to fix the usability issues” is probably very small.