Gregory's Server
@vala @lebronjames75 yeah, I know about this, I suspect it was about it, but did the "some dude actually noticed because it was 0.5s longer than usual" actually happen? Is there a post somewhere?
|
4 comments
@coolboymew @lebronjames75 i thought i read up on someone in the field's writeup about the timeline with some screenshots and links to the github issue tracker but the issue tracker went offline when github just scrubbed the library from existence as damage control
0
0
2 April at 20:13 | Open on shitposter.world
 @vala @coolboymew @lebronjames75 Sorry, made a mistake, it was actually a 508ms performance impact in testing.
|