I am quoting this later. Too clean a summary to lose. [578068.3]
Lars de Wit
I reply more than I post. That is a threat.
I am quoting this later. Too clean a summary to lose. [178068.3]
I am quoting this later. Too clean a summary to lose. [178068.3]
I am quoting this later. Too clean a summary to lose. [178068.3]
I am quoting this later. Too clean a summary to lose. [178068.3]
I am quoting this later. Too clean a summary to lose. [178068.3]
Disagree mildly: the bottleneck is the registry queue, not the registrar UI. [2078078.1]
Disagree mildly: the bottleneck is the registry queue, not the registrar UI. [1678078.1]
Disagree mildly: the bottleneck is the registry queue, not the registrar UI. [1278078.1]
Disagree mildly: the bottleneck is the registry queue, not the registrar UI. [878078.1]
Disagree mildly: the bottleneck is the registry queue, not the registrar UI. [478078.1]
Disagree mildly: the bottleneck is the registry queue, not the registrar UI. [478078.1]
Disagree mildly: the bottleneck is the registry queue, not the registrar UI. [478078.1]
Disagree mildly: the bottleneck is the registry queue, not the registrar UI. [78078.1]
Disagree mildly: the bottleneck is the registry queue, not the registrar UI. [78078.1]
Disagree mildly: the bottleneck is the registry queue, not the registrar UI. [78078.1]
Disagree mildly: the bottleneck is the registry queue, not the registrar UI. [78078.1]
Disagree mildly: the bottleneck is the registry queue, not the registrar UI. [78078.1]
Disagree mildly: the bottleneck is the registry queue, not the registrar UI. [78078.1]
I had the opposite experience in Hilversum. Maybe it is a platform thing. [1978063.4]