After a couple of high-usage outlets got jammed to the point that nothing could be plugged in, I replaced them with ones from the hardware store, and they are a big improvement. The existing outlets are unbranded, and I guess were from a bulk box of the cheapest that the electrician could source.

In my experience, Leviton are OK (much better than what was originally fitted), but Eaton are great -- they require slightly more force than non-TR outlets, but they're consistent, reliable, and I've never had to try more than once to plug anything in.

It was typically used to transmit pages of information (news, weather, etc.) that could be viewed directly on the TV, but the BBC's Ceefax[2] Teletext service was also used to distribute software to the BBC Micro, when equipped with the appropriate Teletext Adapter[3].

In a similar fashion to the Sega Channel system, the Teletext system would broadcast looped data, with popular pages (such as news and weather) being repeated frequently so they would load quickly, and less popular pages taking longer to load (or more accurately, to wait for the next time they appeared in the looped data).

I was interested to see that the Sega system used a bitrate of 8Mbps, which sounded pretty high for the mid-90s, but I see that Teletext had a bitrate of almost 7Mbps for PAL broadcasts, despite being roughly 15 years older!

[1] https://en.wikipedia.org/wiki/Teletext

[2] https://en.wikipedia.org/wiki/Ceefax

[3] https://en.wikipedia.org/wiki/BBC_Micro_expansion_unit#Telet...

Bear in mind that the scheduling support is extremely basic -- the only option available is to schedule six exports, one every two months. You can't change the frequency or the number.

Also, you can't pick when the schedule starts, so if you want backups every two months indefinitely, you have to remember to schedule the next set of backups two months after the final backup of the previous scheduled job finished.

It's better than nothing, but only just.

During one of the live shows, demonstrating e-mail, the e-mail account was hacked, probably the first hack captured on TV: https://www.vice.com/en/article/9ak7w5/as-seen-on-tv-when-ha...

https://www.reddit.com/r/Carpentry/comments/11s6zlr/cutting_...

While we're still not talking microseconds, I think it highlights that moving the blade out of the way needs to happen very quickly in some cases to avoid serious injury.

I always have a failure with Google Fit data, which reports 'Service failed to retrieve this item' on the same JSON file every time. I assume this is something corrupted at their end.

It's not that uncommon for my exports to intermittently show failures with other services -- for example, my latest export, taken on April 20th, also failed to include one of my YouTube videos, with the same 'Service failed to retrieve this item' error. That video is usually included successfully, so I'm guessing this was a glitch.

Nothing major, but I can well believe that others also experience regular errors, although I'm sure we're in the minority.

My understanding is that with single-NDIR sensors (like the MH-Z14 and 19), the auto-calibration is intended to overcome gradual particle buildup and beam degradation in the sensor chamber. While disabling it will prevent the scenario I described, you'll instead end up with gradual sensor shift as the sensor ages. I guess this could be minimised by manually calibrating the sensor outdoors on a regular basis.

Dual-NDIR sensors split a single beam into two chambers, so any degradation of the sensor beam affects both measurements, and the particle buildup in both chambers should also be approximately equal over time, so they should remain accurate over an extended period without any requirement for calibration. I built mine about 4 years ago and I do occasionally check to make sure they read ~400ppm when placed outdoors, last check was around 420ppm which suggests they're behaving reasonably well as they age.

A sibling post[1] mentioned a sensor that is listed as being dual-NDIR so should give reliable readings, and has a USB interface, so that sounds like one possibility.

[1] https://news.ycombinator.com/item?id=32122301

This works acceptably if the sensor is frequently exposed to outdoor air, but in a residential environment that's not always guaranteed, particularly in winter when it's not uncommon to keep windows closed to retain heat. In these situations the sensor will consider the lowest level to be around ~400ppm, even if it's actually much higher. This, of course, scales all other readings, so a sensor might read between 400-800ppm, leading you to believe everything is fine, when the actual indoor range is 800-1600ppm.

Because the auto-calibration happens over a period of time, it can be quite difficult to determine that your sensor is misreading, and the only way to fix it is to expose it to fresh air to reset the baseline.

The best solution I found to this is a dual-NDIR sensor which measures two different light frequencies, one which is absorbed by CO2 and one that isn't. This allows the sensor to know the absolute CO2 concentration, rather than the relative CO2 concentration, and avoids the need for auto-calibration. (I believe for absolute accuracy it still needs calibration for altitude, but for consumer use this makes such a small difference to be irrelevant).

Unfortunately, when I last looked, I couldn't find any consumer-grade sensors which used dual-NDIR sensors, only more expensive and less aesthetic commercial sensors. In the end I built my own using a CDM7160 sensor connected via I2C to a ESP8266, which reports over MQTT.

  Moderna: August 5th, 2020 [1]
  Pfizer: August 5th, 2020 [1]
  AstraZeneca: September 25th, 2020 [2]

  Moderna: November 25th, 2020 [3]
  Pfizer: November 11th, 2020 [4]
  AstraZeneca: August 27th, 2020 [5]

[1] https://www.canada.ca/en/innovation-science-economic-develop...

[2] https://pm.gc.ca/en/news/news-releases/2020/09/25/new-agreem...

[3] https://ec.europa.eu/commission/presscorner/detail/en/ip_20_...

[4] https://ec.europa.eu/commission/presscorner/detail/en/ip_20_...

[5] https://ec.europa.eu/commission/presscorner/detail/en/ip_20_...

Comments URL: https://news.ycombinator.com/item?id=27654465

Points: 3

# Comments: 0

'In order to provide more information about event severity within the S1 designation, S1 severity events have been separated into two columns in Table 1 based on whether each event is of sufficient severity to result in actual or simulated airbag deployment for any involved vehicle. Of the eight airbag-deployment-level S1 events, five are simulated events with expected airbag deployment, two were actual events involving deployment of only another vehicle’s frontal airbags, and one actual event involved deployment of another vehicle’s frontal airbags and the Waymo vehicle’s side airbags. There were no actual or predicted S2 or S3 events'

[0] https://storage.googleapis.com/sdc-prod/v1/safety-report/Way...

There are no border controls when entering Hyder from Canada, as the only way to access the rest of Alaska from Hyder is via seaplane, and those flights are treated as international in origin when they land. There is a inspection station when crossing into Canada, but it is closed overnight -- anyone wishing to enter Canada when its closed must report via videophone.

There's a map of the largest fields in this article:

http://www.cbc.ca/news/canada/newfoundland-labrador/husky-we...

Capacitive touch sensors that registered an X/Y position rather than a simple on/off state were also common in laptop touchpads from around the mid to late 90s. The iPod introduced a capacitive touch wheel to replace the click wheel in their second-generation model, released in 2002.

There were various capacitive touchscreen display devices around before the iPhone, but probably the most relevant to your query (and one of the most well-known, due to its similarity to the first iPhone's technology) was the LG Prada, a phone with a capacitive touch-screen announced about 6 months before the iPhone.

The thing with the iPhone's touchscreen wasn't that the technology was particularly revolutionary -- sure, if you combine enough words together, then you can make the argument that the iPhone was probably the first mass-consumed capacitive multi-touch hand-held consumer device, but you can remove any of those words and it was no longer the first. The revolutionary aspect of the iPhone was, in my opinion, the software that allowed the device to be controlled with the relative imprecision of a finger, rather than a stylus. The actual hardware to process the touch inputs was at best evolutionary, not revolutionary.

https://www.eclipseglasses.com/pages/safety

See the photo at the very bottom of the page for an illustration of the (very minor) differences.

There's a map of libraries on their website:

http://spacescience.org/software/libraries/map.php

If yours is on that list, you should be pretty safe, I think.