C for me, but A would be the fall back if you didn't wanna kill it. On Jun 10, 6:35 am, satyr <murky.sa...@gmail.com> wrote: > How should "twitter" command behave after the end of basic auth > support (*0)? > Options I can think of are: > > A. Support OAuth (using PIN), albeit being insecure (*1). > B. Support xAuth, if applicable. > C. Abandon the command. > > (*0)http://countdowntooauth.com/ > (*1) As I understand it, there are no ways for a Ubiquity command to > hide the consumer secret.
-- You received this message because you are subscribed to the Google Groups "ubiquity-firefox" group. To post to this group, send email to ubiquity-fire...@googlegroups.com. To unsubscribe from this group, send email to ubiquity-firefox+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/ubiquity-firefox?hl=en.
