Did you know Lemdro.id hosts some slick Lemmy interfaces? Currently hosting Photon, Mlmym, and Voyager!

An alternative lemmy client with a sleek design.

If you've paid careful attention to our sticky, you may have noticed Lemdro.id hosts a few slick web app interfaces for Lemmy. Give them a try!

These are active projects, so please do report any bugs to their respective GitHub pages linked below.

What do you think of them? What kind of tools would you like to see for Lemmy?

Lemdro.id Interfaces

Familiar for iOS redditors: m.lemdro.id powered by Voyager
Familiar for desktop redditor: old.lemdro.id powered by mlmym
Something new: nu.lemdro.id powered by Photon

You're viewing a single thread.

50 comments

Is lemdro.id just a frontend? Is it not attached to a particular instance?
- Lemdro.id is an instance but each instance can host mutliple frontends if they like.
- It is an Instance.
  
  Lemmy.world also hosts Voyager at https://m.lemmy.world and MLMYM at https://old.lemmy.world
- It is an instance. This post is in the !android@lemdro.id community of the lemdro.id instance, for example. There’s also !askandroid@lemdro.id or !google@lemdro.id, to name a few
- As mentioned by others, it's a specific instance but with multiple frontends. The main LemmyUI is just one of them!
- lemdro.id is just a frontend, however it does have a special shortcut to the backend that allows it to function better under heavy load (on lemdro.id specifically)
  
  special shortcut
  
  Can you elaborate?
  
  Yes! There are 3 different "types" of Lemmy backends in our infrastructure. "scheduled" types, of which there can only be one, run scheduled federation traffic as well as some smaller load balanced load of requests. The "external" type handles generic requests same as "scheduled" except without scheduled federation tasks. These can spin up or down all the way to 0, as sometimes the scheduled instance can handle everything on its own.
  
  Finally, there is "internal". These are dedicated backend instances that are not publicly exposed and therefore do not handle any federation traffic at all. Lemmy-ui communicates with this internal backend, meaning that our UI has a path that is entirely separate to the federation traffic and should stay responsive no matter what!
  
  I think they mean whether the entirety of lemdro.id is just a webapp like vger.app, rather than an instance as well.
  
  ah, well this is why you usually do the communications stuff haha, I misunderstand people
  
  It's okay, you have +100 technical wizardry stats!

You've viewed 50 comments.