Please read. Significant change on the site that will affect compatibility [ Dismiss ]
Home ยป Forum ยป Bug Report and Feature Requests

Forum: Bug Report and Feature Requests

Version number of single file stories

REP ๐Ÿšซ

I recently received comments on a number of my stories. While fixing the errors, I noticed all of my single file stories indicated Version 1.00, but I recall posting updates to those stories.

The chapters of multi-chapter stories have version control which indicates there have been changes to the chapter.

Both single file stories and multi-chapter stories have a version number. I suspect the story version number of a multi-chapter story is only incremented when the author indicates they are reposting the entire story. But when I repost a single file story, I am reposting the entire story and the version should be incremented, but it isn't.

Am I missing something?

Lazeez Jiddan (Webmaster)

@REP

But when I repost a single file story, I am reposting the entire story and the version should be incremented, but it isn't.

That's odd.

Single-file stories' version number is supposed to be incremented when reposted. The auto-increment is by .1, so a 1.00 story becomes 1.10 after a repost.

I just checked my code, and checked a story I just reposted, the code is there working correctly and the story that I just processed a repost for (new story) has a version number of 1.10. So the system worked as expected.

Try reposting one of your single-part stories as a test and let's see what happens.

Replies:   REP
REP ๐Ÿšซ
Updated:

@Lazeez Jiddan (Webmaster)

I just submitted V1.1 of A Rose by Any Other Name.

ETA: I also submitted V1.1 of Not My Fault.

Lazeez Jiddan (Webmaster)

@REP

I just submitted V1.1 of A Rose by Any Other Name.

ETA: I also submitted V1.1 of Not My Fault.

I processed both and both ended up as version 1.10.

So the system works.

The script that does this has been as is for over 10 years with no changes.

Replies:   Keet  REP
Keet ๐Ÿšซ

@Lazeez Jiddan (Webmaster)

I processed both and both ended up as version 1.10.

So the system works.

The script that does this has been as is for over 10 years with no changes.

But neither show up as "Reposted" under the "More Info" links.

Lazeez Jiddan (Webmaster)

@Keet

But neither show up as "Reposted" under the "More Info" links.

Why would it?

I'm not about to add a 'revised' field to the moreinfo page. This is not something that benefits the average Joe.

A 'revised' date anywhere in a story's info only benefits collectors. Collectors tend to put a lot of pressure on the site already as they tend to be a selfish bunch.

I'm sure if I provide this info, somebody will devise a script to automatically scan those moreinfo pages seeking update date to keep up-to-date some collection somewhere. Such a script would put undue strain on the servers. Currently, collectors are being somewhat slowed down by the limits of the allotment of stories for free members.

About 10% of the current download count for stories come from 'collectors' already. Most collectors tend to be the hoarder type, as in they get the stories just to get the stories, but not necessarily to read them. I know that for a fact as I've been in conversation with many of the collectors that hit the site and got caught.

In the past there was a bug in the download counter that allowed one to download as much as they want if they used a specific technique. I only found out when, on a lark, I wanted to see who has accessed the most stories on the site and was floored to see somebody with a download count of over a million. At the time, the site had only around 5,000 stories. So for anybody to access that much, something would have to be wrong and out of the ordinary. So I contacted the person and it turned out that they download the whole site once a week to sync their collection, and had discovered that technique that allowed them to accomplish it. There were about 20 collectors at the time doing it. When I told the guy that what he was doing was hurting the site's performance he outright told me to fuck off and if I can't run a site well, then I shouldn't have a site.

Once I fixed the bug, and stopped those extreme minority of the site's users, my hosting requirements dropped by half saving me quite a bit of money.

So, no easily-accessible time stamp.

Replies:   Keet
Keet ๐Ÿšซ

@Lazeez Jiddan (Webmaster)

I'm not about to add a 'revised' field to the moreinfo page. This is not something that benefits the average Joe.

This was not about a 'revised' tag. For multi-chapter stories there's a date when that chapter is updated. For single file stories I have seen (Reposted Story) when checking the moreinfo page but that didn't appear for the single file stories REP reposted, which seemed like a bug to me. Why for each chapter and not for a single file story?

A 'revised' date anywhere in a story's info only benefits collectors. Collectors tend to put a lot of pressure on the site already as they tend to be a selfish bunch.

I have to disagree. I'm a sort of collector in that I keep everything I download on my local machine. I do not download anything I don't intend to read. Actually I think I generate less traffic the way I do it because I frequently re-read stories from my converted local copies thus avoiding the otherwise required traffic. I also generally wait until a story is completed and download the zip which obviously uses less data traffic than reading the story directly on the site.

I'm sure if I provide this info, somebody will devise a script to automatically scan those moreinfo pages seeking update date to keep up-to-date some collection somewhere. Such a script would put undue strain on the servers.

If I wanted I can do that with the current information available so any additional info would only make it easier and probably use less data traffic than it would with only the current info. To make it very clear: I do not run a script to do this. I thought about it because there is no other way without a revision list but I decided not to do it specifically because of the strain it could possibly put on the site. I'm not sure you could block it for the someone who is determined to do this.

Getting back to a 'revised' tag. The reason for such a tag in my case was that it allows you to offer a list with revision dates. That too would decrease traffic because readers don't have to check multiple stories using multiple clicks to every moreinfo page, they can see in the list when stories are revised and can pick just those they are interested in.

If you're interested in the way automatically checking for updates is possible I can explain that in a private message. The way I devised doesn't even put an excessive strain on the site :)

Lazeez Jiddan (Webmaster)

@Keet

For single file stories I have seen (Reposted Story)

Not a bug. When a story's size changes during a repost by more than 10%, then it's tagged as such. For revisions that don't change the story's size, they're never tagged.

Collectors tend to put a lot of pressure on the site already as they tend to be a selfish bunch.


I have to disagree. I'm a sort of collector in that I keep everything I download on my local machine.

You're not the type of collectors that I'm talking about.

Getting back to a 'revised' tag. The reason for such a tag in my case was that it allows you to offer a list with revision dates.

Unfortunately, because of past experience, I only see this being way more exploited badly than being a useful feature.

There are always a few that ruin it for everybody else, usually by being greedy or extremely selfish.

If a feature is useful to normal users and many normal users would actually use it, then I would implement it and spend the time to find a way to mitigate the effect of bad actors. But this particular feature is not exactly useful to normal readers. I've been running storiesonline for over 22 years now and this is the first time anybody asked for such a feature, that means it's not exactly in great demand, and the potential for bad behaviour is high.

Replies:   Keet
Keet ๐Ÿšซ

@Lazeez Jiddan (Webmaster)

Not a bug. When a story's size changes during a repost by more than 10%, then it's tagged as such. For revisions that don't change the story's size, they're never tagged.

That explains it, thanks.

REP ๐Ÿšซ

@Lazeez Jiddan (Webmaster)

Thanks.

I must have modified the story and forgotten to repost the changes.

Back to Top

Close
 

WARNING! ADULT CONTENT...

Storiesonline is for adult entertainment only. By accessing this site you declare that you are of legal age and that you agree with our Terms of Service and Privacy Policy.


Log In