this might be related to https://github.com/LemmyNet/lemmy/issues/4865
well, there you go @[email protected] :)
looking over the mlmym code, it appears that there is a hardcoded cookie expiration of 30 days.
You might want to raise an issue on GitHub about this.
image proxying is currently not usable for us anyway, see e.g. https://github.com/LemmyNet/lemmy/pull/4874
correct.
we don't have an eta currently. we're still keeping an eye on issues reported by other instances.
which features are you looking for?
@[email protected], 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 @[email protected] 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, @[email protected] (kbin.social owner, main kbin dev) said 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.
if everything works people typically don't post.
although @[email protected] hasn't had any activity here recently, that doesn't necessarily mean he's not active. also, there might be other people who had the same issue and found a solution, which there probably is one if this just started recently.
or maybe there won't be a response, but you won't find out if you don't try.
The [email protected] community is probably a better place to ask this.
a.lemmy.world just runs the latest version of alexandrite, although there haven't been any updates recently.
this doesn't seem to be targeted against you, just someone not liking the comment. some people order their feed by e.g. active, so such cases will show up quickly.
looking at your recent comments from the last 3 days, many of your comments don't have any downvotes. am I missing something?
this appears to be a UI bug, via API call this can be done.
somewhere in this box? it only shows the option for a moderator i believe
as you deleted it yourself you should be able to undelete it by visiting https://lemmy.world/c/climate
it was a significant part of the brand of a spam/advertisement campaign several months ago
it's removed from our slur filter now
Hi,
there seems to be an issue with the mastodon instance requiring AUTHORIZED_FETCH
.
Lemmy 0.19.3 does currently not have a working implementation of authorized fetch, this should get fixed in 0.19.4 when that is released.
For now, the only workaround is to disable secure mode on mastodon.
edit: see also https://github.com/LemmyNet/lemmy/issues/4451
Keep in mind that this is the Lemmy.World support community, not Lemmy in general, so this post may not be seen by Lemmy devs.
If this was implemented, I doubt it would make it as a core Lemmy feature. This would like have to be built into either clients/interfaces (obviously each one would have to do this one their own), or it would probably have to be built on top of the planned upcoming plugin system.