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

Lemmy.World Announcements

28661 readers
36 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.

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

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
[โ€“] megane_kun 1 points 1 year ago

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.