hunter2_
Joined 3,482 karma
web and audio
- hunter2_Reminds me of when a group is divided into two parts, dubbed group 1 and group A, such that neither feels secondary.
- It seems the common thread is that the f means to introduce G, but not exactly. In my own research, the AI summaries are about as sloppy as I've ever seen, due to the vague and often regional differences (with the difference between ft-lb and lb-ft sometimes being described as relevant, as well).
- Ah! I guess that explains the "f" for "force" in the imperial abbreviation "ft-lbf", to distinguish it from work. I wonder if there's ever been an analogous variant for metric such as "Nmf"...
- So when I torque all 20 of my car's lug bolts to 120 n-M, I've exerted 2/3 of a W-h? So if it takes me 4 minutes, I'm averaging 10 watts? That's neat. I wonder what the peak wattage (right as the torque wrench clicks) would be; it must depend on angular velocity.
- If you want the TV to be on your network (for casting or streaming or whatever) and you also want to filter that traffic (allowing connections only to the services you want to use) then you need it to be on your own network (wifi, if there's no ethernet port) and not on someone else's network (cellular).
- It wouldn't even need to use any sort of standards-based DNS-like thing at all, if they control the server (on a stable IP address in the TV's firmware) and the client (the TV). It could be any data scheme (probably https for simplicity and blending in) along the lines of "give me all the other IP addresses I'll need, which aren't as stable as the one in my firmware."
Regardless, what is the benefit of putting the TV on the network but preventing it from doing DNS lookups anyway, even if you could be sure you succeed?
- > the government [...] only know[s] that I needed to verify an assertion about my age
This is problematic if a majority of things needing age verification are looked down upon; for example, insurance companies would love to know what people don't do things needing age and therefore don't buy alcohol (at least not online).
- I assume eliminating the "loss leader" concept is the main effect, since shops shouldn't otherwise price things as losses regardless? In which case it seems like it's meant to maintain some friction / overhead for people wanting to visit the stores, possibly reducing consumption at least for the price-sensitive.
- I'm envisioning a MySpace / AOL profile situation, if a hole is discovered in the input sanitization.
- The restaurant-next-door analogy, representing fungibility, isn't quite right. If BofA is closed and you want to do something in person with them, you can't go to an unrelated bank. If Spotify goes down for an hour, you're not likely to become a YT Music subscriber as a stopgap even though they're somewhat fungible. You'll simply wait, and the question is: can I shuffle my schedule instead of elongating it?
A better analogy is that if the restaurant you'll be going to is unexpectedly closed for a little while, you would do an after-dinner errand before dinner instead and then visit the restaurant a bit later. If the problem affects both businesses (like a utility power outage) you're stuck, but you can simply rearrange your schedule if problems are local and uncorrelated.
- It's just peculiar especially since the repo readme [0] specifically says "Minimal JavaScript - Only when truly needed" and yet it's used for this food category filtering, a feature for which JS is certainly not truly needed.
[0] https://github.com/Local-Cafe/localcafe-lite?tab=readme-ov-f...
- In many analog pro audio applications, it's actually recommended that a shield be connected at one side only, for this reason. By convention but not necessarily necessity, the bond is typically kept at the receiving end, as that's almost always a device with a grounded power cord (such as a mixer). Many DI boxes feature a ground lift switch as a convenient way to achieve this. But you wouldn't want to disconnect it at both ends, as then the shield has no effect at all.
Anyway, if you had problems with your unshielded cables that would be solved by a shield, but your shielded cables caused a different problem due to the bond at both ends, this technique of using shielded cables but severing the shield at one end of them would get you the best of both worlds.
- No, the comment correctly points out that the "Soup" button (and all of its siblings... the food categories) is inoperable when JavaScript is disabled. You're stuck with "All" instead of nice filtering. There are ways to achieve this without JavaScript.
- I'm getting NXDOMAIN, and various online resolution tools [0] show the same.
[0] https://mxtoolbox.com/SuperTool.aspx?action=a%3alocalcafe.or...
- I agree with no JS, but why PDF over HTML? Hard-wrapping for letter-sized paper (ok, a PDF doesn't need to be letter-sized, but most menus are approximately that) with crapshoot reflow options for soft-wrapping in certain viewer apps is pretty dicey on a phone, mitigated only slightly by rotating the phone sideways.
The only benefit I can think of is if it leads to more frequent updates by the restaurant, due to limited skillset.
- I'm fine with an implied "and," but I disagree that "violations" is scoped only to the final item in the series. It's clearly transitive to each item in the series (security violations, etc.). That said, your point stands that the phrase "copyright and IP" could be the final item in the series (with an omitted "and" at the series level) rather than the final two items, although there wouldn't be a compelling reason to do that in this particular case.
- Aside: I'm well aware that it's just about as popular to use an Oxford comma than to not, but this might be the first time I've ever seen someone omit an Oxford semicolon as it really seems odd to me. But Automatic Semicolon Insertion in Javascript is odd to me, as well.
- It's interesting how much different the landscape was in that era: single-device residential environments would have no firewall at all (just a PC with a publicly-routable IP address) and dial-up kind of fueled this due to PCI slot modems, but as the outboard nature of DSL and DOCSIS modems made it easier to build multiple-device residential environments by adding a router, suddenly everyone had a firewall (as a byproduct of NAT). Then you've got malware, which was far more prevalent on PCs through that transition relative to today, but now we've got IoT stuff probably not being updated as it ought to be, potentially hosting malware that serves as a proxy to sidestep an in-router firewall.