Skip Navigation

Posts
2
Comments
781
Joined
2 yr. ago

  • Ok, I'll start removing the batteries instead and place it where it was then.

  • Overall production != local availability or accessibility

  • I'm confused. Excel is a spreadsheet, that's always in the form of a table.

  • You can't trust Palantir with any agreements, safeguards, or supposedly deidentified or anonymized data. They will use the data anyway, undisclosed. Immoral data is their business. Data association and connection is their business. And they have the scope, prevalence, and collected data for it.

  • Hospitals had Palantir? Wtf

  • "Leaderboard" where rank one scores 0.3% success lol

  • I find it unlikely to be about security. Either it is about control or about money (pressure to induce bribery for lifting), or a combination of both.

  • All it needs is a bribe from Cisco, and it's no problem anymore. Probably.

  • If I were a network packet, I would get very confused by so much routing.

  • If we see a reversal of the policy soon then it was a standard playbook policy announcement to receive corrupt bribery money from some big manufacturers and importers. If we don't, it may very well have been with no takers anyway.

    We've seen it plenty before (within the last year). Like tarrifs, then exclusions, etc.

  • Sure, you can search for alternative sources, hope that the PDF is not just image-scans but indexed and searchable text, and that it has a jump-able table of contents, and that it has not been altered and is up to date. Or you can go through public implementations and try to replicate, infer, and follow implementations or third-party descriptions of the standard. But all of that is error-prone and time and effort investment.

    It shouldn't be like that. A standard should be public so that anyone can implement it, from either side. So anyone can verify and compare against the reference, and call out implementation misalignments.

  • What's this image from?

  • I just want existing standards to be public and accessible, not locked behind 400 600 € ISO. That defeats the whole point of standards.

  • Systemd is more than an init system. Systemd was designed to be different from previous Unix-style single-/narrow-purpose services. Many distros making the switch seems to indicate that such a switch had significant enough upsides or necessities. No?

    I read an article about why Systemd became what it is, and why it makes sense, and that made sense to me. Integration and a fully designed system has advantages over disconnected utilities and systems you have to connect and negotiate, especially on system- and boot-up level concerns.

  • More than hopeful this makes me concerned that change leads to more issues and worsening. That's the expectation they established.

    I followed several of the authors zdnet links. Crazy. Good articles, callouts and documentation.

    The announcement is pretty broad and unconcrete. Some things are listed, and the slow context menu open is one I certainly care about (even when it's not my primary context menu because Double Commander opens the classic one), but everything else is wishy washy and nonesense corporate speak and doesn't include my main smaller issues.

    /edit: oh, and I found the "we heard feedback" (ommission of negative or concern) particularly tone-deaf when they're attemting to tackle criticism. Insane.

  • It was on hold until now to encourage self discovery or sth

    I'm just glad we didn't have to hold the line for a year to read this.

  • Why is it called developer mode if it's supposedly an advanced flow? That has a bad implication.

  • What specifically is a massive win?