“abbabba”
“abbabba” doesn’t match the original regex but “abbaabba” does
“abbabba”
“abbabba” doesn’t match the original regex but “abbaabba” does
curl shit | sudo bash
is just so convenient.
I think it’s more that they haven’t tested the software changing mode mid-mission. At least that’s Scott Manley’s impression(@5:50ish).
Given the software issues thus far, I can see they’d be a bit wary that flipping that switch could cause problems.
I would think they could set it back to autonomous mode but that they have to do the testing and validation to prove the system will tolerate the change with no issues.
I’d love to have human editors to fix up stories, but we have the technology now. There are FOSS tools like redpen that will help with spelling and grammar. AI tools ought to do a somewhat reasonable job of appraising a piece of text and yeah, a second human ought to sign off before publishing. I’d have thought content management systems would have review stages like software development. Authors could accept or override suggestions, but be required to acknowledge them. Like why isn’t journops a thing?
I think you might be right. Another article by the same author seems like it could be entirely made up, only citing Wikipedia for things like the definition of the word ‘confidence’. I don’t know what would prompt it to leave these ‘fill in the blank’ sections though.
I understood [reference] and am continually amazed how news sources don’t have some kind of automated review process to stop stupid errors like that.
To be clear, the record label is Death Row Records. He was initially charged with attempted murder but that was dropped and he wasn’t ever facing the death penalty. He was behind bars for 33 years for running a “nationwide drug trafficking operation that brought in nearly $2 million daily.” Snoop now owns Death Row Records.
Getting paid by the gun lobby.
probably
[citation needed]
Posing with a baggie of thoughts and prayers for victims of a typical mass shooting:
http://web.archive.org/web/20210209185752/https://friendlyatheist.patheos.com/2018/02/19/a-gop-congressman-gave-trump-a-literal-bag-of-prayers-after-the-school-shooting/
Oh, right, yeah. The question was whether others were shot. I didn’t think they were concerned about the shooter and obviously Trump wasn’t seriously hurt.
I thought it was 1 dead 2 injured. That’s what’s on Wikipedia.
Corey Comperatore, the volunteer fire chief was the one who died. Was there another?
I should have made this a top-level comment:
TL;DR: he wasn’t banned, he quit:
On Saturday, I was perplexed by photos online of Trump boarding his plane en route to a bitcoin conference. There was no bandage on his right ear. I re-posted one of the photos on Twitter and wrote, “look closely at his ear that was ‘hit’ by a bullet from a AR-15 assault rifle.”
“Fake news,” someone responded. “It’s the wrong ear,” said another, which of course was not true. “This is an old photo,” which I felt the need to reply to. I re-posted a screenshot of New York Times photographer Doug Mills’ Twitter post of the same situation of Trump boarding his plane, which included the date and time of his photo. Doug is one of Trump’s favorite photographers and Trump has publicly called him “my genius photographer.” So I thought the maga world would at least believe Doug Mills.
They didn’t. The comments turned ugly. Mostly about me, but also some that disparaged Doug Mills. Since 2017, I’ve been accustomed to having vile and hateful comments thrown at me. But I had now exposed someone else, Doug Mills, to be the recipient of hateful messages on MY Twitter account. Not cool.
On top of that, I’ve been at a cabin with no Internet and sporadic cell coverage for the past week, which made it difficult to post anything in the first place but also a challenge to push back against the hate.
So I de-activated my Twitter account. It was a gut decision, made only by me. I am still not sure if this is a temporary or a permanent action.
I was unaware that some on Twitter were a responding that Elon Musk had deleted my account. How would I know? I wasn’t able to access Twitter. I did receive a few DMs here on Instagram about this, but didn’t think much about it. Until…late last night, I received a text message from a New York Times reporter asking me to comment about my supposedly “being kicked off X for posting a photo of Trump’s ear.” And then this morning, I received a text message from a childhood friend who asked, in jest, “Is there a Free Pete Souza donation site?”
It was time to respond. I have so much more I want to say about the state of social media, but for now I want to make it clear that I was not kicked off Twitter. I kicked myself off.
Except PGP is a substring of the ‘technically correct’ term. It’s like someone saying you’re playing on your Nintendo - “Um, actually it’s a Nintendo 64.”
----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEETYf5hKIig5JX/jalu9uZGunHyUIFAmaB8YEACgkQu9uZGunH
yUKi7Q/+OJPzHWfGPtzk53KnMJ3GC8KQGEUCzKkSKmE0ugdI9h1Lj4SkvHpKWECK
Y1GxNujMPRM/aAS2M97AEbtYolenWzgYmO1wt131/hEG4tk+iYeB2Sfyvngbg5KI
y4D7mqpcVWYSf6S13vUX8VuyKeTxK6xdkp95E0wPVLfJwx5o5nH0njLXxeW0IblY
URLonem/yuBrJ6Ny3XX9+sKRKcdI9tOqhMhTxPcQySXcTx1pAG7YE7G5UqTbJxis
wy7LbYZB5Yy0FO3CtRIkA+cclG4y2RMM9M9buHzXTWCyDuoQao68yEVh4OdqwH1U
5AUnqdve5SiwygF/vc50Ila6VjJ4hyz1qVQnjqqD96p7CSVzVudLDDZMQZ8WvqLh
qaFr51xJvH6p6/CP1ji4HHucbJf6BhtSqc8ID9KFfaXxjfZHiUtgsVDYMV0e7u9v
lhcDH/3kmw/JImX25qsEsBeQyzOJsBvxOYD3lZrwSY9+7KNGVQstFrEvCuVPHr72
BQJPIhg3+9g6m36+9Uhs1N6b8G9DsZ6OgnNqr9dGturUg6CtRsLSpqoZq0FT9cLA
tnFTJDaXgx1DZnsLGDSoQQYjZ3vS+YYZ8jG86KGLFyXVK+uSssvorm9YR1/GGOy7
suaxro72An+MxCczF5TIR9n3gisKvcwa8ZbdoaGd9cigyzWlYg8=
=EgZm
----END PGP SIGNATURE-----
It’s a proprietary config file. I think it’s a list of rules to forbid certain behaviours on the system. Presumably it’s downloaded by some userland service, but it has to be parsed by the kernel driver. I think the files get loaded ok but the driver crashes when iterating over an array of pointers. Possibly these are the rules and some have uninitialised pointers but this is speculation based on some kernel dumps on twitter. So the bug probably existed in the kernel driver for quite a while, but they pushed a (somehow) malformed config file that triggered the crash.
For this Channel File, yes. I don’t know what the failure rate is - this article mentions 40-70%, but there could well be a lot of variance between different companies’ machines.
The driver has presumably had this bug for some time, but they’ve never had a channel file trigger it before. I can’t find any good information on how they deploy these channel files other than that they push several changes per day. One would hope these are always run by a diverse set of test machines to validate there’s no impact to functionality but only they know the procedure there. It might vary based on how urgent a mitigation is or how invasive it’ll be - though they could just be winging it. It’d be interesting to find out exactly how this all went down.
For thin clients?