Profile cover photo
Profile photo
Jaime Guaman
About
Posts

Post has attachment

Post has attachment

Post has attachment
Hola
Photo
Photo
2015-07-26
2 Photos - View album

Post has attachment
Voy a dejar esto aquí +Marcelo Pinto
Photo

Post has attachment

Post has shared content

Post has shared content
Coming¹ from Android, the chromium team is now experimenting with Web App install banners on Desktop. By simply enabling the flag named "Add to shelf" at chrome://flags/#enable-add-to-shelf in the latest chromium build², you'll be prompted to add a site to your shelf when this one meets the following criteria: it has a web app manifest file, a service worker, it is served over HTTPS and you've visited it twice over two separate days during the course of two weeks. Note that these requirements may evolve in the future. 

Bypassing some user engagement checks is as easy as toggling the eponymous flag at chrome://flags/#bypass-app-banner-engagement-checks. This allows developers to test that other eligibility requirements for showing app banners, such as having a manifest, are met.
Check out https://events.google.com/io2015 for instance.

For info, the icon used in the infobar is a placeholder for now but that's gonna change.
 
¹ https://developers.google.com/web/updates/2015/03/increasing-engagement-with-app-install-banners-in-chrome-for-android ² https://download-chromium.appspot.com/

Source: https://codereview.chromium.org/1161233005
Photo

Post has attachment

Post has attachment
El nuevo administrador de marcadores de Chrome (42)
Photo

Hi
I found that NIA added a new key to the portal info array which is causing to brake the portal info call. a new boolean key at  index 10 was added, I don´t know what it is, but now is as follows:

[0: "p"1: "R"2: -328470463: -701177754: 75: 1006: 87: "http://lh3.ggpht.com/rl_3b4hS03yaQy_ix4qIszejayBFB4jedYmxJlbVLLG5xpNPaYIFgZPZoUHtZ9sWVFqR_Jbd_LCPaGQMr8Y"8: "Ruinas De La Cordillera"9: Array[0]10: false11: Array[4]12: Array[8]13: "Khah"]

to fix portal info, an edit needs to be done to the portal info parser of IITC as this:

(lines 15185,15186,15187)

      mods:      data.result[11].map(parseMod),
      resonators:data.result[12].map(parseResonator),
      owner:     data.result[13]

hope this help to bring offical fix soon.


Also, botguard array now result of an empty array, causing it to brake IITC at launch.

if you need urgently to access IITC place at line 12877 and edit as follows:

if (niantic_params.CURRENT_VERSION === undefined) {

this edit skip the botguard methods array validation.

warning: DO NOT EDIT IITC script if you don´t know at least basic concepts of javascript, do this only if you need to use IITC urgently, if not, wait until official update appears.
Wait while more posts are being loaded