I use them for a bit of coding leverage, and they require a fair bit of... not hand holding, but explicitness, maybe. Otherwise they wander down the path of statistical averageness, and the average code they saw during training was shit.
So they'll happily serve up a pile of inefficient dogshit, complete with working tests and docs and all of that. And then they'll happily refactor it at your suggestion to slowly turn it into something that's resource friendly and generally secure and generally expandable.
But there's no way for them to do that by themselves if you don't have the basic domain knowledge to guide them in the right direction. You'll just get average code, and once you've been in the game for a few decades, you realise that nice, efficient, quality code is the rarity, not the norm.
xml is better than markdown, you will not change my mind
Markdown is for humans who are writing their prose on the fly and don't want to be bothered with the cognitive load associated with the extra verbiage and rulesets of XML.
XML is for computers which are great with verbiage and rulesets.
It's perfectly fine to have a converter between the two to bridge the gap.
There was a good guide by Linuxbabe on building an email server from scratch with all the bits and pieces and antispam/email verification stuff you need to send mail to the big players, I used it a few years ago to do my server.
Here's the collection of various guides for various ways to do it:
Yeah you also need a vps. Home addresses are pretty much all marked as spam generators these days, and most ISPs proactively block all the common inbound ports for mail servers.
Remember kids, never update software when the change log just says, "bug fixes and performance improvements 😎👍🎉"
Although Meta has their own internal update system that invisibly runs outside the normal channels, because fuck those people who disable auto update on their devices, right?
Yeah, probably won't even dismantle it, just bulldoze this 10 billion dollars into a pit and bury the lot. Then go spend another 10 billion on a shiny new tent+compute
If you're not creating more than 800GB a day of new data you can just let it run with a faster drive as a buffer in front of it.
Or get 10 of them and run them in parallel. Maybe get 11 and throw in a bit of parity, just in case bitrot surfaces after the first 1000 years or something.
It's often not possible on other operating systems. Especially the consumer versions of a certain operating system starting with "W", that system will refuse to have duplicate IPs.
But essentially it's always been possible (but, probably not preferred these days) to have redundant routes/paths on Unix systems. The way you have it now is more of a side effect of being able to do more complex network setups, like using different interfaces to talk to different subnets, or using a slow link as a backup to a fast link.
With your current setup you should get a slow failover ability, for example if you ping some other device and then unplug your Ethernet cable, you'll have a bit of a pause in replies and then they will start again as the stack switches to the other link.
I don't get it? The water doesn't disappear it just goes back into the air again as it evaporates
Water in the air is useless. Water on the ground, in storage, is useful. That's the hard part, it doesn't fall out of the sky on demand.
If the government is running out of water then they should build more desalination plants, in terms of energy
The "government" isn't the one running out of water. It's the population, and desal plants a) aren't cheap b) use more power than what the bare minimum of renewable energy a data center install will provide after it's own usage and c) has environmental issues as well with excess salinity getting put back in the oceans, and - oh yeah - you have to put it next to the ocean.
If companies want to build datacenters, they need to provide cooling methods that don't use prodigious amounts of water, or they can fuck off.
Those alternative methods are entirely possible, it's just that they're not the cheapest option available, so of course nobody wants to do it .
The "metric 600" on your Wi-Fi adapter indicates to the system that it is a higher cost route than your Ethernet one. So the IP stack will prefer sending packets out via the Ethernet port.
Local devices who haven't heard from you lately will send to whatever device gives them a response to their ARP ("who has IP address X?") request first, and seeing as Ethernet is lower latency than WiFi, they will mostly use your Ethernet adapter as their target when sending data to you.
Devices that have received data from you already will have the MAC address of your Ethernet adapter in their ARP table, so they'll just send packets to that without bothering to issue an ARP request.
Devices off your subnet talk to your router, so they don't care about your MAC address, they'll just use IP to talk to your router, who will then do the ARP request and hand the packets on to your computer via whatever interface answers first.
Orrrr - and hear me out - maybe that rag-tag collection of state and federal governments you've got going on over there in the US should have a way of online filing that's free?
You know, like how most civilised countries have been doing for the last decade or so.
Yes, they artificially limit the reach of your posts, and then you pay them to get more exposure. You can also pay to have your posts more visible to particular demographics.
And of course that payment is on a sliding scale, and no amount of money is enough to reach all of your target audience, and it's also for a limited time window.
You know what?
I'd love to hear a little "toot-toot!" and have a little train pull up outside my window, with my parcel on a carriage behind it.