https://www.cyberwarnews.info/2018/01/01/website-dumps-files-from-gottfrid-svartholm-co-owner-of-torrent-site-the-pirate-bay/

Website dumps files from Gottfrid Svartholm, co-owner of torrent site The Pirate Bay

Lee Johnstone1 January 2018

A user on a deepweb forum has posted a thread that lays claim to a leak of data on The Pirate Bay co-owner Gottfrid Svartholm Aka Anakata.

The user has posted a short message and a link to file hosting site mega.co.nz that contains a 3gb zip file. After downloading and doing a quick check over the data it contains 1,903 Files, 291 Folders with a total size of 3.62gb.

The main folder has a mod date of 18/9/2017 but the main files have dates of 30/7/2013. The data within the leak appears to be a full backup of a personal device owned or operated by Gottfrid, with many of the files being personal including images, work and stuff like 'The Ultimate Fake ID Guide 2010 Version 7', you can see a full list of files here.

For now thats it, its new years day.
Enjoy 2018.

Information Security Data Analyst, Investigative Journalist, Technology Lover, Mechanic.

Read More

Elyssa D. Durant 

Research & Policy Analyst

Columbia University, New York

1-15 August 2018 Cyber Attacks Timeline – HACKMAGEDDON

https://www.hackmageddon.com/2018/09/12/1-15-august-2018-cyber-attacks-timeline/

1-15 August 2018 Cyber Attacks Timeline

Paolo PasseriSeptember 12, 2018

Altex Exchange, AT&T, August, Cosmos Bank, Cyber Attack Timeline, Instagram, Livecoin, Michael Terpin, Monero, PGA, Reddit

I am trying to catch up with the delayed timelines, so I am happy to publish the first timeline of August, covering the main cyber attacks occurred in the first half of this month.

Well, it looks like the cyber criminals decided to take same days off, since the number of events collected in this fortnight is sensibly smaller than the second half of July (31 vs. 81).

And the winner is… Cosmos Bank, which had 944 million rupees ($13.5 million worth) stolen through simultaneous withdrawals across 28 countries. And if we move from fiat currency to cryptocurrency, the situation does not improve unfortunately. Well, technically the amount in Monero stolen to Livecoin is "only" equivalent to $ 1.8 million, however it might seem tiny compared to Cosmos Bank, but it's always a decent amount of money. Nothing in comparison to the $240 million lost by an investor, Michael Terpin, who sued AT&T consequently. Livecoin wasn't the only exchange targeted, even Altex Exchange suffered the loss of an undisclosed amount, probably for the same vulnerability.

Other Interesting events include the hack to Reddit (SMS-based authentication is not enough any longer), a massive attack to Instagram users, and I would also mention that ransomware has not mercy since it did not spare the computers of the Professional Golf Association.

But the least doesn't end here! My advice is to read it all and realize the fragility of our identity inside the cyber space. And id you want, you may also have a look at the timelines of the main Cyber Attacks in 2011, 2012, 2013, 2014, 2015, 2016, 2017 and now 2018 (regularly updated… Hopefully!). And do not forget the Cyber Attack Statistics that are regularly published, and follow @paulsparrows on Twitter for the latest updates.

Last but not least, feel free to submit remarkable incidents that in your opinion deserve to be included in the timelines (and charts), and please notice that, starting from this month, it is possible to download the raw data directly from the tools above the table. You may always ask for the raw data, but please do not forget to include a short presentation and the purpose of the project. I am not supposed to accept requests without any details.

Search:

ID	Date	Author	Target	Description	Attack	Target Class	Attack Class	Country	Link
1	20/07/2018	?	MedSpring Urgent Care	MedSpring Urgent Care notifies 13,000 patients after a phishing attack occurred on May 8.	Account Hijacking	Q Human health and social work activities	CC	US
2	30/07/2018	?	Altex Exchange	Altex Exchange acknowledges that a double-counting bug in Monero (XMR) cryptocurrency did result in a major undisclosed financial loss.	Monero Vulnerability	V Fintech	CC	N/A
3	01/08/2018	?	Reddit	Reddit discloses a breach of its systems that compromised user data including some current email addresses and salted and hashed passwords from a 2007 database backup. The attacker gained access to several employee accounts via SMS intercept between June	Account Hijacking	J Information and communication	CC	US
4	01/08/2018	?	Companies and organizations associated with industrial production	Kaspersky Lab ICS CERT identifies a new wave of phishing emails with malicious attachments targeting primarily companies and organizations associated with industrial production. The malware used in these attacks installs legitimate remote administration s	Malware	Y Multiple Industries	CC	>1
5	01/08/2018	?	Amnesty International	Amnesty International reveals to have been targeted by a campaign carried out via the surveillance malware developed by the Israel surveillance vendor, NSO Group.	Targeted Attack	U Activities of extraterritorial organizations and bodies	CE	N/A
6	01/08/2018	booloop	recruitmilitary.com	A user called booloop a publishes a database containing over 850,000 US military officers personal information.	Unknown	S Other service activities	CC	US
7	01/08/2018	?	Hong Kong's Department of Health	Three Hong Kong's Department of Health computers are hit by ransomware.	Malware	O Public administration and defence, compulsory social security	CC	HK
8	02/08/2018	Gorgon	Governmental organizations in the United Kingdom, Spain, Russia, and the United States.	Researchers from Palo Alto Networks Unit 42 uncover Gorgon, a threat actor allegedly operating from Pakistan and targeting governmental organizations in the United Kingdom, Spain, Russia, and the United States leveraging spear phishing emails with Microso	Targeted Attack	O Public administration and defence, compulsory social security	CE	>1
9	02/08/2018	RASPITE	Entities in the US, Middle East, Europe, and East Asia	Researchers from Dragos identify a new activity group targeting access operations in the electric utility sector, called RASPITE.	Targeted Attack	D Electricity gas steam and air conditioning supply	CE	>1
10	02/08/2018	DarkCoder AKA @Th3Falcon	Elbit Systems	DarkCoder AKA @Th3Falcon leaks 10,000 credentials for users and administrators from Elbit Systems.	SQLi	C Manufacturing	CC	IL

Showing 1 to 10 of 31 entries

Elyssa D. Durant 

Research & Policy Analyst

Columbia University, New York

2011 Cyber Attacks Timeline Master Index – HACKMAGEDDON

https://www.hackmageddon.com/2011-cyber-attacks-timeline-master-index/

2011 Cyber Attacks Timeline Master Index

The master index collects all the Cyber Attacks Timeline blog posts for 2011 on a single table, which contains a brief description, an infographic of the timeline and the link to the original article containing references and Hyperlinks.

Follow @paulsparrows on Twitter to get the latest updates on a regular basis, also have a look to the 2012 Cyber Attacks Timeline Master Index.

Date	Description	Original Article	Preview
Jun 22 2011	2011 Cyber Attacks Timeline (Jan-Jun 2011), original chart by Thomson Reuters	2011 CyberAttacks Timeline
Jun 28 2011	2011 Cyber Attacks Timeline (Jan-Jun 2011), enhanced version based on the Thomson Reuters chart	2011 Cyber Attacks (and Cyber Costs) Timeline (Updated)
Aug 2 2011	July 2011 Cyber Attacks Timeline: List of Main Cyber Attacks from 1 to 31 July 2011.	July 2011 Cyber Attacks Timeline
Sep 2 2011	August 2011 Cyber Attacks Timeline. List of Main Cyber Attacks from 1 to 31 August 2011.	August 2011 Cyber Attacks Timeline
Sep 15 2011	September 2011 Cyber Attacks Timeline Part I: list of Main Cyber Attacks from 1 to 15 September 2011.	September 2011 Cyber Attacks Timeline (Part I)
Oct 3  2011	September 2011 Cyber Attacks Timeline Part II: list of Main Cyber Attacks from 16 to 30 September 2011.	September 2011 Cyber Attacks Timeline (Part II)
Oct 20 2011	October 2011 Cyber Attacks Timeline Part I: list of Main Cyber Attacks from 1 to 15 October 2011.	October 2011 Cyber Attacks Timeline (Part I)
Nov 03 2011	October 2011 Cyber Attacks Timeline Part II: list of Main Cyber Attacks from 16 to 31 October 2011.	October 2011 Cyber Attacks Timeline (Part II)
Nov 17 2011	November 2011 Cyber Attacks Timeline Part I: list of Main Cyber Attacks from 1 to 15 November 2011.	November 2011 Cyber Attacks Timeline (Part I)
Dec 6 2011	November 2011 Cyber Attacks Timeline Part II: list of Main Cyber Attacks from 16 to 30 November 2011.	November 2011 Cyber Attacks Timeline (Part II)
Dec 23 2011	December 2011 Cyber Attacks Timeline Part I: list of Main Cyber Attacks from 1 to 15 December 2011.	December 2011 Cyber Attacks Timeline (Part I)
Dec 30 2011	December 2011 Cyber Attacks Timeline Part II: list of Main Cyber Attacks from 16 to 30 December 2011.	December 2011 Cyber Attacks Timeline (Part II)

Related articles

• The China Cyber Attacks Syndrome (paulsparrows.wordpress.com)

Elyssa Durant

AT&T and Verizon want to manage your identity across websites and apps | Ars Technica

https://arstechnica.com/information-technology/2018/09/att-and-verizon-want-to-manage-your-identity-across-websites-and-apps/?utm_source=pocket&utm_medium=email&utm_campaign=pockethits

AT&T and Verizon want to manage your identity across websites and apps

Carriers' "Project Verify" would use your phone as authentication device.

Jon Brodkin - 9/13/2018, 3:31 PM

Enlarge / Project Verify would let you confirm or deny logins for other apps and websites.

Project Verify

The four major US mobile carriers have unveiled a system that would let them manage your logins across any third-party website or app that hooks into it.

"Project Verify" from a consortium of AT&T, Verizon Wireless, T-Mobile US, and Sprint, was unveiled in a demo yesterday. It works similarly to other multi-factor authentication systems by letting users approve or deny login requests from other websites and apps, reducing the number of times users must enter passwords. The carriers' consortium is putting the call out to developers of third-party apps and websites, who can contact the consortium for information on linking to the new authentication system.

"The Project Verify app can be preloaded or downloaded to the user's mobile device," a video describing the technology says. "And then when they face a login screen on their favorite sites and apps, they select the verify option. That's it—Project Verify does the rest."

The carriers hope to launch Verify next year.

Introducing Project Verify.

The carrier system would verify each person's identity with "a multi-factor profile based around the user's personal mobile device," taking into account the user's phone number, account tenure, IP address, phone account type, and SIM card details. The system "combines the carriers' proprietary, network-based authentication capabilities with other methods to verify a user's identity," the carriers say.

Users would be able to log in to Project Verify-linked sites or apps by selecting the verify option within those apps or sites. The Project Verify app would let them manage which sites and apps are linked to their mobile identity.

Is this a good idea?

But do you want your carrier managing your logins across the websites and apps you use on your phone? AT&T, Verizon, T-Mobile, and Sprint aren't exactly the tech industry's best protectors of security and privacy.

The four major carriers were recently caught leaking the real-time location of most US cell phones. After facing pressure from Sen. Ron Wyden (D-Ore.), the carriers agreed to stop selling their mobile customers' location information to third-party data brokers.

The carriers don't face any major rules preventing them from misusing their customers' Web-browsing and app-usage data. Last year, the mobile carriers and other Internet providers convinced Congress and President Trump to prevent implementation of rules that would have forced them to get customers' opt-in consent before using, sharing, or selling their browsing and app-usage histories for advertising purposes.

"I don't trust the carriers"

There are good reasons to be skeptical of the carriers' ability to securely manage logins, security reporter Brian Krebs wrote yesterday.

"A key question about adoption of this fledgling initiative will be how much trust consumers place with the wireless companies, which have struggled mightily over the past several years to validate that their own customers are who they say they are," Krebs wrote. He continued:

All four major mobile providers currently are struggling to protect customers against scams designed to seize control over a target's mobile phone number. In an increasingly common scenario, attackers impersonate the customer over the phone or in mobile retail stores in a bid to get the target's number transferred to a device they control. When successful, these attacks—known as SIM swaps and mobile number port-out scams—allow thieves to intercept one-time authentication codes sent to a customer's mobile device via text message or automated phone call.

AT&T VP Johannes Jaskolski, who is managing the carriers' Project Verify consortium, told Krebs that the system will not centralize subscriber data into a multi-carrier database.

"We're not going to be aggregating and centralizing this subscriber data, which will remain with each carrier separately," Jaskolski said. Verify "will be portable by design and is not designed to keep a subscriber stuck to one specific carrier." It will let the user maintain "control of whatever gets shared with third parties," he added.

But Krebs is still skeptical, and so is security researcher Nicholas Weaver of the International Computer Science Institute at UC Berkeley. Krebs paraphrased Weaver as saying that "this new solution could make mobile phones and their associated numbers even more of an attractive target for cyber thieves."

"The carriers have a dismal track record of authenticating the user," Weaver also said. "If the carriers were trustworthy, I think this would be unequivocally a good idea. The problem is I don't trust the carriers."

Elyssa Durant

9/10/2018

2018-09-10 11:39:30:089 WPAnalytics session started
2018-09-10 11:39:30:169 ===========================================================================
2018-09-10 11:39:30:169 Launching WordPress for iOS 10.7 (10.7.0.3)...
2018-09-10 11:39:30:170 Crash count: 7
2018-09-10 11:39:30:171 Debug mode: Production
2018-09-10 11:39:30:171 Extra debug: YES
2018-09-10 11:39:30:223 Device model: iPad7,6 (iPad7,6)
2018-09-10 11:39:30:223 OS: iOS, 11.4.1
2018-09-10 11:39:30:224 Language: en-US
2018-09-10 11:39:30:224 UDID: 91C0B200-DBE9-4530-A0B9-6B22D35093B5
2018-09-10 11:39:30:257 APN token: 96e23011a780715405b13f238d732e3fc3fd62eebfccf50dd509c42023bad172
2018-09-10 11:39:30:277 Launch options: [__C.UIApplicationLaunchOptionsKey(_rawValue: UIApplicationLaunchOptionsURLSessionKey): group.org.wordpress.C86EDC5A-7675-46DD-B3C2-61681A25E109]
2018-09-10 11:39:30:281 wp.com account: powersthatbeat (ID: 18647202) (verified)
2018-09-10 11:39:30:284 All blogs on device:
2018-09-10 11:39:30:290 <Blog Name: Comcast Must Die URL: https://comcastmustdie.wordpress.com XML-RPC: https://comcastmustdie.wordpress.com/xmlrpc.php wp.com account: powersthatbeat blogId: 148364682 plan: Free (1)>
2018-09-10 11:39:30:291 <Blog Name: PALM BITCH URL: https://palmbitchresist.wordpress.com XML-RPC: https://palmbitchresist.wordpress.com/xmlrpc.php wp.com account: powersthatbeat blogId: 126298627 plan: Free (1)>
2018-09-10 11:39:30:291 <Blog Name: Powers That Beat ©️ 2018 URL: https://powersthatbeat.wordpress.com XML-RPC: https://powersthatbeat.wordpress.com/xmlrpc.php wp.com account: powersthatbeat blogId: 18033618 plan: Free (1)>
2018-09-10 11:39:30:292 <Blog Name: TOS Terms of Silence URL: https://tosthegoodthebadtheugly.wordpress.com XML-RPC: https://tosthegoodthebadtheugly.wordpress.com/xmlrpc.php wp.com account: powersthatbeat blogId: 126146545 plan: Free (1)>
2018-09-10 11:39:30:292 ===========================================================================
2018-09-10 11:39:30:518 Zendesk - read profile from User Defaults: ["name": Penguin, "email": elyssad@outlook.com]
2018-09-10 11:39:30:520 Zendesk Enabled: true
2018-09-10 11:39:30:610 User-Agent set to: Mozilla/5.0 (iPad; CPU OS 11_4_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15G77 wp-iphone/10.7
2018-09-10 11:39:30:894 Loading Stats for the following blog: https://powersthatbeat.wordpress.com
2018-09-10 11:39:30:927 Loading Stats for the following blog: https://powersthatbeat.wordpress.com
2018-09-10 11:39:31:218 🔵 Tracked: notifications_notification_details_opened, properties: {
"notification_type" = "new_post";
}
2018-09-10 11:39:31:534 🔵 Tracked: my_site_tab_accessed
2018-09-10 11:39:31:650 Loading Stats for the following blog: https://powersthatbeat.wordpress.com
2018-09-10 11:39:31:708 Last stats period type: 0
2018-09-10 11:39:31:708 Last stats period type: 0
2018-09-10 11:39:31:933 Last stats period type: 0
2018-09-10 11:39:31:934 Last stats period type: 0
2018-09-10 11:39:32:362 🔵 Tracked: stats_period_accessed, properties: {
"blog_id" = 18033618;
period = days;
}
2018-09-10 11:39:32:371 🔵 Tracked: stats_insights_accessed, properties: {
"blog_id" = 18033618;
}
2018-09-10 11:39:32:609 Device Token received in didRegisterForRemoteNotificationsWithDeviceToken: 96e23011a780715405b13f238d732e3fc3fd62eebfccf50dd509c42023bad172
2018-09-10 11:39:33:450 🔵 Tracked: my_site_tab_accessed
2018-09-10 11:39:33:486 🔵 Tracked: stats_period_accessed, properties: {
"blog_id" = 18033618;
period = days;
}
2018-09-10 11:39:33:496 🔵 Tracked: stats_insights_accessed, properties: {
"blog_id" = 18033618;
}
2018-09-10 11:39:33:641 didFinishLaunchingWithOptions state: 2
2018-09-10 11:39:33:684 Initializing background session: <__NSURLBackgroundSession: 0x1c03c2a30>
2018-09-10 11:39:33:726 Successfully registered Device ID 25965755 for Push Notifications
2018-09-10 11:39:33:899 Shared container media: removed /private/var/mobile/Containers/Shared/AppGroup/D7A5B868-5AF3-4282-B89B-D932838A04AA/Media/image_558286693924044.jpg during cleanup.
2018-09-10 11:39:33:902 Background session task completed. Session:<__NSURLBackgroundSession: 0x1c03c2a30> Task:<__NSCFBackgroundUploadTask: 0x131f37110>{ taskIdentifier: 1 }.
2018-09-10 11:39:44:664 Post 25368 successfully uploaded to site 18033618
2018-09-10 11:39:46:196 Completed processing post and media upload for session group.org.wordpress.C86EDC5A-7675-46DD-B3C2-61681A25E109.
2018-09-10 11:39:46:220 TracksService sendQueuedEvents completed. Sent 8 events.
2018-09-10 11:40:34:646 <WordPressAppDelegate: 0x1c40cdb30> applicationWillEnterForeground:
2018-09-10 11:40:34:663 PingHub connecting
2018-09-10 11:40:34:679 Could not fetch post from share notification.
2018-09-10 11:40:35:023 PingHub connected
2018-09-10 11:40:35:592 <WordPressAppDelegate: 0x1c40cdb30> applicationDidBecomeActive:
2018-09-10 11:40:35:594 🔵 Tracked: application_opened
2018-09-10 11:40:51:303 TracksService sendQueuedEvents completed. Sent 1 events.
2018-09-10 11:40:55:686 🔵 Tracked: activity_log_list_opened
2018-09-10 11:40:57:833 🔵 Tracked: stats_accessed, properties: {
"blog_id" = 18033618;
}
2018-09-10 11:40:57:853 Loading Stats for the following blog: https://powersthatbeat.wordpress.com
2018-09-10 11:40:57:933 Last stats period type: 0
2018-09-10 11:40:57:933 Last stats period type: 0
2018-09-10 11:40:57:949 🔵 Tracked: stats_period_accessed, properties: {
"blog_id" = 18033618;
period = days;
}
2018-09-10 11:40:57:957 🔵 Tracked: stats_insights_accessed, properties: {
"blog_id" = 18033618;
}
2018-09-10 11:41:02:117 🔵 Tracked: stats_period_accessed, properties: {
"blog_id" = 18033618;
period = days;
}
2018-09-10 11:41:06:425 TracksService sendQueuedEvents completed. Sent 5 events.
2018-09-10 11:41:23:304 🔵 Tracked: stats_scrolled_to_bottom, properties: {
"blog_id" = 18033618;
}
2018-09-10 11:41:23:862 TracksService sendQueuedEvents completed. Sent 1 events.
2018-09-10 11:41:26:830 WordPress.WebKitViewController Error Loading [Error Domain=WebKitErrorDomain Code=102 "Frame load interrupted" UserInfo={_WKRecoveryAttempterErrorKey=<WKReloadFrameErrorRecoveryAttempter: 0x1c4a2e720>, NSErrorFailingURLStringKey=https://wordpress.com/?wpios_redirect=http://en.support.wordpress.com/stats/%2523search-engine-terms, NSErrorFailingURLKey=https://wordpress.com/?wpios_redirect=http://en.support.wordpress.com/stats/%2523search-engine-terms, NSLocalizedDescription=Frame load interrupted}]
2018-09-10 11:42:23:875 🔵 Tracked: activity_log_list_opened
2018-09-10 11:42:25:446 TracksService sendQueuedEvents completed. Sent 1 events.
2018-09-10 11:42:56:954 🔵 Tracked: activity_log_detail_opened
2018-09-10 11:43:06:897 🔵 Tracked: activity_log_detail_opened
2018-09-10 11:43:09:626 🔵 Tracked: activity_log_detail_opened
2018-09-10 11:43:10:984 TracksService sendQueuedEvents completed. Sent 3 events.
2018-09-10 11:43:21:013 🔵 Tracked: me_tab_accessed
2018-09-10 11:43:23:687 🔵 Tracked: account_settings_opened
2018-09-10 11:43:25:208 🔵 Tracked: app_settings_opened
2018-09-10 11:43:26:155 TracksService sendQueuedEvents completed. Sent 3 events.
2018-09-10 11:43:27:070 🔵 Tracked: account_settings_opened
2018-09-10 11:43:28:494 🔵 Tracked: app_settings_opened
2018-09-10 11:43:37:349 🔵 Tracked: account_settings_opened
2018-09-10 11:43:38:822 🔵 Tracked: app_settings_opened
2018-09-10 11:43:41:642 TracksService sendQueuedEvents completed. Sent 4 events.
2018-09-10 11:43:43:426 🔵 Tracked: notification_settings_list_opened
2018-09-10 11:43:56:814 URL: wpcom/v2/read/sites/108242590/notification-subscriptions/new/
2018-09-10 11:43:56:912 TracksService sendQueuedEvents completed. Sent 1 events.
2018-09-10 11:43:56:942 Success https://public-api.wordpress.com/wpcom/v2/read/sites/108242590/notification-subscriptions/new/?locale=en
2018-09-10 11:43:56:942 🔵 Tracked: followed_blog_notifications_settings_on
2018-09-10 11:43:56:951 Success turn notifications on
2018-09-10 11:43:58:272 🔵 Tracked: notification_settings_list_opened
2018-09-10 11:44:12:038 TracksService sendQueuedEvents completed. Sent 2 events.
2018-09-10 11:44:20:180 🔵 Tracked: notification_settings_list_opened
2018-09-10 11:44:23:653 URL: wpcom/v2/read/sites/145002780/notification-subscriptions/new/
2018-09-10 11:44:23:883 Success https://public-api.wordpress.com/wpcom/v2/read/sites/145002780/notification-subscriptions/new/?locale=en
2018-09-10 11:44:23:883 🔵 Tracked: followed_blog_notifications_settings_on
2018-09-10 11:44:23:891 Success turn notifications on
2018-09-10 11:44:25:538 URL: rest/v1.2/read/site/145002780/post_email_subscriptions/update/
2018-09-10 11:44:25:987 Success https://public-api.wordpress.com/rest/v1.2/read/site/145002780/post_email_subscriptions/update/?locale=en
2018-09-10 11:44:25:987 Success update frequency instantly
2018-09-10 11:44:25:987 🔵 Tracked: followed_blog_notifications_settings_email_instantly
2018-09-10 11:44:27:167 TracksService sendQueuedEvents completed. Sent 3 events.
2018-09-10 11:44:31:373 🔵 Tracked: notification_settings_list_opened
2018-09-10 11:44:35:913 URL: wpcom/v2/read/sites/148364682/notification-subscriptions/new/
2018-09-10 11:44:36:361 Success https://public-api.wordpress.com/wpcom/v2/read/sites/148364682/notification-subscriptions/new/?locale=en
2018-09-10 11:44:36:361 🔵 Tracked: followed_blog_notifications_settings_on
2018-09-10 11:44:36:370 Success turn notifications on
2018-09-10 11:44:37:529 URL: rest/v1.2/read/site/148364682/comment_email_subscriptions/new/
2018-09-10 11:44:38:158 Success https://public-api.wordpress.com/rest/v1.2/read/site/148364682/comment_email_subscriptions/new/?locale=en
2018-09-10 11:44:38:161 Success turn notifications on
2018-09-10 11:44:38:161 🔵 Tracked: followed_blog_notifications_settings_comments_on
2018-09-10 11:44:39:057 🔵 Tracked: notification_settings_list_opened
2018-09-10 11:44:41:962 URL: wpcom/v2/read/sites/61507328/notification-subscriptions/new/
2018-09-10 11:44:42:123 Success https://public-api.wordpress.com/wpcom/v2/read/sites/61507328/notification-subscriptions/new/?locale=en
2018-09-10 11:44:42:123 🔵 Tracked: followed_blog_notifications_settings_on
2018-09-10 11:44:42:131 Success turn notifications on
2018-09-10 11:44:42:271 TracksService sendQueuedEvents completed. Sent 5 events.
2018-09-10 11:44:43:531 🔵 Tracked: notification_settings_list_opened
2018-09-10 11:44:52:632 URL: wpcom/v2/read/sites/35200408/notification-subscriptions/new/
2018-09-10 11:44:52:800 Success https://public-api.wordpress.com/wpcom/v2/read/sites/35200408/notification-subscriptions/new/?locale=en
2018-09-10 11:44:52:800 🔵 Tracked: followed_blog_notifications_settings_on
2018-09-10 11:44:52:810 Success turn notifications on
2018-09-10 11:44:55:925 🔵 Tracked: notification_settings_list_opened
2018-09-10 11:44:59:515 TracksService sendQueuedEvents completed. Sent 3 events.
2018-09-10 11:45:18:301 URL: wpcom/v2/read/sites/8516690/notification-subscriptions/new/
2018-09-10 11:45:18:452 Success https://public-api.wordpress.com/wpcom/v2/read/sites/8516690/notification-subscriptions/new/?locale=en
2018-09-10 11:45:18:453 🔵 Tracked: followed_blog_notifications_settings_on
2018-09-10 11:45:18:464 Success turn notifications on
2018-09-10 11:45:19:768 🔵 Tracked: notification_settings_list_opened
2018-09-10 11:45:23:660 🔵 Tracked: notification_settings_list_opened
2018-09-10 11:45:29:293 URL: wpcom/v2/read/sites/126298627/notification-subscriptions/new/
2018-09-10 11:45:29:422 Success https://public-api.wordpress.com/wpcom/v2/read/sites/126298627/notification-subscriptions/new/?locale=en
2018-09-10 11:45:29:423 🔵 Tracked: followed_blog_notifications_settings_on
2018-09-10 11:45:29:432 Success turn notifications on
2018-09-10 11:45:29:690 TracksService sendQueuedEvents completed. Sent 4 events.
2018-09-10 11:45:30:677 🔵 Tracked: notification_settings_list_opened
2018-09-10 11:45:37:375 URL: wpcom/v2/read/sites/18033618/notification-subscriptions/new/
2018-09-10 11:45:37:832 Success https://public-api.wordpress.com/wpcom/v2/read/sites/18033618/notification-subscriptions/new/?locale=en
2018-09-10 11:45:37:833 🔵 Tracked: followed_blog_notifications_settings_on
2018-09-10 11:45:37:841 Success turn notifications on
2018-09-10 11:45:40:667 URL: rest/v1.2/read/site/18033618/comment_email_subscriptions/new/
2018-09-10 11:45:41:415 Success https://public-api.wordpress.com/rest/v1.2/read/site/18033618/comment_email_subscriptions/new/?locale=en
2018-09-10 11:45:41:415 Success turn notifications on
2018-09-10 11:45:41:415 🔵 Tracked: followed_blog_notifications_settings_comments_on
2018-09-10 11:45:44:842 TracksService sendQueuedEvents completed. Sent 3 events.
2018-09-10 11:45:45:271 🔵 Tracked: notification_settings_list_opened
2018-09-10 11:45:48:143 URL: wpcom/v2/read/sites/124222175/notification-subscriptions/new/
2018-09-10 11:45:48:313 Success https://public-api.wordpress.com/wpcom/v2/read/sites/124222175/notification-subscriptions/new/?locale=en
2018-09-10 11:45:48:313 🔵 Tracked: followed_blog_notifications_settings_on
2018-09-10 11:45:48:324 Success turn notifications on
2018-09-10 11:46:00:000 TracksService sendQueuedEvents completed. Sent 2 events.
2018-09-10 11:46:19:398 🔵 Tracked: notification_settings_list_opened
2018-09-10 11:46:25:313 URL: wpcom/v2/read/sites/97593290/notification-subscriptions/new/
2018-09-10 11:46:25:486 Success https://public-api.wordpress.com/wpcom/v2/read/sites/97593290/notification-subscriptions/new/?locale=en
2018-09-10 11:46:25:487 🔵 Tracked: followed_blog_notifications_settings_on
2018-09-10 11:46:25:496 Success turn notifications on
2018-09-10 11:46:25:990 🔵 Tracked: notification_settings_list_opened
2018-09-10 11:46:30:142 TracksService sendQueuedEvents completed. Sent 3 events.
2018-09-10 11:46:33:562 URL: wpcom/v2/read/sites/36264918/notification-subscriptions/new/
2018-09-10 11:46:33:723 Success https://public-api.wordpress.com/wpcom/v2/read/sites/36264918/notification-subscriptions/new/?locale=en
2018-09-10 11:46:33:724 🔵 Tracked: followed_blog_notifications_settings_on
2018-09-10 11:46:33:731 Success turn notifications on
2018-09-10 11:46:35:091 🔵 Tracked: notification_settings_list_opened
2018-09-10 11:46:38:956 URL: wpcom/v2/read/sites/126146545/notification-subscriptions/new/
2018-09-10 11:46:39:081 Success https://public-api.wordpress.com/wpcom/v2/read/sites/126146545/notification-subscriptions/new/?locale=en
2018-09-10 11:46:39:081 🔵 Tracked: followed_blog_notifications_settings_on
2018-09-10 11:46:39:091 Success turn notifications on
2018-09-10 11:46:40:575 🔵 Tracked: notification_settings_list_opened
2018-09-10 11:46:45:423 TracksService sendQueuedEvents completed. Sent 4 events.
2018-09-10 11:46:45:811 🔵 Tracked: notification_settings_streams_opened
2018-09-10 11:47:00:572 TracksService sendQueuedEvents completed. Sent 1 events.
2018-09-10 11:47:10:774 🔵 Tracked: notifications_primer_seen, properties: {
location = settings;
}
2018-09-10 11:47:10:783 🔵 Tracked: notification_settings_details_opened
2018-09-10 11:47:15:725 TracksService sendQueuedEvents completed. Sent 2 events.
2018-09-10 11:47:25:227 🔵 Tracked: notification_settings_streams_opened
2018-09-10 11:47:26:494 🔵 Tracked: notification_settings_details_opened
2018-09-10 11:47:28:227 🔵 Tracked: notification_settings_streams_opened
2018-09-10 11:47:29:409 🔵 Tracked: notifications_primer_seen, properties: {
location = settings;
}
2018-09-10 11:47:29:435 🔵 Tracked: notification_settings_details_opened
2018-09-10 11:47:30:890 TracksService sendQueuedEvents completed. Sent 5 events.
2018-09-10 11:47:50:997 🔵 Tracked: notification_settings_streams_opened
2018-09-10 11:47:54:861 🔵 Tracked: app_settings_opened
2018-09-10 11:48:01:107 TracksService sendQueuedEvents completed. Sent 2 events.
2018-09-10 11:48:04:103 🔵 Tracked: notification_settings_list_opened
2018-09-10 11:48:05:183 🔵 Tracked: support_opened
2018-09-10 11:48:05:194 Zendesk - read profile from User Defaults: ["name": Penguin, "email": elyssad@outlook.com]
2018-09-10 11:48:05:195 Zendesk - read profile from User Defaults: ["name": Penguin, "email": elyssad@outlook.com]


Elyssa Durant