tool

I don’t even ask for that anymore because it rarely leads to good ends. What I do now is send an email summarizing the dumb bullshit that they want me to do, describe the detrimental effects that it will have in excruciating detail, ask if there are any corrections and if my understanding is correct, and say that if I don’t get a reply from them by X time, I’ll do $DumbBullshitThing at Y time/date. It gets CC’ed at least one level higher than them in the food chain and also to my personal email address for CYA.

It puts the onus on them, creates a paper trail, and also places the blame on them when shit blows up because they asked me to do $DumbBullshitThing when the consequences were clearly laid out.

It’s so rare for me to have to use the modulo operator I’m actually excited when I come across a situation where I can.

You should settle on Liftoff because some of my code is running in it!

Or not. But it’d be pretty cool if you did.

Not sure what version you’re on, but the “compact” view in Liftoff now (I’m on version 0.10.9) is actually compact:

It’s true, at least for me. I can actually control the focus now instead of digging down a rabbithole of <random topic here> for 6 hours at 3am.

If I’m going down that rabbithole now, it’s because I want to.

Oh man. I am a man that loves tacos and just southwest flavors in general. I have had a lot of tacos from a lot of different places. New tacos, traditional tacos, American/gringo tacos, different culture’s version of tacos, etc. If it’s a style of taco, I’ve almost certainly had it.

The Burger King taco is the only taco that I’ve ever thrown away and refused to finish eating. It is an abomination.

Man, the code in that project is really something else. Looks like something hacked together in a weekend

I think I’m going to fork it and make it… not that.

The stock Pixel phone app has this. If you don’t use the stock phone app, you can’t use this feature.

Just added it to the massive Google graveyard next to Stadia, wave, hangouts, plus, music, etc etc

I am shocked and appalled that Google Reader didn’t get called out in this list and is relegated to the “etc” category.

It deserves more than “etc.”

Gotcha. I’m actually in the process of moving away from Namecheap because of an experience I just had with them. I tried to register a domain about a month ago (the domain my Lemmy instance is on) and it stopped the registration process immediately after I hit the Pay/Checkout/whatever button and told me to contact their support team to register it.

The error message said it was because the domain name was too similar to something that already existed, and that the support team would have to decide whether I’d be allowed to register it or not. So I went to another registrar and registered it with no issue. I really didn’t like that, and it’s enough to make them lose me as a decade+ long customer. I already use Route53 for DNS for all my domains, so it’s not like I was using them for anything else other than a registrar, so untangling that shouldn’t be too much of a pain.

It only costs $6 a month plus the $35/yr for the domain name

My man, you are getting absolutely bent over a barrel by your registrar. You could get that domain significantly cheaper at a place like Porkbun or Namecheap.

just raise awareness about tools like this one https://lemmyverse.net/

I also think that something like LCS or Lemmony should be recommended and/or included in the default Lemmy docker compose file.

That way, when new Lemmy servers get spun up, they will automatically get seeded with content and communities from other existing Lemmy servers.

That’s exactly why we need to give them the boot.

Hard disagree. If you’re running something business-critical, the support that you get with a RHEL license {or any other vendor, for that matter) is worth its weight in gold.

If you can’t fix something, you don’t want to be looking for solutions by sifting through forum posts directed at home users when the business is losing thousands of dollars per hour. That’s what the license is for, and that’s what you pay for.

It’s a decade later, and I’m still bitter about Google Reader’s unceremonious execution.

If it’s that old, I’m betting it doesn’t use HTTPS for its connections. You could do a network packet capture on the XP machine (or if you can find one, hook it up to a network hub with another computer attached and capture there) while performing the “clear error” action and find out how it works/what you need to send to it to clear the error. You could also set up a SPAN port on a switch and mirror the traffic on the port going to the printer to capture the traffic, if you have a switch capable of doing that. If not, you can get one off Amazon for about $100.

It’d be pretty simple to put together a script that sends the “clear error” action to the printer after seeing how it’s done in the packet capture. I’ve done this numerous times, the latest of which was for a network-connected temperature sensor that I wanted to tie into but didn’t (publicly) expose an API of any kind.

Throw in a mysterious comment that says “Don’t change anything below this line or everything breaks” and it’s complete.

“We don’t know why this works, but it does, don’t touch it.” would also be acceptable.

Some places are insanely polluted to the point where you wonder how a whole company could be so braindead and essentially poison themselves.

“That’s the future guy’s problem, my problem is making money.”

No need to wonder. That’s how.

Places like that never learn their lesson until The Event™ happens. At my last place, The Event™ was a derecho that knocked out power for a few days, and then when it came back on, the SAN was all kinds of fucked. On top of that, we didn’t have backups for everything because they didn’t want to pay for more storage. They were losing like $100K+ every hour they were down.

The speed at which they approved all-new hardware inside a colocation facility after The Event™ was absolutely hilarious, I’d never seen anything approved that quickly.

Trust me, they’re going to keep putting it off until you have your own version of The Event™, and they’ll deny that they ever disregarded the risk of it happening in the first place, even though you have years’ worth of emails saying “If we don’t do X, Y will occur.” And when when Y occurs, they’ll scream “Oh my God, Y has occurred, no one could have ever foreseen this!”

It’ll happen. Wait and watch.

You’re literally describing the system that controlled employee keyscan badges a couple of jobs ago…

That thing was fun to try and tie into the user disable/termination script that I wrote. I ended up having to just manipulate its DB tables manually in the script instead of going through an API that the software exposed, because it didn’t do that. Figuring out their fucked-up DB schema was an adventure on its own too.

“No, I can’t come out tonight, I’m optimizing my CONFIG.SYS file so I can have a mouse AND my Soundblaster work at the same time!”