_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.
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.
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.
Of course not. You try to do 0 but that's impossible because you need to do -1 first. So you drop everything, try to do -1 but that's ... It's yak shaving's evil twin!
For me, the peak of decentralization efforts were Beaker Browser [1] and Stealth [2].
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.
I actually can't imagine what are the possibilities the personal web server gives me, compared to github pages or cloudflare pages or tons of other super cheap web hosts.
Ease of use / nice design tools? You don't need a new protocol for it, create your web editor and add plugins for common providers. Your website would be accessible from any browser, nicely solving chicken-and-egg problems.
Free domain names? Plenty of existing systems exists, and many of them are actually compatible with existing browsers.
Availability? Any real server will be way more reliable than your home machine that will go to sleep when unused, get updates, etc. And if you say "IPFS", then you still need to sign up with some centralized service to pin your site, so might as well sign up for webhost instead.
Illegal content? P2P exposes your IP, so your local police has access to it. And if it's kind of the content that is not actually illegal, just heavily frowned upon, there would still be plenty of hosters willing to host you.
Unlimited media storage? That could be a legitimate reason, but most people would want to store their video using dedicated system anyway (youtube / peertube), and modern storage is so cheap, the photos are not going to be a problem (Cloudflare free plan gives you up to 20,000 files up to 25 MB each for free for example)
> if you say "IPFS", then you still need to sign up with some centralized service
Ipfs actually has some inbuilt cashing, so visitors to your site also take part of the load and can serve your assets when your PC/internet is down. All without pinning, purely based on GC timing. So as long as you are online reasonably often and your content has readers you will be fine. Another idea has been to make it so that bookmarking works a bit like pinning so by using the decentralized web you actually archive it (sort of)
How much data can you reliably cache this way, though, especially with bookmark approach? Even free website providers give you gigabyte of space or more, and you are competing with them.
How do you handle outdated pages? A p2p file sharing is one thing. A file is pretty static, but websites change very often. By the time your file got shared all the way across the planet you might be already displaying something else. Do they all have to keep track of the original file?
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.
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.
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.
I've read that slightly dehydrating your plants as they fruit is developing helps increase the capsaicin. You can also blend up the peppers and spray them down, which seems to agitate the peppers, and possibly send a chemical signal for the plant to start produce more capsaicin (although that's all been anecdotal evidence to my knowledge).
The bites themselves don’t cause the plant to produce more capsaicin. It’s natural selection - plants in areas with lots of insects end up producing more capsaicin as a means of protecting themselves. They are hotter, and insects will not bite them as a result.
Happy to be proven wrong if you have sources saying otherwise, but I’m quite certain this is the science behind it.
This is basically the same as arguing that exposure to sunlight won't darken your skin, but it will mean that natural selection gives your descendants darker skin.
There is every reason to expect that a plant's defenses against predation will be more active the more predation it experiences.
Melanin is produced as a reaction to UV exposure. Capsaicin is not produced as a reaction to bug bites. This is basic Darwinism vs Lamarckism, evolutionary pressure vs the idea of inheriting acquired traits.
The spice is an evolved defense mechanism, so if it's not needed, the peppers eventually stop producing it. Couple that with us intentionally selecting for things other than spice, and within a few generations you have a less spicy pepper.
Note I'm not any kind of qualified to talk on this topic. I'm sure someone can give a better & more accurate answer!
It's indeed a defense mechanism, but (from what I understand) it has less to do with bugs and more to do with mammals; pepper plants started surrounding the seeds with capsaicin to ward off mammals (which chew up and destroy the seeds) while still being palatable to birds (which ingest the seeds whole and "drop them off" elsewhere).
Then a certain species of primate decided "Grug inflict pain on self, makes Grug happy" and the rest is history.
No problem for birds either who don't have the taste buds for capsaicin. I had to buy spicy bird food for a while to ward off the squirrels. A little cruel maybe.
The summarized version was that they've selected for milder more consistently flavored jalapeños for mass manufacturing purposes where the companies using the peppers in their products prefer to control the level of spice with capsaicin extract.
It doesn’t solve all aspects I’m interested in. F droid only solves discoverability and only on android.
It doesn’t solve monetization nor does it solve platform integration, it doesn’t work with iOS, it’s not platform agnostic.
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 :)
_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.