@tychotithonus I remember a game where a player had a broken thumb or hand and they where like a center. So he had just a big ass club hand because he didn't need to catch a ball just push other players. Fuck it I found a different one (2013).
As someone who saw the early stages of domain registration (I got my vanity domain from ISI) ...
Watching sub-national .gov domains getting registered willy-nilly - towns, state-level departments, counties, programs/services, all jumbled into the same second level - is excruciating.
[state-2char-code].us used to be a thing - and it automatically kept the namespaces clean and disambiguated. And it made queries like "show me all the domains in Utah" trivial.
Instead, disambiguation is randomly and unparseably overloaded into that second level, in whatever way people feel like (and can achieve uniqueness). Is a "co" suffix Colorado ... or county? 🤷
The .us TLD should have never been privatized.
This account is my favorite self-torture follow. :D
@tychotithonus And, here I thought I was the only one that was super-bothered by this.
CISA is supposed to be defending the .gov domain, but how any anyone even remotely trust it when all these muni's and muni orgs can make silly second-level doms and run anything they want on them?
@jerry FWIW, for the first time, seeing some kind of intermittent cache inconsistency - immediately after editing a post, reloading that post sometimes shows the previous version, and sometimes the current version. (Opening the post to edit is consistent, but display definitely isn't)
@tychotithonus I am not able to see anything anomalous in logs. My best guess is that the CDN was not able to get an update after you submitted the edit and so served you a cached copy. I'll keep an eye on it and see if there's a way to detect such a thing
ISTR that CISSP and some other tech-specific certs have a "violate our code of ethics, lose your cert" clause. But I have no memory of that actually happening. Does anyone know of a case where violation of a code resulted in a loss of tech/cyber certification specifically?
Being found to have violated laws is a deliberately public process, in part because visible censure within the group has cultural reinforcement value. For example, in the license plate club I belong to, the list of people who have been ejected from the club for cause is in every issue of our print magazine (to ensure that those ejected for cause cannot continue to predate on unsuspecting members!)
If loss for cause of a CISSP/etc. cert is invisible to other members ... what's the clause even for?
After the latest update, I'm unable to edit posts using the PWA if the post is over a certain length - the edit option appears to be getting pushed past the bottom of the rendering of the pop-up? @jerry
more and more as i try to help my mom deal with all the "new features" in her computer and phone that don't work for anyone with any sight, eye/hand, or skin chemistry issues, i'm back to this:
'no developer of any device software/OS that human beings use is allowed to touch a single line of code until they have spent 6 months doing user support at an assisted care facility'
Back in 2010, I had issues with seniors whose fingerprints were so worn thin they couldn’t use the fingerprint scanners to clock in.
It’s fascinating and frustrating that people forget that, unless they’re unlucky, they too will be an old and have the coordination and physiological issues they disdain elders for having,
TIL Gmail assumes any "From" email name of the form "String1, String2" means "Last, First".
So when it shows the "first names only" collapsed list of recipients, any "First M. Last, Title/Honorific" - such as "Trapper John, MD" - shows up as just "MD".
@tychotithonus oh, sure, this is part of what makes social media bearable at all. I can even log into Shitter, make sure I am in following mode and get a non-Nazi experience.
And by "make sure" I mean "forget to do it, scroll a bit, and get annoyed by mundane minutiae within less than five tweets". Even in the deliberately created cesspool careful curation still works.
Fewer and fewer web developers are testing their code with tracking blockers and browser JavaScript control frameworks enabled. (For some of them, failing to work when tracking
sites are blocked may even be a deliberate feature!). More and more, basic site functionality is degraded or entirely denied.
Are any of those blocking frameworks moving towards not just blocking, but emulating function calls with dummy return values? (Sort of like some mobile app privacy controls have to reply with dummy data)