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)
Programming.dev Meta
Welcome to the Programming.Dev meta community!
This is a community for discussing things about programming.dev itself. Things like announcements, site help posts, site questions, etc. are all welcome here.
Links
Credits
Oh that's a shame. .ml doesn't have it so I always browsed via mlmym. Do you know why they deleted it?
I don't know, I've asked in an issue of their repo: https://github.com/rystaf/mlmym/issues/77 - they might clarify why they removed it.
Apparently some of the links in the gist file are mirrors: https://o.opnxng.com/ and https://lemmy.bolha.one
The downside of these local mirrors is probably that the auth credentials are POSTed to those sites - apparently due to limitations or Lemmy. But so it would be better instances hosted their own versions
I would back this request. I'd also like to see support for some of the other frontend options, such as Photon.
The way Lemdro.id does it is great:
Lemdro.id Interfaces
lemdro.id powered by Lemmy-UI. m.lemdro.id web app powered by Voyager
old.lemdro.id powered by mlmym
p.lemdro.id powered by Photon
a.lemdro.id powered by Alexandrite
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