-
Notifications
You must be signed in to change notification settings - Fork 5
Ingress Planner retirement #17
Comments
I would like to see IngressPlanner survive. It is an incredibly useful tool. I would be interested in taking ownership. Please let me know how you would like to proceed. |
Hello Robert. Please be aware that a few days ago Google changed its auth security checks. It no longer accept requests from an HTML frame It is now impossibile for Intel/IITC inside a frame to perform google authentication. Don't know about facebook auth. This renders the current planner architecture unusable. Everything should be moved into an IITC plugin, requiring a full rewrite of UI. The domain is therefore useless as of now. You are welcome to submit any rewrite to move the planner into a standalone IITC plugin. Upon checking the rewrite as functional I'll gladly transfer the github repo ownership to you |
Well, that's unfortunate. I was hoping it was just due to the expired SSL cert. Is it possible to replace the iFrame with an HTML5 and repair it that way? That would be a simpler fix. |
I don't think. I use inter-frame messaging to send commands and receive information between IITC and the planner. As you can see the SSL cert issue has been resolved but still Google auth does not work... |
OK, I just ran an experiment with but it's the same result. I assume it's a CORS issue. Facebook auth is also disabled. I'll start a new fork and see what I can do about an iitc plugin. Hopefully someone will beat me to it. |
u man thats so sad :/ |
Fellow agents,
I've no longer been an active agent in Ingress since many years ago. I kept doing some occasional Intel support to field agents, but that too ended months ago.
So my involvement with the Ingress "playing" community is almost zero now.
On December 17th, 2020 the ingressplanner.net domain will expire and I will not renew it.
This repository will remain up and public if anybody wants to run its own fork.
I'm also available to transfer the ownership of both the domain and the repository if anybody would be interested in taking up them.
The text was updated successfully, but these errors were encountered: