Because the lowest common denominator is much MUCH lower than you think it is.

This means it’s easy to indoctrinate and easy to maintain that for a massive number of people.

Scientific illiteracy is extremely high, and actual “6th grade reading comprehension” is the highest level of literacy for > 50% of a country like the U.S. and ~20% are low literacy or actually illiterate.

This means that half of everyone in the U.S. can read and understand what they read at or below a 6th grade level. This isn’t “reading big words”, it’s “tell us about what you read”, “what is the relationship between x & y” type questions.

This comment for example, up to this point only, would be difficult to understand & comprehend for > 50% of people in the U.S. (it demands an 11th grade reading comprehension). And may be misread, misunderstood, or not understood at all.

People are driven to religions to cults and alt conspiracy theories when they don’t understand how the world works around them. They latch onto extremely simple often misleading or incorrect ideas of how the world works because they can understand it and it “makes sense” within their sphere of ignorance (we all have one, this isn’t meant to be a disparaging term).

This means that the problem is that humans are just not smart enough to escape religion yet. It’s the simplest answer, and it appears to be correct.

I don’t think the concern over pinging 1.1.1.1 is warranted.

ICMP is pretty raw Network traffic, meaning you’re not really causing much actual load here.

You can’t even really try to DDOS with normal ICMP packets. You usually have have to max it’s size out at 64KB with an ICMP floor to even think of having an effect. Vs the, effectively inconsequential, 32 bytes of a normal ICMP packet.

You watching a short YouTube video is equivalent Network load as 180 days of pinging for Network up time.

They keep giving us more reasons to sail the high seas.

Naw, they’ll find some way to “incentivize” (punish you for not) viewing ads and enforce it with eye tracking.

Super glue seems appropriate 🤔

“unfortunately your In-Flight Engagement Actions ™️ did not meet the requirements to qualify you for in flight perks such as entertainment and meals”

“Please ensure you are looking directly at the screen while ads are playing to accumulate In-Flight Engagement Actions ™️”

Coming soon to an airline near you.

Ah, the circle of life

They usually do yes however it’s all about prioritization.

You may have hundreds or thousands or open requests and issues.

With tens of thousands of closed issues that were either not reproducible, not actually problems, or largely indecipherable.

There’s usually a feature roadmap which is where most of the development money and time is spent. If it’s an older business application then certain bugs might easily take weeks to find, fix, test, validate, go through user acceptance, A/B test, and then deploy. But fixing is expensive work, so if the bug isn’t severe it’s usually deprioritized next to higher priority work.

Mhm, anthromorphizing insects now.

That doesn’t really resolve the problem of is the media safe.

From a cybersecurity standpoint you should be validating the mime type of the media at a minimum (The actual magic number, not the extension). And running it through ClamAV as well, ideally, before it’s released to your media library.

Client devices probably shouldn’t have admin privileges those should be restricted to the admin UI.

That’s a nightmare waiting to happen when some device pushes an update that deletes your entire library, or a bug in a client does the same.

Quite often, yes, especially for apps.

For nearly a year the Android Amazon app wouldn’t work. It would load, and then when a tracker failed to start, would show a generic error message page.

US bank mobile app wouldn’t login for about 2 months last year.

This happens quite often when apps are built with dependencies they assume will load, and when there is a failure an error boundary catches it and shows an error view.