You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think something weird is going on, unless I'm missing something obvious while looking at the logs.
Overall it seems like the option to include string identifiers is used way more frequently than I would expect, but I'm not sure whether that's user-generated data or bots, and the only way to determine that would be to have UX logs.
Including string identifiers by default is relatively harmless. It's early enough that we can change the option to Exclude string identifiers, set to False by default. Alternatively, we can set the current option to True by default.
The number of searches excluding source strings is also higher than I expect, but I wouldn't touch that (unlike the other, it would restrict the number of results).
The data is particularly fishy when you look at the trend of percentages. Maybe we need to look at the data again, on a busier week (not in the middle of end-of-year holidays).
Logs between 2024-12-09 and 2024-12-29
Total events: 15,446,670
Total searches: 380,486
Include search IDs: 223,546 (58.8%)
Exclude source string: 112,377 (29.54%)
Include rejected translations: 1 (0.0%)
Match case: 1 (0.0%)
Whole words: 3 (0.0%)
Day
Events
Searches
Include IDs
Exclude Source
Include Rejected
Match Case
Whole Words
2024-12-09
601678
26975
14151
10228
0
0
0
2024-12-10
628486
14053
3898
2213
0
0
0
2024-12-11
548421
14312
6584
3192
0
0
0
2024-12-12
526714
13853
5926
2622
0
0
0
2024-12-13
537543
9286
4993
2288
0
0
0
2024-12-14
591097
8854
2707
663
0
0
0
2024-12-15
565133
8293
2996
539
0
0
0
2024-12-16
597035
21817
14523
5171
0
0
0
2024-12-17
1147842
14604
10588
3054
0
0
0
2024-12-18
642743
4493
1711
489
0
0
0
2024-12-19
515669
4214
2116
653
0
0
0
2024-12-20
752621
9716
6671
2661
0
0
0
2024-12-21
1463417
42649
4848
1895
0
0
0
2024-12-22
1243973
10878
8055
4868
0
0
0
2024-12-23
742328
15712
10992
1023
0
0
0
2024-12-24
725259
27390
22369
13591
0
0
0
2024-12-25
784661
31655
18841
13466
0
0
2
2024-12-26
809288
30271
23391
9404
1
1
1
2024-12-27
728427
26820
22519
3523
0
0
0
2024-12-28
618093
19434
14002
11245
0
0
0
2024-12-29
676242
25207
21665
19589
0
0
0
The text was updated successfully, but these errors were encountered:
I think something weird is going on, unless I'm missing something obvious while looking at the logs.
Overall it seems like the option to include string identifiers is used way more frequently than I would expect, but I'm not sure whether that's user-generated data or bots, and the only way to determine that would be to have UX logs.
The script I used is here, with the CSV data for 3 weeks: https://gist.github.com/flodolo/a4b89c2fe6c456de2162be16e24db4be
Including string identifiers by default is relatively harmless. It's early enough that we can change the option to
Exclude string identifiers
, set toFalse
by default. Alternatively, we can set the current option toTrue
by default.The number of searches excluding source strings is also higher than I expect, but I wouldn't touch that (unlike the other, it would restrict the number of results).
The data is particularly fishy when you look at the trend of percentages. Maybe we need to look at the data again, on a busier week (not in the middle of end-of-year holidays).
Logs between 2024-12-09 and 2024-12-29
Total events: 15,446,670
Total searches: 380,486
Include search IDs: 223,546 (58.8%)
Exclude source string: 112,377 (29.54%)
Include rejected translations: 1 (0.0%)
Match case: 1 (0.0%)
Whole words: 3 (0.0%)
The text was updated successfully, but these errors were encountered: