I love the idea of taking on a monopoly, but I don’t like that, without regulation, it has a low chance of success, and the consumer gets to suffer as the monopoly fights back.

Entwistle boo.

You understand that global economic stability relies on people gambling their lives on a dream, right? Well, that and pure willful ignorance.

What would the journalists do? Try to explain that to people, and that nobody has figured out a way to fix it yet?

I know your joking but in case people don’t get it: rich comes from luck, not from hard work.

Don’t work any harder than you have to, thinking it helps. It doesn’t change the statistical chance of you becoming rich.

Many people will say you can help along the luck. Those people are dumb.

Resume field would get an api endpoint that only returns a json resume, and only if the request header is application/json. And the json resume would have embedded json.

I’m not sure it’s as crystallized as that yet, but I agree with your sentiment. Everyone should have the right to choose to die but if the reason is “there was no other option,” then, we should be damn well sure we offered everything we could. Let’s not be taking societal shortcuts to “oh well, we gave it our best shot.”

I support someone’s right to end their own suffering, 100%, but it is very bad form to: be ABLE to help someone, INGORE that they are suffering, but SMILE while helping them polish their gun.

People can defederate from an instance for any reason they want, but if I get what you’re trying to say: you think people should defederate from any instance that has a user that subscribes to all of their communities.

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.

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

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.

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.

It retrieves the last 10 posts and adds the community reference to your local database. It is the same as putting “!community@instance.com” in the search box and clicking search. The retrieval happens whether you look at the results or not.

When I discovered, I felt bad for not checking. As for the load stuff. I intended and wanted to see All the things, and I don’t currently have resource problems for my instance. :) We’ll see how that fairs as things continue to grow!

My dude, I appreciate your spirit, but we’re not going to focus on your irrational fear of abuse. I’ll defend myself for being accused of any such thing, or for being irresponsible. This is intended to make things better, and there’s no evidence it’s doing anything other than that.

If you want to contribute, by all means, show us where there is a problem, other than in your imagination, and it will be seriously considered. Until then, your opinion is still valuable, but you are speaking with authority about something you know little of.

I’m happy to help or take PRs for lemmony. There is also https://github.com/Fmstrat/lcs which I didn’t know about until well into lemmony.

So if I’m understanding this right, the bot account you create for this is the one subscribing to every community, so it’s known to the local system, right?

Yes

As long as I’m not mixing up my main account and my bot account, there should be no observable change on my own account?

Correct, I have it functioning this way and it works great.

How is storage affected on this? If the bot account is subscribing to a number of communities across the fediverse, all that remote content is going to take up quite a bit of space, no?

It does and it will continue to grow. This not not something the tool takes care of, not cleaning up anything old or stale. Space management and “unfollow” is on the roadmap! Currently I can only speak for myself and it is EVERYTHING and it is about 0.25 GB / day of database, and 6-10 GB / day of images.

And will 2FA be supported at any point?

Not on the roadmap. I don’t know how api calls in general work with 2fa since I have not tested or enabled it on my instance. :( Sorry.

EDIT: Changed database/pictures ratio after double checking actual numbers and not looking at used filesystem. :(

Not really. If it worked before, it should work the same, just has more options for control and granularity.

I think it depends on your instance. This version (same script, just updated) allows for more options IF your instance IS mass Overloaded, or you are scared it will be.

Sorry, by comparing now to what; or was as that a superfluous “now,” like “come on now?”

Can you click “sync” and install the OneDrive client? That “mounts” the folder locally and you might be able to treat it just like a normal file.

Do you mean recorded teams meetings or just a video file on a SharePoint site? Is it embedded, or just a file in document collection/OneDrive?

You should write something that detects indiscriminate subscribing and automatically defederates with them.

Calm your tits Mr. Key Reasons.

LHBDM (Lemmy’s Home for Battered or Disheveled Memes)

assistant-TO-THE-upper-middle-deputy-manager

Shocking research by Statistics Canada uncovers surprising economics discovery: people with lots of money lend it to people with less for more than it’s worth: rich people get richer, and poor people get poorer!

“We were so focused on how fast people got sucked dry, we never stopped to realize why,” said Mike Hunt, an assistant-upper-middle-deputy-manager at Statistics Canada.

Mike goes on to say: “We’ve been struggling to classify “monetary gains,” for the lower class. We decided that getting two-for-one coupons, or winning a toonie from a scratcher counts. That way we can say for sure everyone is gaining!”

Correct. All also includes communities fetched but not subscribed to, however these are more like stubs. They are in your database but not being updated with activity since no one is subscribed. At least that’s my understanding.

You should be able to rerun it anytime. It only gets stuff that doesn’t exist on your instance. That’s how it was designed. It is dependent on browse.feddit.de however. :(

https://github.com/jheidecker/lemmony

https://github.com/jheidecker/lemmony

I think you’re right. People will gravitate to the most stable large instances because their “All” will be as close to 100% as possible without doing anything special. I wrote a script to seed instances and update subscriptions, but it uses a single account that is subscribed to everything so that other users can see everything. That’s not something that would normally happen. Maybe that needs to be part of the base software?

Media takes up space. The text from posts and comments is trivial. The database for lemmy.world is only 25 GB. Wikipedia text is only 21 GB.

Politically speaking, the lemmy/fediverse would make a great PolySci thesus. There is no practical universal governance other than sharing the ActivityPub protocol. It is an interesting experiment in how humans behave. Each instance is like a country.

That is exactly what that means and it’s frustrating to say the least, because it’s not clear that’s what’s happening.

It works a lot like like email between instances. Let’s call your self hosted instance “A” and the popular remote instance “B.”

User on A searches for “poodles” and finds a community !poodles@B. When they click the search results: A sends B mail saying “send me the last 10 posts for poodles.” B sends A mail with the posts and the user sees the posts, but none have comments.

If nothing else happens then those 10 posts will just hang out doing nothing on A, but if the user clicks subscribe then A sends another mail to B saying “my user wants to follow poodles.” B replies saying “cool, I’ll send you everything from poodles now.” Now, anything a post or comment happens B checks lots list of subscribing instances and sends copies of them.

If user on A comments on !poodles@B or posts, it creates it on A but sends a mail to B saying “here is some new stuff for poodles!”