There was a bug with KBin some days ago where it would send huge amounts of federation activities to Lemmy instances which would overload them. To mitigate this, lemmy.world and some other instances had to block kbin.social. I believe the .world admins tried to get in contact with @ernest. You can read some more details here.
I would also suggest that you and Ernest join the Lemmy Admin chat on Matrix where this problem was found and discussed.
Right my_user.discussion_languages is the correct one. And it being empty means that all languages are enabled (to avoid storing lots of unnecessary db rows). Im testing with a new account on ds9.lemmy.ml and can see posts marked as English without any problems.
I cant really how such a problem could happen and only affect those specific instances. Can you check through the api which languages are enabled on a new account? The info is under /api/v3/site in the field discussion_languages, it should contain numbers from 0-183 which are all the language ids.
I confirmed this just now, when registering a new account all discussion languages are enabled. However this isnt properly indicated in the lemmy-ui user settings.
When you signup, all languages are enabled by default. I believe it was like this since the feature was first implemented. I recently made a pull request so that languages are automatically configured from accept-language header.
The automatic language tag should only depend on the community language settings and user language settings. Specifically it will build the intersection of both, and if the result only contains one item (excluding “undetermined”), that is used as the post language. The instance doesnt matter at all. And there havent been any changes in this area in a while, so there should be no difference between 0.19.x versions.
I thought maybe the community language isnt federated properly but its identical on all mentioned instances. Also @Camus mentioned that French is enabled in user settings. There is clearly a bug but I cant think what else might be causing it.
Anyway please report such bugs directly on the issue tracker, otherwise I might not find out about it at all.
This is strange because neither of the communities you mentioned has any language restrictions. Can you say what error is being returned exactly? You might have to use browser dev tools to see the details.
Showing authorship would be quite tricky because there might be dozens of editors, and the Lemmy ui simply doesnt have space for that. Editing articles from Lemmy would also be tricky , so yes some type of single signon would make more sense.
Wikipedia is simply the one I’m familiar with, and learning about all these problems was what motivated me to start working on Ibis. But afaik Wikia doesn’t work any different in a technical sense, so of course Ibis can also be used for those cases.
Thanks for the support. I think the era of single, centralized sources of information will soon be in the past.
This would be a project on its own, with writing import scripts, hosting an instance etc. Certainly not something I have time for, just like I’m not running a Reddit mirror for Lemmy. If you or someone else wants to set it up, go ahead!
How would you detect that it’s the same article, only from having the identical title? That could fail in lots of ways.
I agree that it would make sense to integrate a wiki into Lemmy. However that’s much more complicated than a standalone project, because it needs to integrate well with all the existing features. Plus it means more work for all the Lemmy developers, while Ibis could be handled by a completely separate dev team.
Also having Ibis tightly integrated with Lemmy would automatically limit the userbase to existing Lemmy users. The potential userbase for an independent project is much bigger.
That said it would be good if Ibis can optionally integrate with Lemmy, but I’m not sure yet how that would work. The most straightforward option would be to treat Ibis articles as normal Lemmy posts, but maybe that doesn’t make the most sense.