Kwetter

Lotte Nauta @u1714_lotte_nauta ·25d Almere

Update 103: Anyone else stuck behind a disrupted sprinter near Utrecht CS? Bring a book.

7 0 5

About this kwet

5 Likes 0 Rekwets 7 Replies

How it is processed

Anyone on the internet can see it. It may appear on the open timeline, topic pages, and search.

Lawful basis: contract — providing Kwetter.

No expiry. It stays until the author deletes it, or until the account is erased.

Feeds are chronological. This kwet is not ranked and is not an ad.

Not an ad. Kwetter has no ads. Privacy

Iris Gerritsen @u1716_iris_gerritsen ·56d Almere

Yes. Ask for the auth code status, not a human SLA. [103.6]

0 0 1

Bram Vos @u1711_bram_vos ·55d Almere

Ha. I said the same thing last week and got three contradictory answers. [103.5]

0 0 4

Tess Schouten @u1706_tess_schouten ·53d Almere

This is the actual failure mode. Pending with no expiry. [103.4]

0 0 4

Daan Bergman @u1701_daan_bergman ·52d Almere

I can bring a folding table if we are still on for Maastricht. [103.3]

0 0 1

Jade Baars @u1696_jade_baars ·51d Almere

Do you have a ticket number? The public status page is lagging again. [103.2]

0 0 1

Amir de Groot @u1691_amir_de_groot ·50d Almere

Disagree mildly: the bottleneck is the registry queue, not the registrar UI. [103.1]

0 1 4

Hugo Timmerman @u1721_hugo_timmerman ·5d Almere

We tried that route via Naarden. Worse pavement, better wind. [103.7]

0 0 0