thrwwycbr

Why are you using your personal account for work?

_always_ and I mean _always_ have a separate github/gitlab account for work and private things, otherwise you risk getting a lawsuit of your (former) employers. Especially if your work contract assigns all intellectual property rights to the employer.

Checklist security in a nutshell.

Does it have a checkmark? Yes? Must be secure then.

The point he was making was not about the tech or tools to sign commits.

It was about the laziness of humans not actually reading the code thoroughly when they sign it, and therefore negating the point of ledging/signing the state of the project.

I kind of agree with this argument, too.

The process of signing a commit is used in a kind of wrong manner, I suppose, because of your mentioned points.

The "view of the file tree as you saw it" basically implies that signed commits aren't worth anything if the code is refactored or changed later, which inevitably it will.

Using tags as a reference point, however, is the idea of snapshotting a mutually agreed state between multiple parties working on the project.

I think you could take this a little further, and use it to implement a Q&A workflow, where e.g. a code review team and a testing team should sign a specific snapshot as "working as we saw it", and that could integrate very well if you e.g. have a semantic version epoche of your project.

Shouldn't it be step -3 to -1?

As if IPs matter in the golden age of IoT botnets and residential app malware.

You can't even block the amount of subnets that's coming for you in a DDoS attack, thinking a human is able to keep up with something like this is pretty blindsighted and naive. The differentiation of network protocols and relay attacks alone is way too slow to be mitigated in most systems.

Well, technically, capsaicin is the end of the reaction.

Some might argue that all carbon acid amids are - as the name says - products of carbon acid reactions with ammonia.

At least in a natural, non synthesized, environment.

They release enzymes necessary for the spice/acid production. The acid counteracts those enzymes.

If you cut open peppers, you can see the black veins which were bit by bugs, those are the ones containing the carbon acid.

A better way to protect them against virusses but not against bugs that won't harm them is by combining the top of peppers with the root of potatoes, and by using moss to heal the cuts where you combined them (e.g. with a toothpick)

Of course that won't work on an industrial scale, hence them favoring pesticides.

The article doesn't contain the actual reason.

I'd argue that the real reason is that peppers are now mass produced in clean, bug-free, environments.

Which means: No bug bites, no spice.

If you grow peppers indoors where no bugs are, they tend to be a very mild produce. If you put them outside (and have enough insects around), they get much more spicy.

Of course the usage of pesticides contributes to that effect, due to bugs not having a chance to bite the fruits anymore.

Nothing you will ever build will work on iOS, because the minute you make money with it, Apple will kick you out.

Remember headphone jacks? Why do you think they got removed? Because all banking apps were using them, including paypal, square, hsbc and others - due to Apple not leaving any other option to build a credit card reader except by using an audio stream. And then even that got removed :)

All the unexplainable buggy behaviors on Microsoft systems.

We understand, buddy, don't worry about it.

F-droid.org is live and kicking. Reproducible build pipelines of open source apps et al.

Decentralized repos, subscription feeds, key signing, etc.

It only takes one Kape Technologies to unhide all of it.