MrKaplan

joined 9 months ago
[–] MrKaplan@lemmy.world 8 points 2 days ago

!superbowl@lemmy.world

[–] MrKaplan@lemmy.world 4 points 2 months ago (1 children)

you may have been thinking of https://poliverso.org/objects/0477a01e-1166-c773-5a67-70e129601762, which was neither lemmy devs, mastodon devs nor lemmy.world admins

[–] MrKaplan@lemmy.world 13 points 3 months ago

Us not upgrading has nothing to do with making a point.

We're aiming to run a stable instance, which can come at the cost of delayed updates.

We didn't update to 0.19.4, and a few weeks later 0.19.5 was released with a number of critical bugfixes.

0.19.6 will have several more fixes for issues introduced in 0.19.4+, such as a fix for remote moderators updating local communities, allowing admins to filter modlog entries by moderator, as well as some performance issues reported by other instances.

We usually wait for other instances to run the latest version for some time to allow bug reports to surface before we update ourselves.

[–] MrKaplan@lemmy.world 3 points 3 months ago

I'm a member of the Lemmy.World admin team.

Also, anyone can look at the moderation log at https://lemmy.world/modlog

[–] MrKaplan@lemmy.world 4 points 3 months ago (2 children)

It depends on who you're trying to message.

Devs: https://join-lemmy.org/contact
Admins of Lemmy.World: see the post that @Deestan@lemmy.world linked already
Admins of piefed.social: https://piefed.social/about
Community moderators: check the community sidebar, it will show the moderator list

Your Lemmy.World account has been unbanned a couple days ago btw.

[–] MrKaplan@lemmy.world 5 points 3 months ago

It's not automatic, admins have the option to ban with or without content removal.

Different instances deal with this differently and admins are also humans that sometimes make mistakes. Especially during holiday season there are frequently trolls running around with racist, transphobic or other offensive content. Sometimes they're more obvious, sometimes they try to fly under the radar a bit by being less direct. In the end you're at the mercy of the instance admins of the instance you signed up with and many instances will provide contact information to appeal bans.

Since this account was not a Lemmy.World account it's not up to us to decide whether or not the user should be banned and whether their content should be removed.

[–] MrKaplan@lemmy.world 7 points 3 months ago (2 children)

If you're referring to the post Ex Redditors of Lemmy what made you come on over? What happened at Reddit that you made the switch?, their account was banned for trolling and all content associated with the account was removed.

Some examples of their post titles, that likely contributed to their ban

  • African Americans (I hope that PC) have you ever gotten the N word tossed at you and how did you react or feel?
  • How come in most games including the community of gaming I can't mention the word Nazi for have a civil conversation?

They also had a number of other posts that seemed to be doing just fine, so it might be falling in the "stupid kid" category.

The post has since been restored by a community moderator, although the user's account on lemmy.ml is still banned: https://lemmy.world/post/17593614

[–] MrKaplan@lemmy.world 10 points 4 months ago (1 children)

@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@lemm.ee 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 (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.

[–] MrKaplan@lemmy.world 9 points 5 months ago (1 children)
[–] MrKaplan@lemmy.world 3 points 7 months ago

we've switched from using multiple federation sending containers (which are supposed to split receiving instances across workers) to just using a single one.

[–] MrKaplan@lemmy.world 0 points 8 months ago

fwiw, it does not appear to be triggerable from within lemmy at this time.

I've just tried this on another instance and lemmy complains

The webfinger object did not contain any link to an activitypub item

I suspect this currently can only be triggered from threads.

[–] MrKaplan@lemmy.world 6 points 9 months ago

it's not just this community getting hit.

it's mostly !asklemmy@lemmy.ml, !asklemmy@lemmy.world, !opensource@lemmy.ml and !selfhosted@lemmy.world, though some of the latest spam also started arriving in !warframe@dormi.zone

view more: next ›