| |
Fungus
Registered: Sep 2002
Posts: 747 |
Link tools used to production
I would love to see this option, which would be just like the ones for intros/sids used in this production.
It's nice to give credits to the authors of the tools we use to make things yes? :) |
|
... 19 posts hidden. Click here to view all posts....
|
| |
WVL
Registered: Mar 2002
Posts: 924 |
Quote: Good that person who uploads prods to csdb is credited, with all that nonsense you want to add it will be more effort than making actual demo...
It already is.. the top right keeps track of the creator :-P |
| |
mankeli
Registered: Oct 2010
Posts: 152 |
Quote: Good that person who uploads prods to csdb is credited, with all that nonsense you want to add it will be more effort than making actual demo...
Nonsense! It's all about data quality. ;) Kinda just philosophical thoughts about the problem, not that it would be very necessary nor practical to mark all that stuff.
Some time ago I also tried to find which c64 productions Krill has been actually involved in and it turned out to be very hard. :) |
| |
Krill
Registered: Apr 2002
Posts: 3092 |
Quoting WVLI agree, but still your personal page is a mess :-) It's no fun finding a production by Krill or LFT and needing to sift through all the loader credits. Quoting mankeliSome time ago I also tried to find which c64 productions Krill has been actually involved in and it turned out to be very hard. :) It just takes the browser's "search on page" capability with the keyword "code". :)
But seriously, it seems like having a simple set of checkboxes with all credit types defined by CSDb, defaulting to ticked, would suffice.
Then you can untick those you don't care for successively until the release list is neat and short enough. =) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11513 |
improving the credit system so csdb can make a difference between "directly involved" and "indirect connection" should have been implemented decades ago, when people started crediting rob hubbard in every fucking scroller thing that uses a hubbard tune.
without it is a mess indeed, please don't add more of it. |
| |
Fungus
Registered: Sep 2002
Posts: 747 |
I never said anything about stuff appearing on the users profile, that seems dumb if it did that. It should only be on the tool listed. Such inheritance would be silly and messy, which is why I suggested it be like sid/intro is already. |
| |
wil
Registered: Jan 2019
Posts: 66 |
Quote: There’s a lot of data that my OCD wants from CSDb .. but it’s about time I think.
Does nobody else feel like we’re filling these databases with information that only we, ourselves, will ever care about - and that we’re dwindling, not being replenished by new generations?
Maybe the day that the database will be complete, it will be done by the last of us to survive :’-)
I live with the convenient illusion that 2082 some people(*) will celebrate 100 years of C64. Looking forward to the releases and cracks.
(*) or perhaps just some AI bots |
| |
Burglar
Registered: Dec 2004
Posts: 1137 |
Quoting RaistlinDoes nobody else feel like we’re filling these databases with information that only we, ourselves, will ever care about yes
Quoting KrillRecognition is THE scene currency yes
Quoting mankeliSome time ago I also tried to find which c64 productions Krill has been actually involved in and it turned out to be very hard. :) yes
Quoting WVLI didn't want to mess up his page and added the credit in the production notes. This sounds like a good compromise between crediting and not messing things up yes
Quoting chatGPZimproving the credit system so csdb can make a difference between "directly involved" and "indirect connection" should have been implemented decades ago ... without it is a mess indeed, please don't add more of it. yes
Quoting FungusIt should only be on the tool listed. Such inheritance would be silly and messy, which is why I suggested it be like sid/intro is already. yes + on the release page that lists which tools were used.
In my opinion, this could only work if it got properly designed and implemented. Since that's not the case, I would use the current credit system only to give csdb credits to the "directly involved" as to not clutter other credits. Production Info can be used to give credit to tools and stuff.
Quite a few ppl use my tools and a few of them write something about it in prod info, notefile or similar. This always makes me happy, not just for the recognition, but also because it's nice to see ppl using my tools for their prods.
Some dont give credit and dont mention anything, which is fine too I guess. I for sure don't want "code/help" credits on releases I was not directly involved in.
It's hard to draw a line, if everything is in scope, common tools like KickAss and cc1541 would get flooded with thousands of release connections. Not good for the database, a shitload of work to register in the db and delivering a questionable amount of value.
So I guess prod info comment it is for now :) |
| |
TheRyk
Registered: Mar 2009
Posts: 2475 |
Burg nailed it! |
| |
mankeli
Registered: Oct 2010
Posts: 152 |
Quote:It's hard to draw a line, if everything is in scope, common tools like KickAss and cc1541 would get flooded with thousands of release connections. Not good for the database ...
What would be the problem with that? I understand it's less work to just have people to list that stuff in a generic text field, but I don't see why it would be bad for a database to have it in structured form? |
| |
Burglar
Registered: Dec 2004
Posts: 1137 |
Quoting mankeliI don't see why it would be bad for a database to have it in structured form? without knowing the performance characteristics of csdb's postgresql, if badly implemented, the many-to-many queries could cause a (too) high load on the db.
I'm guessing it's being hammered by scrapers quite heavily as it is. |
| Previous - 1 | 2 | 3 - Next |
