Yes? No?
But if a feature is good enough that SHOULD be implemented as an official feature, why rely on add-ons?
Because all the data would be stored by the website servers instead of locally by the users
Comment has been collapsed.
Yes, every "+1" comment has the same server load as a blacklist/whitelist remarks.
However, it is common practice for forums to purge / archive older comments regularly. Whereas blacklist/whitelist remarks will have to be stored permanently.
Comment has been collapsed.
Holy crap I love you. Let me explain.
Google Drive is my answer. Spreadsheet, freely available, wherever I'm logged in. Put whatever you want in there, including names/reasons for whitelisting/blacklisting.
A cloud, for my special data.
Thank you, thank you. Your remark might have been intended as a joke, but it immediately solved all my problems.
Thank you.
Edit:
I already have my first entry.
Comment has been collapsed.
It's useful feature, in the "nice to have" category.
Data storage is not a big issue here, most of tags are short (especially if compared with posts).
Extra server load can be mitigated by restricting places where tags are shown to user profiles and accounts bl/wl config - from where scripts can load and cache the data locally
Comment has been collapsed.
Although I don't use the blacklist/whitelist feature much, I do agree that it would be nice to have. However, that adds to the data that SG would have to keep. I don't know the specifics anyways there are multiple threads like this and you can probably find more info on them:
Edited to add a few simple calculations:
Imagine if you have 100 users only and they each fill up their whitelist/blacklist which I believe is 1000 on each? that's 2000 per user, and 100 users which becomes 200 000 rows of data to keep. This is obviously unlikely that there are only 100 users using the list and/or that they max them out.
Also take into consideration every time someone wants to remove someone from their blacklist or delete the comment then you'd have to search through the database for that specific record to delete it. That's just my thoughts at least.
That being said I don't think it's impossible to implement either but I would say it is not a priority either, I'll vote yes though.
Comment has been collapsed.
If the implementation of black/whitelist is done this way, there ARE already 200,000 rows of data, regardless of whether there are remarks or not. The database will just need to store one more text column to save the remarks.
Removing black/whitelist will have zero impact. Deleting black/whitelist will still be deleting the same row, regardless of whether there is an additional column. Only impact is when user wants to edit the remarks, but performance-wise, it will be almost the same.
Delete row from blacklist where (xxxxx)
Edit row set remarks = 'new remarks' where (xxxxx)
These 2 have the same performance as long as the where clause is the same.
The only database impact are the extra disk space needed for the remarks, and the extra bandwidth for sending/retrieving remarks.
Remarks column does not need to be indexed, and so there won't even be any performance impact on the database itself.
Comment has been collapsed.
SG++ user tagging feature with optional blacklist/whitelist indicator userscript I guess is the only similar methodry.
Maybe even using SG usernotes userscript instead of tagging if you wanted more comprehensive notes.
Comment has been collapsed.
People who worry about resources being used on the servers are just being silly and don't know what they're talking about.
For reference, the data type would be string, and probably would be at predetermined length maximum. If SG can't afford to add one extra cell for blacklist table, they have a bigger problem to deal with.
I'm not saying this feature should be added, it's just it makes me cringe to see people saying big words they can't even understand.
Comment has been collapsed.
Even though this an extremely old thread, I searched before adding my own on the same subject.
I think adding this feature is especially important now with the implemented two-way blacklist. You can't go back into their GAs to look for why you might've put them on the list (perhaps them admitting it's a different game etc). At best now you can only go to their profile and wonder why.
Comment has been collapsed.
8,609 Comments - Last post 6 minutes ago by InSpec
172 Comments - Last post 3 hours ago by Tcharr
88 Comments - Last post 4 hours ago by Deleted2137
241 Comments - Last post 4 hours ago by RCSWE
823 Comments - Last post 6 hours ago by MagicDN
24 Comments - Last post 6 hours ago by steveywonder75
443 Comments - Last post 9 hours ago by crocospect
410 Comments - Last post 6 minutes ago by Petrucius
216 Comments - Last post 14 minutes ago by Momo1991
880 Comments - Last post 20 minutes ago by RePlayBe
224 Comments - Last post 22 minutes ago by RePlayBe
143 Comments - Last post 28 minutes ago by RePlayBe
3 Comments - Last post 28 minutes ago by Axelflox
9 Comments - Last post 1 hour ago by Tachikoma
So when we look back on our whitelist or blacklist, we can recall what was the reason the person was whitelisted or blacklisted.
Yes, I know there are browser extension out there that can do just that. But if a feature is good enough that SHOULD be implemented as an official feature, why rely on add-ons?
Comment has been collapsed.