_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.

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

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.

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.

But one project didn't make enough money and the author of the other one got doxxed into oblivion, so I guess we can't have nice things.

A peer to peer browser has so much potential, I wish somebody else might give it a try. Imagine the possibilities when you can just share the content with others, without needing a web server.

Does anybody know whether there's a decentralized (static/generated) blog for ipfs or similar? Maybe that would make a nice starting point.

[1] https://github.com/beakerbrowser/beaker

[2] https://github.com/tholian-network/stealth

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.

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.

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.

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.

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 :)

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

Decentralized repos, subscription feeds, key signing, etc.

Maybe you should take a look on the Network Tab, because Atlassian sure does have a crappy network stack.

Additionally, the refund policy of Apple is so bad that they keep the 30% and the developer has to pay for refunds 100%, meaning it's a net loss and a lot of indie game devs got doxxed into insolvency because of this.

This very detail is the reason USB flash drives have useless performance numbers on them, which oftentimes lead to 1/100th of the advertised performance.

Everything that's bigger than the sector size (4k) is usually far lower than those numbers.

In WebKit, however, that implies that they refactor the Bridge API that is used in between contexts and processes which was an internal API before and broke away often.

So I'd guess they start to do incremental changes on the Web API implementations first before they break too much anywhere else (e.g. sidebars, UIs, widgets, devtools are rendered differently but rely on the very same Bridge API)

They are a software product fork used by billions, with a team that doesn't get paid to develop on it, with not enough funding to just "buy" a battle tested library which has zero problems; because any bug would literally potentially break the web for years.

SocialVer:

- upvote or downvote major release changes

- emojis to communicate the level of upgrade pain

- emojis to communicate the level of disaster after upgrading