>>24195 here.
Just a quick heads-up that I haven't forgotten. I'm still working on this on-off between exams.
It's still a little too early to publish anything I've made yet. Everything I've made so far has been copied from MAL seeing as that's the base reference I was given (I have never used Anilist, so I don't know how it works,) though they have features I frankly can't see as useful in the context of THP, so I've tossed them aside.
Functionally, it's only at a stage where you can browse existing stories and authors added to the database manually, since I'll have to be thorough when handling user input. The whole idea with the site is to allow users to add and update information, creating an unofficial version of the story list, with the added features of allowing users to save the stories they're reading to a list, easily share said list, share stories with user added summaries and character tags (canon characters only. Maybe OCs if enough people want it.)
Story status, thread listing, dynamic URL generation to THP, and author has been added so far. A story can only have one author at the moment, since co-written stories are rare, I've lowered the priority of allowing multiple authors on a single story. A story holds a reference to the board it's on, but each thread inside the story will hold it's own reference to a board, allowing threads to exist on other boards than the one the story mainly takes place in (this was done to allow the dynamic URL generation to work.)
Currently, the list of threads can't be sorted by hand and will appear in the order of their post number. This should be changed before the beta version is launched sometime soon(tm).
I'm currently working on handling user input, making sure that incomplete information (missing fields, like an empty list of threads, or the lack of any board) can't be added, and the error handling is done in a satisfying way.
Planned features include but is not limited to: user recommendations, story rating, actually making the website that will display the information.
This can be subject to change.
I'm designing the server side as an API, so you can create your own interface if you want to, which is partly why I'm trying to be through with the user input. Anyone will be allowed to pull public data, but creating and updating will require a user. Deleting anything will require authorization, though normal users should be able to request deletion.
If you're thinking about using this site at all once it has launched, it would help me out a great deal if you could write down a wishlist of features you would want, though I make no promise of actually implementing them, more so to give me an idea of what the projected userbase wants.
I'll also have to decide on a name before I can launch the site. I have an idea, a very uninteresting and boring name, but a name regardless. Suggestions are welcome.
Saging because there was no real new information in this post.
