TWPLY - From Alleged Spammer to Sold on Sitepoint in Less Than 24 Hours
Earlier today, ultra Twitter master Robert Scoble called Twply a spammer. Twply basically takes any “@” reply messages on Twitter and sends them to your email. It's hard for me to call Twply a spammer …
Context & Ripple Effects
Twply's 24-hour flip on the [[a:Sitepoint|Sitepoint marketplace]] is a snapshot of the earliest Twitter ecosystem gold rush: thin wrappers around the platform's data could be built overnight and sold just as fast. The service — forwarding @ replies to email — drew an immediate spam accusation from Robert Scoble, echoing earlier fights over what counts as abuse on the network, from the Twerp Scan blocking tool to the mystery of how Johng77536 gamed Twitter. The episode also previews a longer arc in which Twitter itself reclaims control of its data, later cutting off third parties like Scoopler's firehose access once their uses no longer suited it.
First-order effects
- Twply's founder converts a day-old side project into cash via Sitepoint, proving that even a single-feature Twitter utility has immediate resale value.
- Scoble's public spam label puts reputational pressure on Twply and forces buyers of the listing to weigh whether the tool can survive community backlash.
Second-order effects
- Other micro-app builders see that speed-to-market and a quick flip beat polish, encouraging more low-effort wrappers that compete for the same @-reply and notification use cases.
- Twitter faces growing noise from derivative tools, raising the cost of distinguishing legitimate utilities from spam-like behavior across its ecosystem.
Third-order effects
- If wrapper-flipping keeps scaling, platforms like Twitter are pushed toward formal API terms, rate limits, and access revocation as the only way to police an ecosystem they don't control — a pattern that played out for years afterward.
- The line between 'useful notification layer' and 'spam' becomes a recurring governance problem, settled less by community figures like Scoble and more by the platform itself over time.
The trend: This is an early data point in the lifecycle of platform ecosystems: opportunistic third-party wrappers emerge instantly around any open data stream, forcing the platform to eventually tighten control over who may build on it.