Ai-chan posted on 18:25 on 1 May |
Hi, I'm the author of this series and I'd like to request the admin or anyone responsible to use the feed to my blog http://hugginglove.blogspot.my/p/blog-page.html (FSL fiction page) or http://hugginglove.blogspot.my/ (blog main page). I have new chapters over at my blog as well as many other stories that I didn't post at royalroad. Anyway, whoever added it here, thanks. I didn't know about it until one of my readers pointed it out to me. Sorry if I posted this at the wrong section, I tried to look at the other section of the forum but I didn't see any thread about feed request. |
fake-name posted on 07:16 on 2 May |
It initially got added because I parse and provide facilities for watching series from RoyalRoadL. A series being added there with more then three chapters causes a entry to be automatically created. Anyways, I'm happy to use the proper feed update source, I'll see about getting it all set up after work tomorrow. Thanks! As an aside, I've personally been enjoying your fiction. I'm clad you're continuing it. |
Ai-chan posted on 19:02 on 2 May |
Awesome, thanks! And thanks for reading and telling me you enjoyed the story. Please await more chapters sometime soon. |
fake-name posted on 04:09 on 3 May |
Ok, I can parse most of your updates. I have a few comments, in particular apparently the more recent series ("Armageddon") doesn't seem to have tags, which makes scraping it somewhat more involved. Basically, the RSS parsing system sees your site like this:
In most cases, it does a decent job of figuring out what is what from the title. I usually assume that anything with a valid chapter number in the title, and a specified tag is a proper chapter release (there's some extra logic, e.g. if "preview" or "teaser" is in the title, I ignore it, etc...). However, this does depend on the present of either a tag, or completely consistent naming. In this case, I can do things like assume any post that starts with the exact string There is a help entry here which has some more info about what makes a source easy to parse. Also, do you have a preferred name for what I call the feed source? I normally just use the title from the relevant blog page (in this case, "Hugs & Love"), but that's just because it's easy. The feed names are just a giant table I can change to whatever. Thanks If you're curious (or just bored), here's the changes that make it work: |
Ai-chan posted on 08:52 on 3 May |
Oh, sorry that you're having problems. Will it help if I make a page specifically for Armageddon? Sorry if this is not helping, I don't really understand all these rss feed stuff. Please inform me if there's anything I can do (you'll probably have to explain it step-by-step) to make your work easier. As for feed name, yes, you can use Hugs & Love. Thanks a lot. |
Ai-chan posted on 09:01 on 3 May |
I've added two new tags: 1) Armageddon VR - for Armageddon 2) Traps Are Delicious - for Traps Are Delicious multi-choice series. BTW, anything marked as 'Rants' aren't actually releases, they're just comments of what's happening in my life. I also see double entry for Felicia's Second Life. The old one is titled Felicia's Second Life while the new one is titled Felicia Second Life. |
fake-name posted on 01:33 on 4 May |
I wouldn't say I'm having issues, rather having someone who's actually willing to fidget with stuff just makes me excited and then I get distracted in unnecessary technical details. This whole site is basically an experiment in how much I can automate the hell out of basically everything. As long as there is a tag that's applied consistently to chapter releases, and not other releases/rants/etc, that's completely fine and should do everything needed. An extra page isn't needed here, since the feed exaction system just uses the RSS feed, it doesn't actually parse page content, so it wouldn't see the page anyways.
Whoops, yeah, that can happen. The mechanism for trying to guess if two names actually refer to the same series tends to try to err on the side of caution. I manually merged the entries. Thanks! |