1. 16
  1.  

  2. 4

    Loved the article but I think it oversold it a bit: at least on Android the AI completely broke down and started returning “cannot parse token >” for anything I typed.

    1. 2

      I recall hearing something along the lines of “only patrons can use it on mobile”, possibly related to a problem with the processing cost that they solved with in-browser local storage. I can’t find references to it right now (I caught it when the developer was discussing it on twitter) but that’s probably what you’re experiencing – recommend trying it from a desktop instead.