Open sourcing pouet.net ?
category: offtopic [glöplog]
you said you wanna go open, so where's the dump?
having a dump of the db, this also shouldn't be a problem.
Quote:
i wish i could take the 2000+ products i added over the past 12 years, haul them over to demozoo, and be done with pouet forever
having a dump of the db, this also shouldn't be a problem.
most of you are tards
gloom wrote
Maybe he was lazy because he thought it was boring.
Quote:
that was just lazy and boring
Maybe he was lazy because he thought it was boring.
Quote:
Pouet's source code, if someone actually managed to skim through it, would be an eternal source of articles for thedailywtf.
People keep saying this, but it's not THAT bad, especially not when you consider the context (hobby PHP project, started in 1999 vs. "professional, 10 million analytics scripts heavy, buzzword/social crap laden, 2013 web app"). Most ca. ~2000 era web code looks like that or worse. Heck, I regulary visit at least 2 websites made in frontpage some 10-15 years ago.
The security problems and some severe bugs that have survived this long, that's the real issue. Good thing pouet is way too niche and unimportant, otherwise that database would have been wiped out or compromised to hell and back 10+ years ago. And no, you would have never needed the source for that and the backup situation was pretty bad back then too, IIRC. (I hope it's way better now).
tomaes: Well, considering Analogue lives in New York, the time zone difference for getting things looked at in a timely fashion will be interesting.
tomaes, it IS that bad for what I could see at first glance (granted, I didn't spend much time in it, just browsed a bit on github). I understand the "context" as you call it, but that doesn't make it any less bad.
I've written TONS of bad code in my life (many that would fit perfectly on thedailywtf)... the fact that I had an excuse for doing that bad code doesn't make it any better :-)
I've written TONS of bad code in my life (many that would fit perfectly on thedailywtf)... the fact that I had an excuse for doing that bad code doesn't make it any better :-)
Ok. :)
Overall I'm actually quite happy how things seem to turn out after all. We get things fixed etc.; stuff is being worked on. That's (some) progress in my book. :)
Overall I'm actually quite happy how things seem to turn out after all. We get things fixed etc.; stuff is being worked on. That's (some) progress in my book. :)
looking back at this code now does make me cringe my teeth in dismay. i mean, i knew it was bad, but i had somewhat forgotten just how horrible and outdated. :) pouet was my first php+mysql challenge really. and now i'm not sure if i should be feeling horribly guilty for having prolonged it's suffering, or disgustingly proud for actually managing to extend and mantain it for as long as i did back then. it is making me feel somewhat nostalgic though. :D
I've mostly sat here quietly.
analogue's micro-management techniques leave a lot to be desired.
1 mod/admin taking privileges/access from another on any site isn't good - it usually is when the site splinters and is always divisive amongst the user-base. As we've seen on this topic.
All of the interaction I've had with Garg has been positive, he's usually telling me off but....
in the few years I've been here the only admin I've known is him. There are a few decisions he's made which I might question but as someone who volunteers their time & effort for other things myself I can appreciate his input for what it is.
What really concerns me here is the call for db access (or dump). I think it's not a bad thing for the site to be GNU/GPL or something similar. But the db aside from containing data about all the prod also contains all of our info. Some of it vaguely personal. & no matter how hard someone might "scrub" mysql something's going to get missed or overlooked.
In the meantime I've gotta thank kb_(?) for going on about how he likes to troll "my" threads with NSFW stuff (happened once that I can think of) - but it's nice to be thought about now and then.
Anyhoo - I suggest we all keep calm & pouet on.
analogue's micro-management techniques leave a lot to be desired.
1 mod/admin taking privileges/access from another on any site isn't good - it usually is when the site splinters and is always divisive amongst the user-base. As we've seen on this topic.
All of the interaction I've had with Garg has been positive, he's usually telling me off but....
in the few years I've been here the only admin I've known is him. There are a few decisions he's made which I might question but as someone who volunteers their time & effort for other things myself I can appreciate his input for what it is.
What really concerns me here is the call for db access (or dump). I think it's not a bad thing for the site to be GNU/GPL or something similar. But the db aside from containing data about all the prod also contains all of our info. Some of it vaguely personal. & no matter how hard someone might "scrub" mysql something's going to get missed or overlooked.
In the meantime I've gotta thank kb_(?) for going on about how he likes to troll "my" threads with NSFW stuff (happened once that I can think of) - but it's nice to be thought about now and then.
Anyhoo - I suggest we all keep calm & pouet on.
Bombe: :D
ringo:
not sure about the others, but i for one am only interested in the actual prod/groups data, maybe also the comments on the prods - but most definitely not on the bbs or your image threads.
other than that - you DO know that you are posting on the internet, on a publicly accessable site, don't you?
Quote:
What really concerns me here is the call for db access (or dump). I think it's not a bad thing for the site to be GNU/GPL or something similar. But the db aside from containing data about all the prod also contains all of our info. Some of it vaguely personal. & no matter how hard someone might "scrub" mysql something's going to get missed or overlooked.
not sure about the others, but i for one am only interested in the actual prod/groups data, maybe also the comments on the prods - but most definitely not on the bbs or your image threads.
other than that - you DO know that you are posting on the internet, on a publicly accessable site, don't you?
v3nom: I think he was concerned about the user-account information.
Kusma: Just like the rest of us, I think ;)
Quote:
gloom: So you are saying Gargaj has been this super-developer the last four years on pouet.net but there are still SQL-Injection bugs? Maybe you should get yourself a new hero.
lator is such a better troll than me, I cant but stand back and admire his work.
If you had cared to read the source, you would have noticed that the user-account data is stored on the sceneid server - not inside the pouet database.
First I was like: WTF is wrong with Pouet!!! ..and this fucked up thread
But then I was like: oh what the heck, back to TUMBLR.
But then I was like: oh what the heck, back to TUMBLR.
Just to re-iterate: Passwords are not stored in the pouet db.
Whatever future incarnation of Pouet becomes the standard, please include a pony/unicorn picture filter ;)
Quote:
Just to re-iterate: Passwords are not stored in the pouet db.
Emails are, though. (And, strictly speaking, the mapping of Pouet user IDs to sceneID logins is privileged information too.)
Either way, it's certainly not the case that "we can't possibly open up the data, there might be other private information we've forgotten to redact". A quick scan through the db schema is all it needs.
Knoeki: I do find the pony posting a bit annoying. I don't force an unrelated subculture on you at every opportunity, so please, consider using a smiley or something.
yes, the ponies are fucking annoying.
Yep. A feature request for pouet whateverversion if it will ever happen: ability to block images in the BBS, or per user.
