This Community is intended for posts about the Lemmy.world server by the admins.
For support with issues at Lemmy.world, go to the Lemmy.world Support community.
Any support requests are best sent to [email protected] e-mail.
If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.
If you can, please use / switch to Ko-Fi, it has the lowest fees for us
I don't know if it's a problem on my end but today I've got the following error several times while reloading pages:
404: FetchError: invalid json response body at http://lemmy:8536/api/v3/site
I have to quit the browser and wait a few minutes before I can connect again. Never happened before.
I've heard a few more people who had that. I'll investigate
Thank you!
I've also been getting these.
I donβt know if itβs a problem on my end
These are internal failures with lemmy-ui talking to lemmy_server and not understanding it got an error message or timeout back. Not on your end. Every busy Lemmy instance I've been testing on has these problems right now.
Is outbound federation a known issue?
I've just tested inbound from sh.itjust.works and it was instantaneous. But my outbound posts that have worked take hours and none have succeeded for days.
I dunno. Can't see any of that in Lemmy. So I'll have to test if it's our outbound or sh.it's inbound.
Understood. I'm not just trying to get content to sh.itjust.works, though. outbound from here to .ml, kbin, and fedia have all failed. I'll test kbin inbound.
kbin is not instantaneous. It has not appeared and I assume, due to instability, is likely lost. If it comes through I will update with time.
The kbin test comment posted there 4 hours ago according to time stamps. So 5 hours from previous comment
I've been having outbound federation issues from lemmy.world with both kbin.social and my personal Mastodon server, social.goodanser.com. I've also had people report to me that posts and comments are not showing up for them on feddit.de.
Iβve had problems with posts not showing up on sopuli.xyz, so Iβm guessing outbound.
yeah, I've got multiples not making it through.
sh.itjust.works to .world is istantaneous, posts and comments.
other way is failure.
but, sh.itjust.works to kbin.social also has either failed or is taking a long time. But that connection might not be as established.
sh.itjust.works to lemmy.ml test was instantaneous for a comment.
so something is amiss here
Hereβs a similar report, this time with feedit: https://lemmy.world/post/440406
Top comment by @[email protected] says the new version coming tomorrow fixed this issue. Guess weβll see.
Just wanted to say thanks Ruud for all the work and expense. Your diligence is obvious. Thank you.
Thanks for all the work to keep the community running, Ruud!
Do you already know when Lemmy.world is gonna be running lemmy 0.18?
Seconded re. Lemmy 0.18, just because the latest Jerboa release won't support Lemmy.World until it's updated. Edit: don't pull the trigger on a Jerboa update if you're a Lemmy.world fan.
I just wanted to say that I appreciate everything you do. Thanks for the awesome instance.
One thing I've noticed being in the UK. If I come in early morning here it's pretty dead. But if I come in late afternoon it's really chatty and busy. So I'm assuming most people who have migrated here from Reddit are in the US? Not a bug related problem, but it would be interesting to know where in the world everyone has migrated from. Not sure if that's possible though.
another cause of the infinite spinner: you are trying to sign in, but you haven't verified your email address yet. solution: check your email, click the verification link that was sent to you.
The content of one instance can be very out of sync with another.
Example, this thread in beehaw is visible here in lemmy.world, and at the time of writing, not even a 3-day-old comment shows on lemmy.world.
I have been subscribed to this community from beehaw in lemmy.world for those 3 days, which as far as I'm aware is the only pre-requisite to sync. But if syncing takes longer than 3 days...
Hmm, the original thread/community seems to be at beehaw.org, right? Since both of the threads you linked to are referring to the community "[email protected]".
Beehaw is even down right now, so I am guessing that any syncing issues with other federated instances might be caused by a bottleneck at beehaw.org...?
I still don't fully understand how Lemmy works though, so I am not sure.
Beehaw is defederated with lemmy.world, so those posts won't be updated with the content from beehaw.
Yes, you are right. But it had 3 days to sync. The oldest comment is 3 days old. Here is the same thread visible from another instance, much more up to date. I hadn't noticed that beehaw.org is down though. That could explain it. I still find it odd that this instance would not have a single comment on this thread over these 3 days but... yeah I'll take that explanation for the time being, I'll check again when I notice beehaw is back up.
Do you know how the fediverse works regarding this?:
If we take beehaw being currently down as a possible explanation for not seeing any of that thread here then I suppose first the comments need to reach beehaw.
I may as well ask another question, any idea how I would find that thread easily on lemmy.world? I tried pasting the full URL in lemmy.world's search but didn't find it, I had to manually go into that community in lemmy.world's instance and dig through the history to find it. In this case I assumed I would be able to find it by searching the full URL since the thread already is visible in lemmy.world, even if with no comments.
beehaw.org is back up. So lets see how long until that thread updates on this instance.
edit: Ohh.. but beehaw.org is blocking lemmy.world So what would that mean for lemmy.world? Would the normal behavior be that we can see the thread's main post but not any comment?! I thought it was the other way around though, that they don't get any content from lemmy.world but lemmy.world can still fetch theirs.
edit: Ohh.. but beehaw.org is blocking lemmy.world So what would that mean for lemmy.world? Would the normal behavior be that we can see the thread's main post but not any comment?! I thought it was the other way around though, that they don't get any content from lemmy.world but lemmy.world can still fetch theirs.
No, the block goes both ways. Lemmy.world cannot see anything on beehaw.org, and beehaw.org cannot see anything on lemmy.world.
Think of it in terms of one user blocking another on a regular social network.
We're all still learning, but check your facts before posting this type of info so you don't add to confusion about defederation.
@sss had it right. We can still see posts from beehaw, just not comments. If we comment on the posts or make our own posts, they only show up on [email protected] and won't go to beehaw. And syncing seems to be about 3 hours behind there, but that could just be the general sync issues right now, unclear.
Would it be possible to have a setting to open posts in a new browser window, leaving the home feed in its own window?
Things seem to be working with beehive now, too
~~Every time~~ Occasionally when I click on a new post from the front page, it displays the content of https://lemmy.world/post/483076 with the comments of the new post, and I wonder why absolutely everyone is talking about baseball.
This has been happening to me intermittently as well.
At least as of this timestamp, https://lemmy.world/post/660260 says there are 4 comments but there are actually only 3 comments.
It's a known bug in Lemmy 0.17.4 and I still think in 0.18.1 where editing a post can trigger that count to increase. I'm not sure if there is an open GitHub issue on this.
Whenever I upvote a comment or post a comment myself, it expands all of the comment chains I've previously collapsed.
Also still seeing lots of backend timeouts and slow responses, plus I somehow got logged out again (I logged back in after a few tries).
I begin to hate Lemmy's web front end, because it uses so much asynchronous network stuff. The success path works somewhat ok when things are fast, but when things are slow (even if you don't hit an error), you can never tell whether the screen state has caught up to the server state. We need an old fashioned synchronous front end, so if the browser says that a page has finished loading, you can know that what you see on the screen is the final state of the page.
Iβm having the issue of notifications not going away after I view them. I click on the reply to my comment but I canβt get the notification to disappear
The comments view for a community shows recent comments but doesn't identify the threads that they came from, which is confusing. There is a link to the thread from one of the little icons underneath, but since the thread urls just give a numeric identifier without anything showing the thread topic, it's still difficult to see which comment came from which discussion. Example.
Also, the RSS feed for a community only gives the posts, not the recent comments. Since there is a recent-comments web view, maybe there is a simple way to connect that to RSS.
Lemmy appears to track on the server side what posts you have read, so it can show this in the UI. That is terrible for privacy since someone bad could seize the data. If reading history is tracked at all, it should be on the client only.
Anybody having issues with authorization? I was logged out of lemmy in my jerboa app and I had a hard time logging in with an error message saying rate_limited. It's improved slightly over the last couple of hours but browsing communities that I'm subscribed to is buggy and sometimes won't load more than a handful of posts. I also can't seem to upvote or downvote comments because the app thinks I'm not logged in, despite me being able to post in the same thread.
Next to the sorting icon at the top of a community, there is a "?" badge that looks like it is supposed to explain the sorting options. It instead navigations to a 404 page on join-lemmy.org.
This will be fixed in the next version
There are prev/next buttons on every page of a list of posts in a feed (subscribed, unread, etc), including the first and last page of the list. The first page should not have "prev" and the last page should not have "next". In the frequent case when there is only one page, the page should have neither.
Lemmy communities have an RSS feed but there doesn't also seem to be an RSS feed for individual threads, to show new comments on a thread. That would be helpful.
It would also be good if the feeds went deeper, beyond just a handful of posts. I would make them at least 10 posts deep, maybe a lot more. Perhaps they could be paginated, making it possible to go all the way back to the beginning of the community.
I almost feel like asking for an Atom feed to accompany RSS, so it could be called Lemmy Atom, but meh ;).
As of right now (post-18.1 upgrade), when I visit https://lemmy.world/post/848519 it says I have to log in to comment, and the upper right of the screen has a login link. But I'm already logged in, the screen indicates that when I click the login link, and other pages also show that I'm logged in. Quite a few page refreshes don't change this. I'm about to clear cache and cookies and log in again, but this is weird.
If you write a post, preview it, and want to edit it some more before posting, you do so by clicking "preview" again. That is confusing and took some figuring out. The "preview" label on the button should change to "continue editing" or something like that, while in the preview state.