[-] mashhitmyself@lemmy.world 3 points 1 year ago

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

[-] mashhitmyself@lemmy.world -1 points 1 year ago

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.

[-] mashhitmyself@lemmy.world 4 points 1 year ago

sh.it.works.sometimes

[-] mashhitmyself@lemmy.world 2 points 1 year ago

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

[-] mashhitmyself@lemmy.world 1 points 1 year ago* (last edited 1 year ago)

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.

[-] mashhitmyself@lemmy.world 2 points 1 year ago* (last edited 1 year ago)

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?

[-] mashhitmyself@lemmy.world 0 points 1 year ago

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?

[-] mashhitmyself@lemmy.world 1 points 1 year ago

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.

[-] mashhitmyself@lemmy.world 1 points 1 year ago

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.

[-] mashhitmyself@lemmy.world 2 points 1 year ago

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.

[-] mashhitmyself@lemmy.world 2 points 1 year ago

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

[-] mashhitmyself@lemmy.world 2 points 1 year ago

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.

34
submitted 1 year ago* (last edited 1 year ago) by mashhitmyself@lemmy.world to c/nostupidquestions@lemmy.world

Just in case anyone is using their account here to post to off-instance communities: those posts and comments seem to have a very high failure rate. There is a lot of activity and accounts on this instance. This is to raise awareness, not to pull people away or break up the lemmyverse. Quite the opposite really: there is a technical problem on this instance that might be preventing the lemmyverse from functioning as it should.

view more: next ›

mashhitmyself

joined 1 year ago