Yes. That is far more harmonious with nature than using machines of industry to enslave animal species and slaughter them on profit-driven schedules.
Don't get me wrong, I eat meat, but I also understand that the grand majority of fellow meat-eaters have never hunted or reared livestock. Instead they are complete soyboys (ironic isn't it) who merely consume the output from the machine. These same beta cucks will open their mouths to screech "but animals eat animals in the wild!" Completely missing how unnatural an industrialized slaughter machine is.
The only reason they are enslaved is that they lack organization and understanding. Had they those two, they could kill us all.
Most middle managers will either not require this, or require it but find ways to themselves avoid being tagged as logging into their home wifi. The prevailing culture around middle-management is one of inefficiency and rule avoidance. Middle managers need to be replaced by AI already.
There are ways to use AirTags that are true stalking methods and these aren't currently mitigated by Apple. If anything this is a false sense of security. Nerfing their product seems more like corporate CYA than concern for public safety.
What do you mean? This is very much true. We are economically compelled to buy food from supermarkets, for instance, because hunting and fishing have become regulated, niche activities. Compared to someone from the 1600s who could scoop a salmon out of the river with a bucket, we are quite oppressed.
Most people lived on the knife's edge of starvation before the application of fossil fuel energy and nitrogen to agriculture in the 20th century. That's why the global population exploded after the introduction of these technologies. Read "Energy and Civilization" by Vaclav Smil. For most of history, it was an open question the crops you grew would even contain more calories than the physical effort it took to grow them. This means you were spending ~90% of your time (or money if you were in a specialized trade) just on getting enough carbs in grain to avoid keeling over. And, your diet was 90% grain with almost no variety.
Were there a lucky few who found an unoccupied niche where there was some surplus for a generation or two? Sure. But pretending like this was commonplace is like pretending that everyone in the 1600's was a nobleman.
> Compared to someone from the 1600s who could eat a gourmet meal prepared by their 10 cooks every night, we are quite oppressed.
and then the population exploded such that it could only be sustained through modern agricultural methods. We are married to the technology more than before
It was interesting to me finding out how many "urban farms" are nestled in our own cityscape, and how many of those "farms" are actually selling their produce, meats, and even livestock.
Until very recently (like 6 decades ago) the area where I live was right up against rural countryside, with sheep grazing, cattle farms, vegetables grown and everything. And those farmers sold out to real-estate developers.
But there are literally homeowners in SFHs with chickens out front and roosters crowing in the morning. And some of my colleagues own chickens and harvest the eggs every day for their own kitchens and families.
But just going through a few urban neighborhoods on Google Maps, it was not long before I found little farms. And these farms sometimes have websites where they advertise that they are selling produce and dairy: raw milk, fresh eggs, fresh fruits & veg, mutton and even live sheep or goats. And they may be doing it on the sly or under the table, and "raw milk" is especially a controversial marketplace right now, but they do it and seem to do alright.
These "urban farms" are often real close to tactical supply shops running out of some guy's garage, and other little "cottage industries" where people who purchased "McMansions" are recouping their investments, basically by skirting the city's zoning laws and tax regulations around businesses.
So yeah, if you've got a brown thumb like me, you can go shop at a farmers market, or you can look up one of these "urban farms" and buy direct, cash in hand.
... provided you own land that the government allows for agricultural use. And most people can't afford to own enough land to be self-sufficient.
So you're not free to grow your own vegetables either; just like fishing, farming is regulated to manage limited resources. Things get ugly fast when you start raising pigs in your city apartment, or start polluting with pesticide runoff, or start diverting your neighbour's water supply...
You can grow some amount of produce, if you have a garden, but a lot of people don't have their own garden, and if they do it's quite small. To be entirely self-sufficient, you need quite a large area of land just to grow enough food for the entire year.
Most people don't have that, and can't afford that, hence why they take the route of earning money some other way, and using the money to buy food made by others, from supermarkets. They can supplement their diet with home-grown fruit and veg, but few can sustain their family on home-grown produce.
Running an update script every day is good. Certbot defaults to running twice a day. Just use something with similar logic, waiting to renew short-lived certificates until halfway through their validity period. That way the actual load is nice and spread out. And you should get that logic by default if you do a normal setup.
If I would use short-lived certs I would make sure to choose an ACME client that has support for ARI (ACME Renewal Information). Then the CA will tell the client when it’s time to renew.
² By the seventh day God had finished the work He had been doing; so on the seventh day He rested from all His work. ³ Then the on-call tech, Lucifer, the Son of Dawn, was awoken at midnight because God did not renew the heavens' and the earths' HTTPS certificate. ⁴ Thusly Lucifer drafted his resignation in a great fury.
I just got home from a stressful day in retail (oh who am I kidding; every day is stress in retail) and this gave me a chuckle I really needed. Thank you.
Standard memory disclosure: the apple when eaten would be freed, but it would still be read, leaking its contents. Luckily its volume was low, so they couldn't exfiltrate all of it. But still, the heavens are closed for maintenance, pending a rewrite in Rust.
The CA/B Forum defines a "short-lived" certificate as 7 days, which has some reduced requirements on revocation that we want. That time, in turn, was chosen based on previous requirements on OCSP responses.
Those are based on a rough idea that responding to any incident (outage, etc) might take a day or two, so (assuming renewal of certificate or OCSP response midway through lifetime) you need at least 2 days for incident response + another day to resign everything, so your lifetime needs to be at least 6 days, and then the requirement is rounded up to another day (to allow the wiggle, as previously mentioned).
Plus, in general, we don't want to align to things like days or weeks or months, or else you can get "resonant frequency" type problems.
We've always struggled with people doing things like renewing on a cronjob at midnight on the 1st monday of the month, which leads to huge traffic surges. I spend more time than I'd like convincing people to update their cronjobs to run at a randomized time.
I have always been a bit puzzled by this. By issuing fixed length certificates you practically guarantee oscillation. If you have a massive traffic spike from, say, a CDN mass reissuing after a data breach - you are guaranteed to have the same spike [160 - $renewal_buffer] hours later.
Fuzzing the lifetime of certificates would smooth out traffic, encourage no hardcoded values, and most importantly statistical analysis from CT logs could add confidence that these validity windows are not carefully selected to further a cryptographic or practical attack.
reply