So I’m noticing that I don’t seem to get any engagement when I’m posting replies to posts generated on other instances. Just now I thought I’d go directly to a thread on lemmy.world to see if my comment was showing there but it isn’t. Other non lemmy.world users are showing up.
Does anybody else notice this or is it just me?
Example: https://lemmy.sdf.org/comment/6595136 My comment
https://sh.itjust.works/comment/6752604 Who I replied to
https://lemmy.world/comment/6161325 Where the thread originally was posted
Edit: the issue appears to have resolved
You must log in or # to comment.
Today SDF upgraded. This is the version I’m seeing now:
UI: 0.19.1-rc.1
BE: 0.19.1-rc.2As noted in OP’s edit, federation seems to be working now.
I mean, at least it lasted longer this time, but here we are again. Maybe because it’s just an older RC instead of 0.19.1 release.
Edit: https://github.com/LemmyNet/lemmy/issues/4288 is re-opened
Yeah, noticed today that federation is broken again, and nobody loves me or thinks I’m clever.
Is there a status page for sdf.org services somewhere that actually gets updated? Or at least release/update log?
Incredibly annoying to just lose access to services without any notifications.
Is anyone from sdf IT team even here? Do you guys need help? I’d be happy to offer my time/expertise.
I have the same problem.
I think our instance was just upgraded, it might be worth testing if we fixed
19.1 should fix it indeed
Idk… I made a comment here https://lemmy.sdf.org/post/9558280
but it’s not showing on the native instance https://lemmy.world/post/9866880
Interestingly, my test messages to my account on sh.itjust.works from 6 days ago have successfully federated today. And also a test message I sent today.
I can’t see the linked comment elsewhere, but I can see this one on sh.itjust.works and lemmy.dbzer0.com, though not lemmy.world (and also not lemmy.ml).
Hmmm…Maybe, just maybe, it tried to retroactively federate everything that didn’t successfully federate, and the amount of posts, comments, messages and votes somehow broke things. But that’s just unlikely speculation.
Edit: Also, the instance was upgraded to 0.19.1-rc.2 instead of official 0.19.1 stable release, which is newer. I guess that was an accident.
I think things are catching up, im getting replies from other instances now
The post made it, the problem appears to be resolved.
There are a few other threads in this comm about it, been a problem for a while. We’ve been on Lemmy 19.0 rc versions for a long time, but apparently when 19.0 was actually released a week ago it caused propagation issues other places too. 19.1 is out now and hopefully fixes it when this instance is updated.
I’m hoping soon, but also wouldn’t expect much during the holidays.
Ok, no biggie. Just wanted to make sure it wasn’t me. I’ve had a couple harsh words about hexbear and .ml only later to discover that the person I was arguing with was one of the actual developers for lemmy. I was getting paranoid that they shadow banned me or something
Fortunately Lemmy is fully open-source, so we can say categorically that there is no mechanism for shadow-banning in Lemmy.
You can be banned from a community and possibly blocked by an instance, but not shadowbanned from Lemmy.
Is there a way to know that a server is actually running the open-source version of Lemmy and not some proprietary modification?
At the bottom of the pages the version that is being used is displayed above the Modlog link
And nothing prevents someone from modifying the software and keeping the version information.
