klassekatze
Experienced.
- Joined
- Oct 7, 2014
- Messages
- 3,310
- Likes received
- 43,258
So I've tentatively designed a fanfiction tracking site. I'm using it personally but I'm not satisfied with the state of it. I also feel like I'm a lot less likely to miss something obvious it ought to be able to do if I ask other people. I figured QQ was a good place to start since SB and SV have a lot more activity (and do a lot more than just story content), whereas QQ is a slow enough pace I don't have to fear the topic sliding off the first page within a day.
Essentially, the problem that drives me is I read too many stories. Even with threadmarks, as I understand it, you at best get what you get on, say, fanfiction.net: an email per update. I wanted a way to easily track an enormous number of stories even on non-standard sites like SB, SV, QQ, blogs, etc, and be able to see the word count I have yet to to read. Thus, I don't have to eyeball my clogged email for stories or quests with eleventy billion 300 word updates.
But showing is probably better than telling.
http://imgur.com/a/Ehmnb
Story index links are de-duplicated and polled every four hours. Supported sites with logins (like this one) are logged into as required. The site login itself is currently using Google accounts, and I'm thinking of expanding it to a couple other openid providers such as twitter,github,spotify,dropbox,etc. I'd like to avoid having a user/pass login specific to the site because who really wants more logins to keep track of for something so niche.
My current goals if I ever finish this project:
Ability to import favorites, collections, etc from other sites
Ability to create arbitrary numbers of lists, which may be public (which means listed in a public index of lists for anyone to easily find; all lists are accessible if you hand out the link)
Ideally, a mechanism for letting people submit stories to a list, whereupon the list owner can confirm or reject them.
Stories would be able to have author name added where service is unable to auto-magically detect it, and story descriptions as well (appended to legit description if available.)
Find a better name for it
Under the hood it uses a combination of CSS selectors from a database and loaded up blobs of code for troublesome sites like fanfiction.net (by which I mean, doesn't have a section of the html containing a convenient list of links).
So. Does anyone see any problems with this, or anything I haven't thought of and really should, and so on?
Essentially, the problem that drives me is I read too many stories. Even with threadmarks, as I understand it, you at best get what you get on, say, fanfiction.net: an email per update. I wanted a way to easily track an enormous number of stories even on non-standard sites like SB, SV, QQ, blogs, etc, and be able to see the word count I have yet to to read. Thus, I don't have to eyeball my clogged email for stories or quests with eleventy billion 300 word updates.
But showing is probably better than telling.
http://imgur.com/a/Ehmnb
Story index links are de-duplicated and polled every four hours. Supported sites with logins (like this one) are logged into as required. The site login itself is currently using Google accounts, and I'm thinking of expanding it to a couple other openid providers such as twitter,github,spotify,dropbox,etc. I'd like to avoid having a user/pass login specific to the site because who really wants more logins to keep track of for something so niche.
My current goals if I ever finish this project:
Ability to import favorites, collections, etc from other sites
Ability to create arbitrary numbers of lists, which may be public (which means listed in a public index of lists for anyone to easily find; all lists are accessible if you hand out the link)
Ideally, a mechanism for letting people submit stories to a list, whereupon the list owner can confirm or reject them.
Stories would be able to have author name added where service is unable to auto-magically detect it, and story descriptions as well (appended to legit description if available.)
Find a better name for it
Under the hood it uses a combination of CSS selectors from a database and loaded up blobs of code for troublesome sites like fanfiction.net (by which I mean, doesn't have a section of the html containing a convenient list of links).
So. Does anyone see any problems with this, or anything I haven't thought of and really should, and so on?
