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 is an issue for sure, but probably better addressed at the ActivityPub level? IMO, an instance should be limited to a single community.

sh.it.works.sometimes

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

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?

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.

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?

I don’t think it’s a version issue. It could be, but testing I’ve done says otherwise. There’s plenty of 0.17.4 instances that, despite other bugs, have no problem sending and receiving updates from other instances. I hope you’re right. I don’t run the instance so testing reveals mostly speculation.

Live updates to the page is a great feature, but instead of fixing it, they just turned it off for 0.18.0. Gotta start making pull requests…

Not just you. There is something fishy with this instance’s connections to other instances and vice-versa. I’ve been looking into it from the outside. Of all the connections made to my instance, about 80% fail negotiating TLS. I’m not a protocol expert, but it’s ONLY lemmy.world and it’s not a cipher issue, because it does OCCASIONALLY connect and post some updates.