blkpanther me beautiful
category: general [glöplog]
Rowley:
Sorry man, I have not enuff time to look for what BP submitted, put all the wrong IDs I have spotted here or there, next wrap it in BBCode line by line, and post it.
I gave my idea cause it was the simplest way for me to work. NO pouet hacks were considered (what an idea).
After "our" job done, all the ID numbers/prods, automaticly wrapped in BBC would be posted here. And, the rest, would be for you to do...
Sorry man, I have not enuff time to look for what BP submitted, put all the wrong IDs I have spotted here or there, next wrap it in BBCode line by line, and post it.
I gave my idea cause it was the simplest way for me to work. NO pouet hacks were considered (what an idea).
After "our" job done, all the ID numbers/prods, automaticly wrapped in BBC would be posted here. And, the rest, would be for you to do...
Seriously, some ppl who posted here, should have read previously our discussion...
Quote:
And, the rest, would be for you to do...
define "the rest" please- as you know, i will be happy to fix 100% manually verified stuff. but anything less, any assumptions, approximations, probabilities, etc- that's all pointless.
just to be clear, with "100% manually verified stuff" i mean that you have to be sure about the fixes you post because you looked at the prods/groups/platforms/links/etc that are involved. whether you start looking at a prod randomly, or because blkpanther says it might be wrong, or because you get visions about it straight from heaven, is irrelevant to me, i just care about the quality of the fixes: 100%, or nothing at all ;)
I was not talking about apporximations believing that sometimes leaving things untouched is better thant making a bigger mess (good rule used by the HVSC crew).
I proposed my humble knowledge (NOT as yo say "because you get visions about it straight from heaven") and help where I could, with the easiest, way for me. Nothing more.
I believe that in "fix me ...." you are NOT applying the changes with out verifying that, simply cuz they were posted. Otherwise I understand your worries.
OK. I have nothing more to say. Cheers.
I proposed my humble knowledge (NOT as yo say "because you get visions about it straight from heaven") and help where I could, with the easiest, way for me. Nothing more.
I believe that in "fix me ...." you are NOT applying the changes with out verifying that, simply cuz they were posted. Otherwise I understand your worries.
OK. I have nothing more to say. Cheers.
to be precise: we were talking here about C64 inserts only, so "prods/groups/platforms/links/etc" widens importantly.
As I said....
As I said....
you know, i really think we're pretty much on the same page...
we agree here 100%
that's what we need indeed
well, i said that to underline that i don't mind where good fixes come from, as long as they are good fixes. let's put it differently: suppose i sit on the toilet in 5 minutes from now, and i suddenly remember "prod XXX is not from group YYY but from ZZZ". then i go back to the pc, check my idea, and find it is correct. so it would be a good fix, even if i thought of it while taking a shit- that's the point i was trying to make, i'm *not* saying you're some religious nutcase or so ;)
that would be cool, we can sure use some help
not always, indeed. it depends on who posts about what. for example, if you post a fix about an old polish atari8 prod, i would probably add it blind, coz i know you have deeper knowledge in that area than any of us. but if some new user who is only known for posting pictures on the random image thread posts the same fix, sure enough i will investigate first.
so... i suggest that, instead of fighting about things we agree on ;), we move forward now and start actually fixing stuff. :-)
Quote:
I was not talking about apporximations believing that sometimes leaving things untouched is better thant making a bigger mess (good rule used by the HVSC crew).
we agree here 100%
Quote:
I proposed my humble knowledge
that's what we need indeed
Quote:
(NOT as yo say "because you get visions about it straight from heaven")
well, i said that to underline that i don't mind where good fixes come from, as long as they are good fixes. let's put it differently: suppose i sit on the toilet in 5 minutes from now, and i suddenly remember "prod XXX is not from group YYY but from ZZZ". then i go back to the pc, check my idea, and find it is correct. so it would be a good fix, even if i thought of it while taking a shit- that's the point i was trying to make, i'm *not* saying you're some religious nutcase or so ;)
Quote:
and help where I could, with the easiest, way for me. Nothing more.
that would be cool, we can sure use some help
Quote:
I believe that in "fix me ...." you are NOT applying the changes with out verifying that, simply cuz they were posted.
not always, indeed. it depends on who posts about what. for example, if you post a fix about an old polish atari8 prod, i would probably add it blind, coz i know you have deeper knowledge in that area than any of us. but if some new user who is only known for posting pictures on the random image thread posts the same fix, sure enough i will investigate first.
so... i suggest that, instead of fighting about things we agree on ;), we move forward now and start actually fixing stuff. :-)
never should have given keops his pouet status. sorry everyone else, my bad. :/
if the man wants to write a script to help fix the stuff, let him write the damn script. he clearly stated he wasnt planning to inject anything anymore.
blk: you dont have to parse, there are rss feeds of the stuff. maybe not complete but gargaj can easily help you out with that, please catch him on irc.
gargaj: just give him a dump of the database. its all public info anyway. it should even be periodically dumped and placed public somewhere! talk to jeffry to automate it from the backups or something and add a link on the faq. it would be great, not just for public mirror / backup but also to open source it more easily to whoever wants to do some dataviz or alternative frontend to pouet.
if the man wants to write a script to help fix the stuff, let him write the damn script. he clearly stated he wasnt planning to inject anything anymore.
blk: you dont have to parse, there are rss feeds of the stuff. maybe not complete but gargaj can easily help you out with that, please catch him on irc.
gargaj: just give him a dump of the database. its all public info anyway. it should even be periodically dumped and placed public somewhere! talk to jeffry to automate it from the backups or something and add a link on the faq. it would be great, not just for public mirror / backup but also to open source it more easily to whoever wants to do some dataviz or alternative frontend to pouet.
ps: meanwhile, you're not the one cleaning up the shit, we are. It's quite easy to have a strong opinion about stuff when not being involved in the process and the daily work involved.
You're also not the one who had to deal with the recent hammering and scripts that made some Razor prods % popularity skyrocket, involving again the same people who then proposed their "help" again.
You're also not the one who had to deal with the recent hammering and scripts that made some Razor prods % popularity skyrocket, involving again the same people who then proposed their "help" again.
Quote:
its all public info anyway. it should even be periodically dumped and placed public somewhere! talk to jeffry to automate it from the backups or something and add a link on the faq. it would be great, not just for public mirror / backup but also to open source it more easily to whoever wants to do some dataviz or alternative frontend to pouet.
Best f*cking idea yet. rsync FTW?
please don't dump it as one big xml :)
I sweared myself not to post on pouet anymore but I simply have to!
Let me put our statement here again about it. Noone of the rzr guys was involved in that. Nor did we ask anyone to manipulate the stats of our prods. We have been as much disappointed as any other real scener about it when it turns out that someone obviously used tor servers to raised the popularity. In fact we still don't know if that attack stopped because the pouet guys filter the tor traffic (yes again I delivered them a script to filter it but as any help from rzr is rejected I can't imagine they used it) or because the attacks stopped.
Anyway all we could think of was a groupie who was trying to push things for rzr unasked. We still don't know who it was. Pointing the finger on me with "involving again the same people" is simply wrong. Simply stop lying around!
And when it comed to fix the csdb-inserts.
1. Its no script it will be a tool to help make decissions (start actually reading)
2. I don't need or want any access to the db
3. If you reject any help, finally fix it then yourself and stop winning about it
Quote:
ps: meanwhile, you're not the one cleaning up the shit, we are. It's quite easy to have a strong opinion about stuff when not being involved in the process and the daily work involved.
You're also not the one who had to deal with the recent hammering and scripts that made some Razor prods % popularity skyrocket, involving again the same people who then proposed their "help" again.
Let me put our statement here again about it. Noone of the rzr guys was involved in that. Nor did we ask anyone to manipulate the stats of our prods. We have been as much disappointed as any other real scener about it when it turns out that someone obviously used tor servers to raised the popularity. In fact we still don't know if that attack stopped because the pouet guys filter the tor traffic (yes again I delivered them a script to filter it but as any help from rzr is rejected I can't imagine they used it) or because the attacks stopped.
Anyway all we could think of was a groupie who was trying to push things for rzr unasked. We still don't know who it was. Pointing the finger on me with "involving again the same people" is simply wrong. Simply stop lying around!
And when it comed to fix the csdb-inserts.
1. Its no script it will be a tool to help make decissions (start actually reading)
2. I don't need or want any access to the db
3. If you reject any help, finally fix it then yourself and stop winning about it
Quote:
We have been as much disappointed as any other real scener about it when it turns out that someone obviously used tor servers to raised the popularity
and
Quote:
stop winning
Quote:
please don't dump it as one big xml :)
Link me up you beautiful mofo.
Quote:
Quote:Quote:
stop winning
Quote:
(start actually reading)
Rowley Birkin:
Thanx, we do have pretty close way of seing the case. Thanx for your remarks and attitude too.
Will see what can we/I do. It really depends on my time (time, what time?)...
Small question:
Some groups are defined: "Ikari [IK]" - first string as the name, latter as the abbreviation. imagine we got Ikari c64 and Ikari Amiga. What kind of rule we should use to make it standard?
1. Ikari [IK] (c64) ?
2. Ikari [IK] [c64] ?
3. or ????
I am aware that maybe it is not too important, but I like have everything in the order.
Another on is more delicate. I remeber some groups using the same name on the C64, Amiga and the Clone. As the example I will use (one more time) Prestige.
On the c64 it is a different group than on the Amiga. So we will have Prestige (c64) and Prestige (Amiga eventually).
BUT... we all know we got Prestige on the PC, which was a merge of 2-3 groups (well, not all we know that=). So, the question is if in this case do we split their Amiga from PC releases? Or just leave it togeher?
Prestige PC afaIr has Amiga origins. At least one cracker was on the Amiga, but dunno if it was he, who granted the PC groups to use an old Amiga name. But probably there are some C64/Amiga/PC groups with the same name, but hardly have the same origins...
Thx for the answer.
Thanx, we do have pretty close way of seing the case. Thanx for your remarks and attitude too.
Will see what can we/I do. It really depends on my time (time, what time?)...
Small question:
Some groups are defined: "Ikari [IK]" - first string as the name, latter as the abbreviation. imagine we got Ikari c64 and Ikari Amiga. What kind of rule we should use to make it standard?
1. Ikari [IK] (c64) ?
2. Ikari [IK] [c64] ?
3. or ????
I am aware that maybe it is not too important, but I like have everything in the order.
Another on is more delicate. I remeber some groups using the same name on the C64, Amiga and the Clone. As the example I will use (one more time) Prestige.
On the c64 it is a different group than on the Amiga. So we will have Prestige (c64) and Prestige (Amiga eventually).
BUT... we all know we got Prestige on the PC, which was a merge of 2-3 groups (well, not all we know that=). So, the question is if in this case do we split their Amiga from PC releases? Or just leave it togeher?
Prestige PC afaIr has Amiga origins. At least one cracker was on the Amiga, but dunno if it was he, who granted the PC groups to use an old Amiga name. But probably there are some C64/Amiga/PC groups with the same name, but hardly have the same origins...
Thx for the answer.
Ahhh, and thanks to ps for his words!
Cheers!
Cheers!
René Madenmann:
Thanx for that.
Read "fix me beautiful" thou... there we had a conversation about.
Thanx for that.
Read "fix me beautiful" thou... there we had a conversation about.
there are 3 citizen of chernobyl
found ~20 false positives in that list (and fixed those by correcting csdb id's)