Corbin's crazy ideas for OpenAniDB
Posted: Thu Aug 23, 2007 9:40 am
The object of the game is simple. I'm bored, and bored me usually writes strange code that probably violates rules, ordinances, or FCC guidelines. Thus, I'm gonna write out ideas, and you guys are gonna shoot 'em down. (Or approve 'em, but that's unlikely.)
Who I'm looking for: Staffers, since they know the rules; and anybody who's tried out my client. (Right now, that's me and like four staffers.)
Simple ideas:
- Regexp/substitutions for file save path. Feasible, simple, and not done mostly because of laziness. Done.
- Add version numbers to filenames and display data. Not quite straightforward, but possible. Would be one night's work.
- Windows binaries. I finally got my hands on a Windows machine, yay? But, nobody's asked for binaries. If you want 'em, I'll make 'em! Done.
More complex:
- Targeted notifies. Will require writing a notify handling thread. Would only grab notifies related to files in the cache.
- Implement producer list. I don't see a need for it, but then again I'm just one person. Would require work equal to when groups were implemented; that is, three hours. Meh.
- Per-user mylists. In theory, somebody out there needs two mylists for one local account. This would solve that problem. However, in practice, nobody's asked for it.
- More hashes. TTH, MD5, SHA1, CRC32. CRC32 would be very useful to creqers, and could be used offline with a regexp that pulls a release group's CRC32 out from the filename. The others have been discussed at one time or another as being used to uniquely identify files in AniDB proper, and so I should probably implement them.
New territory (no known UDP client does this, so feel free to veto these with "what the **** is your major malfunction, son?"):
- Per-file hashing, filing, and renaming settings, via popup. This would be, as far as I know, a first; when each file is up for renaming and addition to the mylist, a popup can be used to customize settings for each file. This is one of those crazy 2AM ideas. Trashed; bad UI design.
- Keep track of files in the local system. This would be a true endeavor, but the benefit of having every previously hashed file on record would be useful for mylist double-checking and backup list generation, for example.
- All notifies. This is what I wanted the client to be, at one point. The client becomes aware of all data passing through it, and eventually acquires a sizable portion of the database, sort of like an incremental kowai. Requires a notify handling thread. Trashed; violates leeching rules.
- Avdump. Do I need source? Nah. It would be sorta fun to write, and I'm tired of writing so much GUI stuff anyway. Which, of course, leads to...
- Integrated creqs. This was just something that came into my head from nowhere, but a bit of thinking told me that it's not impossible, which is the important thing.
- Replace AOM, lawl. Just kidding, just kidding! Not possible, since I have neither TCP permission nor kowai decryption nor dev blessing nor anything else required for that. I'm leaving this here to remind me not to attempt it. Trashed; violates kowai rules.
- Support for other online anime databases. Prior to a weeaboo on 4chan mentioning this, I had no idea that there were other places, but I suppose that eventual support for other places may be in the distant future... Trashed; needs more information.
I'm falling asleep, but this should be more than enough craziness for one post. Of course, if you've got more suggestions that out-crazy me, then send 'em in!
~ C.
Who I'm looking for: Staffers, since they know the rules; and anybody who's tried out my client. (Right now, that's me and like four staffers.)
Simple ideas:
- Regexp/substitutions for file save path. Feasible, simple, and not done mostly because of laziness. Done.
- Add version numbers to filenames and display data. Not quite straightforward, but possible. Would be one night's work.
- Windows binaries. I finally got my hands on a Windows machine, yay? But, nobody's asked for binaries. If you want 'em, I'll make 'em! Done.
More complex:
- Targeted notifies. Will require writing a notify handling thread. Would only grab notifies related to files in the cache.
- Implement producer list. I don't see a need for it, but then again I'm just one person. Would require work equal to when groups were implemented; that is, three hours. Meh.
- Per-user mylists. In theory, somebody out there needs two mylists for one local account. This would solve that problem. However, in practice, nobody's asked for it.
- More hashes. TTH, MD5, SHA1, CRC32. CRC32 would be very useful to creqers, and could be used offline with a regexp that pulls a release group's CRC32 out from the filename. The others have been discussed at one time or another as being used to uniquely identify files in AniDB proper, and so I should probably implement them.
New territory (no known UDP client does this, so feel free to veto these with "what the **** is your major malfunction, son?"):
- Per-file hashing, filing, and renaming settings, via popup. This would be, as far as I know, a first; when each file is up for renaming and addition to the mylist, a popup can be used to customize settings for each file. This is one of those crazy 2AM ideas. Trashed; bad UI design.
- Keep track of files in the local system. This would be a true endeavor, but the benefit of having every previously hashed file on record would be useful for mylist double-checking and backup list generation, for example.
- All notifies. This is what I wanted the client to be, at one point. The client becomes aware of all data passing through it, and eventually acquires a sizable portion of the database, sort of like an incremental kowai. Requires a notify handling thread. Trashed; violates leeching rules.
- Avdump. Do I need source? Nah. It would be sorta fun to write, and I'm tired of writing so much GUI stuff anyway. Which, of course, leads to...
- Integrated creqs. This was just something that came into my head from nowhere, but a bit of thinking told me that it's not impossible, which is the important thing.
- Replace AOM, lawl. Just kidding, just kidding! Not possible, since I have neither TCP permission nor kowai decryption nor dev blessing nor anything else required for that. I'm leaving this here to remind me not to attempt it. Trashed; violates kowai rules.
- Support for other online anime databases. Prior to a weeaboo on 4chan mentioning this, I had no idea that there were other places, but I suppose that eventual support for other places may be in the distant future... Trashed; needs more information.
I'm falling asleep, but this should be more than enough craziness for one post. Of course, if you've got more suggestions that out-crazy me, then send 'em in!
~ C.