MangaLand


So this site is designed around planning what a better MangaUpdates site would look like. I don't really have any expectations right now because i'm not skilled enough to create something like this yet, but I'll jot down my thoughts. So let's start with the highest-level concepts behind what does make mangaupdates good and thus needs to be preserved, then figure out how to get rid of the worst parts.



What to keep


Fundamentally, a site like mangaupdates is indespensible to serious readers in spite of all of its problems. In my view, the reason it is good is as follows:

  1. It has a very significant userbase contributing new content to it regularly. Scanlators themselves post their releases on mangaupdates, or others do on behalf of scanlators. Mangaupdates is a one-stop-shop for knowing when new releases happen.
  2. An absolutely vast collection of meaningful data about manga in all its forms.
  3. Items have useful connections. You can browse by series, author, group, artist, and a pile of tags, creating real opportunity for discovery as well as real opportunity for gathering information.
  4. Even very old releases can be identified, giving context to a user to look up a stale or long-past release.


What is awful


  1. UI. nothing by way of eyecandy or good interface design.
  2. There is no connection between the actual *file*, the flesh and blood of what makes up the release, and that release. They don't care about filenames for the release, hashes, or anything like that, and since the scanlation scenes are *terrible* at name standardizations this can leave a user in a position where he can't find the file anywhere on the internet.
  3. no public API
  4. Most important, we're trusting a proprietary product run by a bunch of strangers with what may be the single greatest chunk of the entire manga translation scene.
  5. Though proprietary, it is clear MU has no real high-level plan for their database architecture. It's well out-of-date with the scene and it's unlikely it's ever going to be put in a position where it can be overhauled.
  6. Failsafe. MU has no failsafe. It will, inevitably, get shut down and there's no replacement poised to step in. It may die to economic stresses. It may die to legal stresses. It may die to loss of interest by its employees or simply being shifted around. But we must assume that it will die, and there's no sign anyone is prepared for its death in the scene.


Where to go with all this?


The first step is to think about a database. A database that is modular, open, and movable. I plan to prototype a thorough database. What I need is a rip of a big datapool (such as mangaupdates or mangatraders) to populate this database with information. Then, once this database is shared and useful, we can start thinking about making a new site. Making the data portable comes first
Do I really think this all is going to happen? Maybe. I doubt I'm going to be the guy who ultimately does it, but hopefully this kind of brainstorming at least moves along a more motivated crowd.