In other words, make your own certificate authority for your own machines. It isn't that hard.
1. Planned obsolescence built into HTTPS: no HTTPS-aware server device from year 1999 would work with 2023 browsers. Just because "too old crypto". Plain HTTP works.
Being on a buy side I am against HTTPS in such devices, but I understand the sell side's position.
Of course, no https, but.. it is not a platform limitation, just an undemanded feature: how would you get a https cert for 192.168.0.1 or a similar intranet address where those device suppose to work? They are just not for cloud datacenters
A 32-bit CPU is very rich
I read that from recent magnolia commits, it falls back to {12,1}ft for some websites (apparently, some techniques cannot be done on client-side, perhaps, they require proxies in particular countries or google network to impersonate googlebot better)
Moreover, many people are in a grey area of the economy, paying no taxes at all: for example software developers making software for the West.
Looking at the ridiculous "sanctions" of recent days, I cannot say who they are directed against. In long run, they benefit Russia, preventing leaking of brains and capital.
Meanwhile, for The Real Russians, business as usual.
This looks like theatre hurting the wrong people.
You might consider a list of registrars that do stuff you disagree with instead.
I would prefer to work with companies where different nationalities are represented.
90%+ of employees in one country (be it Ukraine, Russia, USA or China) is a geo-risk for clients.
And mind you, Namecheap doesn't ban clients based on their agreement or disagreement with something. It bans pro-Ukrainian dissidents in Russia too.
Racism culture thrives in mono-ethnic companies and this Namecheap case is a good example