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
https://github.com/LemmyNet/lemmy/issues/4039
What the bug means is essentially
- We still get all posts and comments around the fediverse like normal (so youll see posts made in other communities populate the feeds like normal)
- Posts and comments made by users in programming.dev are not visible outside programming.dev
Hopefully itll be resolved soon. If anyones able to get some info that would be helpful towards resolving the bug throw it here or in the github issue
Oh god I thought people hated me.
-_-
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
Isn’t it weird how much those replies or votes matter? It feels good to know that you aren’t shouting into the abyss!
The nice thing in Lemmy is that even when the posts have a lot of comments, you get good engagement. And I haven’t come across many of the bad attitudes from reddit
Nah they’re just ignoring you
This :) I made a question post and I’ve had only my one upvote for 2 days.
I am going to go upvote everyone lol.
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.
I wouldn’t judge the fediverse for Lemmy or kbin, which are pretty new actors. GNUSocial or Mastodon are pretty well established, I don’t remember things like this happening in the “Twitter-like” side
True, I did mostly mean the thread-style sites. Mastodon seems relatively stable for the last year or so
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.
You have that opinion, but then there are others that come along and ask for all kinds of polished features - and not even nicely. “Why don’t you just”.
If you want these “basic features” then the best way to get them is to contribute.
I know of one dev that is making their own threaded forum and link aggregator project using ActivityPub. They are focusing on better architecture while maintaining compatibility with Lemmy’s ActivityPub implementation. They seem to be making good progress, but it isn’t ready for an alpha release yet. I hope they stick with it. There’s a lot of potential for improvements for both administration and user experience over Lemmy’s design.
Yeah I made a post in homeowners asking for advice, and seeing how I didn’t get any responses after hours, ended up posting it ‘elsewhere’ after a long long time. Later realized it could be a federation bug, posted it from my lemmy.world account, and got responses right away.
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)
Yes and I have a post that I will make about this in a bit. I’ve been writing it over the past few days, but haven’t had time to finish it up.
Oh…
Oh.
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.
alright so seems to be affecting most things. My current theory is the instance believes the other instances are dead so wont sent actions to them
deleted by creator
Hey! Seems my instance can receive posts from yours; both [email protected] and [email protected] 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…
