How Mining the Social Web Addresses Changes in Social Media APIs and Data Access

Mining the Social Web is a technical manual about data mining techniques for social platforms, and its site documents how the project was rebooted for a rapidly changing world. According to the site's own account, the third edition overhaul was driven less by routine code maintenance than by a wave of platform restrictions: after the Cambridge Analytica scandal and major data breaches, "APIs were changed. Access to data was severely curtailed. Certain privileges required approval from the platform's developers." The site is therefore useful if you want to understand why social data mining examples age quickly — not as a source of current API credentials or access guarantees.

What the reboot actually involved

The site's post "Rebooting Mining the Social Web for a Rapidly Changing World" (January 27, 2019) describes the project's origin and scope. Co-author Mikhail Klassen recounts being brought in after PyCon 2016 to join Matthew Russell in overhauling the book for a third edition.

The initial plan was narrower than what the project became:

• Modernize the code to Python 3
• Test everything to make sure the code still ran

Klassen notes he had prior data mining experience with Twitter, so the scope "didn't sound too difficult." The project then took "some interesting turns" as the platform environment shifted underneath it.

Why API changes reshaped the book

The site frames the problem as a collision between two timelines: technology moves faster than the publishing cycle, and social platforms move faster still. The sequence described is:

1. 2016 onward — social media comes under much more scrutiny following Cambridge Analytica and major data breaches.
2. Platforms go on the defensive — all the major platforms tightened their posture toward third-party data access.
3. Concrete consequences — APIs changed, data access was severely curtailed, and certain privileges now required approval from the platform's developers.
4. Effect on the book — the manual "was full of examples designed to teach data mining techniques and provide the reader with tools for building interesting applications," and suddenly a lot of that code no longer worked as written.

This is the key mechanism to understand: the book teaches techniques, but the runnable examples depend on platform permissions that the platforms themselves can revoke or gate. When access rules change, the teaching material has to be re-verified rather than assumed to work.

What the site covers beyond the book

The site is organized around a blog, a Quick Start, and an About page, with posts including:

• "How To Mine Your GMail with Google Takeout and MongoDB"
• "Twitter Data Mining Round Up"
• "Blog Posts"

The GMail post is a useful illustration of the site's general approach: when direct API access is constrained, use an export mechanism (Google Takeout) plus a local database (MongoDB) to work with your own data instead. That pattern — substitute a user-controlled export for a restricted live API — is the practical answer the site models for a world of curtailed access.

What this means if you're deciding whether to use it

The site does not state pricing or login requirements for the book or its content, so treat access terms as something to confirm at the source rather than assume.

The takeaway

Mining the Social Web addresses API and data-access changes by treating them as the central problem of the third edition rather than an edge case: modernizing to Python 3, re-testing examples, and documenting how platform restrictions broke the original approach. If you use it, expect to verify every platform-dependent example against current access rules, and lean on export-based workflows like the GMail/Google Takeout example when live API access isn't available.