Kwetter

Fenna Bos @u574_fenna_bos ·24d

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

Saar Brouwer @u576_saar_brouwer ·55d

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

0 0 7

Hugo Timmerman @u571_hugo_timmerman ·54d

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

0 0 8

Iris Gerritsen @u566_iris_gerritsen ·53d

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

0 0 7

Bram Vos @u561_bram_vos ·51d

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

0 0 1

Tess Schouten @u556_tess_schouten ·50d

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

0 0 5

Daan Bergman @u551_daan_bergman ·49d

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

0 0 4

Sven Dekker @u581_sven_dekker ·4d

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

0 0 4