I have some interest in trying to take that on if it’s really unmaintained now. I use mlmym and want to make sure we continue to have an interface that works w/o JS. I have relevant web programming experience, but not with Go specifically.
I’ve started changing some smaller things over on Fedihosting-Foundation-Forks/mlmym. I don’t really have time, motivation or Go knowledge to fully maintain and develop new functionality there, especially as I don’t use it myself, but I’m currently planning to keep it on life support at least and see if I can at least fix some stability issues.
I also already forked and updated go-lemmy, which should now support the latest Lemmy 0.19.11 APIs.
Currently the primary focus for this is to have builds for old.lemmy.world, but I wouldn’t be opposed to have this used as a generic repo if other people want to contribute. I’m currently not planning to intentionally break things in a way that would prevent usage outside of Lemmy.World, but unless there are other people interested in contributing as well, I will primarily just focus on ensuring compatibility with the Lemmy version we are running.
Thanks. I’m still learning both Go and the codebases involved. I’m pretty limited on free time where I’ve got both large enough blocks of time and energy to concentrate effectively on this. I’m also not very enthusiastic about taking on the administrative aspects of running an open source project – I’m only really interested in keeping a JS-free version of Lemmy usable – so contributing changes to a common community fork you’ve already got up and running sounds good to me!
I do have some specific issues in mind that I’d like to implement fixes for once I’m up to speed. In particular:
There is improper filtering when a user submits a comment which results in certain text being stripped from the message instead of escaped properly. I’m not sure if this is an issue in mlmym itself or one of the libraries it uses, but I’d like to track it down and get it fixed.
Federated image links to non-lemmy websites sometimes show up as image_proxy links from the poster’s instance. This is a really annoying issue that results in misleading domains showing up next to posts as well as breaking image display in the post itself.
Comments sorted by ‘new’ (and maybe other modes?) don’t paginate properly.
I may take on some other issues after that, but those three are what I want to fix most right now.
Federated image links to non-lemmy websites sometimes show up as image_proxy links from the poster’s instance. This is a really annoying issue that results in misleading domains showing up next to posts as well as breaking image display in the post itself.
that is not directly a mlmym issue, it’s that people copy links on instances with image proxying enabled and use them in new posts :|
feel free to also raise them as issues on the repo directly to have them documented.
by the way, we run the version on the main branch on https://mlmym-unstable.lemmy.world/, although it does have a domain lock to lemmy.world.
Hmm. That doesn’t really mesh with my understand of how certain prolific posters post (e.g. via automation), but digging into it a bit more, I do see the proxy link via Lemmy-UI even on the poster’s instance, so there’s something besides just mlmym involved here – whether that really is inappropriate copy-pasting or a lemmy bug or what, I don’t know yet.
Regardless, the fact that the image doesn’t load in the post at all for those links seems like an mlmym bug that should be addressed; it’s loadable via Lemmy-UI.
I’ve set up a new GitHub account for association with my lemmy account and will create issues on your repo in a little while.
I have some interest in trying to take that on if it’s really unmaintained now. I use mlmym and want to make sure we continue to have an interface that works w/o JS. I have relevant web programming experience, but not with Go specifically.
@nnrx@lemmy.world FYI, if you’re still here.
That would be great!
I’ve started changing some smaller things over on Fedihosting-Foundation-Forks/mlmym. I don’t really have time, motivation or Go knowledge to fully maintain and develop new functionality there, especially as I don’t use it myself, but I’m currently planning to keep it on life support at least and see if I can at least fix some stability issues.
I also already forked and updated go-lemmy, which should now support the latest Lemmy 0.19.11 APIs.
Currently the primary focus for this is to have builds for old.lemmy.world, but I wouldn’t be opposed to have this used as a generic repo if other people want to contribute. I’m currently not planning to intentionally break things in a way that would prevent usage outside of Lemmy.World, but unless there are other people interested in contributing as well, I will primarily just focus on ensuring compatibility with the Lemmy version we are running.
Thanks. I’m still learning both Go and the codebases involved. I’m pretty limited on free time where I’ve got both large enough blocks of time and energy to concentrate effectively on this. I’m also not very enthusiastic about taking on the administrative aspects of running an open source project – I’m only really interested in keeping a JS-free version of Lemmy usable – so contributing changes to a common community fork you’ve already got up and running sounds good to me!
I do have some specific issues in mind that I’d like to implement fixes for once I’m up to speed. In particular:
I may take on some other issues after that, but those three are what I want to fix most right now.
that is not directly a mlmym issue, it’s that people copy links on instances with image proxying enabled and use them in new posts :|
feel free to also raise them as issues on the repo directly to have them documented.
by the way, we run the version on the main branch on https://mlmym-unstable.lemmy.world/, although it does have a domain lock to lemmy.world.
Hmm. That doesn’t really mesh with my understand of how certain prolific posters post (e.g. via automation), but digging into it a bit more, I do see the proxy link via Lemmy-UI even on the poster’s instance, so there’s something besides just mlmym involved here – whether that really is inappropriate copy-pasting or a lemmy bug or what, I don’t know yet.
Regardless, the fact that the image doesn’t load in the post at all for those links seems like an mlmym bug that should be addressed; it’s loadable via Lemmy-UI.
I’ve set up a new GitHub account for association with my lemmy account and will create issues on your repo in a little while.
Edit – Issue links for future reference:
and just now there has been a PR merged in the upstream repo after i spent some time to get a fork properly set up…
@nnrx@lemmy.world @nnrx@lemmy.ca @nnrx@sh.itjust.works are you still reading on any of these accounts? are you planning to return to maintaining mlmym?