Hey there,

I was using https://mlmym.org/programming.dev/ to browse programming.dev because I don’t really like the default Lemmy UI. However, as of today https://mlmym.org just redirects to this gist: https://gist.github.com/rystaf/4d591ffdcbaab1c49efa406885efd814.

When checking both https://old.lemmy.world and https://lemmy.world - they both resolve to the same IPs - So it seems like the intended use for this UI is not use it though https://mlmym.org anymore, but for the instances to host it themselves under the “.old.” subdomain. In a similar way reddit is doing.

As for how it would look, have a look at https://old.lemmy.world - and probably enable dark mode in the settings.

Was hoping programming.dev would consider supporting this UI as well, under old.programming.dev - It makes the transition from Reddit to Lemmy a lot easier

You can find the repo of it over here: https://github.com/rystaf/mlmym

  • Ategon@programming.devM
    2·
    1 year ago

    snowe was running into issues before getting other frontends to run but if that gets sorted out we can look into adding some alternative frontends (and we’ll have to sort it out eventually to get a beta version of pangora up before it becomes the default UI)

    • RonSijm@programming.devOP
      1·
      1 year ago

      I like how they’ve done it, but from an “instance owner” perspective I can kinda see how it could become annoying to support 5 different FE UIs…

      I’ve tested https://phtn.app - and over there it seems when you login it sends the login request straight to https://programming.dev/api/v3/user/login - (which is good)
      While mlmym sends the login attempt to it’s own backend to proxy it - which is bad, since anyone could alter the code and log the login requests on their server and capture your auth data.

      I’ve been looking into mlmym, but it’s programmed in GO, which I’m not familiar with, so that’s not great (for me) - though I’ve seen you can compile GO into WASM - so my idea is to do that so it can be hosted stateless (like in s3 or even just github pages) without any backend. If then the auth can be fixed, it could practically be used from any location and the instances wouldn’t have to host their own version of mlmym