So a lot of people have found there is a shortage of webcams, work and learn at home, that sort of thing. But did you know you can buy the raw modules? Check out this table, pick one that you like, and then search for that on ebay or aliexpress.

Now I've got a 4:2:2 webcam (of course in 4:2:2 @ 4K mode it does 1fps, but, well, its a smooth and fluid 1fps!). The picture quality is really good (its not DSLR good, don't be crazy, but, its a micro 4/3 sensor @ 4K, its quite nice for a webcam).

Don't be that person w/ the weird up-the-nostril blurry cam that came w/ your ultra-sleek laptop, instead be the person who can't go through airline security without TSA questioning your IED-like attachments.

You're welcome.

https://www.sony-semicon.co.jp/e/products/IS/camera/product.html

One of my favourite YouTube channels well other than the "Live Kittens Channel" is Hand Tool Rescue . It far and away the best restoration of rusted tools channel from Saskatoon. Recently he did a larger version of the iconic King Dick wrench. So, I had to support, and, well, here it is. Its solid steel, heavy 1.275kg, and, Im sure you need one as much as I do.

You can buy your own here.

And watch it being made! And once you've done that, maybe a few more, next thing you know you are wanting a gas-powered washing machine.

Recently the Canada Revenue Agency (or more specifically, the users of it) had a password breach. People had re-used their CRA password on other sites that were hacked. Compounding this is the CRA website facilitated stuffing: automated trying of username/password to check which of the breaches worked.

Well, CRA has responded with a captcha (those 'find all the images containing... tests). But, interestingly, it seems to show other national symbols. See mine below, i'm looking for pictures of a train, but I find Singapore airlines flag carrier, China Airlines flag carrier, US flag, ... None of them trains to be fair! But none of the trains were VIA or CN or CP either.

I'm not sure what i was hoping before, perhaps classic episodes of the Beachcombers and you had to spot which character was John or something like that. Anyway, progress is good.

By now I hope you have all (eligible) installed COVID Alert by Health Canada. I got my weekly results summary from it, and thought I would share for those that are still convinced its Bill Gates 5G tracking chip technology but also scared to read the code to find out (or just scared of facts).

Like all good modern applications, the API is REST and JSON. The app gives you a download as JSON, so I did. Its not very interesting, but, let's look.

First, a refresher. You get a random ID. Every day your ID changes. On your device, you keep a list of other random ID you have seen. Periodically you check the network to see if any of those ID are in a list of people who have indicated they have been exposed. If you are exposed, you enter your test result in the app and it publishes your random ID. Otherwise, it publishes nothing. And, there iis no location.

So lets look at some of my results. I shortened my hash (that unique ID) for readability. It seems that the apps checks somewhat randomly. It checked 4 times on the 21st at 3am, but didn't check at 5am. Dunno why.

For me, the number ID's in my local list (the keyCount) varies between ~370 and ~420. This represents the number of those random ID's I've seen in the trailing 14 day period. I guess(?) each one cycles daily, so if I divide by 14 I get the approximate number of people who run this that i've been nearby? So ~30 people?

timestampkeyCountmatchesCountappNamehash
2020-08-21 09:40:004040COVID AlertrvGFQL6X
2020-08-21 09:14:004040COVID AlertrvGFQL6X
2020-08-21 08:54:004040COVID AlertrvGFQL6X
2020-08-21 08:39:004040COVID AlertrvGFQL6X
2020-08-21 07:31:004040COVID AlertrvGFQL6X
2020-08-21 07:20:004040COVID AlertrvGFQL6X
2020-08-21 04:26:004040COVID AlertrvGFQL6X
2020-08-21 04:08:004040COVID AlertrvGFQL6X
2020-08-21 03:53:004040COVID AlertrvGFQL6X
2020-08-21 03:42:004040COVID AlertrvGFQL6X
2020-08-21 03:31:004040COVID AlertrvGFQL6X
2020-08-21 03:20:004040COVID AlertrvGFQL6X
2020-08-22 08:52:003990COVID AlertykZfXmnf
2020-08-22 06:49:003990COVID AlertykZfXmnf
2020-08-22 05:35:003990COVID AlertykZfXmnf
2020-08-22 04:54:003990COVID AlertykZfXmnf
2020-08-22 04:25:003990COVID AlertykZfXmnf
2020-08-22 04:08:003990COVID AlertykZfXmnf
2020-08-22 03:52:003990COVID AlertykZfXmnf
2020-08-22 03:42:003990COVID AlertykZfXmnf
2020-08-22 03:31:003990COVID AlertykZfXmnf
2020-08-22 03:20:003990COVID AlertykZfXmnf
2020-08-20 23:22:004040COVID AlertrvGFQL6X
2020-08-20 06:48:004100COVID Alertj42FRE28
2020-08-20 05:34:004100COVID Alertj42FRE28
2020-08-20 04:52:004100COVID Alertj42FRE28

Some have asked me to explain. I snooped through the source, but I think this https://www.canada.ca/en/public-health/services/diseases/coronavirus-disease-covid-19/covid-alert/privacy-policy/assessment.html does a better job. The key section is quoted below.

Each device with the app installed is sending out and listening for random codes called rolling proximity identifiers (RPIs) which are not static: On a daily basis, the Google/Apple layer automatically generates a random temporary exposure key (TEK). The TEK of the day then generates a new random ID ("rolling proximity identifier" (RPI)) every five to twenty minutes. It is these ever-changing random IDs that are shared with other devices.

The daily TEK generation and frequent RPI generation are design features with the purpose of minimizing the risk of re-identification of users. (In addition to this, they are designed to minimize data transfer to conserve bandwidth.) The RPIs are not identifiable and are not accessible to the app or transmitted to the key server. By design, the RPIs are meant to be public (they are shared to other devices via Bluetooth), and as such do not provide any form of identifying information in the absence of other information. Even if an RPI were intercepted by a device operated by a malicious actor, it would be an entirely meaningless number, and would not be linkable to a device without significant effort. TEKs are stored on the device, but may only be released to the key server in the case of a positive test result and explicit user consent.

When a user receives a positive COVID-19 test result, provincial/territorial (PT) health authorities who have adopted the app will provide them a one-time code Footnote2 and instructions on how to enter it into the app. Footnote3 The app will validate the one-time code and ask the user if they would like their past 14 days of TEKs to be sent to the key server. Footnote4 If the individual says yes, the app communicates with the Google/Apple layer. The Google/Apple layer asks a second time whether the individual consents to sending the past 14 days of TEKs to the key server. If the individual consents, the TEKs are sent to the key server, allowing other users they have come in contact with in the past 14 days to be notified, once their app has downloaded these keys. App users also have the option of uploading their diagnosis keys for the 14 days following receipt of a positive diagnosis, in the unfortunate scenario where an individual who has COVID-19 cannot self-quarantine (e.g. doesn't have sick leave; lives alone and has to buy groceries, etc.).

TEKs are generated once a day and expire after 14 days on the device. A TEK become a "diagnosis key" once released for upload to the key server. If the user consents to upload and transmit the diagnosis key, other users with whom they were in contact may receive a notification. Footnote5 We note that if an individual has had contact with a very limited number of individuals in the past 14 days, it's possible that the user who receives the notification may be able to associate it with an individual.Footnote6