MrKaplan on Nostr: > > @PugJesus@lemmy.world, you might have been posting only for LW users for a while ...
>
> @PugJesus@lemmy.world, you might have been posting only for LW users for a while :-/
>
this is unfortunately correct for the time being.
while we still have aggressive rate limits in place to limit federation impact from kbin bugs, which started with the measures that sunaurus (npub1gvs…c0rk) mentioned, this wouldn’t impact activities coming from lemmy.world towards kbin.social.
while kbin.social used to break down every now and then based on what i saw people comment, service was typically restored within a short period of time. more recently however, any time i’ve looked at kbin.social in the past couple weeks, it’s only been showing an error page. i suspect it may have been unavailable the entire time, not just at the times i looked at it. looking at our federation stats, the last successfully sent activity from lemmy.world to kbin.social was dated 2024-06-18 00:12:25 UTC, although the actual send date may have been later. successful is also not necessarily guaranteed, as some error codes might be misinterpreted as success due to how servers can be set up and how response status codes are interpreted on the sending side.
if activities sent from lemmy.world don’t reach kbin.social then the posts and comments won’t be relayed to other instances. this is generally an issue in activitypub when instances are down, as such “orphaned” (at the time) communities effectively become local-only communities, isolated islands on all instances that already know about them.
at this point, the last time we’ve received an activity submission (federation traffic) from kbin.social as on 18th of June, so it seems like it was working for some time on that day and has been broken since.
at the start of this month, [@ernest@kbin.social](https://kbin.social/u/ernest ) (kbin.social owner, main kbin dev) [said](https://codeberg.org/Kbin/kbin-core/issues/1383#issuecomment-1999046 ) that he was going to hand over management of kbin.social to someone else, as he’s currently unable to take care of it. presumably this hasn’t happened yet.
> @PugJesus@lemmy.world, you might have been posting only for LW users for a while :-/
>
this is unfortunately correct for the time being.
while we still have aggressive rate limits in place to limit federation impact from kbin bugs, which started with the measures that sunaurus (npub1gvs…c0rk) mentioned, this wouldn’t impact activities coming from lemmy.world towards kbin.social.
while kbin.social used to break down every now and then based on what i saw people comment, service was typically restored within a short period of time. more recently however, any time i’ve looked at kbin.social in the past couple weeks, it’s only been showing an error page. i suspect it may have been unavailable the entire time, not just at the times i looked at it. looking at our federation stats, the last successfully sent activity from lemmy.world to kbin.social was dated 2024-06-18 00:12:25 UTC, although the actual send date may have been later. successful is also not necessarily guaranteed, as some error codes might be misinterpreted as success due to how servers can be set up and how response status codes are interpreted on the sending side.
if activities sent from lemmy.world don’t reach kbin.social then the posts and comments won’t be relayed to other instances. this is generally an issue in activitypub when instances are down, as such “orphaned” (at the time) communities effectively become local-only communities, isolated islands on all instances that already know about them.
at this point, the last time we’ve received an activity submission (federation traffic) from kbin.social as on 18th of June, so it seems like it was working for some time on that day and has been broken since.
at the start of this month, [@ernest@kbin.social](https://kbin.social/u/ernest ) (kbin.social owner, main kbin dev) [said](https://codeberg.org/Kbin/kbin-core/issues/1383#issuecomment-1999046 ) that he was going to hand over management of kbin.social to someone else, as he’s currently unable to take care of it. presumably this hasn’t happened yet.