The document outlines a plan for developing a Rails app in one month to facilitate curated conversations on social media, specifically using Twitter's advanced search capabilities. It details the app's features, including polling, real-time tweet streaming, and sentiment analysis, while emphasizing ease of design and development. The author provides insights on utilizing various gems and APIs, hosting on Heroku, and encourages collaboration for further project involvement.

1. Idea 2 app in 1 monthA birds eye view of rails app development to cut corners, save time, save money and have fun

2. Before

3. After

4. An ideaIdeas are worth nothingDevelopment & Marketing take timeOriginal, simple ideas in 1 Month

5. The problem“Its hard to follow and join inconversation round a given topic with social media. Many people don’t get twitter”

6. The solution“Use advanced search to curate simple, useful conversationsaround popular topics.”Find the interesting stuff easily

7. Design firstI’m not a designer

8. Easy to build

9. Simple to understand

10. Min input for max useful outputMock it up

11. The designAlso radio, confs, news, brands…

12. Chat room style2 pages, 1 click.

13. Twitter Search – Poll vs StreamTwitter to do clever stuff

14. Fast flow of relevant tweets

15. Quick development

16. Cheap to hostPolling+ Super simple REST api+ Powerful query language+ No authenticationVariable unpublished rate limits

17. Result speed can varyPolling CodePowerful Queriesiprug OR from:iprug OR “ipswich ruby” OR ruby near:ipswich -weddingSIMPLE APIhttp://search.twitter.com/search.json?q=QUERY&result_type=recent&rpp=100&lang=en

18. Streaming+ Near real-time access+ Simple REST api+ Keyword filters+ AND and ORNo phrases or NOT

19. Hogs workers/processes

20. Not well suited to Heroku architectureStreaming CodeTracking keywordstrack=iprug, ipswich rubySIMPLE APIhttp://stream.twitter.com/1/statuses/filter.json?track=iprug,ipswichruby-uYOUR_TWITTER_USERNAME:YOUR_PASSWORD

21. Streaming In RubyThere’s a gem for thatgem install tweetstreamBuilt IN DAEmonizATIONTweetStream::Daemon.new(’usr','pwd') .track('term1’, 'term2') do |status| puts "#{status.text}" end

23. Lazy Twitter SolutionSimplest: CURB the basic rest apigem install curbstatus = Timeout::timeout(timeout) dor = Curl::Easy.perform(url) do |c| c.headers["User-Agent"] = ”TB/1.1”end response = r.body_strend

24. Lots of DB WritesOptimize importgem install ’activerecord-import’ tweets = []raw_tweet = grab_tweets()raw_tweet.times do |t| tweets << Tweet.new(to_fields(raw_tweet))endTweet.import tweets

25. Twitter API Quirks- JSON and XML have different data- With Heroku must set a user-agent- Speed Varies- Query Complexity limits- Unpredictable rate limits

27. Twitter Sentiment AnalysisBayesian Classification with Classifier gem+ Interesting for age, mood, personality type- Not so good for sentiment on objectrequire 'classifier’b = Classifier::Bayes.new ’positive', ’negative’b.train_positive ”I <3 my iPhone”b.train_negative ”iPhone can’t make calls #fail”b.classify ”iPhone is a rip off #fail" # returns ’negative'

28. Twitter Sentiment AnalysisNatural Language Processing with Ruby LinguisticsFind the direct object of the sentence => “dog”"he is a big dog".en.sentence.object.to_sFind the infinitive verb form of the sentence => “be”"he is a big dog".en.sentence.verb.infinitive

29. Twitter Sentiment AnalysisCombination of the 2 seems to be successful for some people.

30. Seems complicated

31. No I’m too lazy

32. Cheat: Tweetfeel APIhttp://svc.webservius.com/v1/tweetFeel/tfapi?type=all&wsvKey=mykey&keyword=iprug

34. Extracting Interesting StuffI <3 rubular & regex

35. Detect mentions

36. Detect links

37. Resolve linksf.match(/@[a-zA-Z0-9_]+/)starts_with?('http:')http://api.longurl.org/v2/expand?url=http%3A%2F%2Fis.gd%2Fw&title=1

39. Extracting Video & ImagesKnown video sites youtube, vimeo, livestream

40. Known image sites yfrog, twitpic, intagram etc

41. Get thumbnails don’t make your own #lazyclass TwitpicResolver < ImageResolver SEARCH_SNIPPET = "twitpic" URL = "http://twitpic.com/show/[size]/[id]" THUMB = "thumb" LARGE = "large" ID_EXTRACTOR = /twitpic\.com\/(.*)/end

42. UI StuffSASS & Blueprint = Compass

43. SASS is awesome, nesting, variables, mixins

44. SCSS default SASS syntax now

45. HAML

46. CSS cropping = No imagemagikfaff

47. Highcharts.js (not free)Lazy Adminhttp://ruby-toolbox.com/

48. activescaffold

49. Typus is the laziest - search - authentication - paperclip - configure forms via yaml file

51. Lazy Hosting = Herokugit push heroku master

52. Periodic Workers = Herokuheroku rake tweet:eatnamespace :tweet dodesc "kick off background jobs” task :eat => :environment do require 'workers'Delayed::Job.enqueue(TwitterJob.new()Delayed::Job.enqueue(TwitteratiJob.new())Delayed::Job.enqueue(ExtracterJob.new())Delayed::Job.enqueue(Sentiment.new()) endend

53. Workers Cont…Delayed::Job.enqueueTwitterJob(), :run_at => 10.seconds.from_nowgem install delayed_job_adminHeroku rake jobs:clear

54. Heroku not that cheap Shared database 20GB $15

55. 1 Worker $36

56. 1 Dyno = Free

57. Minimum of $56

58. Will need at least 2 workers and 2 Dynos and soon I’ll need more storage too The Pragmatic/Lazy WayReuse, reuse, reuse

59. 3rd party libraries (highchart, typus, nokogiri)

60. 3rd party api’s (tweetfeel, longurl)

61. Keep looking for an easier way

62. Simple design

63. Let someone else worry about hostingThe Missing Twitter APICase sensitive search

64. Term extraction (Zemanta, YQL)

65. User age, gender, interests

66. Potty mouth

67. Traveller?Did I do it in 1 month?Well kind of…

68. Live on Heroku eating tweets

69. http://falling-galaxy-55.heroku.com/

70. Time consuming adding data

71. Some conversations work great, some don’t

72. Need a bit more filtering cleverness

73. Target is a great way of following SXSW

74. Then onto rating brands, products, mobile…AdvertsGo to talkbackhq.com (next week) 

75. Interested in getting involved?

76. Suffolk Twestival @twestuffolk. Evening of Thu 24th March @ Brewery Tap