dn3500

Standard Ebooks does a nice job of typesetting and proofreading many of the Project Gutenberg books, including this one.

https://standardebooks.org/ebooks/jack-black/you-cant-win

I bought a Tektronix 4014 in 1991 and had it until 2016. During that time it never required any repairs or calibration. Built like a tank. The guy I sold it to had to replace capacitors in the power supply, and still uses it today.

I live in the tropics and there is plenty of sunshine here. So my skin doctor told me to avoid the sun at all costs, always wear suncreen and a hat, don't go out in the daytime. A few years of that and now I have a vitamin D deficiency.

Not only that, it's all jpeg images. Of email messages. I wonder if they printed these out from Lotus Notes on a dot-matrix printer then screenshotted them on their camera phones.

There are various efforts (outside the government) to convert these to pdf and ocr them. I think Internet Archive has a torrent.

An entire 1000 foot reel of 35 mm film only has about 15,000 frames on it, so one part in 30,000 would be good enough. When I worked in TV none of the sound equipment had ovens for their crystals.

We did have a sync generator with a crystal oven. I forget who made it. The sync generator has multiple outputs, the most important one being the color subcarrier, which is 3.579545 MHz for US NTSC (I still remember that number). It also puts out vertical and horizontal sweep signals. The stable timebase allowed us to free run for a day in case we lost the network signal for some reason. The network (NBC in our case) had a cesium clock in New York that they calibrated against WWV for time of day. We locked our clock to their signal, and all our equipment to our clock.

You might consider joining the Citizen Weather Observer Program. It's a great way to share your data with other station owners.

http://www.wxqa.com/

I had a station for a few years. The receiver had a usb interface so no software radio required. I used weewx to import the data. I even had a water temperature sensor off the end of my dock so I could see if the lake was warm enough to swim in.

I had a TV once, can't remember the brand, that refused to stream from my dlna server unless it could contact its own corporate servers over the internet first.

In 1981 I wrote a tool that is still in use today. You can install the package on most major linux distros. This was before we paid much attention to software copyright, and I simply published it with my name on it and no license.

About six months later someone took my code, removed my name from it, made some small changes that didn't change its behavior at all, and re-published it. By that time I had moved on and wasn't aware that it had started to take off.

The man page now has someone else's name on it as author. I don't really regret publishing it but I wish I had put a copyright notice and license on it.

You're supposed to #define GIF_IMPLEMENTATION in only one of your .c files to prevent linker collisions. But yeah I don't get the point. How is this any better than the standard method of putting macros and data definitions in the .h and code in the .c? This is just going to confuse anyone who comes along later and wants to work on the code that uses this thing.

It's not just the headline. "... a single electrode that looks just like a strand of hair and is more reliable than the standard, multi-electrode version." "The researchers tested the device’s long-term adhesion and electrical performance and compared it to the current, standard EEG using multiple electrodes."

I read the story three times and I'm still confused. But I'm sure you're right, and I think it's the author who's confused.

I can't find it now but there is another news report that explains how it's physically impossible for this whale to swallow something that big. At most it could hold a person in its mouth before spitting it out.

Original headline: A Cemetery’s Immortal Residents and the Scientist Who Studies Them

One small correction, WWII rations included instant coffee, but it wasn't freeze-dried, which was invented after the war.

I am 70 and still have the bike my father bought me when I was 14. I ride it every day. The only original parts are the frame, the rear brake post, and the head bearing nut.

That's for one drive. For all 24 it's about 88.7%.

LR and CR cells don't contain mercury and never have. The original 12c battery was a MR44. 'L' is manganese alkaline, 'C' is lithium, 'M' is mercury.

If no character set is specified, plain text content is assumed to be 1252. This probably extends to application/javascript as well but I'd have to check to be sure.

The web pre-dates utf-8, although not by much. Ken Thompson introduced utf-8 at winter Usenix in 1993 and CERN released the web in April, but it would be several more years before utf-8 became common. The early web was ISO 8859-1 by default. But people were pretty lazy about specifying character sets back then (still are actually) and Microsoft started sending or assuming their 1252 character set where 8859-1 was required by the spec. Eventually the spec was changed to match de facto behavior. I guess the assumption was that if you're too stupid or lazy to say what character set you're using, then it's probably 1252. (Today the assumption would be that it's probably utf-8). I'm not sure what the specs say today, but I think html is assumed to be in utf-8, and everything else is assumed to be 1252 (if the character set is not explicitly declared).

It's not hard if you understand how cvs works. The email says the files are in the "src" module, so you select that from the cvsweb page. Then it's just a matter of drilling down to the individual files. Here is the diff for the Makefile for example:

https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/games/quiz/Mak...

As for how you work like that, the number of people with commit access is small and they all know each other. There aren't a lot of branches. Most of the collaboration features of git aren't needed.

Seems like a less than useful comparison, given the very different utilization factors. For solar you'd need five times the capacity to get the same average power.

Also the http:// syntax in urls.

Separate error output was around for at least a decade before this. I know MTS had it in the 1960s, and I don't think it was their original idea. I used a CDC for a while and they had it too. So while this is the story of how standard error was introduced into Unix, it is not the origin story of the concept of standard error.

My family uses about 20 liters a week per person. That's for drinking and cooking.

Strange, I'm in Mexico and if anyone gets blocked it's usually me. But I can read this one.

Anyway here you go:

https://archive.ph/ru5Jm

Most of the system files from when I ran Unix v7 have a mod time of October 15, 1980. I have some files from v6 but the timestamps were not preserved. They would be from 1979.

I don't know if something got lost in translation, but there is pulse dialing, and there is tone dialing. There is no "pulse tone dialing".

I was in high school in 1969, knew some calculus, and was very interesting in programming. In a good size city with a major engineering university and a large high school the main barrier was access to computers. Our school had teletypes connected to a remote mainframe. My friends and I found a few computers at the university we could use at night, but most had card readers and line printers, and none had graphics terminals of any kind. I think the particular combination of skills, interest, and access would have been pretty rare at the time.

I was confused for a minute because I remember playing Spacewar on a PDP-1 in the 1960s and mis-remembered there also being a lander game. But there wasn't, Storer was the first. There is an interesting history here:

https://www.acriticalhit.com/moonlander-one-giant-leap-for-g...

I used to have a 1948 Hallicrafters TV and it had yet another type of high voltage supply. There was a 100 kHz oscillator driving an air-core transformer in normal (not flyback) mode. The potting had gone bad on the transformer, and I couldn't find a suitable replacement, but I did find one that had the right secondary winding. Since it was air-core I just cut the secondary off that and the primary off the original and glued them together. Worked great.

72% is pretty impressive. I have only filed against Firefox, and my fix rate is less than 20%. Some of the rest are "won't fix" but many are still open, the oldest at 16 years.