Lemmy Today

328 readers

1 users here now

If you experience issues or problems with this instance (lemmy.today), this is the place to discuss them. Or if you just want to ask questions about how something works. Anything related to the instance or lemmy itself.

founded 2 years ago

MODERATORS

mrmanager@lemmy.today

replacing mlmym with a fork (code.mschae23.de)

submitted 3 months ago by hexagonwin@lemmy.today to c/lemmytoday@lemmy.today

32 comments fedilink hide all child comments

hello. i'm a happy user of lemmy.today.

i've always used the mlmym frontend available on old.lemmy.today, it generally works well enough. however, there are some minor minor bugs and missing features. (e.g. impossible to navigate to next page when viewing saved posts, impossible to see down/upvotes separated)

i recently came across this fork of mlmym (from this github issue) and it seems to have all those bugs fixed. can we replace the current mlmym with this fork?

thanks for reading

you are viewing a single comment's thread
view the rest of the comments

[–] mschae@discuss.mschae23.de 2 points 2 months ago (2 children)

I implemented the headers today, so version 26.2.1 should hopefully do this correctly now.

I could only really test it in my deployment, so feel free to let me know if you have any issues!

[–] mrmanager@lemmy.today 2 points 2 months ago

It works! I discovered way too late that lemmy was rate limiting traffic from mlmym, because it wasnt part of my nginx config. It was lemmy itself that was doing rate limiting since all requests came from the same docker ip.

But forwarding the real ip headers fixed that, so very good. Huge thanks!

[–] mrmanager@lemmy.today 2 points 2 months ago

Cool. :) I think that will be a very useful feature for a lot of Lemmy admins.

Will play around with it later...!