__jal

For starters, that "just" is swallowing:

- Identify the relevant tokens you want to scan for, and create regular expressions to capture them.

- Create a token alert service which accepts webhooks from GitHub that contain the token scanning message payload.

- Implement signature verification in your token alert service.

- Implement token revocation and user notification in your token alert service.

And that would replace one piece of what this does.

We do several of these things, and bundling them together looks nice; I imagine troubleshooting the pipeline is much easier. We would need the enterprise version because we are on-prem, and our user count compared against the 'pro' edition makes me think this would be a hard sell - high 5 figures/year to replace a few shell scripts is tough.

Reminds me of a saying from the first dot.com crash. (Or at least I heard it then first.)

Tying two bricks together doesn't make them float.

Why keep yourself in a position where you have to ask FB for permission to speak?

Vote with your feet. Build a website FB doesn't control.

Many of us in California don't care if you think they "shouldn't" live here.

I'm perfectly well aware of the economic and tribal arguments. The former are not convincing and the proponents of the latter can go pound sand - given my preferences, I'd exclude them long before I'd exclude immigrants over paperwork.

So, explain this. I mean, it is a positive step that you've backed off your strange "rage" accusation, but why do you consider my stance on the technical merits of this step irrational?

Why does any criticism of systemd have to be due to "rage"? There is this ongoing behavior whereby anything other than fawning praise is treated as irrational and emotion-driven.

You may as well ask why Lennart rages so hard against ZFS.

I think this may be where I step off the train. I grumbled, but can live with it as init, and it is easy enough to disable the ntp and name resolution nonsense to use decent tools.

Buy systemd has no business sticking its nose in authentication or storage, or more generally telling me how to manage users. This is a no.

There has been more than one Cisco vulnerability that struck people as suspicious.

I know it comes to my mind every time I see the string "Cisco zero day", whether or not it seems likely in any particular case.

Don't fall for the trap that this is about "big tech".

It isn't.

It is about your freedom of speech and ability to protect yourself.

The problem would be that they would no longer be academics.

For a lot of people who head down that path, they consider it more of a vocation than a job. It may well be a good thing for all the next folks who consider the path, but it choosing that would come at a large personal cost for them.

Most folks are not that altruistic.