I think you can also register 10 years in advance, or maybe more depending on the registrar, which would cover all other potential snafus like expired card info.

deleted by creator

This is the joke. Absurdist hyperbole only works with a shared assumption or common sense to play against.

If there’s an intended target of this joke, it’s definitely not medication. It would be the inscrutability of the wording of that clinical guideline, which seems to imply morality is divergent but can be cured with stimulants.

Ah! Been there. Allocating lanes on small systems always seems to have more trial and error than I expect.

And here’s that x4 SFP+ card: https://www.trendnet.com/products/10g-sfp-pcie-adapter/10-gigabit-pcie-sfp-network-adapter-TEG-10GECSFP-v2

can’t find any SFP+ card that is x4

Pretty sure mine is x4. I’ll check.

Edit: confirmed.

The API for the PayPal checkout workflow is too complicated for us, but one of us knows how to manually type in the order details to send you an invoice.

deleted by creator

deleted by creator

Heard some buzz and have been meaning to read up. The speech service has been the primary puzzle piece binding me to proprietary systems, but if it’s time it’s time.

deleted by creator

I bet some FOSS voice recognition projects have matured since last I checked, but the closest I had sketched out in the past required external calls to the local speech kit api on macOS or iOS. We’ll get there. It’s too useful to let big tech have a monopoly on it.

deleted by creator

The FOSS-only crowd might flame me for this, but I’d argue this type of scenario is a legit use-case for voice assistants, because “remind me to buy ________” is a fairly easy habit to get into and it’s a single step, fast enough to beat the attention bounce.

Edit: I meant no offense. Reworded to “FOSS-only.”

Maybe yeah. Also got the sense from the strong opinions that this is a preexisting debate, presumably in the context of continuous workloads or cached arrays with minimal spindown intervals. In that context it’s true that rotational disks still often win in energy efficiency and robustness (assuming we’re comparing them to consumer SSDs and not the latest enterprise u.2 stuff that’s rated for continuous work).

Not sure what everyone is arguing about here. Clearly SSD is better for intermittent r/w, whereas HDD can be more efficient at continuous r/w (especially in terms of watts/TB)

Just looking at specs should be enough to see that. SSDs can idle in ready state at close to 0 draw (~0.05w) whereas HDD requires continued rotation to remain ready. So consider an extreme case of writing for 1 minute then maintaining ready state for the rest of the day. For that the SSD will be far more efficient, obviously.

I don’t know, but I’d guess the buffered chipset controller has more stability during certain power state transitions.

deleted by creator

Dammit, I came here hoping to see at least one “I have a very special set of skills.” Oh well.

Yeah I’d cut bait, rebuild from latest tapes. But also…

I’d put the corrupted backups in an eye-catching container, like a Lisa Frank backpack or Barbie lunchbox, to put on the wall in my office as a cautionary tale.

I grew up with traditional/viewport scrolling but IMHO it was better suited for single-layer, static layouts. Natural/content scrolling has the advantage in modal, dynamic layouts with nested scrolling context, which are now the norm.

Explanation: once we introduce multiple layers of content overflow, scroll events control (at least) one active context inside the viewport. Boundaries of scrolling contexts can be ambiguous, especially when scrollbars are hidden. If the user must “move the viewport over the content” but can’t easily predict which viewport will move, the interface will feel less intuitive to them. Natural/content scrolling bypasses all that: forget the viewport, forget active context, just focus on the content and move it around to see what you want.

This is how I learned to stop worrying and love natural scroll.