bloopernova

vor 2 Jahrendiscuss

Oh hell yes, thank you for this.

vor 2 Jahrendiscuss

The threads have probably tripped the flamewar detector. Certain amount of comments plus some other metrics will hide the thread from the front page.

bloopernova

vor 2 Jahrendiscuss

Have any corporations previously tried to deny they were breached?

I'm wondering what AT&T thinks they'll achieve? If they're lying, that is.

bloopernova

vor 2 Jahrendiscuss

"On January 6, 2021, few people at The New York Times remarked on the fact that liberals were cheering on the deployment of National Guardsmen to stop rioting at the Capitol Building in Washington, D.C., the very thing Tom Cotton had advocated."

People burning police cars and a police station in Portland after a man is killed by police, at a time when opinion of police is very low.

Vs.

People invading the US Capitol building during the ratification of the presidential election, at the behest of the losing candidate, while a gallows was erected outside.

Those 2 situations are very different. It's disingenuous or dishonest to say otherwise.

This piece talks a lot about how biased the author's coworkers were, but says nothing of his own biases. The USA isn't going to heal until conservatives reject christian nationalism and instead embrace compromise.

bloopernova

vor 3 Jahrendiscuss

My own somewhat related saying: "Nobody's gravestone reads 'if only I had worked longer hours'"

bloopernova

vor 3 Jahrendiscuss

"To see with eyes unclouded by hate" - Ashitaka, Princess Mononoke

bloopernova

vor 3 Jahrendiscuss

It's something I have to remind myself frequently: leadership got where they are by surviving the cutthroat backstabbing executive gauntlet. I also have to trust my gut when it sends me warning signals about someone, and I get that a lot from "celebrity" CEOs.

After some reflection, I've found that I sympathize with Ilya Sustkever a bit more now. I'm autistic and I suspect he is neurodiverse in some way. I've definitely been misled by manipulative leaders and peers, been enthusiastic for whatever scheme they had, but regretted it after seeing the aftermath or fallout. I can absolutely see ways Sustkever could have been manipulated by others on the board.

bloopernova

vor 3 Jahrendiscuss

Hey that's good stuff, thank you!

bloopernova

vor 3 Jahrendiscuss

uBlock Origin can also be used to modify the DOM or CSS in specific URLs via its "My Filters" screen.

For instance, I use it to switch HackerNews to dark mode, and restrict the width of comments to about 10-12 words: https://gist.github.com/aclarknexient/c39c83f2f97c3c6b1c307c...

It's a great alternative to GreaseMonkey or other user style extensions.

bloopernova

vor 3 Jahrendiscuss

I know, right? I really want one for my wall.

bloopernova

vor 3 Jahrendiscuss

Yes, it doesn't fork a separate process. I doubt I could really tell the difference in prompt responsiveness, but I liked learning about the printf -v COMMA_EPOCH method.

bloopernova

vor 3 Jahrendiscuss

If you like to have the Unix epoch in your prompt, you can do something like this:

    function prompt_epoch() {
        printf -v COMMA_EPOCH "%'d" ${EPOCHSECONDS}
        p10k segment -f 66 -t ${COMMA_EPOCH}
    }

EPOCHSECONDS relies on `zmodload zsh/datetime`. printf -v creates a variable rather than output text. p10k segment is just a function that powerlevel10k uses, you don't have to use it. COMMA_EPOCH is just the current Unix time separated by commas every 3 digits.

If you wanted your own countdown, you could easily do `2147483647 - EPOCHSECONDS` and display that time instead.

EDIT: and if you want to mimic that oh-so-cool clock, you could do:

    printf '%x\n' $EPOCHSECONDS

or assign that to a variable with printf -v, then split the string into pairs. Mimicking the colours of the clock would be fairly trivial too.

bloopernova

vor 3 Jahrendiscuss

Not a silly question!

In this case, we don't have control over the docker images used to build our apps.

bloopernova

vor 3 Jahrendiscuss

Similarly with the command line in general. Yet you'd think it was torture to some developers I know!

bloopernova

vor 3 Jahrendiscuss

    parallel --embed > parallel.sh

Then store that in your source repo and use it wherever shells are used!

bloopernova

vor 3 Jahrendiscuss

You don't have to reinvent the wheel for your script, all the parallel options are ready for you to use and are well documented. It's also packed with features that might take a long time to write into your Python script.

I am trying to use Python by default when writing scripts nowadays, but sometimes the best tool for the job isn't Python or writing your own Python.

bloopernova

vor 3 Jahrendiscuss

See my comment above, there's a shell version you can store in your project repository and use wherever you want with zero installation!

https://news.ycombinator.com/item?id=37208250

bloopernova

vor 3 Jahrendiscuss

There's a shell script version of GNU parallel that's great for CI/CD pipeline tasks. You just keep it in your repo and source it as needed. It's incredibly useful, we use it in one build to batch process a few thousand things in groups of 25.

Edited to add: finally got signed in to work, you create the script via:

    parallel --embed > scriptname.sh

It's about 14,000 lines of awesome and works on "ash, bash, dash, ksh, sh, and zsh"

bloopernova

vor 3 Jahrendiscuss

Sorry, I didn't quite answer your question!

Yes, the expected behaviour would be for the disks to be initialized. Beyond that, it'd be a configuration setting for what to do with new disks. It could be used to extend the existing LUNs, or added as a new pair in a RAID 10 style setup, or added as new members of a different level RAID.

Then it would be up to the sysadmin to extend the LUN, or divide the newly added space among multiple LUNs.

Different arrays have different behaviour with new disk. Some only add to offline LUNs. Some do everything online with lower performance, as you said. Even some super expensive enterprise kit will be very easy to break by adding new disk.

bloopernova

vor 3 Jahrendiscuss

Well, in my sysadmin days we would have test/staging equipment that we'd make sure we knew what would happen when a change was made.

But I don't know the details of what really happened, so I can't make a judgement really. If I could edit my previous comment I would, to be less emphatic that someone did something "wrong".

It could have been that this particular disk array had different firmware or was faulty. All we know is that something unexpected happened.