gwillen

Pharmacies cannot and will not do that (except for insulin, for which it's now allowed in some states, and maybe a few other non-abusable things.) If it's a controlled substance -- which includes most things you'd be worried about withdrawal from -- forget it. If it's a more tightly scheduled drug, you'll have trouble even getting an unfamiliar doctor to prescribe it. It's not that they don't care about your withdrawal syndrome, but they generally care much more about not losing their license.

The satellites will surely have a certain amount of beam steering capability. (You need beamforming for this to work at all, I think.) If you're too far from the border, you may not be able to trick the system into believing you're in the US. (A lot depends on the implementation ... and what governments demand in terms of compliance.)

You can do it in Chrome on macos without the screen going black, if you disable hardware acceleration. I dunno how long that will last, though.

Do you have any writing I can read about your classification? This sounds extremely interesting and useful. (I have some related thoughts, but not 20 years' worth and largely not recorded.)

I keep meaning to write something about this, but: There are two kinds of "why". One is "I understand what you want but I think it's stupid so I'm going to argue with you." That one is insufferable. The other one is "I don't understand what you want, and I need more information to know what to do." That one is inevitable.

Unfortunately the line between the two is very fuzzy, because every request is underspecified, and we fill in the gaps with context and guessing. And everybody has a different threshold for how sure they want to be that they understand the request, before they go off and implement their best guess about what it's asking for.

Name and shame sites that don't support using multiple Yubikeys! I'm pretty sure they're violating the guidelines in the standard if they do that.

The desired class-action status of this suit feels like a stretch to me. Typically, in a class action, the defendant's alleged behavior unquestionably harms the members of the class, which is why it's okay to make them party to the suit without their consent.

In this case, I suspect that only a minority of the members of the purported class actually believe they were harmed by the defendant's actions, and some class members are _paying customers_ of the defendant's product based on the conduct at issue. (Which surely creates some kind of estoppel issue, aside from the dubiousness of the class certification in the first place.)

Could some enterprising attorney get a bunch of members of the purported class to sign on to a brief opposing class certification? (I don't know if that would be an amicus or what, but surely those people have some kind of standing here.)

(Enterprising attorneys: my email address is in my profile.)

I guess the problem here is with "enterprising" -- there's no money there, except to Microsoft, who I imagine might be barred by legal ethics from funding something like this...

Note that the BMC does not always restrict itself to the BMC port. I've worked with machines that have a dedicated BMC port, but also have a BIOS-configurable option (on by default) to let it use whatever port is connected.

Sounds like the flight attendant had an unusually severe case of "making shit up".

> I found it actually worked better if I omitted the x offset from the distance calculation (so just sqrt(y2 + z2)), otherwise objects near the edge of the field of view were weirdly distorted. But I wouldn't suggest doing that in the general case.

I think this is because you should actually just be dividing by y, the perpendicular distance through the screen. Probably adding z to the mix, while wrong, doesn't make it too weird because of the limited set of z values used.

If the result with just division by y looks distorted, then I would suggest fiddling with the value of k, which effectively controls how wide-angle versus telephoto things look.

Disabling it doesn't really work right. It doesn't let you still see history from when you joined; it just lets you see whatever bits of history your client has cached, which resets anytime you restart the client (on desktop) or anytime the client loses state due to memory pressure (on Android, no idea about iOS.) It doesn't really make much sense.

I guess the desktop behavior kind of matches IRC, but it's not what Discord users expect; the mobile behavior is just random, since you can't control when the client is "connected" or not.

I need this on a shirt.

Can anyone translate the amount of NAC the mice got into human terms? Or how the amounts given to COPD patients or the like compares to what OTC supplements have?

I was a fulltimer there around the same time, and I agree. I ended up quitting fairly soon after the G+ real names fiasco blew up, and it felt like a lot of internal "social capital" got burned on that, which was never really recovered.

I don't think the whole place went to hell at that moment, or anything, and your description is maybe a little more dramatic than I'd go with, as to the role of G+... but it definitely seemed like one of the big turning points.

Their site says they will only ship to Austria, Germany, or Italy, and you have to promise you're a medical professional to even get to checkout (I don't know whether it's further enforced if you do have an address they ship to.)

I also got this email yesterday from iTunes Connect, despite the fact that I do not have an account on that service and I don't sell books:

https://9to5mac.com/2022/07/26/apple-book-sellers-tax-britis...

I think they must have sent a whole fuckton of these in error. I got it as well, it seems to be "legitimate" (in that I believe it is from Apple), but my account is not set up with iTunes Connect (and would have no reason to be, and trying to access it confirms this.)

Are you mixing up archive.org (the Internet Archive, a nonprofit company headquartered in San Francisco) with archive.is/archive.ph/archive.today, which ignores robots.txt, and is a for-profit company with unknown owners and an unknown location?

Misleading title:

"The legislation, introduced by Rep. Liz Berry (D-Seattle), makes it illegal for companies to ban employees from discussing “illegal acts of discrimination, harassment, retaliation, wage and hour violations, and sexual assault.” "

> Of course there is a superimposing step, that just means it adds its layer on top of the photo you provide. That's all it means and that's literally what it is doing, that's all I tried to say, heh.

It is not doing this. You are wrong. You are mistaken. You are confused. You do not understand what is happening.

(People have tried to tell you this several times, but you're not listening. shrug One more can't hurt.)

This kind of white-balance fuckery became very apparent last year, when the skies in the bay area turned orange and red from smoke. On many phone cameras, the photos were automatically color "corrected" to be completely wrong, with no option to avoid this.

It's a bit weird -- beta blockers are not technically, from a doctor's perspective, anti-anxiety meds. They suppress the _physical_ symptoms of anxiety, such as increased heart rate. For many people, that seems to have a big impact, and even reduce or eliminate the subjective feeling of anxiety too (specifically when used for performance anxiety; I don't know about other cases.)

I don't think we really have a good understanding of how all this stuff is connected.

Binary logging would be fine if it Just Worked, but my experience is that journald/journalctl does not just work, and when it breaks I don't have logs.

For example, if the system clock is not monotonic, my text logs are still written sequentially in order, and it's easy to figure out what happens. It is the stated view of the journald maintainers that, if your clock is not monotonic, you get to keep both pieces. https://github.com/systemd/systemd/issues/662 (The specific issue described there sounds complicated, but the fundamental problem behind it, which I have hit multiple times, is "if your system can't maintain a monotonic clock at all times, including early boot, then your logs will be mangled.")

Similarly, a text log line is complete the moment it's written, even if the process that wrote it goes away immediately afterwards. Journald, by contrast, performs asynchronous metadata lookups for _each_ log line at some later time, which it apparently does not cache. This means that, when a process dies suddenly, the final messages will not appear in "journalctl -u", because they failed to get tagged with metadata. (I can't find the bug for this, so I haven't verified that it's still open and unfixed at this time. But it has certainly existed for years at this point.)

So no, in principle I have no objection to _competent_ binary logs. Journald does not meet that bar.

Note that not every journald/journalctl is created equal. It's easy to end up with logs written on one computer that journalctl on another computer can't read, even if the latter is a newer version, depending on which settings each one was compiled with (which is mostly a distro question.)

For an app you haven't used in awhile, you'd probably uninstall it.

For an app you're actively using, you'd probably accept the update, but there would likely be pressure on the devs from the percent of people who would uninstall it instead. I think the hope is that this would cause them to think twice about bloating for no reason.

Good catch, it sure reads like an editing error for "not likely", meaning the opposite of what it says.

FYI, 30mg IR (immediate release) of Adderall is an absurdly high dose. If it was all-day it's merely a very high dose, much too high to start on.

The Bitcoin community has moved / is moving to Libera; I think #bitcoin was the second-largest freenode channel, after #ubuntu.

Andrew Lee has now unilaterally rewritten Freenode policy to retroactively justify his actions:

https://github.com/freenode/web-7.0/commit/1194a3e71a427a669...

My sense has been that the things we need to know are mostly pretty clear. There are things we don't know, but it seems that Andrew Lee is the _reason_ (or a reason) that we don't know many of those things.

- Who controlled nickserv/chanserv? I'm not sure, but my impression is that it was probably christel (who was head of Freenode staff) until she resigned, then tomaw (who became head of Freenode staff at that time), until he was served with threatening legal papers ordering him to deliver them to Andrew Lee.