1,475 karma · joined May 8, 2011
October 27th - 29th: Database compromised according to MongoHQ.
22:15 PST 10/31: Notified of breach by MongoHQ
23:30 PST 10/31: Communicated breach to customers
And I thought all impacted MongoHQ customers knew what had happened on October 27th or 28th itself.
Is it open-source, and you need a license to run it behind a firewall?
Now if I talk to couple of friends at digital marketing agencies, they would tell me this is pretty common. The client doesn't need to know or decide how it's done. It's just done.
I have used the same theme in my personal blog, and I occasionally notice the main and posts page turning up blank when I myself visit it. Doesn't happen if I switch to another theme.
These apps had full access permissions to Phone Logs, SD Card, and Network Communications. Users were forced to provide a rating for the apps before the app "allowed" them to login and then crashed.
A related article here: http://trak.in/tags/business/2013/09/21/fake-bbm-apps-fools-...
Since when?
For an article that focuses on GitHub, the distinction between "git", "GitHub" and "majority of the projects hosted at GitHub" must be pretty clear.
1. Install the add-on.
2. Panic that it has deleted all "not open now" websites' cookies.
3. Choose the option to "Suspend Operation" via the add-on icon.
4. Repeatedly "Undelete" all cookies until it's all done.
5. Keep the add-on suspended.
6. Now, for the next few days, I will browse like normal, but will remember to "whitelist" the websites I like to stay logged-in (Hacker News, Webmail, etc.) by clicking on the add-on icon. Remember, it is still "Suspended".
7. After a few days of usage (and when I've re-visited enough number of my regular websites), I will "Resume Operation" on the add-on, where it can start destroying the rest of the cookies like anything.
I think the "Training Period" above in point 6 should have been by default. Somehow.
Wouldn't that allow all the Adwords tracking cookies as well, across sites?
Upon the first run, without warning, I see this: "If you read this, all of your cookies that are not currently in use just self-destructed. Don't panic. You can undo this if you prefer to keep them for now." . . . "Undeletes happen in batches. If you had a lot of cookies, you might need to restore more batches. Click SDC's icon again. Select Undelete (more) cookies from the menu. Repeat this until you get a notification stating that No more undeletes are possible."
Couldn't the extension have simply asked me once before proceeding with the delete in the first run? Basic usability.
The Google Ads also help them keep a track of where the person has been around the web and also acts as a proxy site stats data for Google (irrespective of whether you use Google Analytics or not).
It won't. They are mailing to hisdomain.tld ; probably support@hisdomain.tld
We ended up installing Stash as it seemed that it would reduce administration+maintenance by a tad bit (GUI + knowledgebase) and would be supported by a company responsible for bitbucket. Stash has been a pleasant experience so far.
This is an understatement. There's no reason for them not to do it - it's fodder for them.
You would be surprised what non-geeks tend to do when they have no clue what to do.