12. «Why?» and «For what?»
in details
http://www.slideshare.net/sharifulin/ss-12313103
13. A powerful reason
for me
I was moving from LiveJournal to Posterous,
used transfer scripts and changed Twitter and Facebook
crossposting settings when started to get replies like
'Tolya! Stop it! Enough!'
14. Current analogues
are nice... not!
Slow, awkward, plain, trouble working:
TwitWipe, TwitCide, Delete My Tweets, ...
20. Little experience:
• Getting user profiles after login through
Twitter on websites
• Auto-posting to Twitter with
Net::Twitter(::Lite)
• AnyEvent::Twitter::Stream for real-time
search (hey, @miyagawa!)
48. Too risky to test on
your own account :-)
— You don't care about you Twitter acc, do you?
— Yep!
— So I can delete all your tweets?
— Nooooooooooooooo!!!
49. Simple
debug reguests
To check the quality of client work requests/responses
with before_dispatch + after_dispatch may be used
78. Positive
• Easy solution using pure Perl
(work time is about 30 hours)
• Works fast, really fast
• Right delete tweets
• Any changes, updates, new services
— everything's on the server, no hard
• Real-time statistics
79. Only one negative:
Server's down — the app doesn't work,
users become mad, low rates and spell curses :-)