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.

Ok…

So your point is that a bad logging implementation is bad. And I agree.

I’m not seeing how that’s extendable to implementations as a whole. You’re conflating your bad experience with "log aggregation is bad’.

Just because your company sucks at this doesn’t mean everyone else’s does.

Yeah, ofc it is.

I’m working in a system that generates 750 MILLION non-debug log messages a day (And this isn’t even as many as others).

Good luck grepping that, or making heads or tails of what you need.

We put a lot of work into making the process of digging through logs easier. The absolute minimum we can do it dump it into elastic so it’s available in Kibana.

Similarly, in a K8 env you need to get logs off of your pods, ASAP, because pods are transient, disposable. There is no guarantee that a particular pod will live long enough to have introspectable logs on that particular instance (of course there is some log aggregation available in your environment that you could grep. But they actually usefulness of it is questionable especially if you don’t know what you need to grep for).

These are dozens, hundreds, more problems that crop up as you scale the number of systems and people working on those systems.

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.

Damn, that’s just cancerous

Yeah I had literally no idea what you were talking about until you mentioned the actual name in the comments.

NPM almost universally refers to node package manager in any developer or development adjacent conversation in my experience. Given that both the site, the command, the logo, and the binaries are “npm” makes that more appropriate.

Nginix proxy manager is far to niche to be referred to universally by acronym when it’s only ever used as an acronym when the context for it’s usage has already been defined (ie. In it’s documentation).

This becomes much more clear when you Google the acronym.

It is, but also it’s worrisome since it means support is harder, which means risk of abandonment is higher and community contributions lower. Which means “buying in” is riskier for the time investment.

Not really criticizing, 10/10 points on making something and then putting it out there, nothing wrong with that. Just being a user who’s seen too many projects become stale or abandoned, and have noticed that the trend has some correlation to the technology choices those projects made.

I’ve been looking a platform for personal blog, portfolio, and what not that’s kind of fun to play with without having to build the whole thing myself.

What’s your opinion of this project?

As of today I’m actually in a lucky position where I am now able to set up a secondary NAS at my brother in laws and use that as a backup server that I can back up to essentially in real time.

All it’ll cost me is the hardware and the electricity.

Yes.

I’m sure one can reasonably infer that I do not mean 30 meters.

Conveniently at highway speeds 30 minutes and 30 miles away are essentially equal.

I’ll try and use appropriate notation next time

I might be crazy but I have a 20TB WD Red Pro in a padded, water proof, locking, case that I take a full backup on and then drive it over to a family members 30m away once a month or so.

It’s a full encrypted backup of all my important stuff in a relatively different geographic location.

All of my VM data backs up hourly to my NAS as well. Which then gets backed up onto the large drive monthly.

Monthly granularity isn’t that good to be fair but it’s better than nothing. I should probably back up the more important rapidly changing stuff online daily.

The error posted in the app is from the website itself. It’s likely that the password manager is injecting something into the page which is causing errors.

There are many ways for this to go wrong, it has nothing to do with the web service itself.

We’re on Lemmy are they afraid of being censored because they are writing software catered for NSFW uses?

Other social media’s chilling effects are pretty deeply engrained unfortunately…

And there’s also the live sync extension which allows you to have live document syncs in real time via your own self-hosted CouchDB instance