Do you think I could just leave this part blank and it'd be okay? We're just going to replace the whole thing with a header image anyway, right?
You are not logged in.
Pages: 1
If 1000 posts make you "probably not a nub", is there anything for user woots?
What about the ability to order users by total post woots?
I'd like to see that, honestly. It's not a totally productive mod, but neither is ordering by posts...
thanks
Offline
It would be interesting to see
Back to woot abuse days.
This is a false statement.
Offline
Possible, but not easily so. The way woots are currently stored is as a serialized array attached to each post, not as a separate table like posts. I could write a script to "fix" it if the idea becomes popular enough.
"Sometimes failing a leap of faith is better than inching forward"
- ShinsukeIto
Offline
I was confused for a moment. See, I've been through setting up SQL databases before. As a self-proclaimed self-taught self-accredited (ha) OOP-programmer, my first instinct was to find ways to add member information to an entry. To my dismay, I found there was no array option. -- but I get what you mean.
Or, we could just query every post on EE into the PHP script and loop through to find every woot for every request... ha ha no
How does the server know when a user has reached 20? Is that in a user serialized array?
@Creature: Yes, but not terribly. I saw NK1F had a few pages full of woots. With the 20 limit (which I'd like to increase, but that obviously won't mix with this argument), woot abuse wouldn't be effective. Further, a few well-worded posts on a high-traffic topic would easily outdo the user deciding to woot one person in particular. (or so I think)
Offline
I was confused for a moment. See, I've been through setting up SQL databases before. As a self-proclaimed self-taught self-accredited (ha) OOP-programmer, my first instinct was to find ways to add member information to an entry. To my dismay, I found there was no array option. -- but I get what you mean.
Yeah, it's a VARCHAR filled with the output of PHP's serialize() function.
How does the server know when a user has reached 20? Is that in a user serialized array?
20 what? Like posts or something?
"Sometimes failing a leap of faith is better than inching forward"
- ShinsukeIto
Offline
hummerz5 wrote:I was confused for a moment. See, I've been through setting up SQL databases before. As a self-proclaimed self-taught self-accredited (ha) OOP-programmer, my first instinct was to find ways to add member information to an entry. To my dismay, I found there was no array option. -- but I get what you mean.
Yeah, it's a VARCHAR filled with the output of PHP's serialize() function.
How does the server know when a user has reached 20? Is that in a user serialized array?
20 what? Like posts or something?
20 Woots, a popup message reminding us we have reached the 20 woot cap appears at that point
Offline
Different55 wrote:hummerz5 wrote:I was confused for a moment. See, I've been through setting up SQL databases before. As a self-proclaimed self-taught self-accredited (ha) OOP-programmer, my first instinct was to find ways to add member information to an entry. To my dismay, I found there was no array option. -- but I get what you mean.
Yeah, it's a VARCHAR filled with the output of PHP's serialize() function.
How does the server know when a user has reached 20? Is that in a user serialized array?
20 what? Like posts or something?
20 Woots, a popup message reminding us we have reached the 20 woot cap appears at that point
ah. right. I have a table for keeping track of woot times for each user. It'd be better off as an INT field that gets reset at midnight but woots originally were "X in a 24 hour period", not "X since the last midnight" like it is now.
"Sometimes failing a leap of faith is better than inching forward"
- ShinsukeIto
Offline
Back to woot abuse days.
Starting now just to be safe
Offline
Pages: 1
[ Started around 1738504462.8307 - Generated in 0.048 seconds, 12 queries executed - Memory usage: 1.5 MiB (Peak: 1.66 MiB) ]