WTF Bites
-
I'm all for killing off everyone who still can't use a smartphone and does their shopping lists on paper.
You can take my paper shopping list out of my cold, dead hands!
... oh, wait!
-
@LaoC I'm all for killing off everyone who still can't use a smartphone and does their shopping lists on paper. Fortunately, it'll happen on its own within a few years.
You don't have any female household members, do you?
Not anymore, obviously.
-
@Kamil-Podlesak said in WTF Bites:
@LaoC I'm all for killing off everyone who still can't use a smartphone and does their shopping lists on paper. Fortunately, it'll happen on its own within a few years.
You don't have any female household members, do you?
Not anymore, obviously.
Nor in future, obviously.
-
@LaoC I'm all for killing off everyone who still can't use a smartphone and does their shopping lists on paper. Fortunately, it'll happen on its own within a few years.
You don't have any female household members, do you?
Officially, no. It messes up welfare eligibility.
-
The UX geniuses at Webex have replaced the title bar of the meeting window with a button that can be used to see, briefly, the title of the meeting (among other things).
If only there were some area where they could display the title of the meeting without user interaction. Some kind of, I don't know, bar...
And don't get me started what on what the UI does when I switch to a different monitor with a different DPI (spoiler: all hell breaks loose).
-
When you backup a MS SQL database, it will also back up the (embedded) users too. Of course it can't get back their passwords, only the hashes, so it saves those. But for importing the backup to a new database it creates the users as if what it has was the original passwords…
For a bit of extra confusion, there are "users" on database level and "logins" on server level. So if you do a quick google for how to change password in MSSQL, you get the wrong term, and if you write "alter login" instead of "alter user", you get a rather uninformative error message (no surprise; MS is known for those).
-
This post is deleted!
-
But for importing the backup to a new database it creates the users as if what it has was the original passwords…
So just accept the hash too, what could go wrong?
-
So just accept the hash
tooinsteadI said new database. It does not have the users (yet), so it does not accept the original passwords, only the hashes.
-
So just accept the hash
tooinsteadI said new database. It does not have the users (yet), so it does not accept the original passwords, only the hashes.
So, in other words: you know all the passwords, yet the security audit passes because you use password hashing. Sounds like a quality-of-life feature for admins.
-
In the normal pricing, $415/y is barely any savings at all from 34.99*12 = 419.88. But what are they thinking with the yearly promo price, compared to the monthly?
-
@hungrier cancer anytime.
-
@hungrier Robots (i.e., those who can math) need not apply.
-
But what are they thinking with the yearly promo price, compared to the monthly?
I'd guess the $1.99/month rate doesn't last a full year. I'd further guess that it lasts 3 months. 3 months at $1.99 and 9 months at $34.99 would be $320.88, so $290 would still be a discount. 4 months at $1.99 and 8 months at $34.99 would be $287.88, so about the same as the yearly rate, which would no longer be a bargain. If the introductory discount lasts longer than 4 months, you'd have to be seriously innumerate to take the yearly rate.
-
@HardwareGeek I think you're right about it being 3 months. I took another look at that same link and now, instead of the modal popup I got this at the bottom:
-
@hungrier I got that too, but didn't pay any attention to the pricing, let alone do math on it, because I didn't care; I had (and still have) no intention of subscribing.
-
@HardwareGeek said in WTF Bites:
@hungrier I got that too, but didn't pay any attention to the pricing, let alone do math on it, because I didn't care; I had (and still have) no intention of subscribing.
I'm used to bringing up Firefox's settings and deleting all 'bloom' cookies before clicking a link. Every time.
-
@dcon Private/incognito FTW.
-
@HardwareGeek said in WTF Bites:
@dcon Private/incognito FTW.
Thought I remembered them screaming at me last time I tried that. "You can't browse this site in private mode!"
That will make life easier...
-
@dcon Didn't for me. Maybe Firefox sent them the last cookies saved in non-private mode, so they didn't realize it was private.
-
@HardwareGeek said in WTF Bites:
@dcon Didn't for me. Maybe Firefox sent them the last cookies saved in non-private mode, so they didn't realize it was private.
Could also be that bloomberg changed their site. Or a FF upgrade broke their detection.
Or .Either way, I'm glad I don't have to much with cookies first anymore.
-
-
@HardwareGeek said in WTF Bites:
Or a FF upgrade broke their detection.
Why not? Breaks everything else.
Breaking cookie bullshit is a feature.
-
@hungrier So I did it. Note the fine print at the bottom changes depending on which option you have selected.
-
Nailed it.
-
@HardwareGeek said in WTF Bites:
Nailed it.
-
-
-
@Zerosquare said in WTF Bites:
Under no circumstances should anyone be encouraged to write to Muse and tell them with behavior like this they can go and shove their software.
Wouldn't want to promote Cancel Culture after all
-
Under no circumstances should anyone be encouraged to write to Muse and tell them with behavior like this they can go and shove their software.
Wouldn't want to promote Cancel Culture after allI've a problem with that; I wasn't using their software before and it was vanishingly unlikely that that would have changed even without their BS.
-
@dkf Unfortunately, I am. Their software is good, and I have been, occasionally, an active participant in the online community for it.
The problem isn't the software, itself; it's their website where you can publish your music. The software is FOSS and can be forked (and has been, I guess, maybe, but I haven't yet tried tracking down any forks) and Muse told to go fork themselves.
One can also publish one's music elsewhere. But elsewhere (unless your music is marketable enough to attract an actual music publisher) doesn't have the visibility that musescore.org has. It's similar to social media — "You don't like the way Farcebork runs their platform? Go to Parler or whatever." — you can do that, but far fewer people will see it.
Not that that's particularly relevant to me. I'd have to write some music worth publishing to worry much about the publishing platform. Although I had been planning to put stuff on musescore.org if/when I ever actually finish anything.
-
@HardwareGeek said in WTF Bites:
Although I had been planning to put stuff on musescore.org if/when I ever actually finish anything.
Where were you planning on getting a soul? Don't you need one to compose, that or talent?
-
Firefox suddenly crashes and then keeps crashing immediately on startup. On a hunch I run
debsums -c firefox-esr
, and get an answer: two of its*.so
s are damaged. Nothingapt --reinstall
can't fix, right? Except the crappy university Wi-Fi has just crapped itself again, and I need to run a JavaScript-capable browser to log in. And I need Internet access before I'll be able to run that browser. What would Yossarian do?More on point, how did that happen? I was suspecting RAM because I now see stuff like
BUG: Bad page map in process
in the logs, but that shouldn't have damaged the files, right? I could also suspect the SSD (had bought that one in 2016), since now the files are damaged, but it wouldn't explain the kernel memory corruption, would it? Or maybe it's the elderly Wi-Fi chip shitting into the memory by means of DMA. Or something else. Of course, the S.M.A.R.T. attributes are stellar, and Memtest86+ seems to be passing (haven't ran many tests though). Ugh.
-
What would Yossarian do?
Fuck the nurse.
Wi-Fi hotspots were not available on phones of the time. This was not a problem due to the lack of WiFi.
-
that shouldn't have damaged the files, right?
it wouldn't explain the kernel memory corruption, would it?
Once you've got corruption of either critical files or kernel memory, it's pretty much anyone's guess what will happen next. Stuff stops behaving according to specification, sometimes catastrophically, sometimes subtly.
The other component to consider for a fault (apart from your analysis) is the motherboard/chipset. If that fails (which I've seen happen in a coworker's Solaris workstation over 20 years ago) then you get the weirdest errors and they manifest most strangely. It baffled the poor maintenance engineer for weeks, as it tended to only fail when the guy was not in the building…
-
which I've seen happen in a coworker's Solaris workstation over 20 years ago
I always wondered if anyone ever actually used Solaris.
-
which I've seen happen in a coworker's Solaris workstation over 20 years ago
I always wondered if anyone ever actually used Solaris.
Yeah, lots of people had to do real work before Linux.
-
I always wondered if anyone ever actually used Solaris.
It was used a lot in the 1990s. Back then, PC hardware was mostly rather… low in quality compared to the workstation market, so Sun (and other Unix vendors like SGI and HP) pulled in masses of money providing actually good computers to people who could afford it. By about the change of the millennium that was starting to flip over, as particularly PC graphics hardware got to the point where it commonly had enough memory to drive 1024×768 at 24 bits per pixel. (This was also when Linux started to eat the other Unixes alive.)
Everything took a long time to die; hardware was in service after all, and lots of service deployments were structured around the older ways of doing things…
-
WTF bite of the day
I have a personal EC2 instance running Ubuntu that hosts my virtual table top. It's been running slowly for the past few sessions, with odd issues trying to log in.
Today, when I went to switch it over to my nephew (who shares it)'s campaign world, it wouldn't respond at all. Fired up the EC2 console, it's failed its reachability test. Rebooted it and was finally able to get in via SSH. Only thing in
/var/log/syslog
? "Yeah, can't talk to the IP4 network dohicky. Killing everything." (ok, not those words). But basically "watchdog says this is taking too long to respond, so killing it." Which brought the whole system to its knees and cut it off from the outside world. Guess I need to be in the habit of rebooting it every few weeks. Thankfully all the data is in a separate volume or in S3, so no data loss.
-
@Benjamin-Hall well thank goodness for
systemd
-
The other component to consider for a fault (apart from your analysis) is the motherboard/chipset.
Thanks for reminding me. I really didn't want to think of that, because then I'd have to switch to the backup laptop. And something tells me that MATLAB (everyone here speaks MATLAB, and so must I) would be a pain in the eyes on a 7 inch display.
-
which I've seen happen in a coworker's Solaris workstation over 20 years ago
I always wondered if anyone ever actually used Solaris.
At the university the CS terminal servers where running Solaris, iirc. Was nicer to use than the AIX the central servers were running on. But it was also the time the stereotypical bearded Unix nerds had to explain to me how to use this fvwm2 shit and why its usability was 15 years behind Windows. (Okay, they didn't explain the latter. That would require admitting it first.)
@error_bot !xkcd tar
-
-
the stereotypical bearded Unix nerds had to explain to me how to use this fvwm2 shit and why its usability was 15 years behind Windows.
If they used a window manager instead of the console in text mode, they were No True Bearded Unix Nerds.
-
@Zerosquare said in WTF Bites:
the stereotypical bearded Unix nerds had to explain to me how to use this fvwm2 shit and why its usability was 15 years behind Windows.
If they used a window manager instead of the console in text mode, they were No True Bearded Unix Nerds.
I talked about explanining it to me, not what they were using.
But still, with a window manager you can have so many more xterms open than just with text mode consoles. That's why X was invented anyway, right?
-
which I've seen happen in a coworker's Solaris workstation over 20 years ago
I always wondered if anyone ever actually used Solaris.
My first job as a programmer was on Solaris. Very expensive hardware with very poor performance. And extremely loud fans.
-
The other component to consider for a fault (apart from your analysis) is the motherboard/chipset.
Thanks for reminding me. I really didn't want to think of that, because then I'd have to switch to the backup laptop. And something tells me that MATLAB (everyone here speaks MATLAB, and so must I) would be a pain in the eyes on a 7 inch display.
I don't see any reason it would stop being a pain at any display size.
-
@error_bot tar czvf your.mom.tar.gz ./your.mom
-
which I've seen happen in a coworker's Solaris workstation over 20 years ago
I always wondered if anyone ever actually used Solaris.
My first job as a programmer was on Solaris. Very expensive hardware with very poor performance. And extremely loud fans.
That just sounds like you didn't get an expensive enough one. Pretty sure the last Solaris I worked on was on x64
-
@Zerosquare said in WTF Bites:
the stereotypical bearded Unix nerds had to explain to me how to use this fvwm2 shit and why its usability was 15 years behind Windows.
If they used a window manager instead of the console in text mode, they were No True Bearded Unix Nerds.
No True Bearded Unix Nerd would use the console*, they'd use
screen
in a tty.