So, I am one of those old school types who mains with Firefox and Noscript. And also a filthy casual that just goes on lemmy.world. But half the images are broken because I’m expected to allow scripts on like 30+ sites to see most of the posts. I’m literally expected to allow /all/ the scripts from a domain just so I can see a dang picture behind the thumbnail. That’s the entirety of the scripting needed. That seems ridiculous. Is there, I don’t know, a server/way that makes it so I don’t have to blanket allow all these scripts? To put it in meme form (not sure I’m doing it right, never seen the show): “It’s an image of a banana Michael, what should it take, one Raspberry Pi running Docker?”
MrKaplan already forked it and is keeping it on life support for lemmy.world. I’ve been trying to make enough sense of it to fix several issues that have been bugging me for a while, and will contribute my fixes there if I can figure them out.
I’ve only got a few hours each weekend where I have good concentration + enough free time to work on it, and don’t know the relevant languages (Go, Rust, TypeScript), so my progress is pretty slow… but I’m still poking at it.
Thank you and @[email protected] for your work!
Wow thanks for the info and the work. I don’t use it much since 99% of my Lemmy use is on mobile and I prefer stock Lemmy for admin stuff, but I know at least a few of my users use it.
I’m going to see if that fork is something I can just drop in the docker compose file. That’ll be awesome if so.
Do they intend to make it 1.0 compatible or is this beyond the scope right now?
I don’t know what anyone else intends to do, but if I can fix the issues I’m currently looking at – and no one else has stepped up in the interim – I’ll at least take a look at the 1.0 stuff. (I use mlmym and would like it to keep working…)
tbh it’s probably not going to be too complicated to switch to 1.0. the current api is generated from lemmy-js-client, but 1.0 api has an official openapi file. if there is a decently usable openapi generator for go that would probably not be too complicated to swap in instead and adjust the api calls in mlmym code.