Sounds like you did a thorough job as a QA tester. As a software engineer, I love to see it.

The first time I read the headline, I thought it meant that the United staff were attacking the passenger. Thankfully I guess they weren't a doctor.

User agents are essentially deprecated and are going to become less and less useful over time. The replacement is either client hints or feature detection, depending on what you're using it for.

discord on FOSS projects

I don't understand why this was even a thing to begin with. FOSS projects using non-FOSS platforms is kinda weird, especially platforms with unclear financial situations like Discord.

Seems like a TCP/IP stack issue rather than a browser issue... 0.0.0.0 is not supposed to be a valid address (in fact, no IPv4 address with 0 as the first octet is a valid destination IP). The network stack should be dropping those packets.

0.0.0.0 is only valid in a few use cases. When listening for connections, it means "listen on all IPs". This is a placeholder that the OS handles - it doesn't literally use that IP. Also, it's used as the source address for packets where the system doesn't have an IP yet (eg for DHCP). That's it.

You don't get a new Emoji by creating a change .org petition lol

You need to write a proper proposal and send it to the Unicode consortium: https://unicode.org/emoji/proposals.html. If it gets rejected, it's four years until you can reapply for the same Emoji.

I've already got a Forever Mouse though... I'm using a $25 Logitech M705 I bought 10 years ago, before they cheaped out and replaced the metal scrollwheel with a plastic one. Works great. I have to replace the battery once every two years or so. I've got an 11-year-old Logitech mouse at work too.

lol at the DO NOT TRUST keys.

I've learnt over the years that you have to make the example code fail to compile or print out huge user-visible warnings or something like that, otherwise people can and will use it as-is in production, hard-coded keys and all.

Even if you make it print out a huge message, some manufacturers will just comment that out while keeping all the other dummy example data.

I've seen several production OAuth/OpenID servers that accepted an app ID and secret from a "how to set up an OAuth server" tutorial, and in one case the company was using that app ID for all their production services.

You mean Google it then go to the 10th page to find a sketchy site with an article that agrees with you?

Alternate version:

> use the internet

> it works

> thank you furries

(for whatever reason, there seems to be an overrepresentation of furries in network admin roles)

This is likely legacy code. Firefox used to have a lot of issues with WebRTC, so practically all video conferencing systems blocked it. Teams probably has some "block Firefox because it doesn't work properly" check that was written 5+ years ago and none of the current developers are even aware of its existence.

Well-coded ones did feature detection instead of checking the user-agent, meaning they automatically started allowing Firefox as soon as it implemented all the required features.

Feature detection is usually the way to go. If your website / webapp depends on a particular feature, check if that specific feature exists, rather than checking for particular browsers. Browser checks are still needed in some cases, for example Safari sometimes reports that it supports particular features but it really doesn't (or they're so buggy to the point where they're unusable), but that's relatively rare.

Do websites count? Vine fizzled out but it would have been a huge success with today's TikTok crowd.