Is this being worked on/looked at? I ask since the post mentioned discussion was happening with the .id admins but I haven’t seen any answers about whether that’s a priority (it seems Lemdro.id is the one that needs to federate with k.bin).
Just kinda bummed since I use kbin the vast majority of this time.
Edit: ah cool, quick turnarounds are sexy. Thanks @cole@lemdro.id!
Edit: A fix has been deployed, and federation should work now. Unfortunately, kbin.social is taking its sweet time federating with us, it is probably overloaded. Lemdro.id is already accessible from other kbin instances such as fedia.io (https://fedia.io/m/android@lemdro.id)
Hello! Admin here at lemdro.id. This is the result of several problems in the lemmy default reference nginx config. I am working on resolving this right now and should have it fixed within the next 30 minutes!
Once you’ve finished updating it, can you share the changes you made to your Nginx config? If the default references have issues with them, I’d like to make sure mine doesn’t have the same problems.
sure! take a look at this issue: https://github.com/LemmyNet/lemmy-ansible/issues/106
It is likely yours is fixed if you deployed recently
You can test an instance like this.
Find a local user on the instance and get their page (https://instance.tld/u/username).
In linux:
curl -X GET -H ‘Accept: application/activity+json,application/json’ https://userlink
If the result is html they have not patched, if it is json, they have patched.
curl -X GET -H ‘Accept: application/activity+json’ https://userlink
Will return json all the time on all instances.
I patched my kbin instance to send just the latter until it’s resolved everywhere.
Thanks! I use my own deployment that uses Caddy, and I based it on their example Caddyfile. But it looks like I might be good. Their reference Caddyfile accepts application/* with an asterisk, which seems to sidestep this issue entirely!
Great news! Likewise, kbin.social doesn’t seem to be updating content from lemmy.world communities either (I’m seeing some a week late).
Not sure if this is related, but I tried replying to a comment from a user on kbin, and my instance wouldn’t send the reply. They still have federated posts and top-level comments though, even mine. Maybe their queue is just overloaded.
It looks like it’s working again. Interesting! https://kbin.social/m/android@lemdro.id
I’m happy to see the merger and happy to see /r/Android show up on Lemmy. I think it’s nice to see it move off of Lemmy.world. as well. It will help lighten the load.
Man, I’m really not feeling the community merge. Moving the 5th biggest lemmy.world community to one that’s like 12x smaller in subscription size feels like an unnecessary hit to any momentum it had. Especially because asking people who moved places like Reddit to move again does not sound like a good idea (though obviously less effort than moving to another website).
I do hope I’m completely wrong though and hope this comm gains lots of traction. Moving to an instance dedicated to tech does sounds like a good idea (although I don’t know the benefits yet). Also, if it had to happen, better now than later.
Oh shoot you’re right. Did not know that. From my community I see 1.6k, and from lemdro.id its 3.6k.
I like anything that pulls users away from big instances and onto smaller ones. Guys, it’s not a DECENTRALIZED system if you’re all centralizing on one massive instance.
The advantage to decentralized to me is not to have more instances, its that if things go wrong everyone can bail.
To where, if the big instance that everyone centralized on goes to shit? The internet itself is decentralized. Anyone can run a website, but no matter how enshittified corporate websites become, people are “somehow” still stuck on Google, Meta, Microsoft etc. websites and services.
I wish there was a way to keep communities “in sync”, like you have the big and small communities with the same posts and comments, everything’s the same, so people who are on Lemmy.world could go to Android@Lemmy.World and have the same content we have here without having to discover this community.
Would help combat fragmentation, and the sync could be broken if things go south
Thanks for sharing your thoughts on this, truly. The hope is to actually have better accessibility from across the Fediverse with the move. Lemmy.world is grappling with some challenges that come along with its scale, including being de-federated from Beehaw. Lemdro.id currently maintains federation with both and, with the fixes Cole made to the Lemmy Nginx config, should be accessible just fine from Fedia as well.
One major plus here is also our time zone coverage for moderation. Steve and Devgard help fill out our moderator time zone spread, which is quite comprehensive now. We’re already seeing attempts at spam in the Fediverse and moderator tools aren’t quite there yet… so the manual efforts are pretty key!
I agree. I can understand this is a tech-focused instance but that doesn’t means Lemmy World was not right for us. If someone creates an Android-focused instance then we would move again because that would be even more suitable than this one?
However I expect the community to keep growing and next time it would be nice if mods ask the members before taking decisions that affect the whole community.
lemdro.id was actually created with the original intent of hosting Android, but has kind of grown a little to more general technical content in the same realm. I definitely hear your point though. Personally, my hope is this helps take load off of lemmy.world. This is my contribution to make the fediverse more viable long-term as it continues to grow
I’m still learning about the fediverse. How does this community fund itself long term?
I agree as well, I think a vote next time with the members of the community would be better before making a change.
It seemed like the community over on lemmy.world had more posts and subscribers as well. As someone else mentioned, at a time like this when users are moving from Reddit to Lemmy, now users are being asked to move again to another community. I understand its not hard to click subscribe on the new community, but at the same time all of the posts and comments will no longer be displayed here.
Glad to see this has been solved thanks to Cole addressing a bug in the Lemmy’s Nginx config!
