Very Hairy Jerry

@urda @blenderdumbass :blobheartcat:

@rglullis I think the donation model is working ok at this scale, but I don’t believe it will scale up to the hypothetical future we were discussing on the show where the fediverse became the social media platform for the masses. There are somewhere around 1 to 2 million active fediverse users, depending on how you count. If that were 100x or 1000x larger, we would simply crumble - I don’t think the general architecture scales that well (think of all the duplicate storage that we end up paying for across various instance) and generally, people who use social media are far less concerned with the core value propositions of the fediverse, like privacy and whatnot. I know that’s hard to accept, but we’re here because that’s how we think. So no, I don’t think we will have a future where a 500,000,000 active user fediverse can be operated off of donations from members. I also very much doubt that people would pay a fee to be here when corporate social media alternatives are “free” to them

@rglullis @blenderdumbass I have donations from members that cover the costs.

@Chozo @Novamdomum can you DM me your IP address? The site has been under a heavy ddos by scrapers and I think my script to identify those scrapers got a little carried away.

@[email protected] @[email protected] why would you think that’s AI generated?

@[email protected] the second and third order impacts of this could get interesting

@melroy @jwr1 @arotrios @vaguerant I cannot express how awesome the mbin team has been. I have no idea how kbin.social was able to operate with that many users while running kbin. I can definitely see mbin working for that large of a user base, though.

@[email protected] @[email protected] @[email protected] I had to remove /m/test too, and now the delivery queues are holding at zero, as they should be.

@[email protected] @[email protected] @[email protected] hopefully you’ve seen my other messages on Fedia. I think I’ve fixed the problem by deleting /m/fediverse and purging the backlog of deliveries. The threads mentioned above were delivered but due to the issues with /m/fediverse (and possibly /m/random) the server was running way behind because it was spending all its time retrying deliveries that would never be accepted by other instances. Sadly I think I’m going to have to leave /m/fediverse deleted till the underlying mbin bug gets fixed.

@[email protected] @[email protected] @[email protected] it got here. I will go check.

@[email protected] I removed the block. I’ve been having some luck in reducing the server load today with the help of the mbin team.

@[email protected] messages to/from threads has been causing some major problems with the message processing queues on fedia.io. To keep the instance running, I had to block it until I can sort out why.

Being mentioned in the same breath as the others in the post above is wholly inappropriate. Those are the MVPs. I just pretend to know what I’m doing.

@IlliteratiDomine @DarkThoughts I found the problem - it was an error I introduced when moving fedia,io to containers recently. it works now.

@IlliteratiDomine @DarkThoughts Thanks for tagging me. I wasn’t aware there was a problem. I’ll take a look.

@konsi where does that view come from?

Hello everyone. If you care about fedia.io, please read this: https://fedia.io/m/fedia/t/350673

Note: it’s good news-ish

@liaizon @geekgrrl @fediverse agree. I haven’t played with it much, but it seemed a lot further ahead than WF

@geekgrrl @liaizon @fediverse sadly Plume is dead - and I fear that writefreely is also dead software walking. I will have to look at the others…

@Cavalarrr @ernest I did what all the cool kids are doing and disabled federation on fedia.io. The problem isn’t really the local users as much as all the content being federated in.