[lkml]   [2014]   [Mar]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC] QR encoding for Oops messages
On Tue, Mar 18, 2014 at 11:49 PM, Matthew Garrett <> wrote:
> 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 to provide the service. Obviously I never
> got around to actually writing the code, so this is great!

That would have worked as well, I guess. I really hope to get this
into shape for it to be accepted.



> --
> Matthew Garrett |

 \ /
  Last update: 2014-03-19 21:41    [W:0.129 / U:20.492 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site