Fri, Dec 6
I've used the token method (but feel free to change it if the log method makes more sense!)
Thu, Dec 5
It looks like other extensions use that library and sign the JWT with the $wgSecretKey so I think that should be fine.
Wed, Dec 4
Tue, Dec 3
Mon, Dec 2
Tue, Nov 26
Looking at the mocks: https://prtksxna.github.io/wmf-cu-prototype/
Fri, Nov 22
Thu, Nov 21
It seems like we should:
- extend TablePager
- implement getQueryInfo() (to specify the initial query)
- implement preprocessResults() (to attach the additional data to each row)
- implement getFieldNames() (to ensure the field names are what we want to display)
Wed, Nov 20
or rather, the problem does not exist on he, it only exists on en.
Tue, Nov 19
Mon, Nov 18
I've created T238603: Placeholder text on Special:Investigate seems unnecessary as a follow up to my concern in T237034#5672654
@Prtksxna This seems really busy to me...
the placeholder text seems unnecessary.... do we even need it at all?
This is driving me bonkers... for me it seems to happen on Firefox, but not Chrome
Sun, Nov 17
Sat, Nov 16
Fri, Nov 15
I ran this query on eswiki:
SELECT TO_SECONDS(MAX(cul_timestamp)) - TO_SECONDS(MIN(cul_timestamp)) AS duration FROM cu_log WHERE STR_TO_DATE(cul_timestamp, '%Y%m%d%H%i%S') > DATE_SUB(NOW(), INTERVAL 1 YEAR) GROUP BY cul_user, cul_reason HAVING COUNT(cul_id) > 1 ORDER BY cul_timestamp
I could create a graph as you suggested earlier, that might reveal more insights.
Thu, Nov 14
Re-opening to give opportunity for QA.