Website: https://yellowapple.us
Email: northrup @ the above domain
Keybase: [ my public key: https://keybase.io/yellowapple; my proof: https://keybase.io/yellowapple/sigs/JfN02l9FJTFqFnACyDFYbK7yNYFSlzTvPktWnPQiTZg ]
meet.hn/city/us-Reno
- yellowapple parentAnother possible factor driving the decision to use numbered file descriptors: the logic to validate that a file exists (or can exist) at a given path, is readable/writable, etc. gets punted to the shell instead of being something the program itself has to worry about.
- AFAICT this doesn't affect activating via a KMS server (incl. KMS emulators like vlmcsd), correct?
- It worked on Linux since basically day 1, though I haven't played it in awhile so who knows if things have broken since then.
- Why is any of this legal? This is pretty clearly fraud.
- I've been pondering something similar as a modern approach to fat binaries, basically around a table like
The advantage would be that binaries could be partially fattened, i.e. every function would have at least one implementation in some cross-platform bytecode (like WASM), and then some functions would get compiled to machine code as necessary, and then the really-performance-dependent functions would have extra rows for different combinations of CPU extensions or compiler optimization levels or whatever — and you could store all of these in the same executable instead of having a bunch of executables for each target.CREATE TABLE functions (name TEXT, arch TEXT, body BLOB);As a bonus, it'd be possible to embed functions' source code into the executable directly this way, whether for development purposes (kinda like how things are sometimes done in the old-school Smalltalk and Lisp worlds) or for debugging purposes (e.g. when printing stack traces).
- > There's always the lazy approach of storing JSON blobs in TEXT fields, but I personally shy away from that because you lose out on a huge part of the benefits of using a SQL DB in the first place, most importantly migrations and querying/indexing.
SQLite at least provides functions to make the “querying” part of that straightforward: https://sqlite.org/json1.html
- > Running the same wattage device at 240V instead of 120V would decrease the amperage, assuming the device was designed to handle either voltage.
Well yes, but usually the whole point of switching to 240V is to get more power than what 120V can supply. The people complaining about electric kettles being “slow” in the US compared to the EU would still be complaining if those kettles always pulled the same number of Watts on both 120V and 240V, because it's the Watts that determine how fast the water heats up. The amperage is therefore probably going to be at minimum approximately the same in that case — and probably higher if you're doing something more intensive (and therefore requiring more current) with that new 240V outlet than just running an electric kettle (like running a stove or a clothes dryer or an air conditioner or an electric car charger or a rack of 10+ of those 600W-PSU-laden computers — hence those usually getting beefier 20A+ circuits while everything else in a house might be 15A).
- The risk they'd allegedly take on by letting me use an “insecure” device is far lower than the risk already inherent in, say, the card having an RFID chip in it that anyone can silently scan from a distance unless I happen to have the foresight to buy and use a fancy RF-blocking wallet (that actually does block RF signals), or the card having all of the authenticating info¹ printed directly on it such that anyone who has access to it for the whole three seconds it takes to snap a photo of both sides can then use it to make purchases on quite literally every website that accepts credit cards.
Needless to say: letting me use an “insecure” device for tap-to-pay would considerably lower their risk compared to me not using a device at all and instead using a physical card — even, again, ignoring that my device is in all likelihood considerably more secure (and therefore exposing them to even less risk) than it was in its stock configuration.
----
¹ except for my ZIP code, which is easily guessable if you know roughly where I live — which I don't exactly keep particularly secret!
- Fantastic news! I've been hoping for Exchange support for a long while.
- Yeah, that root detection is the bane of my existence, beyond just RCS. Even entirely ignoring my phone having much stronger security than with the stock OS (and therefore rendering the whole “security” excuse to be complete BS), if I want to take on the risk of using an “insecure” device for payments or whatever then that's my choice to make and mine alone.
- That's a great way to warm up your house if the wires between the panel and the outlet ain't rated for the higher amperage ;)
- More critically: just because a company is worth $1 trillion doesn't mean it has anywhere close to $1 billion in cash at all, let alone able to be earmarked to a given project (at the presumed exclusion of other projects).
Granted, a project like this probably doesn't strictly need all $1 billion all at once, but I'd argue it's better to get whatever necessary funding upfront instead of risking having sunk a partial investment without being able to obtain the rest should the company's financial situation change.
- RCS has been a royal pain for me on Android, too. Partially my fault since I'm using non-default ROMs (LineageOS on my Fairphone 4, which I then replaced with GrapheneOS on my Pixel 9a), but also mostly Google's fault for taking as janky of an approach as possible when it comes to its Messages app (which seems to be the only actively-maintained Android SMS app with RCS support, because of course it is).
The Graphene folks have at least been making progress on getting it working (my understanding is that Messages expects special permissions from Android and Play Services that GrapheneOS has to specifically whitelist without blowing massive holes in the Google Play sandbox, and without those permissions it fails to verify the phone number for certain carriers — T-Mobile included, in my case). Hopefully whatever fix they come up with works for the long haul; it was really annoying to have RCS working fine for all of two weeks only for it to immediately start failing again when the required RCS endpoint switched from Google's Jibe instance to whatever T-Mobile is allegedly maintaining themselves.
- On the other hand, based on supply v. demand I'd expect an MS-DOS attack to be pretty expensive these days :)
- Being within the same order of magnitude is pretty impressive IMO, especially before 6 years' worth of performance improvements.
- > it's basically impossible to remove an instruction
laughs and/or cries in one of the myriad OISC ISAs
- I get the same impression w.r.t. RISC-V v. MIPS similarities, just from my (limited) exposure to Nintendo 64 homebrew development. Pretty striking how often I was thinking to myself “huh, that looks exactly like what I was fiddling with in Ares+Godbolt, just without the delay slots”.
- I think you're taking a metaphor a bit too literally.
- One of the very few things I like about macOS is that it rebinds the CUA key from Ctrl to Cmd, freeing up Ctrl for these Emacs-style text navigation keybinds. It's odd to me that seemingly zero Linux distros/DEs do this by default.
- Time saved also ain't the only factor here. I'll often automate something not because it actually saves a lot of time, but rather because it codifies an error-prone process and having it scripted out reduces the risk of human error by enough of a degree to be worth spending more time on it than I'd save.
- > Every time I get a new system I would have to set everything up again
Sounds like something you could automate with a script :)
- Many years ago I wrote a library I called “Ruby on Bales”¹ specifically due to my frustrations with the state of command-line argument parsing for Ruby scripts. I haven't touched it in a long while; maybe I should revisit it.
----
- A conference in which hackers congregate.
My favorite recent one was Handmade Seattle, but that one's kaput as of this year, and it seems everything else along similar lines is overseas and/or invite-only.
- Love it! I'll absolutely be borrowing some of these :)
On every machine of mine I tend to accumulate a bunch of random little scripts along these lines in my ~/.local/bin, but I never seem to get around to actually putting them anywhere. Trying to knock that habit by putting any new such scripts in a “snippets” repo (https://fsl.yellowapple.us/snippets); ain't a whole lot in there yet, but hopefully that starts to change over time.
- > In place of phone projection, GM is working to update its current Android-powered infotainment implementation with a Google Gemini-powered assistant and an assortment of other custom apps, built both in-house and with partners.
I guess I'll add that to the ever-growing list of reasons why I'll never buy a GM vehicle manufactured in the current century.
- The problem with assessing nerd writing for whether it's AI-assisted is that the AIs themselves are trained on nerd writing.
- The only thing I hate about how boring OpenBSD upgrades are is that I often forget that there are new features I could be exploiting for my server configs. Everything works too smoothly so I'm rarely (if ever) forced to dive into the docs to fix things.
- Congrats on another release. Upgrading my machines went without a hitch :)
- > wait, how did they get the same verse by verse chord progressions to match?
Usually these AI covers don't use AI for the whole thing, but rather specifically for melding the to-be-impersonated voice into some given melody. That's been possible for a couple years now with decent results; one of my favorite examples is that of Plankton from Spongebob singing Disturbed's cover of “Sound of Silence”: https://www.youtube.com/watch?v=7eLRsw9mkmY
Possible that these newer ones are also using AI to generate other musical elements, but it's probably all being combined after-the-fact rather than being generated all at once.
- Meanwhile, I don't really care much about resale value because when I buy a car I typically intend to drive it until it dies.
In this sense, EVs depreciating faster than ICEVs is exciting, since if my current Tacoma prematurely gives up the ghost (or I buy a second car) I can add “snag an EV for cheap” to my list of available options.