With the ESA supplying the spacecraft, most of the software is likely to be competently written and/or open-source. This will prove to the Martians that there is indeed intelligent life on Earth.

It's a good question and one I'm working on trying to get an answer to. By giving AI hard, complex engineering problems, and then getting engineers to look at the output to determine if that output is meaningful or just expensive gibberish.

By doing this, I'm trying to feel around the edges of what AI could reasonably be used for. The trivial engineering problems usually given to it are problems that can usually be solved by people in a similar length of time. I believe the typical savings from AI use are in the order of 15% or less, which is great if you're a gecko involved in car insurance, but not so good if you're a business.

If the really hard problems aren't solvable by AI at all (it's all just gibberish) then you can never improve on that figure. It's as good as it is going to get.

I've open sourced what AIs have come up with so far, if you want to take a look. Because that is what is going to tell you if good can come out of AI or not.

I would think it goes further. If the company has already failed (ie: no longer exists) then the action is not taken by the company but a former employee of that company (even if said former employee was the CEO). Former employees are not granted special authority over PII or over company-owned information.

Irrelevant. PII protections are not subject to company discresion.

The conversations are not private, but PII laws nonetheless still apply. Anything in the messages that violates PII privacy laws is forbidden regardless of company policy. Policy cannot overrule the law.

Now, in the US, where privacy is a fiction and where double-dealing is not only perfectly acceptable but a part of workplace culture, that isn't too much of an issue. The laws exist on paper but have no real existence in practice.

However, business these days is international and American corps tend to forget that. Any conversation involving European computers (even if all employers and employees are in the US) falls under the GDPR and is under the aspices of the European courts and the ECHR, not the US legal system. And cloud servers are often in Ireland. Guess what. That means any conversation that takes place physically on those computers in Ireland plays by European rules, even if the virtual conversation was in the US.

This was settled by the courts a LONG time ago. If you carry out unlawful activities on a computer in a foreign country, you are subject to the laws of that country.

It has *much* more to do with the memory card's erase block size.

NTFS wants to use a 512 BYTE or 1kbyte allocation unit size. (Dont believe me? Right click your system volume, and choose properties. See what your allocation unit size is.)

This size was selected because it is 1:1 the sector size of original winchester style hard disk drives, which makes those sizes the most efficient to transfer to or from the disk controller.

Modern drives tend to favor 4kbyte sized sectors, but still emulate 512 BYTE ones.

FAT had cluster (allocation unit) sizes quite a bit larger than this. Usually between 4k and 16k, but 32k and 64k clusters are supported.

For early flash memory cards, 32k and 64k cluster sizes were 1:1 what the eraseblock sizes of the flash array were, meaning having the filesystem use that size gave the best possible efficiency with the device controller.

SDHC and SDXC devices though, have erase block sizes that (cough), 'greatly exceed' (cough) what FAT32 can support.

ExFAT however, happily lets you use cluster sizes in the MULTIPLE MEGABYTES size range, allowing the flash makers to still have 1:1 cluster->erase unit parity, and maximized device IO efficiency.

Your camera formats that card as ExFAT because that's what the SDCard Assn demands.

The SDCard Assn demands it, so that they can reliably claim the write speeds written on the top of the card.

NTFS will annihilate flash cards with write amplification, and have piss-poor io performance writing to them.

Yes, and no.

For PCs of the late 90s and early to mid 00s, yes. 'To promote NTFS.'

For Memory cards?

No.

That's much more closely tied to 'convenience of the memory card consortium'. Specifically, 'It's VERY convenient for the filesystem to have an allocation unit size that is a whole divisible factor of the erase unit size, with 1:1 being *oh so VERY convenient*!'

For devices up to about 32gb in size, this 'convenient coincidence!' Held. Larger devices however, have erase unit sizes far too large for FAT32 to be 'convenient' for.

This is, (among other reasons), my microsoft created ExFAT. It's 'FAT', with 'Absurdly large cluster sizes!'

Exactly what the memory card consortium THIRSTED for.

It also let mictosoft get a shiny new exclusive patent that *everyone* would need to get a license for, which is what *microsoft* THIRSTED for.

This marriage of convenience saw fat32 not having 'official' large volume support for ages.

I would not at all be surprised if this recent change coincides with ExFAT patent expiration.

News At Elevenses.

To me the hoops that smoothbrains will jump through to avoid IPv6 and stay on legacy IPv4, especially when hosting, is pathetic. NAT, port forwarding, tunnels, blah blah blah blah.

I have something like ~1.2 trillion times the number of routable addresses that the entire IPv4 space has. Not all are reachable, of course, just the services that need incoming access and they're each on their own isolated DMZ.

It's possible that cetaceans have a true language. They certainly have something that seems to function the same as a "hello, I am (name)", where the name part differs between all cetaceans but the surrounding clicks are identical. The response clicks also include that same phrase which researchers think serves the purpose of a name.

But we've done structural analysis to death and, yes, all the results are interesting (it seems to have high information content, in the Shannon sense, seems to have some sort of structure, and seems to have intriguing early-language features), but so does the Voynich Manuscript and there's a 99.9% chance that the Voynich Manuscript is a fraud with absolutely no meaning whatsoever. Structure only tells you if something is worth a closer look and we have known for a long time that cetacean clicks were worth a closer look. Further structural work won't tell us anything we don't already know.

What we need is to have a long-term recording of activities and clicks/whistles, where the sounds are recorded from many different directions (because they can be highly directional) and where the recording positively identifies the source of each sound, what that source was doing at the time (plus what they'd been doing immediately prior and what they do next), along with what they're focused on and where the sounds were directed (if they were). This sort of analysis is where any new information can be found.

But we also need to look at lessons learned in primate research, linguistics, sociology and anthropology, to understand what ISN'T going to work, in terms of approaches. In all three cases, we've learned that you learn best immersively, not from a distance. If an approach has failed in EVERY OTHER SOCIAL SCIENCE, then assuming it is going to work in cetacean research is stupid. It might be the correct way to go, but assuming it is is the bit that is stupid. If things fail repeatedly, regardless of where they are applied, then there's a decent chance it is necessary to ask that maybe the stuff that keeps failing is defective.

Forgot to add: if you enable IPv6, be sure to use the browser extension IPvFoo. It shows a small 4 or 6 in your URI bar to let you know what protocol you're connecting to. Once enabled, you'll see just how much stuff out there actually is IPv6.

Started the move about 18 months ago when I decided to get off my lazy ass. My ISP gives out a /56 prefix, so that lets me run 256 /64 subnets/VLANs in the house, currently there are ~10 in use. Everything get a GUA through SLAAC and I use RAs (Router Advertisements) to give ULAs to everything. Any external facing services get their own VLAN and /64 for the system(s) as needed. Firewall blocks all incoming as they usually do by default and I punch a hole for the external-facing systems. They can't reach back into the network, they only answer the phone. All the systems update DNS dynamically if the prefix or full address ever change.

I have an SSH bastion set up. In all this time there has not been a single SSH attempt from the internet. On IPv4 it was constant background noice.
For those legacy IPv4-only systems on the internet, I set up NAT64. I have an IoT VLAN and IoT 2.4 GHz wireless network that are only IPv4 because a lot of IoT network stacks are junk.

I'm still farting around with it, but man oh man, there's no way I'd go back to IPv4. It was one of the best moves I've done in ages.

Can't wait until I can smell the drauger of Skyrim.

Security isn't convenient.

Security isn't easy, but it isn't hard either.

Assume you're' a target (because you are) and make it so that you're hardened. Don't be the easy target. Criminals are lazy.

Instead of fearing AI, use it to secure software and make it better.

We have nothing to fear but fear itself.