Yes.
I noticed my authenticator app (KeePassXC) offers the ability to customize the TOTP parameters (SHA function, time step, code size). But no combination of settings seems to produce a valid code.
I assume Lemmy uses the suggested defaults in the RFC 6238 standard?
This is definitely the top of the can. The bottom doesn't have the same taper. There's also no way that thin flange around the rim is one shaped piece of metal. That's definitely the seam between the top of the can and the lid.
What I'm not gonna say is whether the photo is real or altered. I want to assume in good faith that it's real. It's not entirely far-fetched that an un-punched lid blank was crimped onto a can.
Connect, Sync, and Boost all told me to go kick rocks.
Evidently, whatever happened, it doesn't seem to be an issue with your platform.
It only just hit me a month or two ago just what a timezone, as described by IANA, actually is.
I'm from the eastern half of the US state of North Dakota. We run on what we'd collloquially call "central time", often abbreviated CST. That's UTC-6:00 in winter and UTC-5:00 in summer (technically CDT, but whatever).
Long ago I had it passed down to me from on high that the IANA timezone indicator I should use for my local time is America/Chicago. Ok. Easy enough. Why Chicago, though? I long guessed because it happens to be one of the largest localities in the CST block? That is in fact the answer if you read the rationale of the tz database, but I did not know this at the time.
What threw me off, though, is that there are other localities that seemingly map to the same time zone block. Like America/Mexico_City, or America/Indianapolis. What's up with those? When I set my computer system clock to them, they behave just like America/Chicago does. Why are these here? And why these cities, specifically?
Then, imagine the loop I was thrown for when I discovered three timezone definitions exclusive to North Dakota. Those being America/North_Dakota/Beulah, ../../Center, and ../../New_Salem. What the fuck..?? These are literal nowhere towns. Midwest America is the middle of nowhere. North Dakota is the middle of nowhere within the Midwest. And these three towns are the middle of nowhere to the rest of us in North Dakota. What is going on? Why are there three tiny timezones in the middle of nowhere in the middle of nowhere in the middle of nowhere? And they're all right next to each other!
Then, it clicked. What do these three places have in common? These towns all used to be in the next timezone over ("Mountain Time", MST), but later decided to jump over to CST.
There's a humorous story for why this happened. Supposedly, drinkers in the capital city, Bismarck, would stay to bar close. Then, they'd all hop in their cars and drunk drive to the sister city across the river, Mandan, for an extra hour of fun, causing untold chaos in the process. The jump was allegedly to curb this. Sadly, that story apocryphal. In reality, it was just because it was economically favorable to be time-aligned with the state capital city. But I digress...
If you were, say, looking over historic records of events recorded in both Bismarck and Beulah, where records are always taken simultaneously, and your data happened to span back before this switchover, there would be an inexplicable point in time where after it the timestamps would match, but before it, they'd be offset. So, to encode that, Beulah gets its own unique timezone all to itself that indicates this historical switchover exists.
It also explains why there are three tiny timezones all right next to one another. Three counties participated in this switchover, and to make it happen, each one had to individually pass laws to enact it. These laws all took effect on slightly different dates. Thus, if we wish to capture the nuanced time shifts in all three counties, each county needs its own bespoke timezone.
IANA timezones aren't just representations of all the time zones that currently exist. They are representations of every unique permutation of historic clock changes for every place on Earth. That's fucking nuts! Knowing that, I went from being shocked that there are so many timezones to being shocked that the list of timezones is as short as it is!
There's a new RFC in the pipeline that will address this.
It's already been approved, just needs to slooowly crawl its way theough the final publication queue.
I seem to have been screwed over by TOTP.
Hearing that this update was supposed to make borking your account harder to do when setting it up, I enabled it. Put the secret in my authenticator app, got my six digit code, and away I went.
Now, a few days later, having changed nothing on my end, Lemmy.ml won't accept my TOTP code. My session token on desktop is expired so I can't remove it now.
Currently my only lifeline to this account is my logged in session in Voyager, which, as far as I can tell, cannot access the TOTP setting. (Or any profile setting, for that matter... am I just stupid?)
No email to recover from, either. That's on me, I guess. Ugh.
Not sure what my recourse is, if I even have any.
I originally had mine mounted on /, to make them easy to type. But that set one of my highly opinionated friends wretching, so I re-mounted them to /media// to placate him and symlinked them to my home directory instead.
It's frustrating how often Linux systems, when approached with a "where is the canonical location for ?" question, have an answer ancient use cases practically no one has anymore, but no satisfying answer for extremely common use cases like permanently mounted backup drives, where to put web server hosted files, or even where to install applications that don't come from package managers (/opt/? /usr/bin/? /home//.local/?).
1000 is the default ID given to the first-created user on Debian-based systems.
May or may not be the case with other distros. Haven't checked.
The only difference you seem to be highlighting here is that an AI like ChatGPT is only active when queried while an insect is "always on". I find this to be an entirely irrelevant detail to the question of whether either one meets criteria of intelligence.
I had struggled with Gradle off and on for something like five years before eventually learning that Gradle files were executable code files (as opposed to static data files such as .ini) written in Groovy (as opposed to some unique esoteric Gradle lang), and the code within them interacts with implicitly declared objects.
All of that could have been figured out very quickly with a cursory look over the documentation. I just never read it until way past the time I should have. That's on me. I just wanted the stupid magic Gradle incantation that would get my stupid Minecraft mod to compile.
Also, I gotta say, holy crap I hate Groovy. All of its syntax ""sugar"" just makes it hard to read unless you already know what's up. The unique ways it makes code look like not code was the bulk of the reason why I took so long to figure out that Gradle files were code in the first place.
I know you can write Gradle files in Java instead of Groovy, but at this point that just seems wrong. Build files shouldn't look like source files. I have no objective justification for this, it just doesn't feel like the way.
Thank you for the suggestion of Voyager, I have installed it and it looks quite nice!
Pokemon names nearly always deviate from the spellings of their constituent root words in at least one superficial way.
There are a couple odd exceptions like Electrode and Talonflame, of course. And even more now with paradox mons, but those are, uh, a special case.
My point being, I am confident the "sudo" in "Sudowoodo" is not a nod to
sudoat all, it's just a coincidental side effect of corrupting "pseudo". As they do.I suppose if one really wanted to know, one could just ask Nob Ogasawara himself, the one who named Sudowoodo. He's on Twitter...