I loved XBMC and still use Kodi to this day. Back then, I even proposed and POCed what's now a part of their Add-On system, essentially a fuse-like virtual file system forwarded to Python. Before that, each Add-On had to bring its own UI. This was basically my first OSS contribution and the community was really supportive and welcoming.
"The GUNMAN project had a major impact on the intelligence community as a whole. It brought about a greater understanding of the thinking and operations in a totalitarian society. The community became more aware of the hostile electronic threat against the U.S. As <redacted> explained, "If any other agency such as CIA or the State Department had discovered the bug, this change would not have occurred because they would not have publicized the incident." NSA, however, briefed all levels of government to warn them of the danger. NSA was not out to assess blame; it took the problem-solving approach." (p. 17)
The word "totalitarian" is hyphenated, to make the line justified. Anyone else try to search for the phrase with a Ctrl-F, come up with zero, and jump to the conclusion that the spooks had redacted the document?
I should perhaps look into having my paranoia treated.
Just think: if everybody posted article snippets with no commentary, we could crowdsource the entire article being redundantly posted piecemeal to HN and nobody would need to click through to the article at all.
If it is a chrome extension and is installed via the Chrome Web Store, it can be updated silently in the background if I'm not mistaken. So in theory, wouldn't it be possible to serve Google with a NSL and force them to silently push a modified update to a targeted user that reveals the private key?
Ya, I'd build it myself if I wanted to rely on the security of it. We'd have no way to know if the source is the same in the Chrome Web Store as it is in the open source project sign we can't check the signature.
Here's the technical background: ClickSend consists of an Android App and a Java server. Both register with a Google App Engine backend. If you send a file to the Android App, the Java server opens an HTTP server, generates a random URL for the file and sends this as a push notification (GCM) to your Android device, along with all IP adresses of the server. The client is triggered by the notification and tries to reach the server on all IP adresses and opens the URL. This allows for direct streaming of multimedia content (player App needed) or downloading. The data never passes through our servers, so it only works if server and client are connected to the same network.
We are currently preparing to launch this so all feedback is appreciated.
No comment yet from anyone at Google after nearly 24 hours. This probably breaks every App using the builtin authentication. If anyone knows a workaround, I would appreciate hearing about it!
Are the results any different from the original? Does using an image instead of an iframe have any effects on the results? What are your thoughts on this?
Well, this is not surprising. If you put less content directly on the first page, users have to click on links in order to view the content that is directly accessible in the desktop version, which generates more page views.
