Biggest problem for Lemmy and similar applications is scalability and controls and detection for bots.

The compute costs to operate instances are astronomical compared to the actual user load they receive.

That’s a bit of a side problem compared to bots though. Bots are a real problem that services like this are not equipped to handle.

They are already arriving to some degree.

The difference being is that Lemmy and other similar services have zero controls or ability to handle bots or bop traffic if those bots were bots from 2014.

Not bots from today.

It’s a bit of a problem and honestly with increasing bot traffic across the internet and fedaverse being extremely vulnerable to it It’s absolutely bat shit insane, but I don’t see any other option than somehow having some form of human verification.

It’s a problem

I’m guessing I must have missed something here when I made that comment. I visited the link in the body of the OP not once, or twice, but three times to verify I wasn’t losing my mind. Even went into reading the readme, some issues…etc to verify.

I’m now realizing that in my Lemmy client the link in the body is more obvious to click on than the actual article itself.

Did you go to the repo before running your mouth? It’s awesome-selfhosted data.

What AI slop?

Edit:

I’m guessing I must have missed something here when I made that comment. I visited the link in the body of the OP not once, or twice, but three times to verify I wasn’t losing my mind. Even went into reading the readme, some issues…etc to verify.

I’m now realizing that in my Lemmy client the link in the body is more obvious to click on than the actual article itself.

Naw, they’ll get legislation passed that carves our extra protections for their robot guard dogs.

Considering these companies own the legislative process, and the government formed and ran by the people no longer serves the people, and is instead a funnel for class traitors to enforce the will of the Epstein class on all of us.

Sooooo

More pandering to the lowest common denominator

It was a typo. Fixed.

Makes sense. I appreciate your replies

The commit history is 1 day.

Which is incredibly suspicious.

“Child safety” has simply become the marketing department for a rent-seeking surveillance industry.

Damn ain’t that the truth.

They want to identify the bots from the humans. Partially for advertising.

It is, but WSL is also pretty much shit.

I’ve been maining Windows with WSL at work, and it works great, till it doesn’t. And then it just sucks, and sucks, and sucks.

Almost always has to do with processes on WSL.not being killed by connectors to their windows counterparts. And docker desktop, holy hell, docker desktop and WSL just love to turn WSL into sludge.

I’ve been fighting with it for years, WSL is an awesome idea, it works great when it works. But as soon as you out real development loads onto it it just folds.

Why the comically long hairs in panel 3?

And it’s not red, to indicate this, why?

Clearly these are long hairs!

And instead install a chromium based browser, right?

That’ll eventually die the same way Firefox does because forks only survive by way of subsidized capabilities off of the work of the Firefox engineering team.

There is no winning here.

California, Colorado and New York now.

Honestly is getting insane.

Given how many states are pushing legislation like this and how quickly they’re doing it, there’s effectively no way to push back against it…

I do hope that they stop this bullshit though.

The maintainer you and said that they tirelessly tested, reviewed and verified changes over the course of 3 weeks to make sure that things were running and operating correctly.

This is how it should be done. It’s not like they’re vibe coding this.