![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://media.kbin.social/media/7c/2e/7c2ea86f465a9c71b8502a8c0b557d93dc0a9914bf425d92b2c802a3de80f9d2.png)
Is this an acceptable viewpoint
No. Go away.
Is this an acceptable viewpoint
No. Go away.
I guess that’s possible. The instances I mentioned look like this:
https://fedidb.org/network/instance/parapheum.com
2 posts, 1 comment overall.
It had 10 users two days ago and 4.6k today, not a single one of them seems to have posted or commented.
Some small instances are seeing sudden increases in numbers of registered users (4k to 5k new users) but not an equivalent growth in activity, my guess is someone is creating accounts on instances without captcha enabled for account registration. Most of the top 10 fastest growing instances shown here fit that criteria.
Hexbear migrated to upstream Lemmy yesterday (they were running a home developed fork from an earlier version of Lemmy). I submitted the instance to fedidb earlier today (after a bunch of failed attempts because fedidb kept erroring out/timing out for some reason). Afaik, federation is not active (yet) on their instance.
Hexbear.net migrated to upstream Lemmy.
Lemmy has an option to mark an account as a bot under user settings, OP had a bot icon next to their username on all of their posts with a message that said the account was a bot. They have since disabled that setting for their account, so it no longer shows up, but you can see how someone could have jumped to the conclusion that the account was a bot (this icon won’t show up on all Lemmy UIs, it’s missing from the mobile website/Jerboa app, but it’s shown on desktop). Anyway, no need to use such incendiary language, you may not be angry but it can easily come off as that over text.
This is something that I don’t quite get because Kbin doesn’t even have an option to collapse comments, are there are any other things that you think Kbin does better than Lemmy? I also don’t like how the thumbnails are stretched for image posts, and that images open on a second page load instead of inline. The lemmy experience in 0.17 was a bit messy with webhooks, but 0.18 is much better (check lemmy.ml for an instance running 0.18).