Page MenuHomePhabricator

gu_home_db not being set for newly created users
Open, Needs TriagePublic

Description

Related to T316470: Unable to set gu_home_db for some older users...

Using the same query; select gu_registration from globaluser where gu_home_db IS NULL OR gu_home_db = "";, not long after running the population script, we have new rows that have just been created with no gu_home_db set.

| 20170817144254  |
| 20170817144606  |
| 20190718160719  |
| 20220828142035  |
| 20220828142112  |
| 20220828142113  |
| 20220828142226  |
| 20220828142237  |
| 20220828142239  |
| 20220828142250  |
| 20220828142307  |
| 20220828142313  |
| 20220828142332  |
| 20220828142412  |
| 20220828142421  |
| 20220828142439  |
| 20220828142457  |
| 20220828142511  |
| 20220828142522  |
| 20220828142524  |
| 20220828142525  |
| 20220828142548  |
| 20220828142554  |
| 20220828142628  |
| 20220828142643  |
| 20220828142701  |
| 20220828142711  |
| 20220828142712  |
| 20220828142715  |
| 20220828142726  |
| 20220828142824  |
| 20220828142833  |
| 20220828142843  |
| 20220828142853  |
| 20220828142909  |
| 20220828142948  |
| 20220828142958  |
| 20220828143000  |
| 20220828143002  |
| 20220828143010  |
| 20220828143012  |
| 20220828143018  |
| 20220828143036  |
| 20220828143043  |
| 20220828143058  |
| 20220828143130  |
| 20220828143141  |
| 20220828143143  |
| 20220828143200  |
| 20220828143202  |
| 20220828143220  |
| 20220828143221  |
| 20220828143224  |
| 20220828143247  |
| 20220828143256  |
+-----------------+
1349 rows in set (21.387 sec)

It seems reasonable to set a users gu_home_db to whatever wiki they sign up on

Event Timeline

I'm not sure if I've said this publicly before, but I think that a single "home wiki" as a software concept doesn't make much sense in the modern world. I don't believe the current breakage is intentional, but I'd much rather entirely remove the column than fix it.

I'm not sure if I've said this publicly before, but I think that a single "home wiki" as a software concept doesn't make much sense in the modern world. I don't believe the current breakage is intentional, but I'd much rather entirely remove the column than fix it.

Fair. There's probably some historic assumptions that aren't so relevant now. Might be worth checking with Stewards and others who may use it as an indicator of something else...

Could be worth starting the process of formally deprecating it....

In 2018:

"home wiki" is not a real concept. CentralAuth has the concept of home wiki purely for SUL migration. It is useless, and often wrong. You should not use it for anything.

So...

I'm not sure if I've said this publicly before, but I think that a single "home wiki" as a software concept doesn't make much sense in the modern world. I don't believe the current breakage is intentional, but I'd much rather entirely remove the column than fix it.

I agree... except I've since come to realize that "home wiki" is a reasonable social concept that people end up wanting to use for stats and whatever, and it's probably likely that if we remove it, people will end up implementing their own home wiki algorithms.

I thought there used to be a bug that asked for the ability to choose one's home wiki, I think if we do keep it around that would be worth having.