I’d rather guess that it’s the wrong error message. Like e.g. there’s a communication error with a downstream service and they just catch Exception broadly and convert it to this error message. That would also explain why the non-filled value defaults to 0.
We had something similar where there was a check that checks whether the password is the same as the user name, but then it showed the “Password is too short” message to the user instead because of an overly broad try-catch.
Parthenogenesis only makes sense if the unfertilized offspring is male. Because that way one female can create males to fertilize her to make females.
The other day when asking about the sex ratio of chickens, it told me that fertilized eggs turn into male chickens while unfertilized eggs become female chickens.
Yeah, I had the same thought as well…
Exactly. That’s why your comments have a ton of downvotes and hardly any upvotes.
Go back to reddit.
No, you don’t get to dictate what everyone else on Lemmy is going to get.
You are not a savior, you are a spammer.
This is not how Lemmy works. This is not how anything about Lemmy works. Please, look at how ActivityPub works, what instances are, what communities are, when content from a community is copied to another instance and how scaling on Lemmy works.
Come back to continue the discussion when you have an idea what you are talking about.
Repost communities have been tried before, dozens of times. Literally every two weeks some new user comes along, thinks they are the first one to ever think of this idea, writes a bot and trashes all the feeds with whatever that guy thinks is cool.
People don’t want any content, they want worthwhile content that they can engage with and have meaningful discussions about, not their whole feed spammed full with pure copy paste.
Imagine you want to sell people on the concept of e-mail. There’s not a lot of messages going around, so you come along and say “People want more e-mails” and start spamming like crazy. “Here’s a hundred cat videos for you! There’s a few dozen chain emails for you! Here, take a few hundred messages from ‘hot singles in your area’!”
Do you not understand the difference between good organic content and spam?
Have you ever looked into the tech behind Lemmy? The way it’s set up it is already at a breaking point for non-profit instances.
If Lemmy had Reddit size, it would literally crash and burn, and the problems are on a concept level, so they could only be fixed by trashing the whole concept and rewriting from scratch.
What do you think is more appealing?
A subscribed feed with a few dozen posts about various meaningful topics with a few dozen comments, that were shared by an OP who cares about the subject, who replies to comments, and where there’s an actual community.
Or
A subscribed feed that’s flooded with hundreds of reposted memes by an OP who is essentially a bot, who doesn’t even know they (re)posted the memes and hardly any comments under the posts, because there are more posts than viewers.
You don’t grow an user base by spamming so much garbage into it that it quenches every chance of a discussion and drowns out any posts about relevant topics.
If I want an endless stream of copied memes with no community around it, I go to imgur.
Nah, there’s just a repost bot spamming my whole feed, making it really hard to find any worthwhile discussion.
Nope. Network effect happens if there’s a network. For that you need an adequate amount of eyes per post so that people can start commenting and discussing stuff with one another.
Dump in hundreds of copy-posted memes without enlarging the user base and it does exactly the opposite of the network effect: With much more posts per viewer, the viewers are spread thin over the posts which means there are never enough people on one post to actually start a meaningful discussion in the comments.
Git is a tool originally developed by Linus Torvalds himself. Github is one platform of many that uses Git. Similar to Gitlab, Bitbucket, Codeberg or Gitea. You can also directly use git without a platform around that.
As a developer you really should know that. That’s basics.
The problem is that Reddit is many orders of magnitude larger than Lemmy. r/comics has 1.5 mio weekly visitors. All of Lemmy combined has just ~50k monthly visitors.
One repost bot alone can swamp all of Lemmy, totally drowning out everything else. The biggest issue there is that it’s dead content. The thing that makes something like Reddit or Lemmy better than just a random webcomics feed is the comments. So if a ton of non-organic content gets reposted, that dilutes the comments too much meaning that people don’t actually see eachother’s comments any more and thus no discussions happen.
That’s pretty much my point. Actual Nosql does have use cases, but more often than not it was used for hype reasons. “Everyone uses Nosql, let’s not become legacy and hop on the Nosql train!”
Document DBs came out of Nosql, and are pretty much the same as SQL for most use cases, just with their own funky syntax.
And then again there are the use cases where people use SQL without relations, basically as a Nosql DB. Just do ORM for everything, do the database stuff in memory in Java and just use SQL to dump crap into.
Yeah, there’s like two projects that use Haskell. Doesn’t change the fact that it’s the language that most people know and will never write anything productive in it.
Fashion really does go in cycles.
This here.
When I got into programming I figured it would be mostly linear technological progression. Every once in a while something new gets invented that’s better than the last iteration, so we discard the last option (except for legacy stuff) and everyone moves to the better thing.
But since then everything that was cool back then became uncool and cool again at least once.
I like the SQL/No-SQL cycle. SQL is powerful, but it’s also slow and clunky and if you do it badly it gets really slow. So we invented No-SQL DBs. They are fast, lightweight, but also barebones and limited. So we add functionality here and there, and before we know it we have another variant of SQL with a different syntax. So we head back to use real SQL. But then we realize it’s slow and clunky and if you do it badly it gets really slow. So we invent a new No-SQL DB and the cycle continues.
Why do programs written in Haskell not have side effects?
To have side effects someone would have to run the programs.
They enshittified, yes, but uptime isn’t a topic of enshittification. You don’t make more money by reducing uptime.
Uptime, especially for a critical service like Github, that tons of businesses actually depend on, is a sign of not being able to keep your infrastructure and development under control. And getting below 90% is really, really shameful.
Yeah, that’s a terrible decision in the docs. Don’t ever add a path where anything on the shell can execute user-modifyable code as root.
As soon as you do that, you lose any protection that comes from separating root users and non-root users. Because now any malicious program can just use docker to elevate its code to root.