Information Overload - Beehaw style
douglasg14b @ douglasg14b @beehaw.org Posts 2Comments 67Joined 2 yr. ago

What about misinformation?
Without downvotes it will slowly bubble up to the top because the only barrier is finding enough people gullable or ignorant (precisely, not demeaning) enough to believe it. Or if it's "pop culture misinformation", it rises to the top by virtue of it being popular misinformation.
Both of those are not ideal for quality conten, or fact based discussion and debate when vote counts exist. As more often than not more votes = more true to a layman.
We've seen this on any other platform that have "the only direction is up" mechanics, because the only direction is up.
Another risk is promoting misinformed communities, who find comfort in each other because their shared, incorrect, opinions of what should be fact based truths find common ground. I don't think those are the kinds of communities beehaw wants. Thankfully community creation is heavily managed, which may mitigation or remove such risks entirely.
What I'm getting at is what will the stance be here? If beehaw starts fostering anti-intellectualism, will that be allowed to grow and fester? It's an insidious kind of toxicity that appears benign, till it's not.
To be clear I'm not saying these things exist or will exist on beehaw in a significant capacity. I am stating a theoretical based on the truth that there is always a subset of your population that are misinformed and will believe and spread misinformation, and some of that subset will defend those views vehemently and illogically.
I would hate to see that grow in a place that appears to have all the quality characteristics I have been looking for in a community.
The lowest common denominator of social media will always push to normalize all other forms and communities. It's like a social osmosis. Most communities on places like Reddit failed to combat and avoid such osmosis. Will beehaw avoid such osmosis over time?
Yessss
How about forgetting words? I'm in a profession where trust of your intelligence & knowledge is rather important to "getting shit done". And nothing tanks your reputability then stumbling mid conversation/explanation/argument because you forgot words and terms...
It's super frustrating, and sometimes I spend over an hour trying to find the word.
Yeah, diagnosed at 31 here. So many coping mechanisms that do or don't work.
Unfortunately during the summer I have to choose. My meds or decongestants to at least reduce the misery from bad seasonal allergies.
Can't make doctor appointments, can't remember to call a contractor to fix the porch, forget to call people on their birthdays, forget to cancel subscriptions, can't remember to do simple task, or return things under warranty....etc I always remember things in the middle of the night, when you can't call any of the businesses or people you need to call, or drop anything off.
Work is my hyperfocus time, so all the other tasks and todos I have vanish from my brain till after, even with meds.
It's frustrating man, I feel ya, shit sucks.
The word "gut" is a red flag for pseudoscience. There's no such thing. Talk about specific organs and areas of the digestive system, not a "gut".
Is it though? Or is this overconfidence in knowledge? And you are just creating misinformation?
Given this is a term used in the journal of Nature, the U.S. National Institute of Health, Universities (ie. Cambridge, Oxford), The American Society for Microbiology (ASM), the EU European Science Commission, the UK National Health System, and is used within countless publications to succinctly describes the "human microbiome" which is largely composed of the microbiome in the digestive tract (otherwise known as the "gut"), you are most definitely wrong.
It's an actual term with a definition, just because you aren't aware of it doesn't mean it doesn't exist...
Is a "digestive tract" also not a thing because it doesn't describe a specific organ? How about the endocrine system? What about your immune system? Your body is made up of systems that interact in complex ways across organs, and often the organs themselves are not the important bit either.
I would suggest you at least read the Wikipedia page before spouting such nonsense as this.
This is one of the times I wish the downvote button was enabled, this sort of nonsense shouldn't be able to bubble up to the top by virtue of just finding enough people who also don't know better.
Applies to software engineering as well!
Often the "logical reasons why" are you fooling yourself into thinking you know all the invariants, when you really forgot or misunderstood at least one.
It could, and will. Hopefully they are taking advantage of CDNs for image delivery so they aren't paying high egress costs and can keep it in slow, cheap, storage.
I'm honestly surprised that Lemmy hasn't embraced distributed, community, hosting. Many existing niche communities (outside of Lemmy) operate with the ability for others to run their service to serve up images and media, or to act as workers for computationally expensive operations like compression or encoding (Which will also save you a ton of space). Even gamificating it in the case of e-hentai.
Hard drives (Tapes even more) at home/office are incredibly cheap compared to cloud storage costs (even including networking, server, redundancy...etc hardware costs), but come with reliability concerns, which is where a distributed community becomes critical. Though you'll always have to have them stored somewhere like Backblaze B2, or somewhere slower/cheaper/frozen to ensure safety.
Honestly surprised it isn't using redis already 😧
Often end up plopping redis in as an ad-hoc caching layer pretty early during application development for backends that are expected to be load balanced. It's super simple to use, has low resource costs relative to it's load capacity, and solves for a lot of low hanging fruit as far as DB access performance goes.
Opinion:
It should definitely be a reasonably high/critical priority roadmap item 🤔. The time cost is negligible assuming your ecosystem has a decent redis library, if you're an expert in the codebase (major/primary contributor) it can be as easy as a few days to do a cleanup (assuming redis/lib familiarity/docs) and knock out all the low hanging fruit. And the benefits can be enormous, like 10x, 50x load decreases enormous.
Alternatively:
Read replicas as @kool_noot said. If not, some dev work is required.
This can sometimes work as a quick fix to address application perf problems without adding infrastructure, but time cost is more or less based on codebase quality & conventions, since you'll be touching a lot more queries to make this change. And you'll need to slap in a config that handles deployments without a read replica.
Then users of Lemmy could have as many read replicas as they want behind a load balancer/proxy which lets them scale in that direction going forward.
This is actually a common solution for read performance anyways.