Hello Lemmings.

I will be attempting to make a federated anime tracker this summer, but I am not quite sure what features people would want and how I would get the details for animes, mangas, etc.

For the latter: What I thought was to either scrape other anime websites continuosly in the background, but this most likely is against the ToS of every anime tracking website, such as AniList or MAL. (I actually asked anidb.net for special access to their DB because apparently you can request access to it, but I’ve been left on read by the two staff members) My second idea was to make it an anime tracker website where animes are only user-submitted. And the user submissions would be approved by assigned moderators. However, I think this would be quite inconvenient. I’d like to get your opinions and/or ideas for this.

For the former: So if you have any requests or suggestions, please drop it down in the comments section.

Thanks in advance.

  • @[email protected]OP
    1•2 months ago

    What do you mean by “lists in the code”? Which lists and do you mean by “in the code” hardcoded?

    • @muhyb
      2•2 months ago

      Well, since 100k titles would make a pretty big database, at least storing the metadata like years, seasons, genres etc as hardcoded could make it run faster than going full-fledged JSON, at least I meant that. However this will be an open source project and there will be localizations, so now it doesn’t look like a good idea to me somehow.

      • @[email protected]OP
        2•2 months ago

        What? What do you mean full-fledged JSON. I won’t be storing the animes in JSON, but in a PostgreSQL DB. I don’t understand what you mean…

        • @muhyb
          2•2 months ago

          Sorry for the confusion. Don’t take my words literally, I’m not an expert on databases. I use JSON for my job and it’s enough for me, so use what database your project needs. But by full-fledged I meant completely leaning on databases which may slow some things down for the server side. However I now checked PostgreSQL and it seems much better for large datasets, so I don’t think that would be a concern for you.

          • @[email protected]OP
            2•2 months ago

            Oh, I see. Ok, I get it now. JSON indeed would be very slow for this project. I also do think of maybe caching some stuff for this reason.

            • @muhyb
              2•2 months ago

              Yeah, that would be nice for the running seasons I guess. Maybe even a couple years worth seasons since most of the traffic will come from those.