What surprises me the most about these decompilation projects is that they post the whole decompiled code instead of just a list of directives to feed into a given (hopefully open source) decompiler.
I used to be somewhat active on a ROM hacking message board, and there were rules about how users could share their modifications. Users had to share a patch. Uploading or linking to prepatched or original binaries was prohibited, and moderators would routinely intervene and remove them. Having been exposed to such measures to avoid action from copyright holders in the past, I just don't understand why it is so popular to just post the code openly.
Perhaps there is a concern that the croudfunds could be considered a third party payment under subsection 4.
The only explanation that I can think of for the subsection was to prevent a defendant from claiming that a source like the decedent's own life insurance should be counted against the restitution, but that seems a bit far fetched.
When I first learned about how privileged ports worked, I thought a better system would be to have per port security that resembles filesystem security. That is, each port would have an owner that can decide which users may use the port. A program could run before starting network services that would load the security information into the kernel, and equivalents to chown and chmod would be available to update the persistence file and the kernel in tandem (or separately).
Ground source heat pump systems can handle colder climates well. Underground, the temperature is rather stable through the year. This is especially true when the loops are installed vertically.
I wonder if there have been any efforts to sabotage crowdsourced AI training and content moderation by signing up on crowdworking platforms and intentionally providing false responses. A large and tech savvy enough sabotage ring could use a browser extension or the like to keep their responses straight and increase the odds of their fake answers being accepted.
In February, Arkansas eased restrictions on municipal broadband. I had a quick look at the text of the bill, and it appears that municipalities must get grant funding as opposed to issuing bonds or using general funds.
A somewhat related development in Arkansas is electric co-ops, which were started to provide electric service to rural areas, starting telecommunications subsidiaries with rather firm plans to build FTTH over their entire service area. Several of these have been started in the last few years. Arkansas could see some remote rural areas without paved roads or public water get symmetrical gigabit internet before many urban centers.
That was true of the DSP-1, but not true of the SuperFX or SA1.
The DSP-1 was a preprogrammed microcontroller that preformed certain calculations that would have been inefficient to preform on the SNES CPU. The inputs were written to a memory mapped location, and the outputs read back. An interposed copier could simply redirect these reads and writes.
The SuperFX and SA1 used the cartridge's ROM and RAM for program and data, and therefore these enhancement chips are placed between the SNES bus and the cartridge memory. The cartridge memory is unavailable to the SNES bus while the enhancement chip is executing, as in the SuperFX, or the the enhancement chip enters wait states while the CPU is accessing the cartridge memory, as in the SA1.
Is anyone else having the video stop with a buffering spinner and little or no network activity a few seconds after starting the stream?
EDIT: I ended up working around it by switching between the two lowest quality settings each time the stream hung. Disabling Adblock Plus on the page and adding Flashblock exceptions had no effect.
This reminded me of a toy I had as a kid: the Tomy Tutor Play Computer. The screen was a lenticular lens over a paper scroll, and pressing the space bar caused the lens to move vertically.
My parents bought a second hand Tandy 1000TX in the early 90s, largely for my use. I remember being excited playing with the Deskmate music software, but that did not last long. After about two days, the Deskmate disk became corrupted, and I was never able to get the disk working again.
The PC speaker does not have much of a DAC. Before the common use of ASIC chipsets, the PC speaker was connected to one of the channels of a clock divider chip. The other channel was used to drive the timer IRQ.
When a program wanted to produce a tone, the program took the input frequency of the clock divider divided by the desired frequency and programmed it into the clock divider. To control the duration of the tone, a DOS or BIOS call was available delay the program or the program could hook the timer interrupt vector. The program would then turn the speaker off or start the next tone.
Programs could also turn the output bit on and off manually. Some programs could turn the bit on and off rapidly to play arbitrary sounds. There was even a Windows driver to play sound through the PC speaker, but it disabled interrupts, causing the clock, keyboard, mouse, and network to stop while the sound was playing.
I used to be somewhat active on a ROM hacking message board, and there were rules about how users could share their modifications. Users had to share a patch. Uploading or linking to prepatched or original binaries was prohibited, and moderators would routinely intervene and remove them. Having been exposed to such measures to avoid action from copyright holders in the past, I just don't understand why it is so popular to just post the code openly.