Try submitting a pull request for something in one of the core repos.

They behave as if every line of code in your commit is a sentence proclaiming “Why yes, your wife is a whore, your dog doesn’t love you, AND your baby is ugly.”

I’m not kidding, there’s no hyperbole in that statement. Go read some of their declined pull requests threads for some entertainment.

Even those who try to contribute to the project get eventually feeling pushed out.

Submitting a pull request to one of their repos on Github was really an experience, and I can tell you that I will never submit another one to the Lemmy project while they’re still the lead devs based on that experience.

It would be better to our them on blast on social media since that sometimes gets the companies attention to try and fix PR.

Works almost every time. I had a ticket with a vendor open at work for just about 3 months, and then only replies I’d gotten on the ticket was the “We’ve received your support request which we’ll promptly ignore!” autoresponse upon opening, and then another auto-response a month later saying the ticket was being assigned to another department. I’d replied to the ticket ~20 times asking for updates in that time.

I finally got sick of essentially yelling into an empty room and called out the company, their marketing team, their support team, and their CEO on Twitter, making sure to @ each one of them in the message. I got a reply from their CEO and an actual human responded to the ticket less than an hour later.

It’s shitty and a last resort, but it’s generally very effective.

I have a Hisense and had a similar experience. I was watching something fullscreen on an HDMI input, and then it suddenly switched inputs and showed a fullscreen firmware update prompt. I had no choice available other than to agree to update the firmware, no cancel button, couldn’t change inputs, nothing, the only choice was to update the firmware. So I unplugged the TV.

About 10 seconds after I powered it back on, the exact same update prompt happened, still with no choice to decline it. I pulled power and booted it back up one more time just to be sure, met with the update prompt again.

This made me very angry.

The next time I powered it on, I had a packet capture running to see where it was phoning home. I created a firewall rule blocking all the hostnames it tried to connect to at startup, pulled the plug, and then booted it back up. No more update prompt, and it hasn’t happened again. Good thing they don’t download and pre-stage the new firmware, I guess.

Let me know if you want the hostnames and I’ll PM them to you.

Eh, it depends. Other low-level things (systemd, glibc, etc) need a reboot too.

It’s likely because they use it as the primary/unique identifier for the account, which is just dumb. It’s like they’ve never heard of a UUID/GUID before.

BTW, any authenticator app works when it tells you to use one. They all use a standard, so it doesn’t matter which one you use.

Eh, it’s a little more nuanced than that, there’re more standards for MFA code generation than just TOTP.

And even within the TOTP standard, there are options to adjust the code generation (timing, hash algorithm, # of characters in the generated code, etc.) that not all clients are going to support or will be user-configureable. Blizzard’s Battle.net MFA is a good example of that.

If the code is just your basic 6-digit HMAC/SHA1 30-second code, yeah, odds are almost 100% that your client of choice will support it, but anything other than that I wouldn’t automatically assume that it’s going to work.