Zeitpunkt Nutzer Delta Tröts TNR Titel Version maxTL So 29.09.2024 00:01:26 2.877 0 386.887 134,5 Toot Café 4.2.12 500 Sa 28.09.2024 00:01:10 2.877 0 386.750 134,4 Toot Café 4.2.12 500 Fr 27.09.2024 00:01:20 2.877 0 386.620 134,4 Toot Café 4.2.12 500 Do 26.09.2024 00:01:08 2.877 0 386.505 134,3 Toot Café 4.2.12 500 Mi 25.09.2024 00:01:11 2.877 0 386.409 134,3 Toot Café 4.2.12 500 Di 24.09.2024 00:00:05 2.877 0 386.276 134,3 Toot Café 4.2.12 500 Mo 23.09.2024 00:01:16 2.877 0 386.186 134,2 Toot Café 4.2.12 500 So 22.09.2024 00:00:59 2.877 0 386.101 134,2 Toot Café 4.2.12 500 Sa 21.09.2024 00:00:11 2.877 0 385.999 134,2 Toot Café 4.2.12 500 Fr 20.09.2024 00:01:16 2.877 0 385.839 134,1 Toot Café 4.2.12 500
Alex Russell (@slightlyoff) · 04/2017 · Tröts: 6.890 · Folger: 7.046
So 29.09.2024 02:40
What sort of data would have cleared the bar? And how should an exception-based policy read? I might write a blog post on this, but the high points would be:
- observable (by measurement or proxy) interaction depth; i.e., how frequently do users or servers update the *same* data across a session?
- falsifiable claims about research into user devices and networks
- P90+ gates for latency across all critical user journeys
- ...which implies having defined what those journeys are
[Öffentlich] Antw.: 0 Wtrl.: 0 Fav.: 1