As per this post, it seems Lemmy World is having federation issues. I’ve had some of my posts and comments get suspiciously low response, so I’ve looked into it and it turns out that many of them aren’t showing on other instances.
Here’s an example: my Payday 3 post is only visible on Lemmy.world:
Meanwhile, in other instances, it doesn’t show up at all:
It’s not clear if this issue is exclusive to this instance but I thought I’d give people a heads up. I reposted and now it showed up in other instances. If you feel like you’re getting no response from other communities, check on another instance if your content is visible, otherwise repost it.
It isn’t just Lemmy.world, and isn’t limited to v0.17 either. Lemmy.ca, which has been running v0.18 for days, is also not seeing a lot of federated content, nor accurate community subscription counts from other instances, including lemmy.ml and others running v0.18. I’m posting this from my .world alt because .ca is showing zero comments in this thread.
There have been several not-so-friendly comments made about the issues by someone in [email protected], calling out the site admins of .world and .ml for not sharing their server logs, and the overall silence on the issue. The user’s concerns are genuine, but I don’t agree with their behaviour.
I suspect the devs were/are completely overwhelmed by the mass influx of redditors these past two weeks. I assume someone is looking into it, but frankly I wouldn’t blame anyone if they chose to step away for a few days. I think a lot of folks (particularly “the masses”) forget that these are largely volunteer efforts, by people with day jobs.
Thanks for your reply. This site isn’t even a month old and the user growth is spectacular. Lemmy hasn’t ever been tested with these amounts of users.
I’m sure the devs are doing their best in getting it all more performant. Meanwhile the team at lemmy.world is trying to get a grip on what’s happening with federation. There’s not much to be found in logs, anyone who can help troubleshoot this let us know. The only real adjustable setting is the federation workers. We’ve apparently either set that too high or too low. I’m gonna set the log level back to info on the hopes we get some queue stats…
To be continued
No worries, and I completely sympathize with the situation. My hat is off to you site admins, and the lemmy devs, for keeping things afloat these past couple of weeks, often at great expense of both time and money. I am confident that all of these kinks will be ironed out in the coming months, and in the meantime I am happy to have a few alts to hold me over.
Back in my day 1 month old sites had 0% downtime and no reported glitches. 1 million daily active users! There’s no need for beta software either cause 2.0 was always the perfect release.
Those were the days!
Looks like grandpa has gotten into the horseradish again.
Thanks for the response.
Most people here know we are in alpha. Shit will happen. Gonna take a while to get these systems ready to take over reddit.
for not sharing their server logs
WTF do users think they have a right to see these at all? Just because Lemmy is open source doesn’t mean you get to run the damn thing.
Also my condolonces on you being a Canadian.
That’s pretty much what I yesterday called the lemmy.world bubble.
Just clicked on a Futurama related post on Lemmy.world front page, it opened wtih this MLB Game Thread as content instead of what I clicked on. **This is happened more than once. Previously I thought I derp clicked on the wrong item **
I’m not kidding when I say I opened a meme post and the picture was from the “bulges” page. The comments were the correct meme post comments though. I went back and forward again in my browser and the image was correct.
This has been happening to me for at least a day now. Reloading fixes it and brings you to the post you thought you were in.
Funny thing is sports communities are the ones I block as I come across them, and this glitch circumvents blocked communities.
Workaround, I had to do the same on kbin.
Editing your comment triggers another sync, often an edit will make the comment or post synchronise to all other instances.
Correct me if I’m wrong but .18 lemmy doesn’t support captcha, so lemmy.world is waiting for a patch before updating so we don’t get flooded with bots.
Edit: fixed typo
Correct, re: captcha *
There should be a fix in a day or two, there was an issue with captcha to my understanding.
If it was reposted and worked that’s not a federation issue right? Could it be that world isn’t on .18 yet?
I believe this is a side effect of the 0.17 vs 0.18 split which unfortunately wasn’t backwards compatible. Once 0.18.1 rolls out with readded captcha everything should be hunky-dory again.
Was [email protected] the instance that was not showing the post?
Yes, I ended up reposting there and it shows up now.
Lemmy.world is definitely having federation issues. Lemmy in general is having a lot of federation issues, but it looks like lemmy.world is being effected more so due to the number of accounts and activity on lemmy.world in combination with different versions of lemmy handling messages a bit differently with different implicit assumptions.
I got a report earlier that my community wasn’t showing up on https://browse.feddit.de earlier as well, but it’s back now. I’m not sure how it works but I assume it’s related.
Any idea on that 0.18.1 release? I have no idea how much work is required to add re:capcha. Are we talking days, weeks or months off work?
It just got approved after some edits
… and merged to
LemmyNet/lemmy:main🙂
To add some specificity to this:
I’ve been unable to post to [email protected] or [email protected] successfully. And the comments seem to be failing to load at all.
Here’s to hoping its the .18.x vs .17 issue. But I figured I need to post an official report of my problems somewhere, and this topic seems the most applicable location.
I’ve also been “Subscription pending” on [email protected] for… at least 20 minutes now. Suspiciously long times to get that resolved.
5 hours later, I’m still “Subscription pending”. I dunno if this is related to the issues, but I figure I should document the problem here.
Just wanted to let you all know that the federation with kbin.social is working fine.
