nickwitha_k (he/him)

  • 23 Posts
  • 3.37K Comments
Joined 2 years ago
cake
Cake day: July 16th, 2023

help-circle




  • Like much of the newer x86 stuff is RISC-like wrappers on CISC instructions under the hood

    I think it’s actually the opposite. The actual execution units tend to be more RISC-like but the “public” interfaces are CISC to allow backwards compatibility. Otherwise, they would have to publish new developer docs for every microcode update or generational change.

    Not necessarily a bad strategy but, definitely results in greater complexity over time to translate between the “external” and “internal” architecture and also results in challenged in really tuning the interfacing between hardware and software because of the abstraction layer.







  • I get it but don’t “get it”. I suppose I tend to think in terms of small groups rather than manipulating crowds of rubes that have been keeping in a state of perpetual outrage through decades of right-wing talk radio and TV, and are so desperate to be told what to do that P. T. Barnham would say “Hey now, that crosses a line.”

    I’d still suggest that it might be less charisma and more an audience so primed that they’re near auto-ignition being subjected to a Hitler-fanboy who picked up a few things from professional wrestling.

    Then again, I also don’t “get” celebrity worship and numerous other NT things.





  • Unironically, depending on how the supply chain is arranged for your industry, it may actually be cheaper to move your manufacturing off shore and eat the tariff once instead of getting nickeled and dimed for every single item you need to assemble on shore.

    And that’s not even accounting for forecasting, which is still necessary in the stupid-frail JIT approach. Noone will want to sign a long-term supply contract when they could get screwed by sudden tarrifs and the JIT people have to rely on luck to avoid subjecting customers to sticker-price whiplash.

    It’s all just so fucking stupid.

    Edit: Not sure what my auto-correct meant there. To be clear I was intending to state that JIT logistics is stupidly frail because it is unable to smooth out uncertainties in supply chains and a single distribution or price swing in a necessary component can result in the material costs of the product going so high that the business either has to sell at unpredictable prices, eat the difference, or set the base price higher and pocket the difference when favorable.




  • I’ve done a lot of SysAdmin and DCOps stuff in the past so, thought I’d give you some plausible suggestions (haven’t dug deep into Lemmy DB stuff and DNS/Federation of the stack, so not sure all is practical).

    Scenario 1 - Preserve and merge when access is restored

    Setup

    • Spin up two VMs/VPS (or one that has enough grunt for two Lemmy servers). Call them robak.slrpnk.net and slrpnk.net and point DNS appropriately.
    • Pull federated content from other instances and place it on robak, set as read-only.
    • Sync important comms to (new) slrpnk.net without content.
    • Allow users to sign up, vetting as possible (all mods). Keep a list of those that are vetted (call it vetted.list). Inform all users that any non-vetted users will have their content dropped when access is restored.

    Merge!

    • Once access is restored, ensure that (old) slrpnk.net is set to read-only.
    • Schedule a maintenance window (announce more time than you are likely to need).
    • During the maintenance window, put (new) slrpnk.net into R/O, or just block external access.
    • Query the db on (old) slrpnk.net for all users.
    • Subtract the vetted users from vetted.list from the list.
    • Drop all records from the resulting list of non-vetted users from (new) slrpnk.net.
    • Insert the records from vetted and new users (those without conflicts) into the DB on (old) slrpnk.net.
    • Validate that everything is working
    • Cut over DNS and spin down the new VMs/VPS.

    Scenario 2 - Server is in DC or Admin able to facilitate access

    • Get a db dump/backup.
    • Spin up temporary slrpnk.net on a VM/VPS.
    • Use backup of temporary server to restore data to original, when possible.