> I think I could live with all the other components being metric, if they just had a way to work with standard U.S./Imperial containers as well.
As far as I know mason jars (of that size) are the same everywhere so it should work with whatever containers decided to use that standard
> Oh, and they need a 120VAC design for the motor and all the electronics inside.
After reading the BOM it looks like the only electrical components are the limit switch, rotary switch, motor, and the support components soldered to the motor, so a 120VAC design would only need to replace those with equivalent 120VAC components.
> Or, a design that can handle both 120VAC and 240VAC, as well as both 50hz and 60hz.
AFAIK that would either be a 120VAC model with a PCB to compensate in 240VAC areas or a DC motor with PCB
On some sites it's possible to work around this type of linkification bug by percent-encoding the last character (percent symbol followed by 2 hex digits representing the ASCII character):
I wouldn't expect KODI/OSMC to provide an unofficial YT client. However, the "app" availability issue is a big one for devices like this if they are to compete with spyware-ridden Android TV boxes on one hand and Linux HTPCs on the other hand. The Android TV boxes are cheap and support all streaming platforms. The Linux HTPCs are free (as in freedom), typically far more powerful (can double as consoles/emulators) and don't restrict the user in any way.
I have TOR enabled in my firefox (in a container) just for that. It just seems madness for me (as a non-spaniard) that 2 links of the HN startpage are blocked for football. We are not talking the regular terrorism, abuse/illegal content whatnot. No, censorship to protect football IP.
You can use xcancel.com or farside.link's nitter redirect to avoid that, if you're on Android it's easiest to use URLcheck‡ with these chunks added to the pattern checker:
```
"Twitter to Nitter": {
"regex": "^https?:\\\/\\\/(www\\.|mobile\\.)?(twitter|x)\\.com\\\/(.)",
"replacement": "https:\/\/farside.link\/nitter\/$3",
"enabled": "true"
},
"Twitter image to Nitter": {
"regex": "^https?:\\\/\\\/(pic\\.twitter|pbs\\.twimg)\\.com\\\/(.)",
"replacement": "https:\/\/farside.link\/nitter\/pic\/$1",
"enabled": "true"
},
```
(I haven't updated my copy of the Twitter image regex for the rename because I haven't seen any X.com image links and upstream seems dead)
They don't have a relevant item in the FAQ but it sounds like they place each block manually directed by a schematic overlay