Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Post History

50%
+0 −0
Q&A Please gray out the usernames of automatically-imported accounts on the main Users listing

This was originally intended as comment on ArtOfCode's answer, but got too long for that. Listing a name on the site's Users page IMHO very clearly claims that person is a user of the site. Note t...

posted 4y ago by celtschk‭  ·  edited 4y ago by celtschk‭

Answer
#2: Post edited by user avatar celtschk‭ · 2020-02-23T07:39:52Z (over 4 years ago)
  • *This was originally intended as comment on ArtOfCode's answer, but got too long for that.*
  • Listing a name on the site's Users page IMHO very clearly claims that person is a user of the site. Note that this is *not* about the name displayed under imported posts (those are marked anyway), but about the user listing.
  • And while I don't know the code base, I can't imagine it being *that* difficult. After all, the information is there, or else you couldn't display it on the individual user's page nor support claiming of the posts.
  • If the information is there, but not very accessible right now, the solution should be simple:
  • 1. Add a new column “is_imported_user” to the users table, which defaults to false. Set it to NULL for all existing users. Do not yet act on that field (that is, the field exists in the database, but QPixel ignores it). Making it default to false means that newly created users automatically get the right status, without touching the QPixel code.
  • 2. Run a background process that looks for NULL entries in that column of the user table, checks for each such user whether it is an imported user, and sets the column accordingly. It doesn't matter if this process is slow (it will certainly have low priority so that it doesn't impede normal use). Maybe it will finish in a week, maybe in a month. Since during that time, nothing visible changes, it doesn't matter too much.
  • 3. After the process finished, you've got a simple boolean field in the user table that you can act on. Therefore now you can grey out the corresponding users with minimal effort and very little runtime cost. Note that from now on, the background process is no longer needed.
  • *This was originally intended as comment on ArtOfCode's answer, but got too long for that.*
  • Listing a name on the site's Users page IMHO very clearly claims that person is a user of the site. Note that this is *not* about the name displayed under imported posts (those are marked anyway), but about the user listing.
  • And while I don't know the code base, I can't imagine it being *that* difficult. After all, the information is there, or else you couldn't display it on the individual user's page nor support claiming of the posts.
  • If the information is there, but not very accessible right now, the solution should be simple:
  • 1. Add a new column “`is_imported_user`” to the users table, which defaults to false. Set it to NULL for all existing users. Do not yet act on that field (that is, the field exists in the database, but QPixel ignores it). Making it default to false means that newly created users automatically get the right status, without touching the QPixel code.
  • 2. Run a background process that looks for NULL entries in that column of the user table, checks for each such user whether it is an imported user, and sets the column accordingly. It doesn't matter if this process is slow (it will certainly have low priority so that it doesn't impede normal use). Maybe it will finish in a week, maybe in a month. Since during that time, nothing visible changes, it doesn't matter too much.
  • 3. After the process finished, you've got a simple boolean field in the user table that you can act on. Therefore now you can grey out the corresponding users with minimal effort and very little runtime cost. Note that from now on, the background process is no longer needed.
#1: Initial revision by user avatar celtschk‭ · 2020-02-23T07:38:56Z (over 4 years ago)
*This was originally intended as comment on ArtOfCode's answer, but got too long for that.*

Listing a name on the site's Users page IMHO very clearly claims that person is a user of the site. Note that this is *not* about the name displayed under imported posts (those are marked anyway), but about the user listing.

And while I don't know the code base, I can't imagine it being *that* difficult. After all, the information is there, or else you couldn't display it on the individual user's page nor support claiming of the posts.

If the information is there, but not very accessible right now, the solution should be simple:

 1. Add a new column “is_imported_user” to the users table, which defaults to false. Set it to NULL for all existing users. Do not yet act on that field (that is, the field exists in the database, but QPixel ignores it). Making it default to false means that newly created users automatically get the right status, without touching the QPixel code.

 2. Run a background process that looks for NULL entries in that column of the user table, checks for each such user whether it is an imported user, and sets the column accordingly. It doesn't matter if this process is slow (it will certainly have low priority so that it doesn't impede normal use). Maybe it will finish in a week, maybe in a month. Since during that time, nothing visible changes, it doesn't matter too much.

 3. After the process finished, you've got a simple boolean field in the user table that you can act on. Therefore now you can grey out the corresponding users with minimal effort and very little runtime cost. Note that from now on, the background process is no longer needed.