Kwetter

Julian Postma @u4677_julian_postma ·5d Tussen de Vaarten 393

v404702.404702 Anyone else stuck behind a disrupted sprinter near Lelystad? Bring a book.

7 0 0

About this kwet

0 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

Lars Voskuil @u4703_lars_voskuil ·51d Tussen de Vaarten 393

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

0 0 0

Nina Wolters @u4698_nina_wolters ·50d Tussen de Vaarten 393

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

0 0 0

Niels de Vries @u4693_niels_de_vries ·49d Tussen de Vaarten 393

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

0 0 0

Maud Hendriks @u4688_maud_hendriks ·48d Tussen de Vaarten 393

I can bring a folding table if we are still on for Oostvaardersplassen. [404703.3]

0 0 0

Koen de Wit @u4683_koen_de_wit ·46d Tussen de Vaarten 393

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

0 0 0

Liv Veldhuis @u4678_liv_veldhuis ·45d Tussen de Vaarten 393

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

0 0 0

Noor van Dijk @u4708_noor_van_dijk ·21h Tussen de Vaarten 393

We tried that route via Rotterdam Blaak. Worse pavement, better wind. [404703.7]

0 0 0