Stories of Tie Up Games

harveygasson wrote: ↑4 months ago ... It would be such a shame to see this place and community go the way of so many others.

tiedinbluetights wrote: ↑4 months ago

harveygasson wrote: ↑4 months ago ... It would be such a shame to see this place and community go the way of so many others.

I wholeheartedly agree. My suggestion of making the site registered access only came mostly out of frustration of having to wait hours or days for the bot attacks to decrease in intensity a bit. But, that would make the site disappear off the search engine results. It is already happening to some extent: searching for "tie-up stories" on Google used to bring up the index page plus dozens of others related to the site. Now, you mostly get a direct link to the fictional stories for adults, indicating that the bots are mostly scraping those stories. I have a really cheesy story there that has gotten literally 1000 of views a day, something that has never happened to me before on this site, given that there is no way my stories are that interesting to view.

If we wish to keep the site visible to non-registered users, searchable via Google, and accessible 24/7 to registered users, we may indeed need to go to Cloudflare or similar service, but that's up to the site owner to decide. If the site ends up costing much, much more to maintain, due to higher server tiers and defences, we will need to make the decision if a few of us are still willing to pay voluntarily higher and higher amounts, to allow the rest of us (including a**-holes behind bots) to freely access the site, or if we should all pay each our fair share to access the site. I, for one, while willing to pay a reasonable amount per year as an individual, am getting sick and tired of having to pay for free-loaders, especially bot operating free-loaders (my apologies for skating on political thin ice).

Bigballgag1 wrote: ↑4 months ago

tiedinbluetights wrote: ↑4 months ago If we wish to keep the site visible to non-registered users, searchable via Google, and accessible 24/7 to registered users, we may indeed need to go to Cloudflare or similar service, but that's up to the site owner to decide. If the site ends up costing much, much more to maintain, due to higher server tiers and defences, we will need to make the decision if a few of us are still willing to pay voluntarily higher and higher amounts, to allow the rest of us (including a**-holes behind bots) to freely access the site, or if we should all pay each our fair share to access the site. I, for one, while willing to pay a reasonable amount per year as an individual, am getting sick and tired of having to pay for free-loaders, especially bot operating free-loaders (my apologies for skating on political thin ice).

I understand the point you are trying to make. However not everybody is in a position to contribute financially. If you were to change this site to a subscription based one or put it behind a paywall, I actually think you would kill it quite quickly. Who is going to pay to write a story? Especially when places like deviantart and other sites are free?

One of the many positives of this place is that it is open and accessible to all. The fact you can contribute is great, however in my opinion it makes you no better than anyone else. The last couple of lines of this post I find quite irritating actually, a kick in the teeth to many of the story writers on here and those that contribute to the content available on this site but are unable or unwilling to contribute financially. Perhaps i am reading this the wrong way, apologies if so.

Bigballgag1 wrote: ↑4 months ago As others have mentioned, i am grateful to the admins and those that keep the site up and running especially on a volunteer basis. I also understand how the error messages are annoying. However i think sometimes some perspective is needed.

Bigballgag1 wrote: ↑4 months ago The old site (I believe), locked down the adult story sections. If this is what the bots are looking for, perhaps it makes sense to lock these sections down to accounts only and have new user requests needing approval before activation. No idea if this is possible or feasible, just a suggestion.

Fandango wrote: ↑4 months ago Please note that I am in no way, shape, or form a coder. I do not know what half of the words that I am about to post mean. But this is a solution that I found posted online in regards to what appears to be the site's issue:



There's no problem with the database, the problem is in how you handle database connections from your software.

The way your script is set up is that every connection to your web server also opens a connection towards MySQL. That's not the scenario you want.

Raising the limit won't fix the issue, it will just delay yet another error. What you should do is use persistent connections.

One of the reasons why using php-fpm instead of server API's such as mod_php is preferred is because a set number of PHP processes is booted and a pool of connections to services is created.

The flow would be the following:

use php-fpm. Apache and nginx can use FCGI interface to speak to php-fpm processes
raise a relatively low amount of child processes for php-fpm. This shouldn't be overly large, default config usually works out, I'll make a guess that you don't run a hexacore system so 4-6 child processes should be fine
use persistent MySQL connections
What does this do? Your server accepts the request and sends it to php-fpm, which processes it when it becomes free. Each process uses 1 connection to MySQL. This means you can never hit some sort of hard limit like you have.

If your server is busy, the server should queue up the requests until PHP is capable of handling them. Be it Apache or nginx that you use, this approach will work well.

If your site is busy, it's likely that web server is working faster to accept connections and serve static content that PHP is to process dynamic content. In this case you have an option of adding another physical machine (or more) that runs php-fpm. Instructing your web server to round-robin between machines that serve PHP is trivial, for both of mentioned web servers.

Bottom line is that you want to utilize your resources in an optimal way. Opening and closing MySQL connections on every request isn't optimal. Pooling connections is.

Just a thought, if anybody with control knows what that means, agrees, and is capable of adjusting it accordingly.

AlexUSA3 wrote: ↑4 months ago On the old site, we used to do monthly blanket deletions of all accounts that hadn't more than one post. We chose one because many bots are sophisticated enough to make a convincing introductory post. I don't know if that would work here, but I mention it as something done in the past for security reasons.

OrdinaryWorld wrote: ↑4 months ago For example you can't see (all) images unless you have an account to view the story.

AlexUSA3 wrote: ↑4 months ago On the old site, we used to do monthly blanket deletions of all accounts that hadn't more than one post. We chose one because many bots are sophisticated enough to make a convincing introductory post. I don't know if that would work here, but I mention it as something done in the past for security reasons.

chadmc90 wrote: ↑4 months ago Also, I fail to see how inactive users pose a security risk.