this post was submitted on 11 Jul 2023
17 points (100.0% liked)

/kbin meta

12 readers
1 users here now

Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign

founded 1 year ago
17
lemmy.ml is no longer shadowbanning kbin. (lemmy.ml)
submitted 1 year ago by [email protected] to c/[email protected]
45 comments fedilink hide all child comments
 

Apparently one of the lemmy.ml admins was overzealous in banning all User-Agent strings that contained the word "bot". Bans were entered for all of the individual strings containing that word which were observed in their webserver logs, which impacted kbin's reported agent of "kbinBot".

The issue has been fixed, and I observed that one of my kbin posts to a lemmy.ml community was successfully pushed to the original instance.

Edit:

Here are all the links that I've found with the lemmy.ml admins discussing the issue:

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago (1 children)

A community migration tool would 100% make sense for both Kbin and Lemmy, especially if there were an option to link the old, read-only community to the new location, redirect users to the new location from the old. That would also facilitate consolidating communities who want to consolidate.

[–] [email protected] 0 points 1 year ago (1 children)

If I signed up to a mag on one instance, that doesn't mean I want to sign up to it on a different instance.

[–] [email protected] 1 points 1 year ago

Fair, so perhaps just a notification that goes out if an instance moves? Community with its settings and posts moves, but the users can be invited (or not, per their settings) to migrate too?