Last Tuesday.

Do we want to be the void?

Too bad the users are partially yelling into the void: https://lemmy.world/post/609080 Hope it gets fixed.

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

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.

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.