2FA

I'm no nanoengineer but the equipment used to produce NAND is really expensive and sensitive (nanometer scale after all) so I'm guessing that time frame includes calibration and verification of all the machinery.

I'm no nanoengineer but the equipment used to produce NAND is really expensive and sensitive (nanometer scale after all) so I'm guessing that time frame includes calibration and verification of all the machinery.

I'm no nanoengineer but the equipment used to produce NAND is really expensive and sensitive (nanometer scale after all) so I'm guessing that time frame includes calibration and verification of all the machinery.

I'm no nanoengineer but the equipment used to produce NAND is really expensive and sensitive (nanometer scale after all) so I'm guessing that time frame includes calibration and verification of all the machinery.

I'm no nanoengineer but the equipment used to produce NAND is really expensive and sensitive (nanometer scale after all) so I'm guessing that time frame includes calibration and verification of all the machinery.

I'm no nanoengineer but the equipment used to produce NAND is really expensive and sensitive (nanometer scale after all) so I'm guessing that time frame includes calibration and verification of all the machinery.

I'm no nanoengineer but the equipment used to produce NAND is really expensive and sensitive (nanometer scale after all) so I'm guessing that time frame includes calibration and verification of all the machinery.

I don't think the software supports it yet on the 4, but on previous Pis, you only had to boot from SD the first time and after that, you can use USB or Network booting.

Always take Google's scraped info with a grain of salt, it's not always accurate. Always check the source they link to.

It's port 32400, if that was a mistype.

It's not a JEDEC requirement per se but some manufacturers implement it, Micron I'm pretty sure does.

*clears throat*
 
RISC-V
 

It's not a JEDEC requirement per se but some manufacturers implement it, Micron I'm pretty sure does.

can't you just run rsync -av /old/home /new/home
 
 

1. Remote access can be done through either a VPN server to access your LAN or using something like NextCloud or both. There are other methods as well like SSHfs but I've never used it personally.
 
Points 2 and 3 conflict, JBOD by definition does not provide parity nor redundancy. If a drive fails, you lose all the data on that drive. RAID and certain file systems (such as ZFS) can help to provide redundancy and parity but they aren't backups either, which you should have.
 
FreeNAS or OpenMediaVault are good solutions for a pure NAS system. FreeNAS should ideally have use ECC memory but not technically required, and their 1GB per 1TB of raw storage requirement is only needed if you want to use the deduplication feature, which you shouldn't because it's kind of broken, otherwise you can get away with a bit less RAM.

Pihole doesn't work against ads that are delivered as part of systems that also deliver legitimate content, for example Cloudfront. They use randomized strings in the URL and also deliver regular content using the same method.

Pihole doesn't work against ads that are delivered as part of systems that also deliver legitimate content, for example Cloudfront. They use randomized strings in the URL and also deliver regular content using the same method.

Pihole doesn't work against ads that are delivered as part of systems that also deliver legitimate content, for example Cloudfront. They use randomized strings in the URL and also deliver regular content using the same method.

No, especially if it has internet access.

Samsung uses a queue TRIM implementation in most of their firmware that behaves badly with Linux, and has previously been blacklisted. I can't find the current list at the moment but this was a commit in 2015 about Samsung TRIM issues https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/ata/libata-core.c?id=9a9324d3969678d44b330e1230ad2c8ae67acf81

Ironically enough, I'm running one that is blacklisted at the moment with Linux (840 EVO), it just doesn't support all TRIM functions.

Samsung uses a queue TRIM implementation in most of their firmware that behaves badly with Linux, and has previously been blacklisted. I can't find the current list at the moment but this was a commit in 2015 about Samsung TRIM issues https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/ata/libata-core.c?id=9a9324d3969678d44b330e1230ad2c8ae67acf81

Oneplus certainly sends some information to their servers in China as has been previously documented, which even ignoring Chinese spying shouldn't shock you (read telemetry). Huawei is not only a mobile electronics manufacturer but also a network equipment manufacturer (switches, routers, aps, etc.) so they have a much wider impact and are more well known whereas Oneplus is a rather niche manufacturer. Should also be noted that Oneplus had a revenue of $1.4 billion USD in 2017 vs Huawei's $105 billion in 2018. That alone should tell you the scale of each company and why one is more publicly criticized than the other.

You're being obtuse for the sake of it. 
 
You can look at me all you want in public (IP address). But I do not, have not, and will not, accept a "EULA" (they aren't legally binding) that allows my private data to be sold to the store next door (the website next door). The information is mine and yours, not the companies'. We should maintain full control of our data without having to seclude ourselves as you're suggesting. 

Every event is considered individual until you identify a relationship with other events.
 
Also, that's exactly the butterfly effect. You're treading into philosophy now instead of stats.