I'm going to let bugbot run over the weekend and then share some details about how to use it with others.

If your state-issued ID has a "sex" field, then technically you live in a state that maintains a genital registry.

Feel free to share that with your conservative friends.

Some of the best people I've known were trans and enbies.

💙🩷🤍🩷💙

Mi casa es su casa. My rights are your rights.

#TransRights #TransSolidarity

Today, we're bidding farewell to codeaurora.org. It had a good run, but all projects have moved on to other platforms.

Good bye, good friend, and thanks for all the fish.

/me carefully, gingerly, with some cringing, enables bugbot on the first valid-looking bug and waits for results.

I’m generating my own artisanal message-id’s, thank you.

https://paste.centos.org/view/d7c0ef61

Oh no, neomutt switched to entirely randomly generated message-ids in the latest release. I'm not fond of this either. :(

I've got to say, that considering who is developing it (the person behind SSB, for one), I am interested to see how the AT protocol shapes up.

https://atproto.com/

Yes, there may be a few bugs there. Probably. Or there could be zero bugs. It's like looking for a black cat in a dark room -- you won't find it until you stumble over it.

Nice, Lore and B4 make a brief appearance on Picard!

Bugbot status update: it's now able to monitor lore lists and start tracking threads as bugs based on an arbitrary query. E.g. you can mention "bugbot engage" in a thread and the entire thread will be converted to a bugzilla bug (if the email of the person issuing this command matches a bugzilla account with "editbugs" group membership). Any subsequent messages in the thread will be automatically added to the bug as new comments. Any comments posted on the bug via bugzilla interface will be sent to original recipients.

Now working on the other direction -- bugs added in bugzilla will be converted to mailing list threads and sent to proper maintainers (based on certain conditions, e.g. a "bugbot" flag needs to be set to "on" and the cf_subsystem custom field needs to match the corresponding MAINTAINERS entry). Should be done tomorrow, at which point I'll be looking for early testers. :)

@shanselman Help, Fallout 4 story lines are bleeding into my reality.

RE: https://hachyderm.io/users/shanselman/statuses/110065829678443226

This is how wizard paintings in Harry Potter work. They emulate dead people based on statistical analysis of things they have previously said.

Of course, I can only imagine the kinds of terrible effects this could have on people in mourning, so I predict legislation restricting this practice.

https://futurism.com/chatgpt-emulating-dead-people

Thanks for the DDoS, HN. I didn't have any plans for the afternoon anyway.

I've blocked more accounts in the past day than in the entire past 4 months.

I picked Akkoma because it looked more fun. No other reason.

Heh, I can tell when Linus posts by the amount of 500 errors I start seeing on the social system. Need to start optimizing our setup.

The erlang stack itself is actually doing great, but the database load spikes like crazy. It's actually a known problem of pleroma and derivatives -- the db backend could use a lot of loving, especially when it comes to optimizing queries.

Here's my _personal_ view on the Baikal Elektroniks situation. This is not any kind of official statement by LF.

First of all, everyone must understand that Baikal Elektroniks is a company that produces equipment for pretty much a single client -- the Russian state. You can nominally buy a computer with a BE chip as a private citizen, but in reality you'd never do so because a) it's almost impossible to get, b) you'd buy a much slower chip and pay 4-5 times more than you would for any other chip available on the market. So, it's accurate to say that BE produces equipment pretty much exclusively for the Russian military and its state run businesses (who are mandated to buy BE equipment by law).

Second of all, and most importantly -- getting your patches accepted into mainline means receiving a lot of very expensive labour and computing resources gratis: you not only get free code reviews from maintainers, but you also benefit from a bunch of behind-the-scenes CI infrastructure that runs checks on your code -- both at the patch stage, and later as part of regular integration/CI/fuzzing runs. Any treewide changes, such as security improvements by efforts like KSPP, will also be automatically applied to any in-kernel drivers and architectures.

So, in reality, accepting code for any hardware into the Linux kernel means helping to test, maintain, and debug that code for years to come. The resources for that are pooled from many device manufacturers with the understanding that these efforts will be part of the tide that "lifts all boats," including their own. However, in the case of Baikal Elektroniks the situation becomes tricky. Yes, Linux is free software (free as in libre), but maintainers and CI infrastructure require funding. BE is placed under strict sanctions in many countries due to its direct affiliation with the Russian military, so companies funding CI and maintainer efforts have to consider if their money is directly benefiting a sanctioned company (and, indirectly, the Russian military).

So, it may be true that the rising tide lifts all boats, but if that boat is a Russian military warship, you have to decide what kind of message you send them.

Hmm... Looks like I may need to resize the database backend for Akkoma, as I'm starting to see db query load spiking.

Humans: I shouldn't have to remember your preferred pronouns
Same humans: this table is a "he" if you're German, a "she" if you're French, and "it" if you're English.