I'm actually already working on this It requires a few changes with how queries are done currently, but I'm hoping to roll it out today or tomorrow.

 

I've rolled out multi-crossover support. The counts are coming, but will take a bit more work.

Additionally, old Scryer has been removed. https://scryer.darklordpotter.net/ is now Scryer 2.0.

 

Also done. It's sorted descending by count of fics.


Gauging interest: I'm thinking of building a Chrome extension / FF extension that beaconed what you were reading back to Scryer. This way Scryer could keep bookmarks for you and tell you if you've already read something. How many would actually use it?

I'd use it, so I'll probably build it regardless.

There's a lot of other potential opt-in analytics that might be interesting. e.g. plotting reading speed per hour, and number of words read per week + stories read per week.

 

Good idea. I've added that to the list, along with default search settings.

You'll have to install the extension, which would be the "opt in".

 

Definitely on my TODO list. This feature will require some planning. Until traffic increases though, I'm not certain the value for effort is there yet.

The viability of Scryer is really dependent on 1) getting more data and 2) building personalization / assistant-style features. Scryer has to be more than a search engine.

--------------------------

Minor update tonight, pairings (as much as FFN tells us, I haven't done any extra summary inference) are now shown in search results. Also squashed some various bugs.

Edit: disabled pairings, there was an unfortunate bug in the parser that requires a reindex of FFN.

 

Pairing view (which characters the author claims are paired) has been reenabled. Additionally, sorting / searching by DLP scores has been fixed, which was broken by a bug in a new version of ElasticSearch.

I've also brought back an older sorting mode broken in the past by another ElasticSearch upgrade called Popular and Recent. This mode ranks stories by update date and blends in reviews, follows, and favorites. It's most powerful when used with a more specific search (e.g. -slash + your favorite characters) or a smaller crossover category.

Next up: 3 new fandoms (which ones? You decide.), user accounts + DLP account linkage to then lead to automatic FFN bookmarking via Chrome extension + rating/note taking.

 

After user accounts are implemented, I'm planning on adding saved searches, blacklisted authors, and default searches (your template for searches).

 

Naruto, Bleach I would like to see on the new Fandom. I can't think of a third. I have no third.

 

Needs moar Twilight.

 

I've deployed seven new fandoms and their respective crossovers into the search index.

• Dresden Files
• Fate/stay night
• Naruto (still backfilling, ~50% done)
• Stargate SG-1
• Stargate Atlantis
• Star Trek: TNG
• Star Wars

Crossovers have been loaded as well.

Next up:

• X-Men?
• Doctor Who?
• Dragon Age
• ?

I'll be rolling out new fandoms by request and popularity. Currently been looking at fandoms often crossed with HP.

Edit:

• Avatar: The Last Airbender
• Legend of Korra
• Halo
• LOTR
• Bleach
• ASOIAF
• Buffy
• Mass Effect
• Avengers
• X-Men the Movie

Are now all in progress backfilling. I'll enable access to them tomorrow once initial indexing has completed.