not at all. nobody can revert edits, only the creator can edit it again.
moderators can restore removed (mod action) posts and comments, but not deleted (creator action) posts and comments.
this is a completely different issue than the one seen on the newer lemmy versions unfortunately. i believe that issue in newer lemmy versions is already prepared to be addressed in the next lemmy release.
for some reason youtube/google decided that hetzner customers don't get any opengraph metadata anymore, so it doesn't really matter which lemmy or even client in general we use. fetching youtube pages with curl yields the same result where the necessary metadata isn't included.
this also affects other instances hosted on hetzner.
it does indeed. i've let @ruud@lemmy.world know.
there's another sync issue where posts in local communities don't show any comments, i had forgotten about that. there are several posts in !syncforlemmy@lemmy.world about that issue, as well as 2 issues on the github issue tracker.
I was surprised to see such a large part of our active users using Sync, although given that there aren't really any bad breakages yet it shouldn't be that unexpected.
The comments in local communities issue seems a lot more serious than "only" not marking posts as read, I've read about that before and totally forgot about it since. There were quite a few threads in !syncforlemmy@lemmy.world about that.
If anyone wants to spend some time on figuring out which change exactly broke this for Sync we might consider a patch to restore compatibility with the old API if it's simple enough to do. I probably won't have time to look into this much until somewhere in January, and my time will probably be better spent with migration preparation and testing of Lemmy itself there.
People looking for alternatives might find some inspiration in !lemmyapps@lemmy.world.
https://semver.org/#spec-item-4
Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.
that isn't saying that you should change things, but it's technically not against semver.
given that the lemmy api is versioned separately though and it's currently at v3, with v4 in active development, that would be good to avoid breaking changes there. I don't know if that one is supposed to be sever though.
they're generally not read. it's just a bot account.
we need to update the text there to clarify that, it's come up a few times already, including people reporting automod pms.
in most cases these pms are a result of community moderator actions, so it's generally recommended to contact the community mods about this.
thanks for the image. for some reason i can't see the firewall event for your attempt, but when i tried to upload the image myself i found the event. it's a rule related to a php file upload vulnerability in software we're not even using, it's disabled now.
a JSON parsing error is certainly unexpected. I wonder if you happen to be triggering some automatic Cloudflare WAF rule.
could you try uploading the same file from a computer? before uploading, please open your browser dev tools (F12) and visit the network tab. it should show some more details in there. especially the response tab should show an actual error message. in the headers tab, you could also share the value of the cf-ray header with us and we can take a look at our logs. please be careful not to share everything you see in that network tab, as there are values visible there that allow taking over your lemmy account. specifically cookies and the jwt value; in some cases also an authorization header. cf-ray is not sensitive, it's just an identifier associated with the individual request.
feel free to pm me the cf-ray value rather than posting it publicly.
view more: next ›
Unfortunately at this point I don't see another option.