Basically, it rebuilds Windows DPAPI from first principles, which is fine (I've done it many times myself!), and something non-Windows platforms sorely need. It changes the impact of malware from "they dumped all our secrets from prod to their C2" to "they got some encrypted values, and now someone will need to figure out our methodology and underlying keys", which is a meaningfully higher bar.

My reply was from an audio mastering perspective.

Ehhm, yeah, duh? You don't resample unless there is a clear need, and even then you don't upsample and only downsample, and you tell anyone that tries to convince you otherwise to go away and find the original (analog) source, so you can do a proper transfer.

Sharing/in-place-repurposing conduit is not something I'd recommend, but if you must, leave a few dummy cables (a.k.a. 'pieces of string') on the initial install...

Cables for direct burial only like to be bent once or twice, and then only gently. Anything else may very well break the armor (whether plastic or metal), after which all bets are off.

Still, for the outer jacket to become brittle to the extent described, something else is required, which may very well turn out to be "shoddy manufacturing"...

Another thing that should not have happened is installing the cable in loops in this way: any 'building' or 'underground' type cable needs to be of the exact length required at the demarcation point, fastened properly to prevent movement and terminated on a proper patch panel (can be a one-port box-type thingy for small setups), from where you use regular patch cords to connect your equipment.

(Loops are definitely allowed though, but that use case is mostly for aerial fiber to enable repair splices, and there are some very specific bend-radius and strain relief requirements, which, again should be spelled out in the cable data sheet)

For popular senders: sort-of: in your incoming mail server, substring-match the display name of the sender against popular brands, and ensure the actual domain matches.

This works remarkably well for proper brands (FedEx et al), but breaks down when the brand name regularly occurs in "normal" names, the sending brand sends mail from all over the place, or "innocuous" impersonation takes place all the time.

Like, somehow, From: "VODAFONE" is a 100% legit sender (assuming SPF and DKIM verification pass), despite both Vodafone and DPD being pretty common impersonation targets. You'd think they'd know better, but alas.

So, yeah, room for improvement and such...

Meanwhile, my life expectancy is, like at least twice that 'prior to WW1' and my disposable income at least 20 times my take-home pay in 1917.

Bloody EU, innit...

Source: me and my wife traveled extensively by public transport in, well, at least Pakistan. The other countries are indeed sort-of hairy, but mostly for job-clearance-related reasons.

Ah, so there is a chance!

(But, seriously, you can probably do it in another 48 hours...)

Also note that since the MS-EU settlement, the SMB protocol is quite extensively, if a bit passive-aggressive opaquely, described in a series of documents that Microsoft updates to this day, e.g. https://learn.microsoft.com/en-us/openspecs/windows_protocol...

No, I want to be able to @import "tailwindcss" without feeling guilty.

> I've rarely found that any template site

Well, meet https://basecoatui.com -- and there's more where that came from.

So, ehhm, no, I'm not ignoring the salient part of your comment: you are ignoring the entire point of my post, which is that if Tailwind had a non-React monetization strategy, things maybe, possibly, might have worked out better.

Also: sure, some places overdo it on the pricing: I distinctly remember walking out of a Rotterdam (somewhere in The Netherlands) establishment due to them charging 25 Euros for a lunch sandwich, like 2 decades ago, despite this not being a fancy place at all. No inflation in sight, just greed and/or an inability to read the target audience...

"Our website templates are built using Next.js, so all of the markup is written using React"

And the individual components that make up these templates don't seem to have pricing attached, nor non-React usage examples?