my phone tried to autocorrect "god speed" to "god died" just now
-
my phone tried to autocorrect "god speed" to "god died" just now
@aeva If AI were to try and take over the world, autocorrect might be a suitable initial vector.
-
@aeva it turns out, actually Waiting for Godot was about Duke Nukem Forever all along
@aeva *it turns out, sometimes the juice is not worth the squeeze
-
undefined oblomov@sociale.network shared this topic
-
@notthatdelta i think i'm using gboard with as much google being creepy turned off as i can muster without turning off the swipe spelling feature. auto correct is not quite the correct term here because the two words have similar swipe patterns
@aeva ahh I see, makes more sense knowing about swipe. I never did figure that out myself, heh.
-
my phone tried to autocorrect "god speed" to "god died" just now
-
my phone tried to autocorrect "god speed" to "god died" just now
@aeva don't do speed, kids
-
my phone tried to autocorrect "god speed" to "god died" just now
@aeva Goddied You! Black Emperor
-
my phone tried to autocorrect "god speed" to "god died" just now
@aeva just now? God died long ago.
-
my phone tried to autocorrect "god speed" to "god died" just now
@aeva too much messaging about dark souls? :3
-
my phone tried to autocorrect "god speed" to "god died" just now
@aeva Autonietzsche.
-
@rygorous it has many contextually dependent mutually contradictory interpretations the way I use it. if we're talking king of kings god it's infinity + 1 speeds per second. if we're talking a god with more of a Waiting For Godot vibe, then perhaps we're on more of an epsilon per second timescale
-