a few feature suggestions
category: general [glöplog]
1) in groups.php?which=XXXX include the thumb, or pig, in the 'last comment' field.
2) disable [img] tags from users with 0 glöps. if that doesn't help with the inane shocksite crap, increase the limit to 500 glöps :-) (i tend to browse through some of the threads after lunch.)
one or both of these suggestions might be serious.
2) disable [img] tags from users with 0 glöps. if that doesn't help with the inane shocksite crap, increase the limit to 500 glöps :-) (i tend to browse through some of the threads after lunch.)
one or both of these suggestions might be serious.
2) is not a totally bad idea but a per-message +- rating system coupled with a "hide-all-messages with rating <0) should do the trick, I think.
imho fakeuser and pr0hnstahr userlevels should be enough to control this issue... theoretically.
3) pay gargaj a substantial amount of money so he can take time off work and finally finish v2
<lawl>but but but... didnt kebby finish v2 ages ago?!?!</lawl>
4) remind gargaj that you're a foot taller than he is and would REALLY REALLY like to see v2 finished
hermes i don't think it would work that well. you could always generate fake-users to up your ratings.. Unless the ratings would be based on glöps, again.
havoc i was mainly thinking about 'earning' the 'right' to post images. fakeuser and pr0hnstahr labels could be applied afterwards.
gargaj what if i'll buy you a beer the next time we meet? would that suffice?:-)
havoc i was mainly thinking about 'earning' the 'right' to post images. fakeuser and pr0hnstahr labels could be applied afterwards.
gargaj what if i'll buy you a beer the next time we meet? would that suffice?:-)
come to function (hereby avoiding my untimely death in the debtors' prison) and we'll discuss :P
2. Wouldn't people start writing (even more) crap comments on the product pages to increase the glop count?
uncle-x: i dont object to that idea, but imho we (sh/c)ould use those already available tools to solve at least part of the problem right away
rob: glops is not really relevant i guess, as you dont get any for posting on the bbs
but seriously.
i'm working on it. rly.
the new layout will be a cleaned up codebase, which allows a whole lot more when it comes to adding new features - the code is already shaping up and prototyping is becoming fairly easy, but there are so many pages on pouet to reproduce that it's getting a bit tedious.
hopefully after function i'll have a bit more time for it.
i'm working on it. rly.
the new layout will be a cleaned up codebase, which allows a whole lot more when it comes to adding new features - the code is already shaping up and prototyping is becoming fairly easy, but there are so many pages on pouet to reproduce that it's getting a bit tedious.
hopefully after function i'll have a bit more time for it.
rob: could be, but i guess people wouldn't be arsed to put that much effort into it then. especially if the glöp limit couldn't be reached with a few comments.
gargaj: could i have at least 1) even if i don't come to function?:-)
gargaj: could i have at least 1) even if i don't come to function?:-)
also.. just avoid the threads that have 'random' in them.. should keep you pretty much out of trouble at work at least :D
1) is now implemented
gargaj, i assume that it's a conscious choice that you're doing v2 mostly alone - right? i wouldnt at all mind helping recoding some of the pages, and doing some peer reviewing and whatnot (i'm a lot better at php than at democoding, just in case anyone wonders)
i think he's afraid it would turn into spaghetti hacks code again if he open sourced it.
i don't mean open sourcing, i mean me joining the team and helping with doing decent software engineering on this one. i promise i won't nag about design decisions already made (except if they're about security and stuff like that of course).
up to the man. :)
dont listen to skrebbel!!! he'll secretly embed happy hardcore midis in the pages!!111
skrebbel: here's how it works in my head - first i wanna lay down some coding conventions, basecode, stuff that kindof forces the code from not turning into a slow unmanagable mess of semicolons with french variable names, portuguese error messages and hungarian unslept nights. once i'm done with that and it has been PROVEN to work (i.e. the stresstesting is done and major clunks are straightened out BEFORE it's live), i'm happy to give part of the reins away - from that point on it would only depend on someone giving you an account.
ps awesome for the 1.
skrebbel: i offered the very same thing, and he said "come to function and make a release" instead...
priorities are priorities :)