How comes the archiving notion?
I've got a threadsuck utility finished that's awaiting testing from ita (nudge, nudge ;) ).
'Dirty Girls'
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
How comes the archiving notion?
I've got a threadsuck utility finished that's awaiting testing from ita (nudge, nudge ;) ).
The threadsucker might break the bandwidth's back.
In theory, that won't save any space unless we store the files off buffistas.org. I haven't run the numbers, but the HTML might very well be bigger than the data in the tables.
The threadsucker might break the bandwidth's back.
Does the sucker work via hitting the server, or internally by grabbing stuff from the DB? If the latter, no bandwidth issues at all.
They shut the site down, if I read the fora right.
Don't they just charge us more? That seems wrong.
If the info gets to a browser, there will be bandwidth issues.
As for the charging, I think they shut it down, and then ask for more money. At least, that's what some users have experienced.
I think they shut it down, and then ask for more money
That's wrong like a wrong thing on National Wrong Day.
Perhaps we need to contact them soon and say "we might need more bandwidth" or something?
We're early in the month, so I'll just send out feelers.
Certainly less bandwidth is used threadsucking, say, 100 posts, than is used by retrieving 10 pages of 10 posts each.
'Tis true. As will the ability to set how many posts are displayed per page. Jon, where would you put that in the set profile page?
It already works, there's just nowhere to set it.
(Mine's 20).
We should have a contingency plan, a way to get them their money quickly if we go over the limit, if our collective funds aren't liquid or accessible. Let several people know the URL for the credit-card money infusion, and the funds could reimburse them. How much money are we talking, anyway? Maybe we don't want to ever pay to go over the limit.