this post was submitted on 17 Jun 2023
7 points (100.0% liked)

Lemmy.World Announcements

28383 readers
8 users here now

This Community is intended for posts about the Lemmy.world server by the admins.

Follow us for server news ๐Ÿ˜

Outages ๐Ÿ”ฅ

https://status.lemmy.world

For support with issues at Lemmy.world, go to the Lemmy.world Support community.

Support e-mail

Any support requests are best sent to [email protected] e-mail.

Report contact

Donations ๐Ÿ’—

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

Ko-Fi (Donate)

Bunq (Donate)

Open Collective backers and sponsors

Patreon

Join the team

founded 1 year ago
MODERATORS
 

Update. I asked a friend of mine to take a look at the Lemmy.world front page via his browser (vanilla Firefox) and it works as expected.

I also did an earlier test on a chromium browser and it also works as expected.

It might just be that my browser is breaking stuff, which I need to investigate deeper.


When trying to access Lemmy.world from the desktop, I see this blank-ish page (see attached screenshot). And whenever I try to click Subscribed, Local, or All, the same error message pops up on the lower-left-hand side of my screen:

SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data

I wonder if it's connected to the work our admins have been doing recently.


For disclosure, I am using LibreWolf and a userscript to make Lemmy pages look like old.reddit. I've turned off the userscript to check if the error disappears, but to no avail.

I may have missed more details that might be helpful, but I'm willing to give such details.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 1 points 1 year ago

Thanks for the hard work and the speedy response.

Unfortunately, the frontpage isn't still showing any posts. I did a test from a chromium browser just now and it's working as expected. I don't have a vanilla Firefox to test things with, unfortunately, but at least I've managed to narrow it down to my browser breaking things.

Again, thanks, and if there's any more detail you might need, I'm more than happy to provide them.