That’s an interesting one. I know it depends on configuration, but in the run-of-the-mill case, does connecting through VPN stop local services to listen on local IPs? I know our corpo VPN kills local LAN access but I’m curious what the default for OpenVPN/Wireguard might be.

The OS interfaces provided to apps (generally POSIX) have no idea what HTTP is. They’re much lower level than that. If an OS is to control what protocols are used by apps, it has to offer some functionality that does HTTP for the apps and apps have to use it. Unfortunately the only way to force that would be to disable the general OS interfaces so that apps can’t just use existing libraries that use those. If you did that your OS would become useless in other ways that rely on the basic interfaces.

The other way the OS could do anything about it is to inspect network traffic going over its network interfaces. That would be a significantly different can of worms and it’s not free in terms of processing power and therefore battery. Then you’d have the screams of privacy people that Android or iOS is looking at all network traffic.

So all in all, the OS isn’t very well suited to police application level protocols like HTTP. At least not on devices whose primary purpose isn’t network traffic related.

Shimano LINKGLIDE cassette and chain should be able to handle that much torque and more. It’s got more metal where needed and is a bit heavier as a result. You should try it.

New Shimano XT can take 200Nm for a bit but it gets eaten relatively quickly if you keep running that much torque through it.

Importantly, most drivetrains have to be able to handle 200-ish Nm of torque because that’s what gets applied when you ride standing up. However the ones intended for human use don’t handle that torque continuously. Every time you run that much torque through it, the metal surfaces wear out significantly more so after some wear, you get abnormal behavior.

My Tangent snapped a Shimano XT chain in less than 1000km. I think that system could reach 200Nm peak torque. I had to switch to stronger chains and limit the torque to stop it from eating metal. That’s easier these days since there are stronger ebike-specific drivetrain components from Shimano and others. 😂 But I don’t ride that anymore.

It’s a pretty standard arrangement from what I can tell.

For reference, Bosch, Yamaha, and Shimano all have eMTB motors putting out 62.7 lb-ft (85 Nm) max torque.

This might be more related to legal power limits and less that they can’t figure out how to reduce a motor.

A design that stood out for me in this space was Dave’s Tangent which developed something like 200Nm with 80:1 cycloidal reduction in 2.8kg.

And they package drives correctly.

I don’t know if SPD ships to where you are but a manufacturer recertified 16TB from them goes for ~$160. I have 7 drives from them so far, 5 in continuous use since spring, no issues so far.

If it was larger and more likely to cause major long-term damage I’d have added last name Friedman.

Oh nice. Just gotta dress em up like Unifi or Aruba then stick em up on the ceiling.

Apps don’t use the system browser to connect to REST endpoints. Neither do they use the OS. Apps typically use a statically linked library. There are use cases for HTTP-only connections so it’s unlikely that those libraries would mess with forcing or even warning its users that they’ve used HTTP instead of HTTPS. Point is Google and Apple can do little in this regard. Unless they scan apps’ source code which could be possible to some extent but still difficult because URLs are often written in pieces.