🧐

  • 5 Posts
  • 41 Comments
Joined 3 years ago
cake
Cake day: February 17th, 2021

help-circle



  • modlog having different actions in different pages.

    I think you misunderstood what I meant by separate lists. That’s how they are stored internally.

    Each one of them are fetched and then COMBINED to create the view you’re seeing.

    ie. P1 of Modlog = P1 of Banned Actions + P1 of Post Removal Actions + … + P1 of Admin appointment Action


  • I’m sorry but that doesn’t seem to be the case. All pages have all kinds of mod actions. Unless I’m misunderstanding what you mean by “type of mod action”.

    What i meant to say is that each type of mod action has it’s on pagination and the main modlog just squishes them together based on page number. check the last items of page 1 they are all admin appointments, there are only a handful of them and they don’t happen anymore. they appear in page 1 because they belong to page 1 of it’s type








  • Yeah so it is kind of related, see this comment

    Sorry to bother you again, it took me some time to find this again on GitHub. This login bug I was experiencing was introduced when fixing this other login bug, you can see in that commit that eq was changed to ilike but now your new pull request reintroduces that old bug with the case-sensitiveness of the usernames during login. I think the solution to both bugs would be converting to uppercase before comparing with eq (and having a computed uppercased column indexed on the database). I don’t know enough Rust to propose code changes or send a pull request, I hope my description of the solution is good enough for someone more knowledgeable to write the code.






  • Also, wouldn’t this concept be better implemented as an alternative interface for Lemmur instead of a whole new app?

    I think that’s what she is saying essentially taking the data from Lemmy api and displaying it like a chat app

    ie.

    • communities -> group chat
    • Posts and comments -> threads within group chats