- Messages
- 3,295
- Reaction score
- 227
- Points
- 63
I've noticed (after seeing a couple of hinty things in the Free Hosting support forum) that chats are no longer explicitly mentioned in the ToS. This leads me to ask (for planning purposes):
Will well-behaved, resource-light chats be tolerated now (or at some point in the near future)? I would assume that even if the answer is "yes", resource monitoring would still be in full force, and people who can't play nice with the other kids in the sandbox will be given at least a time-out.
A feature I'd like to add to a [completely repurposed] site could, at times, become near enough to real-time to have been a suspendable offence under the old rules (doing SSO with an outboard host is a real pain in the ol' derriere -- and firing up an instance at Google once you've been inactive for an hour takes forever).
It'd be short-history (and probably flat-file, since I don't want to maintain a history -- nothing nefarious going on, but the name of the target audience includes the word "Anonymous" prominently) with a low update frequency. Figure a couple of hundred words per posting, one user enabled for submission at a time, with a small hard-limited group (a dozen tops) participating at any one time and an update frequency that would be in line with the expected usage pattern (certainly not more than one request per minute per user, probably once every 90 seconds would suffice, and that for a text file). I know I can write that to be very tight and light, and it would be tremendously easier for me to do it all in one spot than to spread the wealth (a site here plus an app back-end elsewhere). And the "meetings" would be twice a day for an hour max (and usually at ungodly hours, which is why the online option popped up in the first place).
Is it worth my while planning something like this for near-term deployment? I can do benchmarking and stress-testing locally to make sure it's well-behaved and bulletproof. Or will I have to wait until we've thrown enough into the kitty to pay for something with a bit more processing headroom?
Thanks for taking the time to look this over.
-- Stan
Will well-behaved, resource-light chats be tolerated now (or at some point in the near future)? I would assume that even if the answer is "yes", resource monitoring would still be in full force, and people who can't play nice with the other kids in the sandbox will be given at least a time-out.
A feature I'd like to add to a [completely repurposed] site could, at times, become near enough to real-time to have been a suspendable offence under the old rules (doing SSO with an outboard host is a real pain in the ol' derriere -- and firing up an instance at Google once you've been inactive for an hour takes forever).
It'd be short-history (and probably flat-file, since I don't want to maintain a history -- nothing nefarious going on, but the name of the target audience includes the word "Anonymous" prominently) with a low update frequency. Figure a couple of hundred words per posting, one user enabled for submission at a time, with a small hard-limited group (a dozen tops) participating at any one time and an update frequency that would be in line with the expected usage pattern (certainly not more than one request per minute per user, probably once every 90 seconds would suffice, and that for a text file). I know I can write that to be very tight and light, and it would be tremendously easier for me to do it all in one spot than to spread the wealth (a site here plus an app back-end elsewhere). And the "meetings" would be twice a day for an hour max (and usually at ungodly hours, which is why the online option popped up in the first place).
Is it worth my while planning something like this for near-term deployment? I can do benchmarking and stress-testing locally to make sure it's well-behaved and bulletproof. Or will I have to wait until we've thrown enough into the kitty to pay for something with a bit more processing headroom?
Thanks for taking the time to look this over.
-- Stan
