> This turned out be caused by a periodic (10/hour) function in our code. The main purpose of this was to refresh our route handlers from an external source. This was implemented by deleting old handlers and adding new ones to the array. Unfortunately, it was also inadvertently adding a static route handler with the same path each time it ran.
I don't understand the need of refreshing route handlers. Could someone explain they needed to do this, and also why from an external source?
We refresh periodically as we dynamically deploy new UI code, which can be accessed at new routes. (/home and /homeV2 for example) This allows us to not have to restart our servers or push out new server code just to serve a new UI at a different (or the same) route.
It sounds to me like some kind of configuration/IT-infrastructure-control issue. I wouldn't be surprised if it relates to some sort of "we want a way to toggle this live without an actual code-push" narrative.
In this case TextSecure has end-to-end encryption, and supposedly even hides metadata when using the push service (which is hosted on Google Push Framework). Feel free to check the source yourself, or take Moxie's word on it, but I think their "track record" is a bit cleaner overall, regardless of the acquisition of WhisperSystems by Twitter.
I also "cloned" a well known python article extraction library (goose) on Github with my own api & new functionality and my repo ended up doing super well (even better than the original).
I don't understand the need of refreshing route handlers. Could someone explain they needed to do this, and also why from an external source?