• 6 Posts
  • 219 Comments
Joined 2 years ago
cake
Cake day: June 8th, 2023

help-circle


  • Computers have systems (BIOS, EFI, ACPI) that give the people who make the machine responsibility for providing a standard, publicly-defined way for the OS to enumerate the hardware, and to use the hardware in a basic way even if the OS has never heard of it. Linux can get a kernel panic on the screen even if it has no idea what your GPU is, because EFI understands it and Linux understands EFI. It is set up this way partly because there’s a real possibility of hardware being added or removed, partly because people routinely mix and match parts, and partly because IBM mistakenly designed a good system that was easy to work in and not one that kept them in business.

    Phones (and phone-derived systems like the Raspberry Pi and other single-board computers) don’t implement a standard. The hardware and its boot process assumes tight integration between the hardware and the software, usually to the point where the bootloader refuses to load anything not signed by the device manufacturer, unless it is satisfied that it has been given that manufacturer’s permission to be unlocked. (Computer secure boot implementations generally trust, for example, Microsoft, as well as the machine owner, who can load their own keys.)

    Instead of the CPU developers releasing example EFI implementations, they release forks of the Linux kernel that they maintain as long as that chip is the latest chip they sell, and then fork off the mainline kernel again for their next chip. And the device makers ship devices by starting with the chip maker’s kernel, customizing it for the device, giving it a “device tree” that tells it everything that is supposed to be in that particular device, and shipping it. For a few years they port patches from the current kernel onto this forked kernel, and then they stop. With no standard to develop software against, and no documentation for what’s in a device and how to use it like there is for the standard’s interfaces, the only practical way to run software on a device is to start with that patched kernel.

    Mainline Linux refuses to adopt and maintain the chip and device makers’ low-quality, chip-and-board-specific kernel changes (often because they break the kernel for other uses), so you can’t generally use a mainline Linux kernel instead. If you tried to tease out and improve the device-specific patches to the point where mainline Linux would take them, the device would be hopelessly outdated by the time you were done and you would have dozens of job offers to occupy your time as a highly skilled embedded Linux developer. The work is not practical given the tiny number of people who would benefit from it for a particular device, and how little it pays off compared to just buying a new device with a more up to date forked kernel available.

    “Maintaining” a device for LineageOS or other open software eventually collapses under the weight of mainline Linux’s changes and the necessary chip and device maker patches no longer being practically reconcileable.




  • I think to test it you’d need to do some kind of comprehensive analysis, something like a big spreadsheet of a convincingly unbiased sampling of states (or states-at-points-in-time), evaluated for libertarianism-vs-authoritarianism. But you’d need to have a way to distinguish whether differences between states were caused by inherent per-state effects (or by more mechanistic runs-with-the-state traits, like “having a written constitution” or “being a monarchy”), or by “circumstances”. So you’d need a way to measure plausibly-causitive circumstances and then see how much of the variance they explained.

    It’d be a big project and hard to do in a controlled way across a large enough sample, but if you sent enough history grad students out to rate things like “worker organization” in 1925 Germany and “protections for human rights in constitutional law” in 1975 New Zealand on 5-point scales, you might be able to get a data set that could answer this question.







  • It works on some devices; they do sign the builds as far as I can tell. But the bootloader itself needs to be convinceable to trust the LOS signatures, and needs to understand the secure boot implementation used in the Android that the current LOS is built from (since Android has re-done it all a few times). Nobody knows anything about bootloaders to figure out which of them can do this or how they would be induced to do it.




  • You’re I guess looking at a feed of everything there is with no anchor to the correct side of politics? Try that with ActivityPub and just ingest the entire ecosystem with no home instance or blocklist and you’ll get lots of this.

    But I think you are right that the Bluesky PDS will not refuse to host you for saying things along the lines of “The US should continue to sell all kinds of weapons to Israel”, whereas a lot of Mastodon instances might be expected to kick you off for expressing this stubbornly common opinion.

    But I’m not sure it’s quite fair to expect a public service to share exactly the correct Overton window that one has oneself. That sort of enforcement on Bluesky is meant to be at the level of the custom moderation service/labeler, not at the data storage layer, since users more or less are meant to control that themselves.

    And if you pick a good labeler it will enforce that only the correct people are allowed in your view.


  • planish@sh.itjust.workstoAsklemmy@lemmy.mlWhy is NPD so stigmatized?
    link
    fedilink
    arrow-up
    10
    arrow-down
    1
    ·
    7 months ago

    I dunno dude, it’s super weird. Sarah Z has a video about this, IIRC the explanation there was something like, people have latched on to “narcissist” as a thing one doesn’t need to worry that one is oneself but can be tacked on to anybody one dislikes. Also there are demons involved for some reason.

    (Having killed ShortFatOtaku’s Twitter guy, and taken all his stuff, how would “the narcissist” go about extracting the validation??? Sounds made up.)

    (Also it’s always “the narcissist” like there’s just one extremely busy person out there.)

    NPD might make people struggle with empathy, but nobody, who is out there thinking everyone they meet could be “the narcissist” who is out to get them and not worthy of respect or consideration, is themselves killing it on the empathy front.


  • Usually the routers you install OpenWRT on are really a CPU with one port to a VLAN-capable switch, and the port labeled WAN on the device is just VLAN’d separately by default. One cool thing OpenWRT lets you do on “normal” hardware is change the VLAN settings on the switch ports which are not accessible under stock firmware.

    But if they are shipping “just” the router piece and making people go get their own VLAN-capable switch, I’m not sure what hardware exactly they expect people to use? And I’m not sure what being connected to the switch over one real 2.5G cable is going to do to LAN/WAN throughput, vs. how a “normal” router ties the CPU into the switch through means not known to mortal minds. Maybe it is just as good, maybe it is a huge bottleneck. It is definitely going to add cost over the $89 sticker price.

    But if most people are just going to run fiber modem straight to WiFi, maybe this is the right config actually?



  • You don’t necessarily have to tell all prospective employers about all experience. If you think your resume is getting bounced from some kinds of openings because they think it is odd they you have this degree, don’t list the degree when you apply to those sorts of positions. Don’t talk about having the degree. If asked point blank if you have a degree, say something about your personal philosophy on why degrees aren’t important, or how your life’s goal would be to get a Ph.D. in art history or some other discrete and personable non-answer.