I just want to say old.lemmy.world is fantastic. However, old can have negative connotations. Can we declare that OLD be an acronym for Optimal Lemmy Delivery?
I just want to say old.lemmy.world is fantastic. However, old can have negative connotations. Can we declare that OLD be an acronym for Optimal Lemmy Delivery?
Yes and no.
old.lemmy.worldis anmlmym clientthat is preconfigured to use thelemmy.worldinstance. The client and the API need to be compatible for them to work together smoothly. It is possible that,mlmym.orgmight update their client to match changes in the lemmy API, butlemmy.worldcould still be using an older version of the lemmy software. This could lead to compatibility issues between the client onmlmym.organd the API onlemmy.world, leading to loss of functionality or inability to connect at all.However, since lemmy.world hosts their own instance of the
mlmym clienton old.lemmy.world, they have the option to continue using the older version of the client until they update their lemmy server software to work with the newer API version.I apologize if this explanation is a bit long-winded and unclear; it’s 1 AM here, so please feel free to ask if you need any further clarification.
The technical aspect is pretty far outside my understanding. I was mostly curious if the user experience is different on one vs the other.
The technical aspect is pretty far outside my understanding. I was mostly curious if the user experience is different on one vs the other.
Oh well then, other than the potential for API version differences possibly causing outages then no. They ought be identical.
The API versioning breakage is also fully hypothetical on my end, I’ve no idea quite how mature Lemmy’s API is at the moment, and how often breaking changes are made.
Largely no, old.lemmy.world is on the lemmy.world instance, which is the biggest difference right now.