preview
The latest posts on Lemmygrad have not federated to Hexbear (4588 behind currently).
The latest posts on Lemmygrad have not federated to Hexbear (4588 behind currently).
@Trying2KnowMyself@hexbear.net
they/them/their/theirs/themself
Don’t worry, you can be a misogynist on Hexbear! Just make sure you’re talking to a pup-girl first so you have plausible deniability and can complain that you aren’t being interpreted charitably enough for your blatant misogyny.
The latest posts on Lemmygrad have not federated to Hexbear (4588 behind currently).
The latest posts on Lemmygrad have not federated to Hexbear (4588 behind currently).
The latest posts on Lemmygrad have not federated to Hexbear (5450 behind currently). There was an outage there recently which probably contributes.
The latest posts on Lemmygrad have not federated to Hexbear (5450 behind currently). There was an outage there recently which probably contributes.
At some point, it appears lemmus.org has decided to block us, though they still appear on both our linked and allowed instance lists: lemmus.org/instances
Unsurprisingly:
Surprisingly:
Anyways, I continue to not understand how federation actually works. I said something in the past about lopsided federation, but that was a case where federation in both directions was the expectation, and it’s clearly not the case this time - it seems like lopsided is perhaps exactly what we expect.
Since Hexbear’s side of things seem to be working as expected, and so does the lemmus side, I’m not going to follow up with any admin pings myself on this one, but figured I’d document it still in case someone else strongly feels like partially federating with an instance that won’t federate back should be changed.
At some point, it appears lemmus.org has decided to block us, though they still appear on both our linked and allowed instance lists: lemmus.org/instances
Unsurprisingly:
Surprisingly:
Anyways, I continue to not understand how federation actually works. I said something in the past about lopsided federation, but that was a case where federation in both directions was the expectation, and it’s clearly not the case this time - it seems like lopsided is perhaps exactly what we expect.
Since Hexbear’s side of things seem to be working as expected, and so does the lemmus side, I’m not going to follow up with any admin pings myself on this one, but figured I’d document it still in case someone else strongly feels like partially federating with an instance that won’t federate back should be changed.
cross-posted from: lemmygrad.ml/post/10944631
as far as i can tell, hexbear users are seeing all content from grad including comments and posts but lemmygrad users arent seeing any content from hexbear, so if you make a post in a hb comm and arent getting replies this is why
Comment from @muad_dibber@lemmygrad.ml suggests it’s an issue on the Hexbear sending side @CARCOSA@hexbear.net
cross-posted from: lemmygrad.ml/post/10944631
as far as i can tell, hexbear users are seeing all content from grad including comments and posts but lemmygrad users arent seeing any content from hexbear, so if you make a post in a hb comm and arent getting replies this is why
Comment from @muad_dibber@lemmygrad.ml suggests it’s an issue on the Hexbear sending side @CARCOSA@hexbear.net
There are newer posts: lemmygrad.ml/c/socialism
I haven’t checked other comms holistically, but spot checking GenZedong, the only missing post is due to a user being banned on hexbear.
There are newer posts: lemmygrad.ml/c/socialism
I haven’t checked other comms holistically, but spot checking GenZedong, the only missing post is due to a user being banned on hexbear.
It looks like federation from Hexbear to discuss.tchncs.de works, but not the other way around. For example, on db0 we can see a user reply to a Hexbear comment, but it doesn’t show up when viewed from Hexbear. Maybe this is an intentional side effect of how (de?)federation works, but this post seems to suggest we intend to be federated, we appear in their linked instances, and not in their blocked instances, while our linked instances shows them, but allowed does not (it has discuss.techncs.de though, which appears to no longer exist?)
Anyways, it seems like the relationship shouldn’t be so one-sided. Either neither direction should work, or both should, but maybe there’s just something I don’t understand here.
E: also adding a screenshot of my comment to the post, because while I assume y’all can see it, I don’t really fully understand what happens with posts/comments in this comm:

It looks like federation from Hexbear to discuss.tchncs.de works, but not the other way around. For example, on db0 we can see a user reply to a Hexbear comment, but it doesn’t show up when viewed from Hexbear. Maybe this is an intentional side effect of how (de?)federation works, but this post seems to suggest we intend to be federated, we appear in their linked instances, and not in their blocked instances, while our linked instances shows them, but allowed does not (it has discuss.techncs.de though, which appears to no longer exist?)
Anyways, it seems like the relationship shouldn’t be so one-sided. Either neither direction should work, or both should, but maybe there’s just something I don’t understand here.
E: also adding a screenshot of my comment to the post, because while I assume y’all can see it, I don’t really fully understand what happens with posts/comments in this comm:
