Hey everyone. Currently the instance is being affected by a bug that prevents outbound federation. This seems to have started when the instance upgraded to 0.18.5
Im pinning this post in the instance while it is affected by the bug so everyone is aware as this affects everyone in the instance
Theres an open issue on the lemmy github repository and we are attempting to track down why this is happening and fix it
Bro me too LMAO. I've posted a few thoughtful, well thought out comments to bring some perspective to a conversation... No replies, no comments, nothing. I was beginning to think Lemmy was dead
Hey! Seems my instance can receive posts from yours; both !godot@programming.dev and !programming@programming.dev seem to show the latest posts (newest one is from 19 hours ago). Can this federate back?
edit: I made a whole comment on the issue page without realizing that 19 hours ago was also when you fixed federation... congrats on getting things to work! And maybe my coffee shouldn't be as strong...
All related I’m sure but just noting this for the record based on what I’ve experienced:
making a user a mod of a community that’s located on another instance is not federating
mod log changes are not federating
changing the icon for a community on another instance is not federating
post deletion on a community from another instance is not federating
user profile changes are not federating to other instances
outbound comments are not federating to other instances
Important to note that if you search for a direct post link from another instance using the URL search, it triggers outbound federation for that post and the post becomes visible to all other instances.
Also adding onto this but there was an issue with the pictrs storage getting full that made the instance offline for a couple days while it affected it and so the instance could be moved to object storage. (communicated about over on the mastodon account since the site was down https://mastodon.social/@programming_dev/111237442491837823). Thats a separate issue from this one (and prevented this from getting tested properly for a bit)
I wish the devs good luck on solving this. Popping up on multiple instances and seemingly unrelated to the update. Wouldn't want to be the one debugging.
I hope this is banished, and quickly. This absolutely ruins Lemmy as everything feels quieter than it really is because you see fewer posts, and worst everyone feels ignored themselves as you don't even get any upvotes let alone replies.
This bug is like half of users are suddenly shadow-banned, something designed to stop users from interacting.
This whole fediverse feels very shaky tbh, we have this issue now but as someone who is usually on kbin there's been issues like these from the start - posts not getting propagated to other instances, mod actions not being sent or updated, missing entire domains because of the bugs in the filter, etc. Add to that legitimate choices like defederation and domain blocking, it just feels fractured and nonfunctional because I still need a separate account on every instance to actually participate on it.
I know it's a FOSS project with no guarantees and everything these people do is in their free time but I really wish stability and basic functionality was the first thing they focused on, otherwise everything else is in vain since it's on top of an unstable foundation.