Probably not too hard to make one! Pandoc is doing most of the work.

I think the biggest improvement would be if someone had an Apple developer account and could go through the notarization process so that it could be easy to install. Probably also with bundling pandoc. And it would be nice to get it into the Mac app store.

In terms of the functionality of the actual tool, the markdown it produces has more escaping than I would like. Several special characters seem to be always escaped, to be on the safe side, when instead they could be escaped only when necessary.

I like both logos individually, but they don't look quite right next to each other. I think this should also be moot, though, because two apps is silly. Better to have a single menu bar app, with two clicks, one for markdown and another for normalization.

Instead of modifying the paste buffer, it would be nice to have a key combination for "apply the transformation and paste". This one might not be possible, though perhaps it could be faked by modifying the buffer, pasting, and then restoring the buffer, very quickly.

That works quite well, and I used it for a while, but even though it is supposed to be entirely client side, I still would prefer not to be pasting anything non-public.

Why?

In general, the longer your sightlines the better UVC does and vice versa. While air purifiers are a cost per amount of filtered air, UVC depends on how much air the beam can go through before it's (mostly) absorbed by the wall / ceiling / floor / people.

Do you not feel obligated to tell people that such lights are present, in case they have a different assessment of the long-term safety than you do?

I do think that's a good idea, yes:

• Before deploying them at the local contra dance we announced a trial.  Afterwards we polled attendees (only one person in 200 didn't like the idea), and announced deployment.  Now it's listed on the website, along with information on our mask requirements and glycol vapor usage.
• Before setting one up at Thanksgiving I also wrote to my relatives, linked them to faruvc.org, explained why I thought this was a good idea given my aunt's immunocompromised status, and asked if anyone had objections.
• I had one set up at the EA dinner we hosted last night, but it wasn't in the main room and I told people about it.  I'm planning to announce before the next one that we'll have it in the main room.

I remember how ApeFest caused eye damage with UV lights.

It sounds like it was UV-A ("blacklight"): "Yuga carried out the investigation with Jack Morton Worldwide, the event agency that produced this year’s ApeFest. Together, they 'determined that UV-A emitting lights installed in one corner of the event was likely the cause of the reported issues related to attendees’ eyes and skin.'"  This would have been visible as a deep purple glow that makes things fluoresce, so the problem is probably not that attendees didn't know UV-A was present but instead that attendees should be able to trust organizers to keep things like this to a safe level and the organizers didn't do that.

If you place the lamps so they're only above people's heads you can use 254nm bulbs, which are much cheaper (they're essentially standard fluorescent lights with UV-transparent glass and no phosphor). People have done this for a long time in places like TB wards, but you do need to be pretty careful about placement to ensure your 254nm UV really is only shining in the space above.

Of course the ideal method is to have the UVC light internal to your air conditioner/heater unit, which is already circulating the air, so you can blast everything passing through that with enough UVC to annihilate any and all pathogens in the air, but that requires retro-fitting to AC units and stuff.

To get equivalent protection this way you'd need to cycle your air through your HVAC much faster than you likely currently do. Which would be noisy!

I hadn't seen that study, thanks for sharing! I've added it to faruvc.org, and added a warning that people shouldn't consider 233nm LED sources as equivalent to 222nm KrCl sources.

Sorry this took me so long to fix, but it should work now! https://faruvc.org, https://www.far-uvc.org, and https://far-uvc.org should all redirect to https://www.faruvc.org.

(https://www.faruvc.org is hosted on GitHub pages, and I'd tried to use my DNS registrars redirect system to point the others there.  This doesn't work, though, because it only uses HTTP.  They could totally make HTTPS work, via LetsEncrypt, but they haven't.  So instead I needed to point those three aliases at the same VPS that serves https://www.jefftk.com , make that VPS get the certs, and then make that VPS redirect them to the canonical site.  Possibly there was a better way to do it, but this is working now.)