trapperkeeper74

It one of those things we don't want to experiment with to find out. Interestingly, the burning of fossil fuels is arguably an uncontrolled climate change experiment that might lead to thermohaline disturbances, an Ice Age and/or hypercanes.

Yup. LBS is useful in detectors and such.

Basically, the US needs a national ID "card" with PKI system... not to rob people of their privacy but to free them from the tyranny of marketplace anarchy which resulted in the absence of global unique person identifier de-facto globbing onto a number meant for pensioner and disabled benefits. Basically, it should be illegal to use SSNs for anything but Social Security. Taxes should have a tax ID for taxes alone. Instead, secure public key systems to authorize or refuse requests with authenication and nonrepudiation, using a public identifier that can be shared widely but isn't also a magic access authorization detail.

As it happens, IIRC, circa 2000, US schools and universities had to change their databases and systems to not use SSN's as student IDs because of identity theft problems extending from this very core problem.

The US through law must deleverage SSNs and make them public-safe, and promote/mandate a real PKI non-profit system for authentication and authorization for the greater good.

If Atom is any benchmark, plugins will be created, abandoned, forked, abandoned and then the API will churn breaking everything every so often because "change is cool." It's the same segment of programmers with 0-6 months of experience whom can't be bothered to delve deeper into computer science, professsional software engineering or static compilation. Instead, just waste everyone's RAM and processor cycles with inefficient interpreted scripts and also bounce from shiny tech to new shiny tech.

LOL. I dropped Atom back to Vim the same reason.. electron apps are just too slow and memory-hogging compared to native apps.

This is a huge security, privacy and battery-drain nightmare.

Unassociated Wi-Fi chips constantly broadcast their MAC addresses allowing customer targeting and broadcast their previously associated SSIDs, allowing tracking of people when combined with SSID location databases like SkyHook.

Unassociated Bluetooth is also a privacy and security attack surface.

Finally, it's going to drain the already undersized iPhone batteries even more by not putting chips into powersave modes.

Apple smh fail, fail and fail... they really jumped the shark on this one. I hope this changes but I'll be skipping iOS updates for now and will skip future iPhones if this doesn't change, in addition to already skipping future MacBook Pros because of their horrendous unrepairability and unupgradability.

Virtue $ignaling.

BTDTBTTS. Way back when in uni, we had to deaign a working CPU with everything at the time but superscalar, MIMD and reservation/retire. Pipelined CPUs can get faster clock rates by splitting up hardware into more (smaller) stages, but at the expense of total latency (due to adding pipeline regisers) AND slower pipeline stalls on branch prediction misses (pipeline has to be emptied of wrong micro-ops). The overall CPU can only be as fast as the slowest stage.

It looks like this Si are the mostly combinational logic for a stage and Pi are the pipeline registers between stages (nearly all signals between stages should be buffered by pipeline regs). IO is omitted but it's the same overall architecture.

    Clk --------+---------------+---... ....
                |               |
                \               \
      +-> S0 --> |P0| --> S1 --> |P1| --> .... --+
      |                                          |
      +------------------------------------------+

Hooray!

In general, dnscrypt can help defend against DNS privacy loss for situations like these.

There is a subtle cargo cult fallacy that occurs in many crypto construction competitions: that resource light (time, RAM & operations) in hw/sw is "good." Certainly, minimum performance is necessary but being too cheap means brute-forcing is also cheaper. I wish resource-adaptive algorithms that require a minimum of RAM and ops in both hw and sw optimized implementations a-la scrypt were the rule, not the exception.

State actors can easily afford ASIC AES and SHA2 brute-force farms, and that's a concern, especially with monocultural recommendations to "always use AES/SHA2." Now that Keccak's been chosen as the basis for SHA3 in-lieu of more hw expensive alternatives like ECHO, the cost of cracking has been reduced for future scenarios. Do we really want to slash the security margin for a modest bump in runtime performance?

Prohibition hasn't ever worked and will never work... it just makes criminals rich. It's an addiction that needs comprehensive, overlapping cessation programs.

If enough people are sleeping rough, Hep A is an issue among others.

It's still FUD.

Apple also doesn't fulfill all of its GPL obligations (eg components used in iOS, example: libstdc++) and their OSS releases lag a month or more behind software releases.

LibreOffice Base?

Churn and reinventing the wheel accomplishes nothing but creating busywork for many hundreds of thousands of users, creates an unnecessary learning curve and wastes time. They should've just fixed/rewrite net-tools for new interfaces and added flags for parsable output.

Breaking changes is very uncool.

It would be difficult to find, outside of a full totalitarian regime, a country that doesn't exploit media, including news, advertising and pop culture, for manufacturing consent customized to monetize and motivate the populace to be compliant, profitable, useful consumers.

The "two-sides" cargo cult is often a false equivocation: like teaching evolution and creationism. There are some obviously wrong opinions that aren't worth legimitizing. That is different than a reporter playing devil's advocate, finding adversarial opinions and asking tough questions. It is especially onerous when one "side" is one of these alt-right or mainstream rags that push talking points agenda instead of honest facts.

And prefer redirection to cat.

    whatever < file.txt 

not

    cat file.txt | whatever

Also, there is no need for - or z on GNU tar in t or x modes:

    tar tf whatever.tgz
    tar tf whatever.tar.bz2
    tar tf whatever.txz
    ...

    tar xf whatever.tar.gz
    tar xf whatever.tar.Z
    ...

all work just fine

Diff eq-like behavior is everywhere: species population, popularity, technology, market saturation, economics, spring rates, etc.

(Malthus was partially ;) mistaken.)

At Stanford, the strongest towers (on the hill) are/were AT&T (via Cingular). There are/were whole buildings with zero Verizon coverage.

Source: an enterprise Cingular sales rep whom later worked for Motion Computing.

There also used to be a spot on I-80 between SF and Sacramento where AT&T phones routinely dropped calls.

IANAL: Claiming active duty when not maybe subject to prosecution under the Stolen Valor Act and/or various types of fraud.

They need to add more Apple-branded app/support in third-party IoT/connected consumer devices beyond HomeKit and charge a subscription for extra features: walled-garden beachheads in other gardens.

Also, Apple needs more third-party integrations like replacing the browser, email and so on.

Finally, there needs to be more ways for third-parties to add jailbroken-like changes to the system in a nuanced, safe, trusted manner.

Untested code.. even if you're writing a kernel, you've got to find a way to mock/stub/double/fake your way into unit testing, smoke testing and integration testing. Cucumber isn't a requirement, but having appropriate layers of assuring production code is correct is fundamental to sustainable software engineering.

There are three really big hardware assurance problems:

0. Trusting any bit of silicon isn't backdoored or buggy.

1. Trusting any opaque binary firmware isn't backdoored or buddy.

2. Having "firewall" level of control of bus device lifecycle not in control of the user action and/or system policies.

We need more peripheral firewalls, external firmware imaging IDS/IPS like this project and depotting open-source chips that can be functionally OCR'ed under xray/microscope.

Exactly. If a corporate-government complex wants to "starve" cryptocurrencies and untracked assets while maximizing financial intelligence gathering for a myriad of purposes, they can eliminate physical currency and make sure the banks are as walled-gardens as possible. Control to track more of what consumers do for the benefit of the elite under false promises like "convenience" and FUD like "black money."

The construction seems bad, but FIPS isn't anywhere close to being as good as NACL, and scrypt isn't the enemy. Bad constructions, lack of nuance and faith in certifications are the enemies.

300 mph tornados tear up everything except some roadways, foundations and deeply-driven steel pilings. 500 mph would just make a messier mess. If that were multiplied over continental size, that would definitely extinct some species.

The content of the landing page (since it appears broken, here's the content from Reader View):

Equifax Announces Cybersecurity Incident Involving Consumer Information

[Equifax CEO statement] https://youtu.be/bh1gzJFVFLc

No Evidence of Unauthorized Access to Core Consumer or Commercial Credit Reporting Databases

Company to Offer Free Identity Theft Protection and Credit File Monitoring to All U.S. Consumers

September 7, 2017 — Equifax Inc. (NYSE: EFX) today announced a cybersecurity incident potentially impacting approximately 143 million U.S. consumers. Criminals exploited a U.S. website application vulnerability to gain access to certain files. Based on the company’s investigation, the unauthorized access occurred from mid-May through July 2017. The company has found no evidence of unauthorized activity on Equifax’s core consumer or commercial credit reporting databases.

The information accessed primarily includes names, Social Security numbers, birth dates, addresses and, in some instances, driver’s license numbers. In addition, credit card numbers for approximately 209,000 U.S. consumers, and certain dispute documents with personal identifying information for approximately 182,000 U.S. consumers, were accessed. As part of its investigation of this application vulnerability, Equifax also identified unauthorized access to limited personal information for certain UK and Canadian residents. Equifax will work with UK and Canadian regulators to determine appropriate next steps. The company has found no evidence that personal information of consumers in any other country has been impacted.

Read More