Messages in this thread | | | Date | Tue, 18 Mar 2014 21:49:09 +0000 | From | Matthew Garrett <> | Subject | Re: [RFC] QR encoding for Oops messages |
| |
On Mon, Mar 17, 2014 at 02:59:47PM -0700, Teodora Baluta wrote:
> As far as decoding is concerned, there are a lot of apps on mobile devices > that decode QR codes (just text mostly). In order to make this work, an > app which also decodes the QR code is needed. I will be working the next > couple of weeks on an Android app which scans the Oops encoding QR and > sends it to a server which keeps track of these Oopses that are sent to > it making a sort of stream of the latest Oopses. Any thoughts on what the best > workflow would be are more than welcomed.
When I was thinking about doing this a while ago, my plan was to simply encode the oops as a URL - that way existing QR reader software would work and there's no need to write a specialised application. I also registered the domain kbu.gs to provide the service. Obviously I never got around to actually writing the code, so this is great!
-- Matthew Garrett | mjg59@srcf.ucam.org
| |