For anyone else wondering, btw, it’s because lemmy expects all ‘id’ fields to be unique, so it would error if the inner object actually was a copy of the original vote.
Thanks for the reply. I see the request has been posted by someone else and has been acknowledged/tagged. I guess it is just waiting for the feature to be implemented now.
For anyone still not able to access slrpnk.net, here’s a copy of the help thread in the slrpnk meta community:
It seems like there is an issue with the upgrade from Lemmy version 0.18.5 to 0.19.2 where the old login cookies are not accepted any longer and right now the only way to fix it is to manually delete the old cookies for slrpnk.net from your browser storage and log in again.
For Chrome: Settings > Privacy and Security > Third-party cookies > See all site data and permissions > Search for slrpnk.net > Click trashcan icon
For Edge: Settings > Cookies and site permissions > manage and delete cookies and site data > See all cookies and site data > Search for Slrpnk.net > Click little ‘v’ dropdown arrow > Click trashcan icon
For mobile apps: Log out fully and log back in again.
The Lemmy devs identified the issue and it will require another bugfix release that will hopefully happen soon.
Maybe they have been blocked by your instance. I still get content from there. That has actually been one of the reasons for me to create my own instance.
I had something similar just happen and I’m pretty confused because I see in the lemmy.world modlog that my post was deleted but I posted here, on .ml… though when I look here I don’t see it either but it’s also not showing up on modlog…
this line was causing it to fail to start, I commented it out and it started working, then I needed to clear my local cookies to load the page for some reason
no, just that I’ve read that it is discouraged to put the compose files to “latest” so they get updated periodically. I updated a day or two before 0.19.2 came out I believe.
I have started changing the compose file to upgrade but the changes are more extensive than I thought, more commands and other additions so I had to pause until I have more time (tomorrow or the day after I hope). Thanks for asking though. :)
So I performed the upgrade and it bricked my install completely. The reason seems to be that something cant handle png icons and after about 4 hrs of working on it, searching and trying different approaches, the site is now back online. Now I need to take an extended break and tomorrow I might check if the error messages are gone. I did find some of the same in the log just a couple mins ago so I dont think this has helped. I might have to turn off backtraces so its less convoluted.
74 characters, but 203 bytes when they're UTF-8 encoded. My guess is that someone wasn't careful with (or had some technical reasons for) counting UTF-8 characters versus counting bytes, and taking away the last character brings it to 199/200 bytes and it fits into the field again.
lemmy_support
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.