Log inRegister an accountBrowse CSDbHelp & documentationFacts & StatisticsThe forumsAvailable RSS-feeds on CSDbSupport CSDb Commodore 64 Scene Database
 Welcome to our latest new user danikAdmiral ! (Registered 2024-12-17) You are not logged in - nap
CSDb User Forums


Forums > CSDb Feedback > Pointless rule-enforcement on CSdb
2010-11-09 12:26
DeeKay

Registered: Nov 2002
Posts: 363
Pointless rule-enforcement on CSdb

Okay, you all know how I like CSDb-drama, but usually I don't create any myself, but in this case Groepaz anal-ness about CSDb-rules simply forces me to:

Here's the story: We released the PAL/NTSC version of the NUFLI editor. It pretty much only included the new universal displayer, so we kept everything else the same. However, as I noticed on X while working on Electric's Tiger, it got somehow corrupted, meaning that it would CRASH and DESTROY your picture when you drew with sprites under certain circumstances. I notified Crossbow and he confirmed it and started working on a fixed version, which i tested extensively to make sure it's all A-ok (that's v1.12)

Okay, so I approached Groepaz and asked how to best solve the problem that there's a BROKEN version of our NUFLI editor on CSDb that actually DESTROYS images! I was really willing to play by the rules (=not deleting it and not stealthily replacing it with a fixed version), but whatever I suggested and did (renaming it to "Buggy-ed" so people wouldn't find it, using the "this file is corrupted" feature in the file dialogue), he said it's all not allowed and reversed anything I would try. Now I'm locked out of our own tool and can't edit it, great. Talking about admin power abuse... I dunno what his problem is seriously, sometimes he just loves to piss people off for no reason whatsoever...

Okay, so now there's still the broken v1.11 online which people can happily download. But why the FUCK would anyone want a broken version of a tool that DESTROYS your picture? This is not some 90% party version of a Demo, so what's the fucking point? Okay, so we released it corrupted, our bad. But should we be punished indefinately for it when we FIXED it meanwhile? And why can't I simply use the "this file is corrupted" feature? What's the point being anal about THAT, too? I mean - you CAN still download it and masturbate over a disfunctional c64 tool if that's your sexual preference, but at least you'll know it's br0ken! The *only* hint that it's broken is in the comments, which thank god GroeFaZ didn't delete...

Good v1.12: NUFLI Editor V1.12
Bad v1.11: NUFLI Editor V1.11 [broken]
 
... 86 posts hidden. Click here to view all posts....
 
2010-11-09 13:24
Mace

Registered: May 2002
Posts: 1799
There's a feature called 'goof' in CSDb, where you can comment on buggy software.
I helped you...
2010-11-09 13:41
DeeKay

Registered: Nov 2002
Posts: 363
Okay, we did find a solution on IRC: I'll repackage the .prg of the b0rked version with a DON'T-USE-THIS.txt in the folder /dont/use/this/its/buggy/and/will/destroy/your/picture/if/you/use/the/sprite/mod e/ and re-add that...
2010-11-09 14:03
Steppe

Registered: Jan 2002
Posts: 1510
Really, if you can't bend the holy CSDb rules even in cases like that, accept my deepest condolences. This is silly, and if you lost touch to reality that much to not know when to turn a blind eye to something you really should go out and take a walk for a change.
2010-11-09 14:06
Celtic
Administrator

Registered: Jan 2002
Posts: 807
Due to some personal issues perff wont be back for a while, but when he does i will ask him about versioning :)
2010-11-09 14:11
chatGPZ

Registered: Dec 2001
Posts: 11384
Quote:
Really, if you can't bend the holy CSDb rules even in cases like that, accept my deepest condolences. This is silly, and if you lost touch to reality that much to not know when to turn a blind eye to something you really should go out and take a walk for a change.

please elaborate how making sure a certain something in the database means exactly what its supposed to mean can be silly. especially in a case like this, where it is about a simple yes/no question.

to make it clear again: "this image is corrupted" is a feature ment for those people who do nothing but look around csdb and add/fix/complete a lot of entries (you know who you are). it is NOT for users to know wether a certain release works or not. and as such, the information "this release is somehow broken, for whatever reason" is completely irrelevant, because the people adding/fixing entries need to know wether another working version of this release may eventually exist. and as a result marking something as corrupted which was simply broken from the start and was never released in working form is misleading and contraproductive.
2010-11-09 14:25
Mr. SID

Registered: Jan 2003
Posts: 424
What about the option of marking a release as "deprecated"?
Meaning: "Hey, it's archived, you can still download it, knock yourself out with it, but you should also know that there's a newer version, which is probably much better...".
Archive saved, Release platform improved, everybody wins, right?
2010-11-09 14:29
chatGPZ

Registered: Dec 2001
Posts: 11384
ofcourse, that would be an option
2010-11-09 14:40
daison

Registered: May 2005
Posts: 90
but...?
2010-11-09 14:46
chatGPZ

Registered: Dec 2001
Posts: 11384
same as always, perff is very busy these days (and completely gone for a while due to personal reasons atm) and he is the one who would implement this stuff. and there already is a long list of TODOs aswell :)
2010-11-09 15:25
Oswald

Registered: Apr 2002
Posts: 5094
Quote: Quote:
Really, if you can't bend the holy CSDb rules even in cases like that, accept my deepest condolences. This is silly, and if you lost touch to reality that much to not know when to turn a blind eye to something you really should go out and take a walk for a change.

please elaborate how making sure a certain something in the database means exactly what its supposed to mean can be silly. especially in a case like this, where it is about a simple yes/no question.

to make it clear again: "this image is corrupted" is a feature ment for those people who do nothing but look around csdb and add/fix/complete a lot of entries (you know who you are). it is NOT for users to know wether a certain release works or not. and as such, the information "this release is somehow broken, for whatever reason" is completely irrelevant, because the people adding/fixing entries need to know wether another working version of this release may eventually exist. and as a result marking something as corrupted which was simply broken from the start and was never released in working form is misleading and contraproductive.


Lengthy strawman. Steppe has lead.
Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 - Next
RefreshSubscribe to this thread:

You need to be logged in to post in the forum.

Search the forum:
Search   for   in  
All times are CET.
Search CSDb
Advanced
Users Online
Acidchild/Padua
The Human Co../Maste..
Ghost/Quantum
ΛΛdZ
wil
Jazzcat/Onslaught
Linus/MSL
LordNikon/Dekadence
LightSide
katon/Lepsi De
Guests online: 86
Top Demos
1 Next Level  (9.7)
2 13:37  (9.7)
3 Mojo  (9.6)
4 Coma Light 13  (9.6)
5 Edge of Disgrace  (9.6)
6 What Is The Matrix 2  (9.6)
7 The Demo Coder  (9.6)
8 Uncensored  (9.6)
9 Comaland 100%  (9.6)
10 Wonderland XIV  (9.6)
Top onefile Demos
1 Layers  (9.6)
2 Party Elk 2  (9.6)
3 Cubic Dream  (9.6)
4 Copper Booze  (9.6)
5 No Listen  (9.6)
6 Rainbow Connection  (9.5)
7 Dawnfall V1.1  (9.5)
8 Onscreen 5k  (9.5)
9 Morph  (9.5)
10 Libertongo  (9.5)
Top Groups
1 Performers  (9.3)
2 Booze Design  (9.3)
3 Oxyron  (9.3)
4 Triad  (9.3)
5 Censor Design  (9.3)
Top Swappers
1 Derbyshire Ram  (10)
2 Jerry  (9.8)
3 Violator  (9.7)
4 Acidchild  (9.7)
5 Cash  (9.6)

Home - Disclaimer
Copyright © No Name 2001-2024
Page generated in: 0.049 sec.