@jws Wasn't sure of your email, so PM'd on ADN.
// @matigo
@matigo They sent me a screenshot, so it was definitely real. :( Was a desktop browser of some sort. I'll email you the email to send a new account to as a workaround.
// @jws
@matigo Someone I invited is getting an "invalid API endpoint" error when submitting the beta form. :(
@matigo Strikethrough the used ones for now? Or prefix "redeemed:" rather than having it on a separate column?
If you make the code a link to the redeem page so I can copy paste directly (no assembly required), my invite sending time would be notably reduced on mobile. :)
// @jws
@matigo I can't see whether or not an invite code has been used on my phone. Even in landscape, the code is too long, and pushes the right side of the table off the screen.
@JeremyCherfas It does, but needs the part where the analogy is grounded in that scenario. And it's leaky and half-wrong, as analogies tend to be. :(
// @phoneboy @streakmachine @jws @kdfrawg
@konrad There is a lot of non-web software, though. And that often has more than enough resources to go around. (And humans are SLOW!)
// @matigo @jws
@JeremyCherfas IP address: Somewhere you can deliver mail.
MAC: A specific mail slot.
NAT: Things are sent to Jim @ Huge University. Huge University's mailroom translates that into an internal mailstop and forwards it along internally. When Jim sends mail, it gets sent as from Jim @ Huge University, and responses go back there. Jim's mailstop is known only to the Uni.
// @phoneboy @streakmachine @kdfrawg
@konrad Likely because it's fast enough till, suddenly, it isn't. If you work on small datasets or don't have a huge workload, you might never run into the isn't in practice. Even mobile devices have gotten quite snappy and powerful these days.
// @matigo
@matigo ^[ is good enough for anyone.
More seriously, I have Ctrl rigged up to treat a tap as Esc, and just whack it with my left palm as needed while staying on the home row. Works a charm!
// @peemee