I was meaning to be authoritative, and I am low-key blaming the admin team. I grant them the benefit of the doubt though. I still don’t think it has anything to do with the 0.18.0 upgrade.

EDIT: I don’t care what the admin team does, how loyal or dedicated they are, or anything like that. I just want the reddit alternative to not suck.

OMG. You’re right! I just edited the title. Which, lol, will not show up everywhere.

Why did this get downvoted? Something being an “issue” on GitHub is about as meaningless as something can be. Unengaged developers are usually the result of unengaged users. I’m saying IF your admin (not that they did,) submitted an issue and then is just sitting back and waiting, that’s shitty.

That’s what I am doing to suss it out. I’m a data nerd so I’m looking carefully at how to contribute and watching what’s going on sub-meta…

That is an issue for sure, but probably better addressed at the ActivityPub level? IMO, an instance should be limited to a single community.

It’s really quick to get running. You need a fairly reliable IP/hostname as this is how your server will talk to all other servers and users. If you use dynamic dns, make sure it’s rapidly updated if your ip changes.

Upload will depend on your user’s activity (posting/voting/commenting.) Download will depend on that PLUS what the users are subscribed to.

sh.it.works.sometimes

A lemmy developer more familiar would have to answer that. It seems inconsistent at best. How consistent it was designed to be might be up for debate, but the average users understanding should AT LEAST match that…

I can see a LOT of failed network connections from lemmy.world to my instance and results of comparing posts. That’s the data I have. :)

Fair enough. Keep in mind, being popular doesn’t magically bestow the knowledge, resources, or willingness to handle issues.

No you’re not. It’s good to test. There might be differences in our client’s view due to other CDNs, proxies, caching etc. I’m just convinced it’s lemmy.world’s outbound networking. There might be other instances with other problems, and yes the upgrade could be a factor, but the lemmy.world issue is clearly and forwardly apparent.

Hilarious. This comment doesn’t show on sh.itjust.works, which makes total sense. lemmy.world is responsible for sending it to other federated servers. Maybe kbin > lemmy right now?

Just to be clear: if you load these two pages: https://sh.itjust.works/post/446063 and https://lemmy.world/post/609080 that are identical?

Do it. Be super aware of how federation works though. The more stuff your users subscribe to the more network traffic you will need to accommodate.

Look. I’m not pointing fingers, but I know a thing or two and I can say with a high degree of certainty it is lemmy.world. :) Does the admin care? Do the users? Who knows. I just thought it was important information to have.

The silent failures are what actually miff me the most. Like to an uneducated user, everything is just working fine, but in reality they are stuck in lemmy.world.

It’s a known issue, but if you look at the issues, the reason for it is “could be lots of things.” Relying on a FOSS project to fix the problems of the community is kind of naive. If the admins don’t step up then I’ve no sympathy for them when the whole thing crumbles.

I don’t think it can be fixed without scaling up the instances, which isn’t for the faint of sysadmin heart, even if you CAN afford the hosting.

Correct. I am not testing with any of those instances. You shouldn’t expect that to work at all, but I guess some users might not know.

Like you mentioned afterward. Comments and posts just plain failing to land on any other instance. Also I run an instance for testing and can see incoming connections. lemmy.world fails at a protocol level, not at the application level. It’s a, IMHO, bandwidth issue. Hopefully the admin is aware and wants to fix it. I’d say he has a responsibility, but he doesn’t. lol.

This post can be an example. Check: https://sh.itjust.works/post/446063 Do you see our conversation?