Problem/Motivation
US National security
Proposed resolution
Let the US government easily access data managed within Drupal
Remaining tasks
Develop secret API and alienate any "foreign" user
User interface changes
Any change should be invisible to the user
API changes
Replace Symfony routing component with NSA routing component
Related Issues
Privacy in a global community
Comments
| Component: | routing system | » base system |
C'mon, let's be honest here. A back door is not just limited to the routing system.
I would like to suggest a "Push puppet purchase" feature (PPP in short, as we can't just give away the feature's internals to anyone!), which will allow the NSA to have one of their puppet companies purchase other companies, in case those won't willingly give up their user's data themselves. This feature was already implemented for Microsoft's takeover of Skype, but it was thought to be needed only once, so the code underperforms and is hardly documented. As I expect the NSA to need this increasingly often in the near feature, it would greatly reduce their workload if we build a well-documented API for them. It would also make Drupal their platform of choice over competitors such as Wordspy™ and Priva3™.
Bumping to major, as my uncle, who is a senator and close friends with Obama, promised me a promotion when I get this done.
| Status: | Active | » Closed (fixed) |
This has been provided in Drupal core since the 1.0 release. I realize the API hasn't been very stable, but why would we let backward compatibility or the plight of our users hold us back?
| Status: | Closed (fixed) | » Closed (won't fix) |
Apparently my sense of humor doesn't extend to destruction of the Constitution. :)
| Status: | Closed (won't fix) | » Closed (fixed) |
Can we at least make bad judgement a requirement for the NSA to use this feature?
Comment #1
Anonymous (not verified) commented
yes, let's get this in so we can backport to all D7 sites, like whitehouse.gov.