HN user

radiowave

875 karma
Posts0
Comments413
View on HN
No posts found.

My experience has been that CertBot doesn't play well with CNAME delegation, but it's probably very situational, like depending upon which DNS hosting provider plugin you're using.

My solution was to give up on CertBot and use dehydrated instead. This did require me to come up with a script to make the necessary API call to the DNS hosting, which dehydrated will then run as necessary.

Yes, Whisker is exactly what came to mind for me as well.

I don't currently use Smalltalk, most of my code is now written (and read) in vscode. The means available for showing the context around the code under consideration (splitting and resizing panes, hunting through lists of tabs, scrolling around) feel pretty crude by comparison.

Brings to mind the phrase, "the innate animosity of inanimate objects".

(Can't remember now where I chanced upon this.)

Though that's still incomplete, because (more of the context stuff that you just have to know already) the "A" here refers to the frequency-weighting scheme used in the measurement, and not to the reference level (which is SPL).

It should probably be given as: dB(A) SPL, or dB SPL (A-weighted).

At a rough guess from the audio samples, that array is producing an acceptance angle much narrower than any Soundfield mic is capable of. The noise source is only 45 degrees off-axis; I'd say any first-order microphone polar pattern (i.e. those a Soundfield mic is capable of) would capture more of the noise than is demonstrated here.

Of course, you can improve on the rejection of off-axis sound by instead using a microphone with a more specialized polar patten (e.g. a shotgun mic), but then you lose the property of the pattern being steerable merely by signal processing.

Lastly, such an array of dirt cheap pressure sensitive mic capsules with some clever computation behind them strikes me as the sort of thing you could throw Moore's law at, if you could justify the quantity. Whereas, Soundfield mics don't make much sense unless you're working with very precisely machined pressure-gradient capsules.

Still, I get the feeling it'll be a while yet before this technique starts looking viable for audio production work, but it's very interesting.

My dad worked on something similar, when during the 1980s the coal-fired station he worked at had to convert to two-shift operation, from the three-shift operation that it's 1950s design had intended. He described this process as, "bashing hell out the machines to make them do things they weren't designed to."

One interesting detail was that the more rapid startup and cooldown of turbines meant that blade spacing couldn't be as tight as before, reducing efficiency during operation. (The turbine casing has less thermal mass than the rotor, and hence contracts faster during cooldown. The spacing of the blades needs to account for this.)

I remember him from the Squeak Smalltalk mailing list, probably early 2000s. He wrote a set of bindings for the pcre regular expression library, which I used quite a bit, but which was never picked up for inclusion in Squeak (because pcre "isn't portable enough").

And, with his intellectual property hat on, he was a regular source of advice to the Squeak community (none of it in an official capacity, he would hasten to add) as they worked through the process of relicensing from the original Squeak License to MIT.

Right. And also, the photographer likely wants high ISO film, to be able to take a very short, crisp exposure of the moment of impact, without needing to gamble on the amount of cloud cover, and hence available light.

ISO 1600 colour film will have been available at the time, but was probably pretty poor compared to B&W.

Changing the focal length doesn't inherently change the perspective, and (resolution and lens aberations aside) is exactly equivalent to cropping.

What changing the focal length does do is (e.g.) make you stand further back, and that changes the perspective, causing distance compression, etc.

There's a lot from the D-50 that's missing on an MT-32, like 50% of the ROM capacity, and all of the filters and effects.

And on top of that, DigitalNativeDance is an outlier. It was (for its day) such a profligate use of ROM that it's not even representative of what a D-50 could do, in general.

Not that this contradicts your main point about GM constraining the choice of sounds.

Yup, I gave up on certbot after trying to understand why I couldn't get the Digital Ocean DNS plugin to work, which is maintained as part of the Certbot repo. (This was a few years ago, so details may have changed.)

I discovered the issue was that the plugin does some pretty broad-brush guesswork about which domain in your DNS hosting it should actually populate with the response value. If you own a bunch of similar domain names (as many orgs do), the plugin may guess wrong.

Much happier to be using dehydrated, and I don't regard it as a major impediment that I had to spend 10 minutes hand writing the necessary API call to the DNS provider.

For sure, VLAN config is one of the most extremely "How and why did anyone end up designing it this way?" thought-inducing areas of Mikrotik config.

But I will say that the boxes of theirs that I bought about ten years ago are still going strong, never had a device fail on me, still receiving OS updates, still able to export and re-import my config to any of a wide variety of newer devices when the time comes.

Clearly they're not the right choice for everybody, but there are certainly up sides, if you're willing to grapple with the config.

Agreed. I've worked in a company that was AS9001 certified, and pretty much the first things a quality auditor would have wanted to look at would be non-conformances and concessions. With than number of missing signatures we'd have been skinned alive, and it would likely have prompted the auditor to then turn the place upside down looking for more problems.

That would then have produced major failings in the audit, if not the outright revocation of the quality accreditation, which I would then expect to be followed up on by an audit from the customer (which in the case of TFA would be Rolls Royce), asking some rather uncomfortable questions of the management, examining whether the inter-company concession process was being adhered to, and perhaps reflecting internally (i.e. within RR) - "Do we think these folks are the right people to be making these parts for us?"

From what I've read here it seems to me that Rolls Royce were astonishingly lax in not riding their subcontractors nearly hard enough, quality wise.

One pragmatic solution to this is to use an email relay service to handle the outbound mail. Now, the hair-shirt self hoster's response to this idea might be, "But that means trusting a third party!" And indeed it does. But as the parent comment points out, in the vast general case we're committed to trusting whichever third parties our correspondent uses (or finding alternive means of communication.)

I know what you mean about the filmic module, and while I'm inclined to think that it doesn't necessarily invalidate his criticisms of Darktable, it does make me wonder whether he's the right person to fix these things.

It's a good question, and deserves a more detailed answer than I'm able to give without more first-hand experience with trying to use Windmill in this way. But my sense of it is that there's likely to be a chunk of legwork involved in the passing of parameters and credentially over to the remote host, capturing both stdout and stderr from the remote site - things that Rundeck handles pretty much seamlessly - and a concern that using Windmill like this the question of which host the job is executing on isn't a first-class concept, like it is in rundeck.

It's likely that in time I will evaluate Windmill to get a more detailed understanding of this - there's definitely aspects of it that are very substantial improvements on what can be done in Rundeck.

But inevitably, the question of whether to learn & install & maintain two separate systems side by side, with some degree of overlap in their functionality, vs. just picking one system to do the whole job and living with the shortcomings of whatever it doesn't do so well - it's always going to be a difficult one to weigh up.