Demigodrick

Demigodrick, 4 months ago

So it looks like they’re pushing to us OK, but we’re struggling to push our stuff to them. I did just try to visit the site and got a 502 error so not sure if they’re having issues over there?

This link shows a bit more detail and you can see hexbear under “failing instances”. Lemmy.ml and lemm.ee have the same issue as us, and I’m sure others will too. So either Hexbear’s incoming federation is broken or they’ve been offline enough for instances to automatically flag them as offline.

Will see if there is an easy fix for this, but hopefully the federation fix in 0.19.2 will prevent this from happening in the future (if this is what it causing the issue and not a config issue hexbear side).

Demigodrick, 4 months ago

So after the upgrade we pushed all our stuff to them (I can see our posts on hexbear site directly now) so with any luck everything has been fixed :) let me know if you see anything else not right!

Demigodrick, 4 months ago

The issue lies with lemmy.world who are still on lemmy version 0.18.5. If there is any downtime or an issue with their server (of which historically there has been a lot of) then federation doesn’t work properly and the server won’t push new comments or posts to other servers. There can also be some discrepancies based on when someone subscribes too, although I don’t know if that’s been fixed now.

You can see this happens on other servers too:

• reddthat
• lemmy.ml
• db0

The newest version of lemmy (0.19) contains a persistent federation queue so federation issues from between 0.19 servers should be massively reduced.

Idk why lemmy.world hasn’t updated either, but it would be a benefit to the lemmyverse for them to update soon.

Demigodrick, 4 months ago

No worries :)

I think the easiest way to summarise federation is to think of email - the servers email each other for each action that happens, but when the server doesn’t work properly, that email doesn’t get sent and you end up with situations like this unfortunately.

Demigodrick, 4 months ago

Whoops, forgot to add to the post!

Its https://opencollective.com/lemmyzip

Demigodrick, 4 months ago

I think the general consesus is that its to do with the new peristent federation queue, i.e. if the server goes down, it won’t lose any posts to federate, which should improve federation across Lemmy.

In terms of financials, I’ve tried to keep it at 12 months in the bank at any one time, in case of fluctuations (or situations such as this one!), so the overall goal would be around £375.

Demigodrick, 5 months ago

We updated to 0.19.1 so the fixes have been applied here

Demigodrick, 5 months ago

Only about 2 seconds, not enough to register on any downtime detectors!

Demigodrick, 5 months ago

Following the community vote we’re still defederated with threads and have no plans to change that.

Lemmy 0.19 introduces the ability to make your own choice by allowing you to defederate with threads yourself regardless of server though. With any server on 0.19 you can go into your settings and add threads to your blocked instance list.

I think it’s also important to point out that they’re only testing federation with mastadon at this point, there’s nothing to say they are in a position to federate with Lemmy. If/when that changes this community can have further discussions on the subject.

Demigodrick, 5 months ago

Oh dear 🙁 I’ll check if there’s any open issues on github and if not I’ll open a new one so they can fix it.

Ps - welcome!

Demigodrick, 5 months ago

Probably worth exploring. Scaled for me is just full of the lemmit repost bot!

Demigodrick, 5 months ago

I do, I have to keep it on in case a bot account starts spamming stuff (plus there are some good bots out there!). I’ll probably personally block that lemmit bot at some point though.

Demigodrick, 5 months ago

I think you’re lost friend, but Lemmy.zip will deploy 0.19.1 once released.