Trixter

I co-founded MobyGames with one of my oldest friends. About a decade later, it weighed very heavily in my favor getting a DevOps position at a quant trading firm, as they were looking for people with initiative, unconventional thinking and troubleshooting skills, and a willingness to solve problems.

A more complete chess that fits in a boot sector is Toledo Atomchess: https://nanochess.org/chess6.html

This is missing the broad concern with hallucination: You are putting your trust in something that delivers all results confidently, even if they were predicted incorrectly. Your counter-argument is lack of trust in other sources (podcasts, the education system), however humans, when they don't know something, generally say they don't know something, whereas LLMs will confidently output incorrect information. Knowing nothing about a certain subject, and (for the sake of argument) lacking research access, I would much rather trust a podcast specializing in a certain area than asking a LLM.

Put more simply: I would rather have no information than incorrect information.

I work in a field of tech history that is under-represented on wikipedia, but represented well in other areas on the internet and the web. It is incredibly easy to get chatGPT to hallucinate information and give incorrect answers when asking very basic questions about this field, whereas this field is talked about and covered quite accurately from the early days of usenet all the way up to modern social media. Until the quality of training data can be improved, I can never use chatgpt for anything relating to this field, as I cannot trust its output.

The original programmer specified "peanut butter" in the original docs, but being the author of a format does not make you a linguist. If each component of Graphics Interchange Format is pronounced properly, it is hard-g gif, and not the peanut butter.

That's missing some of the bigger picture. One of the reasons streaming 4k content is at a lower bitrate is because it has to deal with network hiccups and fit inside the buffer of most playback devices. A computer or phone has plenty of room, but streaming 4K content to a TV or chromecast/roku/firestick/etc. does not. Faster bandwidth means keeping the bucket full more reliably.

In the mid-90s, when CPU heatsinks didn't need to be screwed in, thieves discovered that the new ZIF/zero-insertion-force sockets also make good zero-removal-force sockets.

OP has also told you in these threads that their business pivoted 2 months ago and no longer has adult content, so it is a valid business, yet was still banned.

As previously suggested, w3fdif has mostly been supplanted by bwdif. w3fdif can produce shimmering, whereas yadif does not, which is why bwdif operates like yadif but uses the better field matching of w3fdif.

In high school in 1988, a friend and I discovered a vulnerability in the netware deployment of 30 IBM PS/2 Model 30-286s in our brand new computer lab that allowed us to insert programs into the autoexec netboot sequence. Prior to that, we'd been hacking on the (brand new at the time) VGA registers and figured out how to switch from 80x25 text mode to 320x200 256-color graphics mode with no flicker or glitches, as both modes have a refresh rate of 70Hz. So he created a TSR that preloaded a digitized picture of a clown face (a popular upload on BBSes at the time) into A000:0000, and after about 4 minutes, it would display the clown face for a few frames and then immediately switch back to whatever the user was working on. We gave ourselves away because we couldn't stop laughing in the corner of the room watching all the students get very confused/horrified looks. One bonus was the comic timing of a student calling the instructor over, having him stare at the screen for 3+ minutes, turn away, then have the clown face flash when he wasn't looking.

My friend's name was Brian, one of the smartest people I've had the privilege of knowing. Ten years later, we created mobygames.com.

codec is coder/decoder. Not sure where you're getting your other definition. "codec"s are required to both create, and play back, a file with a certain compression algorithm.

I co-founded MobyGames: https://www.mobygames.com/

While the site has had its ups and downs, and changes of ownership, it is usually the first validating reference for any computer game entry on wikipedia (which it pre-dates by nearly two years).

I never had a problem playing it on my 386-40 with ISA VGA... I just hit F5 to go into low-res mode. Worked great.

This is a class of "sprite" generators, which I find fascinating. This one in particular seems very good, although I wonder how much of that is our brains* filling in context.

*I am, evidently, a mushroom cloud

Even HEVC works depending on the client support; for example, I stream h.265/HEVC to my 4K TV and it decodes it just fine. (Which makes me wonder what formats the OP has things stored in that plex has to transcode, or what client device they're using)

Since his last comment is still visible, it's the comment he left afterwards that may have actually started the ban (and was removed). So this could be disingenuous.

It required a 386sx or better with 4MB of RAM, and EGA or better graphics card.

This is quite reasonable for 1992, and the extra ram was likely needed only for the graphics. DESQView itself could run on an 8088 system and didn't even require EMS (although if you did have an EMS board, and configured the system so that the EMS board backfilled the latter 512K, it could multitask much larger programs at the same time as that enabled it to swap entire programs in/out of lower address space instantly).

I've been a low-level 8088 coding hobbyist for many years, and DESQView is still incredibly impressive to me, especially since I know what it has to do under the hood to work and be stable.

> At that time, printers already printed yellow dots with the serial ID.

No schools in 1987 had color laser printers with this technology (and I doubt many businesses did either). Any students trying to do something fishy would have had to make do with, at best, 24-pin dot matrix printers with color ribbons.

Before you start rolling this into a video codec, please consult the sources of UT Codec, which has been state of the art in this space for many years. Or, at least, use UT Codec as a direct basis for comparison, to see if you are beating it in terms of compression/decompression speed.

Modern lossless video codecs don't care that much about saving space, since you're burning gigabytes per minute anyway; the key is that the compression and decompression are as transparent as possible, to reduce the bandwidth to/from the storage medium. A good lossless codec can be used to scrub through and edit on a video editor's timeline, so decomp performance is what's most important.

Also, any such lossless video codec is going to need more than 8 bits per component; most real-world footage coming off of phones and cameras is 10-bit Rec.2020. If it is too difficult to position QOI for real-world sources, you can certainly keep it 8-bit and market it as an animation codec or similar; just keep it in mind.

RLE on runs of deltas is in very many compression schemes; it's a common technique (probably so common that many authors don't deem it worth mentioning). Lossless video codecs in particular (huffyuv, lagarith, utcodec, etc.) have had this going back 20 years at least.

> liblz4 probably benefits from decades of tweaking & tuning to get there

Decade, singular. LZ4 was proper around 2011. But the real reason it's faster is because its not doing nearly as much work as QOI. LZ4 is just about as asymmetric as you can get.

I'm active in the vintage personal computing space, and I find it funny when this topic crops up every decade or so under a different name. In the 1980s, there was a entire software category of "personal knowledge management systems" where each product claimed it had the best system. "Second brain" is no different; it's a group of concepts that may or may not work for you, but as these comments show, they certainly don't work for everyone.

For those who wish to experiment, this method has existed for Photoshop for a long time as a plugin: http://www.descreen.net/eng/soft/descreen/descreen.htm

I can't have any music playing when programming, because my brain focuses on the music and I get nothing done. My wife is ADHD, and she must have music (and possibly something else) playing, or else she can't get any work done. I've always wondered if people who need music to work are ADHD, based on my limited sample size (no pun intended).

Yes, but you were likely paid more than $100 for your time to prepare said documents and have them ready.

> This is censorship. It's why I'm posting anonymously for the first time in a long time.

I think you're confusing censorship with accountability.

I don't see the point of this project. It essentially turns the IBM PC into an embedded system where the only program you can run is the one you burn into the ROM. There is little, if any, advantage to avoiding the use of interrupts. While using unused MDA memory as general purpose memory is cute, it doesn't offer any advantage since you can't reasonably disable DRAM refreshes on the PC (and still get any usable work done), so you might as well use RAM you know will be present on all PCs.

The entire point of the BIOS is so that programs could use BIOS calls and work on any PC or clone without needing to worry about the underlying hardware. Such programs still work today (if you can find a way to boot/run them) which is fairly astonishing 40 years later. The project states "The purpose of this project is to explore controlling the IBM PC hardware in non-standard ways." Okay, well, that's cute, but unless there's an advantage, why bother.

If you're going to do that, you might as well make a demoscene demo...

The short answer: The live broadcast switching/transport industry has been slower to adapt to 4K HDR than other industries, primarily because there is no live broadcast (ie. cable, satellite, over-the-air) support for 4K or HDR.

YouTubers can do 4K because modern desktops (and some laptops) have h.265 decoding/encoding acceleration, and they're typically only dealing with 2 content streams on a single timeline. An NFL broadcast is a living nightmare compared to that.

Vintage Computing: http://www.vcfed.org/forum/forum.php

Very pure community around all things vintage computing; has stayed mostly the same for 12 years (and still very helpful).

LPC (think Speak'n'spell, PCjr speech adapter, etc.) and variants is really the only way to achieve this. A 1.44MB floppy has 1,457,664 bytes available after formatting. LPC at 2400 bits per second means you can store 80 minutes of speech on a 1.44MB floppy.

A big flaw in the OP's testing is that he converted the audio to 8-bit PCM before feeding it to the encoders. That added 48dB of high-frequency noise and distortion for absolutely no reason. He might have found his sibilants ("s" sounds) sounding better had he not done that.

Besides, I don't think my interrupt handler and API would be of that much interest (oOoooh, sexy, an API!)