in short form, we have HAproxy running on a hetzner cloud VM for Lemmy/Lemmy-UI, another HAproxy VM for the alt UIs, a VM for the alt UIs.
for the main LW box, which runs lemmy containers, lemmy-ui, pictrs and a database each for lemmy and pictrs, we have a physical box with an EPYC 7502P 32 core CPU, 128GB memory and NVMe SSDs.
considering that we’re coming from 0.19.3, this does still introduce quite a few bigger changes for LW.
there are various mentioned in [email protected], the main one i was referring to was the one where in some cases posts in local communities won’t show comments.
partial breakage, the stuff that people on other instances have already been experiencing for a while.
iirc there are still some additional issues with sync arising with the update, but it won’t be entirely broken.
local server time is UTC.
time in UTC is included both in the title and the post itself.
incremental backups might also be something worth looking into
unfortunately it seems that people are trusting google search results to be accurate without following links.
as far as I can tell this is a combination of reddit returning the subreddit creation date as the timestamp that will show up in search results yet including images of recent posts, which google will then use as an indicator of “the image exists on this page”. this will lead to a 7 year old subreddit with recent posts showing as the image being present on a 7 year old search result. if people actually follow the link they’ll see it’s just a link to the subreddit and not to an individual post.
are there actually this old posts?
this seems like google + reddit being a shitty combination. i’m seeing fewer results but the two results i get that are 7 years old are just links to the subreddit, not to posts, which is likely throwing off the date on there.
other reverse image searches like tineye don’t show any prior images, so it’s very likely that you’re just fooled by misleading search results.
unless you can produce links or other evidence about actual 7 year old content please correct your comment.
I have already commented the same on the other post.
once it’s ready.
this post didn’t follow our usual process for announcements/changes and lately there have been several other events that required a lot of our attention as well.
we’d love to have posted an update on this topic a week ago already but we haven’t finished that within the team yet.
hi, you’ll probably have a better experience here if you tag your post with the correct language or post in english.
note that this isn’t available in all interfaces/clients, but the default web interface supports this.
alternatively, you could see if there are any spanish gaming communities to participate in.
i don’t speak spanish, but this community looks like it might be better suited: [email protected]
Unfortunately at this point I don’t see another option.
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 @[email protected] 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 [email protected] 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 [email protected] 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 [email protected].
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.
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.
we’re still investigating some performance issues due to one of the lemmy processes hammering our CPU :/