Thorsten Bux

@hgoebl for example on Android I'd expect to get the phone type: Pixel or Nexus 6 or Galaxy S6. These values are part of the user-agent on Android and on...

@hgoebl @serbanghita thanks for your positive response :). Unfortunately, regular expressions are one of my weak spots but if you could point me in the right direction I'm happy to...

@serbanghita sounds good. I've done some research so far and it looks like there is nothing we can do if the client is a Firefox on mobile because the userAgent...

@hgoebl @serbanghita is that the list you are looking for? https://support.google.com/googleplay/answer/1727131?hl=en Also available as google doc https://docs.google.com/spreadsheets/u/1/d/16gXm7mGsXY_wQjTsRJYQVKkIjR8c3v-MAliAiRs0E3c/pub?gid=0&single=true (thanks to @philip-lamb for the links)

@kalwalt great idea. I was thinking about something like that but haven't started yet to look into possible options. Having that includes into jsartoolkit makes total sense to me.

Yes good idea for sure. Two things, 1 yes zip.c is included but I think what we can handle in JS is preferred to using c/wasm code. 2 Browsers might...

> > Yes good idea for sure. > > ok! 😄 > > > Browsers might be handling decompress zipped artifacts automatically. That is one thing to consider before looking...

https://stackoverflow.com/questions/32172704/is-gzip-automatically-decompressed-by-browser

Hi there, how are you. I looked a bit into that today and found that compressing all artifacts (fset, fset3, iset) into one zip won't work as a browser can't...

@carnaux what do you think?