Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)W
Posts
6
Comments
110
Joined
3 yr. ago

I once met a person that never drank water, only soft drinks. It's not the unhealthiness of this that disturbed me, but the fact they did it without the requisite paperwork.

Unlike those disorganised people I have a formal waiver. I primarily drink steam and crushed glaciers.

  • I wouldn't attack via USB, that path has already been too well thought out. I'd go for an interface with some sort of way to get DMA, such as:

    • PCIE slots including M.2 and external thunderbolt. Some systems might support hotplug and there will surely be some autoloading device drivers that can be abused for DMA (such as a PCIE firewire card?)
    • Laptop docking connectors (I can't find a public pinout for the one on my Thinkpad, but I assume it'll have something vulnerable/trusted like PCIE)
    • Firewire (if you're lucky, way too old to be found now)
    • If you have enough funding: possibly even ones no-one has thought about like displayport + GPU + driver stack. I believe there have been some ethernet interface vulnerabilities previously (or were those just crash/DOS bugs?)
  • I recommend using a different set of flags so you can avoid the buffering problem @thenumbersmason@yiffit.net mentions.

    This next example prevents all of your ram getting uselessly filled up during the wipe (which causes other programs to run slower whenever they need more mem, I notice my web browser lags as a result), allows the progress to actually be accurate (disk write speed instead of RAM write speed) and prevents the horrible hang at the end.

    dd if=/dev/urandom of=/dev/somedisk status=progress oflag=sync bs=128M

    "oflag" means output flag (to do with of=/dev/somedisk). "sync" means sync after every block. I've chosen 128M blocks as an arbitrary number, below a certain amount it gets slower (and potentially causes more write cycles on the individual flash cells) but 128MB should be massively more than that and perfectly safe. Bigger numbers will hog more ram to no advantage (and may return the problems we're trying to avoid).

    If it's an SSD then I issue TRIM commands after this ("blkdiscard" command), this makes the drive look like zeroes without actually having to write the whole drive again with another dd command.

  • Why did the CT fail? Is it only 2WD? Bad power distribution algorithm to wheels? Stranded on belly (low clearance)?

    EDIT: Yes possibly bad power distribution, but I don't necessarily trust the source.

    He said on Instagram that the Tesla didn't have locking differentials — a mechanism that can help improve traction on difficult terrain— "due to software issues." He also said the tires had not been "aired down" to improve traction.

  • No. Modern FPGAs do not use any UV light or have any windows. For storage they use flash memory (same as what's used in MicroSD cards, USB sticks and SSDs). Some (most?) require you to provide this yourself externally.

    Old EPROM (not EEPROM) storage had windows and needed UV to erase, but that's decades old. I'm not sure if FPGA was common nomenclature back then (PAL/GAL/CPLD were probably the market).

  • Are FPGAs particularly suited to solving PDEs? I just did a search and there seem to be some papers discussing implementing various PDE solving algorithms on FPGAs, but I'm not sure if it's a task uniquely suited to them.

  • https://github.com/maltejur/discord-screenaudio

    A custom discord client that supports streaming with audio on Linux

    Jaysus, I wish this were a world where stuff like that wasn't necessary.

    Uneducated question: what's the benefit of a dedicated client over running it in a normal browser?

  • I've been using PipeWire this year on my Void Linux laptop & desktop. It's been mostly OK but has a few problems. For years I have been using plain ALSA (with no custom configuration) because pulseaudio causes me regular issues across multiple machines (mostly silently failing).

    Pros:

    • I don't have to use Chromium for my mic to work on online video conf (WTF Firefox)
    • "EasyEffects" lets me quickly fix crappy youtube audio (bad gain normalisation, way too much sibilance) with a minimum of effort.

    Cons:

    • Sometimes breaks all audio until I manually restart it (hey, just like pulseaudio. This problem never happens when using ALSA straight)
    • First time setup is complicated, involving environment variables, dbus user session buses and multiple daemons (running just pipewire isn't enough). Why can't it handle this all itself? Surely it should notice if these things are missing and just fix it itself? Compare this to straight ALSA where you (1) do nothing and then (2) everything works (except Firefox mic support)
    • I can't have multiple audio outputs all unmuted at the same time. Eg my headphone output and my rear speaker output. If I override this (using alsamixer) then it gets forgotten next boot anyway, it seems to be out of scope of PipeWire's understanding.
  • Can you describe the issue? I don't use Discord (and I presume the problem might depend on what browser you use).

  • Finally did this a week or so back, I had one of the original accounts (username login, not email). Made me feel like shit and manipulated, all to make Microsoft happier.