qprimed

someone genuinely interested for intellectual reasons would likely not fall for it. I would imagine that a non-trivial percentage of “antiquity enjoyers” are very light on history substance and heavy on history feelz.

once the appropriate brain tickles have been pushed into their heads their “history substance” feed content becomes decidedly propagandized.

heh, forgot about the standalone web server in certbot. thats a good ephemeral option.

if you are able to run a public web server, then certificate issuance via certbot http challenge works pretty well. the web server can serve a really simple static page with little to nothing on it - but of course its another potential vector into your network.

if your public domain DNS makes use of a supported dns provider or you run your own publically accessible dns server, then dns certbot challenges are great and more flexible than http.

others may suggest neat work arounds for the http challenge issue, but if you have access to a supported dns service I would look at that option. certbot has helpers for quite a few public services as well as support for self hosted dns servers. I run my own public dns servers, so thats the option I chose and use certbot hooks, cron and bash scripts to rsync the updated carts to the propr hosts for the various services I run privately and publicly.

if you are using http cert retrieval, certbot needs a place put the temp. token to authenticate your contrrol of the domain your are creating a certificate for. usually that will be the same webserver you want to serve the certificate from.

if you are not running an actual weberver on port 80 that certbot can insert a token for, certbot cannot complete.

this is, of course, in addition to other possible issues such as ISP port blocking - but without a web server listening on TCP/80, you will have to use other authorization methods (like DNS) to generate a cert.

are you actually running a web server on that host? iirc, certbot will place a temporary token to be served by your web server (Apache, etc.) to show that you actually control the domain you are requesting a cert for.

I switched to DNS based retrieval as soon as let’s encrypt offered it, so its been years since I retrieved certs via http.

The All-In-Plan privacy policy also says that HP may “transfer information about you to advertising partners” so that they can “recognize your devices,” perform targeted advertising, and, potentially, “combine information about you with information from other companies in data sharing cooperatives” that HP participates in.

this company abomination is dead to me.

not a recommendation (I have not used any pulse to tone converters), but this may help you out.

wow, man. like, such a load of buzzkilling stuffed shirts.

when I finish work on my finite improbability generator, hook it up to a Bambleweeny 57 Sub-Meson Brain (with integrated atomic vector plotter) and fire it up with a nice hot cup of tea, these respectable physicists are definitely not invited to the party – no matter what the hostess says.

CyberPower CP1500AVRLCD (various version iterations) UPS units have been cheap, reliable go-to choices in many instances.

they are stepped square-wave units, but are used quite a bit in home-lab setups and are pretty well supported by NUT if you are on linux.

edit: I have used them for years to replace APC units. only issue has been cosmetic input voltage vs output voltage reporting mismatch via USB on very early v1 units.

at this point the codebase is in daily flux, it really comes down to RTFS. the transition from websockets to http seems to be mostly in-place, so there may be some opportunity to begin normalizing the docs.

totally agreed on the need for more complete and accurate documentation, but without an auto-documenting sourcecode framework, I would expect API documentation to lag. in the meantime we just live life on the edge - it will improve over time.

edit: word

right to your very soul.

isnt it great to know you are making a positive difference?!

hello, fellow human!