▲ 3 ▼ Did you know Lemdro.id hosts some slick Lemmy interfaces? Currently hosting Photon, Mlmym, and Voyager! (nu.lemdro.id) submitted 3 years ago by Curated_Android@lemdro.id [B] to c/android@lemdro.id 5 comments fedilink hide all child comments 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
[–] menehar@feddit.ch 0 points 3 years ago* (1 child) Is lemdro.id just a frontend? Is it not attached to a particular instance? permalink fedilink source hideshow 2 child comments replies: [–] cole@lemdro.id 0 points 3 years ago* (last edited 3 years ago) (1 child) 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) permalink fedilink source parent hideshow 2 child comments replies: [–] Justly0250@lemdro.id 0 points 3 years ago (1 child) special shortcut Can you elaborate? permalink fedilink source parent hideshow 2 child comments replies: [–] cole@lemdro.id 1 point 3 years ago 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! permalink fedilink source parent
[–] cole@lemdro.id 0 points 3 years ago* (last edited 3 years ago) (1 child) 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) permalink fedilink source parent hideshow 2 child comments replies: [–] Justly0250@lemdro.id 0 points 3 years ago (1 child) special shortcut Can you elaborate? permalink fedilink source parent hideshow 2 child comments replies: [–] cole@lemdro.id 1 point 3 years ago 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! permalink fedilink source parent
[–] Justly0250@lemdro.id 0 points 3 years ago (1 child) special shortcut Can you elaborate? permalink fedilink source parent hideshow 2 child comments replies: [–] cole@lemdro.id 1 point 3 years ago 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! permalink fedilink source parent
[–] cole@lemdro.id 1 point 3 years ago 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! permalink fedilink source parent