hawkwind @ hawkwind @lemmy.management

💩 🫘

---

Read more

Posts

4

Comments

185

Joined

2 yr. ago

In this context it would be an account with the sole purpose of boosting the visible popularity of a post or comment.

IMO, likes need to be handled with supreme prejudice by the Lemmy software. A lot of thought needs to go into this. There are so many cases where the software could reject a likely fake like that would have near zero chance of rejecting valid likes. Putting this policing on instance admins is a recipe for failure.

You’d think someone with the foresight to make a freaking logo for their bot (that looks like a robot) could tick a box that says “I’m a bot.” :)

You guys got potato chips?

I actually wrote it with the flip side of your centralization argument in mind. If a community exists outside of the popular ones a user may never even know of its existence. Having more show up SHOULD be better to prevent centralization no? It requires the users to change their browsing behaviour but at least they don’t have gonsearching offsite.

$14.80

The weird rage people have about this. I'm not sure where it comes from. If there are 100 communities, only the top 1-5 will contribute 90% of the content. If you have even one user subscribed to the top 20 or 50 communities, you are already likely getting 90%+ of this traffic. After subscribing to literally every community in the lemmyverse, I promise your instance will not see any meaningful increase. I'm willing to be proven wrong, but not one of the ragers has offered a credible reason other than fears based on misunderstanding. No offense.

Yup. 256 GB should be enough database space for anyone though.

So just refreshing the page one time after login fixes it? It could be something to be fixed in the code, but there might be a way to fix it with a browser-side script in the meantime.

In Germany they pronounce it VasMan.

A handy chart: https://i.pinimg.com/originals/18/a4/2f/18a42ffa5c733c7c6bb86b547fb0647f.png

It's a cruel irony that we use an enclosure to help print materials with a higher Tg but the printer itself is printed of materials with the same or lower Tg. It makes perfect sense that your ABS parts are going to get mushy when you crank your heated bed to 100 and put the whole thing in a box. :)

I think your idea is on the right track when thinking longer term and assuming the worst case in both design and admin behavior. :)

The whole network needs to be split into "active" and "archive." New activity (or at the very least stubs to where new activity is happening) needs to be updated regardless of where it occurs without having to capture anything extra.

It increases load during execution. Afterward it’s not significant. My instance is heavily instrumented and monitored. The load this incurs subscribing to 24000 communities is less than adding a single, moderately active user to your instance.

It’s a huge miss if the intended design was to silo information.

What this provides, as far as I’m concerned, is essential to prevent centralization to a few instances.

Is there a better way to do it inherently in Lemmy itself? Probably, and I am excited to help with that!

It increases load during execution. Afterward it’s not significant. My instance is heavily instrumented and monitored. The load this incurs subscribing to 24000 communities is less than adding a single, moderately active user to your instance.

It’s a huge miss if the intended design was to silo information.

What this provides, as far as I’m concerned, is essential to prevent centralization to a few instances.

Is there a better way to do it inherently in Lemmy itself? Probably, and I am excited to help with that!

It doesn’t matter. Most of the work is happening on the instance, regardless of where the script is running.

I'm not convinced either one of us knows what the software is SUPPOSED to do, and I am pretty sure nobody knows what it's actually doing. Here's another thread: https://github.com/LemmyNet/lemmy/issues/3163

There is some discussion. https://github.com/LemmyNet/lemmy/issues/2947

I am still fairly confident that it shouldn't be storing images, but I'll admit my pict-rs directory is growing quite fast compared to the database. Have to keep a close eye on this.

Thanks! I'm sure you'll chime in when the lemmyverse falls over because of this irresponsible script.

Your argument does not gain validity by adding irrelevant verbosity:

Federation ain’t doing great.

The linked issue has nothing to do with this script or lemmony.

Federated replication load scales with the number of instances multiplied by the number of communities they subscribe to.

That's a hasty generalization that you just made up.

Server counts are growing at ~10x per month.

That's great! I hope they keep growing!

The defaults of this script encourage single-user instances admins to bump their sub count ~70x from something like 100 communities to something more like 7000 communities.

Nobody is encouraging anyone to do anything.

Users of this script actually literally don’t understand how federation works. They think they’re proxying through to the upstream instance while they browse rather than getting firehosed with the entire lemmyverse by they’re asleep.

That single user asked a question and got berated by a jerk.

It doesn’t take a rocket surgeon to figure out that global federation worker queues are not in great shape, or that a default that encourages single-user instance owners who have no idea what they’re doing to bump their sub count 70x isn’t helping the situation. If you think this is in my head I can’t help you. But I can help others understand that running this script with default settings is an awful and unnecessary idea.

You can help others understand what it is. That's a great thing to do. It would be nice if you could do that without being a dick.

I don't really think so, but i'm open to working with anyone if they see this happening, up to deleting the entire project.