NOTICE: Community locked. Join us at !android@lemdro.id)

TLDR: To promote unity and simplicity, we’re ‘merging’ with c/Android over at lemdro.id (a new, tech-focused Lemmy server!)

Don’t worry, you don’t need to make a new account. You can still join it even if your account is on Lemmy.World — just click this link c/Android at Lemdro.id and subscribe, the same way you did here. Indeed, many of you are already based on instances other than LW — that’s the handy thing about the fediverse.

Why are you doing this?

We’ve thought hard on this decision, and had some long chats with not only the team running c/Android over there, but also the admin of lemdro.id itself.

Our feeling, and our decision, is that while having multiple communities for the same topic is a key strength of the fediverse, we’re keen to avoid unnecessary fragmentation for existing members and confusion for any newcomers.

As most of you know, the team at lemdro.id are experienced moderators, having run the Android subreddit before The Great API Quake of 2023.

Why don’t they simply join us here?

LW is a great instance, but lemdro.id’s entire purpose is tech, and its admin is working hard to make it the fastest and most robust instance around for people like us. It’s the right home for this community.

How does it benefit me?

We’re hopeful that our goal of a community managed by experienced moderators is aligned with your expectations for a well-run, respectful community.

We also believe that a fast, dedicated ‘world’ of tech communities will prove ideal for people like us — people who expect excellent uptime and reliable, fast loading of its features and functions. (No pressure, lemdro.id team! 😂)

Lastly… Well, see the next point.

What happens to this community?

We have locked this community.

As we’ve said above, we want to avoid fragmentation and duplication of threads, and that’s best achieved by not having two identical communities.

Unfortunately, we can’t just pack up all the threads here and take them to lemdro.id, but they’ll live on as an archive.

It’ll always be here if we need it, but right now it’s only a few weeks old — despite its massive growth — which means locking it won’t rob us of too much historical content.

See you over at c/Android at Lemdro.id!

EnglishMobster,
EnglishMobster avatar

Also over here on Kbin, can't join https://kbin.social/m/android@lemdro.id. They need to fix their federation settings.

exscape,
exscape avatar

I subscribed just now. 31 others were before me.

eatmoregreenfood,
eatmoregreenfood avatar

2nd

EnglishMobster,
EnglishMobster avatar

They locked their community on Lemmy, so none of these replies will likely federate. I sent @mikestevens a DM on Lemmy.world, though; hopefully they see it and can get it fixed.

MxM111,
MxM111 avatar

still 404 not found for me.

1Fuji2Taka3Nasubi,
Pamasich,
Pamasich avatar

In case anyone looks in here in the future:
It works now, kbin and lemdro are federating, the link in the post just doesn't work for kbin. Correct link is https://kbin.social/m/android@lemdro.id

radialmonster,

404 Not found

quortez, (edited )
quortez avatar

Ah, in the meantime Kbin can't federate with lemdro.id because of a config issue, leaving us with no Android magazine. Fun fun fun

atocci,
atocci avatar

It seems to work now in case you haven't tried in a while like me.

ImaginaryFox,

The idea of more communities being on different instances is a good thing to avoid issues that can come with centralization. Just need to fix the federation so kbin users can join too.

SnowboardBum,
SnowboardBum avatar

Well Lemdro.id and Kbin better federate or eff it

Drusas,

Yeah, as a kbin user, I'm not going to follow it to some random instance.

tal, (edited )
tal avatar

According to lemdro.id's instances page, it is configured to federate with kbin.social and a number of other kbin instances.

https://lemdro.id/instances

However, I don't see any metadata from any of the kbin instances on that page. If that is not normal, I am wondering if something is broken that is causing it to fail to federate with kbin.

https://kbin.social/d/lemdro.id doesn't show any messages from it, either.

EDIT: lemmy.world also doesn't show any metadata on its instances page for kbin.social, and I know that those two are federated and working correctly.

https://lemmy.world/instances

So that lack of metadata might just be an artifact of kbin and lemmy in their present forms interacting.

Lemdro.id is configured to federate, though.

EDIT2: Someone filed a bug on it on the kbin issue tracker. I'm not sure that it's actually a lemmy or kbin issue, but at least it's on the radar.

https://codeberg.org/Kbin/kbin-core/issues/637

Pamasich,
Pamasich avatar

deleted_by_author

  • Loading...
  • tal, (edited )
    tal avatar

    Hmm. If they blow up on arbitrary User-Agent strings, I'd think that they are going to also have problems with client software.

    EDIT: Not to mention that search engines will probably fail to index their content.

    tal,
    tal avatar

    Definitely a lemdro.id issue. Not kbin nor lemmy.

    The admin at lemdro.id thinks that he fixed it, says that they believe it to be a problem with the default ngnix configuration in lemmy.

    https://lemdro.id/post/21449?scrollToComments=true

    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!

    Pamasich,
    Pamasich avatar

    deleted_by_author

  • Loading...
  • tal,
    tal avatar

    But if that was the issue, surely it would have affected other lemmy instances too.

    I'm inclined to agree, but the flip side: if it's purely due to rejection of User-Agent, then fedia.io should also be unable to federate, since I doubt that they've modified their User-Agent, and he's correct that fedia.io can see content from lemdro.id -- I can see communities on lemdro.id while browsing fedia.io.

    Could be that there are multiple issues, I suppose.

    Pamasich,
    Pamasich avatar

    Ah actually, I think I'm just an idiot. Sorry about that.

    I blindly reused the curl -I --user-agent "kbinBot v0.1" https://lemdro.id/u/test because I assumed, after successfully using it on 30+ of the top instances, that "test" is just a mandatory user on every instance. But it turns out lemdro.id simply doesn't have a user like that, that's why it fails.

    tal, (edited )
    tal avatar

    Ah, gotcha, thanks for following up, especially since others might be banging on this. But no harm, no foul. It's not like there's some standardized "kbinlint"/"lemmylint" tool. Yet, anyway. Everyone's kinda feeling their way in the dark.

    EDIT:I'd also add that I'm a little skeptical that he has it right either about his changes fixing it for kbin.social. I don't know how kbin handles this, but I would think that it wouldn't do a full dump of all the content on another server before displaying some of it. But I don't see anything at all at https://kbin.social/d/lemdro.id and that seems suspect that it's "slow but federating right now" and more that it's not federating at all.

    EDIT2: Wait, no, just started seeing it when searching for @android@lemdro.id on kbin.social.

    EDIT3: And it's visible: https://kbin.social/m/android@lemdro.id

    Midnitte,
    Midnitte avatar

    Looks like it's fixed

    Hairyblue,
    Hairyblue avatar

    Kbin here too. Can't join.

    HidingCat,

    Gah, it hasn't federated yet with Kbin. :(

    Midnitte,
    Midnitte avatar

    Seems like there's a bug affecting the given links for us as well.

    trafficnab,

    It almost works, but it's linking to /c/android@lemdro.id instead of /m/android@lemdro.id (also it's not federated with kbin yet)

    Chozo,
    Chozo avatar

    I'm still learning how federation works, but I thought that there was supposed to be some sort of automated process that the users can initiate to begin federating with new instances? I seem to remember something about once a user manually subscribes to a community, that their instance then auto-federates, or something. I could also be way off base here or just thinking of some other feature entirely.

    EnglishMobster,
    EnglishMobster avatar

    You are correct, but you're supposed to search Kbin for @android@lemdro.id. For whatever reason, the lemdro.id folks haven't set it up so Kbin is allowed to federate, and thus it doesn't work.

    mizzyc,
    mizzyc avatar

    So the problem is at lemdro.id config? I don't know if I understood it well

    Chozo,
    Chozo avatar

    Ah, thanks for clarifying that for me!

  • All
  • Subscribed
  • Moderated
  • Favorites
  • android@lemmy.world
  • khanakhh
  • DreamBathrooms
  • InstantRegret
  • magazineikmin
  • osvaldo12
  • mdbf
  • Youngstown
  • cisconetworking
  • slotface
  • rosin
  • thenastyranch
  • ngwrru68w68
  • kavyap
  • ethstaker
  • JUstTest
  • tacticalgear
  • modclub
  • cubers
  • Leos
  • everett
  • GTA5RPClips
  • Durango
  • anitta
  • normalnudes
  • provamag3
  • tester
  • megavids
  • lostlight
  • All magazines