Suggestion: About suggestions and general CS QoL *UPDATE

[Kururu]

i’ve been watching this thread and saving a draft for weeks lol and have so much to say but i’ll try to not make this long

1. c$ inflation = bad. theres so many ideas to fix/curb it why there hasn’t been anything done is beyond me. and don’t even get me started on the sorting suggestions

2. i have not put a dime into this site since coming back in 2023. i buy gems on fr and trade for c$ that way. if there was more QoL updates i would put money in this site but nah. if there was fundraiser to update this site sure i’d put $20 in why not

3. my main point: the suggestions forum isn't very efficient at all. the amount of suggestions that just sit unanswered is too many. yes this point has been brought up but DUDE, suggestions need to be given a clear yes or no within THREE YEARS max. being shot down is so much better than being in the dark. im aware 3 years for most people is way too long (and i agree don’t you worry) but with how slow the process is now 3 years really isn’t that crazy

4. we aren’t privy to everything so while it feels like money is being pocketed it really could not be but who knows. if on the off chance cs is scraping then again give me a freaking reason to put money in this site! i know you know a lot of users feel this sentiment

5. yes i truly would love if the site were down for an extended period of time IF it meant some serious changes were changes were made (tho from what it sounds like this wouldn’t be totally necessary). at the VERY least the way suggestions are handled must be changed. like kite said, if it comes down to announcements for bigger changes, then so be it. but theres literally no reason for a suggestion to be active for over 10 years, thats ridiculous put bluntly. and you know what, hey if there is something big behind the scenes let users know so we aren’t in the dark being sad lol


side note: if im wrong on any of this just lmk i’ll edit lol

This is such a good TLDR, thank you for summarizing everything so concisely and adding your own suggestions. This basically is exactly what I'm thinking too.

[Darni]

bumping since I just saw in another thread people discussing a similar topic

[sonnenblume]

Bump and support.
It's just amazing that it's been ten years and this is still the same.

[nickjr]

I just found this thread (as in, the one I'm posting on now), and I don't wanna read through all of it, but I thought I should post a link to another thread on the same topic since searching its thread ID within this thread didn't bring up any hits (so it looks like no one has mentioned it yet)

my support post from back then still stands now:

[snip] I think even one or two more coders could help for the small QoL things, especially those that don't require deeper knowledge of CS's code/databases/other things about how CS is set up.

(e.g. The suggestion to move pets from their individual pages is probably fairly simple to code, but to code it I think you'd still need to know which databases to touch so you can actually move the pet. So even if you could just copy-paste the regular move code, you'd still need to familiarize yourself enough with how CS is set up to make sure the code works. That's a small QoL update that needs deeper knowledge.

The suggestion to confirm logout, however, shouldn't require any knowledge of how CS works. And it's pretty simple to code (unless we want a fallback of an entire confirmation page for users who have JavaScript turned off, but even that shouldn't be too bad). That's a small QoL update that doesn't need deeper knowledge.)

And for the bigger things... I think even having someone to give pseudocode or structure ideas could be helpful. That's a good chunk of doing any substantial programming.

I kinda wonder how the admins would want to solicit volunteer coders, though. There are the issues of trust and skill, brought up previously. I guess I'll have to polish my programming interview skillz not only for real life but also for CS??

and also, here is a specific post from the thread I want to highlight because it may provide a little more insight (if something like this hasn't already been shared)

[snip]

also, a small tiny tidbit of new information: I found the phpBB files for a small phpBB forum that my friends and I have (private, just for us) and... wow

I kinda understand why there haven't been any new coders to this day. Some of the phpBB files where you make stuff happen... have........... some info that is sensitive and that I bet even moderators won't see.

But! Those files were basically database files. (phpMyAdmin) I haven't found the files for the actual webpages, and I can't imagine that they would have any sensitive info. So my point from the previous page still stands: Getting more coders on board for small QoL updates (cough confirm logout cough) shouldn't be that bad

[snip]

[Clayflower.]

bump

Any staff member can forward suggestions to Nick. Our current method is basically a thread where we link popular suggestions for founder review. I stated this in another thread, but we are working on a more efficient way of forwarding suggestions that would involve “rack and stacking” ones that have gotten the most support, seem to be easy to code / implement, etc., and listing them all on one living document. This would prioritize what we would like to see answered first, second, and so on to provide you all responses on if said suggestions are possible, in progress, and so forth. By consolidating everything, it should hopefully make the process easier on both staff and Nick.

thank you for the explanation! it's always a bit reassuring to have a glimpse of what's going on behind the scenes.

can i ask how often that thread receives responses from nick with the current set up - just kind of a ballpark estimate? i think a lot of people in this thread would appreciate knowing just how involved nick still seems to be, as obviously a lot of us looking from the outside in believe he's,,, not around nearly at all anymore.

[Clayflower.]

bump

Any staff member can forward suggestions to Nick. Our current method is basically a thread where we link popular suggestions for founder review. I stated this in another thread, but we are working on a more efficient way of forwarding suggestions that would involve “rack and stacking” ones that have gotten the most support, seem to be easy to code / implement, etc., and listing them all on one living document. This would prioritize what we would like to see answered first, second, and so on to provide you all responses on if said suggestions are possible, in progress, and so forth. By consolidating everything, it should hopefully make the process easier on both staff and Nick.

thank you for the explanation! it's always a bit reassuring to have a glimpse of what's going on behind the scenes.

can i ask how often that thread receives responses from nick with the current set up - just kind of a ballpark estimate? i think a lot of people in this thread would appreciate knowing just how involved nick still seems to be, as obviously a lot of us looking from the outside in believe he's,,, not around nearly at all anymore.

[Clayflower.]

bump

Any staff member can forward suggestions to Nick. Our current method is basically a thread where we link popular suggestions for founder review. I stated this in another thread, but we are working on a more efficient way of forwarding suggestions that would involve “rack and stacking” ones that have gotten the most support, seem to be easy to code / implement, etc., and listing them all on one living document. This would prioritize what we would like to see answered first, second, and so on to provide you all responses on if said suggestions are possible, in progress, and so forth. By consolidating everything, it should hopefully make the process easier on both staff and Nick.

thank you for the explanation! it's always a bit reassuring to have a glimpse of what's going on behind the scenes.

can i ask how often that thread receives responses from nick with the current set up - just kind of a ballpark estimate? i think a lot of people in this thread would appreciate knowing just how involved nick still seems to be, as obviously a lot of us looking from the outside in believe he's,,, not around nearly at all anymore.

[Clayflower.]

bump

Any staff member can forward suggestions to Nick. Our current method is basically a thread where we link popular suggestions for founder review. I stated this in another thread, but we are working on a more efficient way of forwarding suggestions that would involve “rack and stacking” ones that have gotten the most support, seem to be easy to code / implement, etc., and listing them all on one living document. This would prioritize what we would like to see answered first, second, and so on to provide you all responses on if said suggestions are possible, in progress, and so forth. By consolidating everything, it should hopefully make the process easier on both staff and Nick.

thank you for the explanation! it's always a bit reassuring to have a glimpse of what's going on behind the scenes.

can i ask how often that thread receives responses from nick with the current set up - just kind of a ballpark estimate? i think a lot of people in this thread would appreciate knowing just how involved nick still seems to be, as obviously a lot of us looking from the outside in believe he's,,, not around nearly at all anymore.

[Clayflower.]

bump

Any staff member can forward suggestions to Nick. Our current method is basically a thread where we link popular suggestions for founder review. I stated this in another thread, but we are working on a more efficient way of forwarding suggestions that would involve “rack and stacking” ones that have gotten the most support, seem to be easy to code / implement, etc., and listing them all on one living document. This would prioritize what we would like to see answered first, second, and so on to provide you all responses on if said suggestions are possible, in progress, and so forth. By consolidating everything, it should hopefully make the process easier on both staff and Nick.

thank you for the explanation! it's always a bit reassuring to have a glimpse of what's going on behind the scenes.

can i ask how often that thread receives responses from nick with the current set up - just kind of a ballpark estimate? i think a lot of people in this thread would appreciate knowing just how involved nick still seems to be, as obviously a lot of us looking from the outside in believe he's,,, not around nearly at all anymore.

[Clayflower.]

bump

Any staff member can forward suggestions to Nick. Our current method is basically a thread where we link popular suggestions for founder review. I stated this in another thread, but we are working on a more efficient way of forwarding suggestions that would involve “rack and stacking” ones that have gotten the most support, seem to be easy to code / implement, etc., and listing them all on one living document. This would prioritize what we would like to see answered first, second, and so on to provide you all responses on if said suggestions are possible, in progress, and so forth. By consolidating everything, it should hopefully make the process easier on both staff and Nick.

thank you for the explanation! it's always a bit reassuring to have a glimpse of what's going on behind the scenes.

can i ask how often that thread receives responses from nick with the current set up - just kind of a ballpark estimate? i think a lot of people in this thread would appreciate knowing just how involved nick still seems to be, as obviously a lot of us looking from the outside in believe he's,,, not around nearly at all anymore.