Tweets

1. » 19 Feb '13, 6pm

   [link] was hacked, interrupting Heroku services and putting sites using Rails at risk | [link]
2. » 04 Feb '13, 3pm

   RT @mattwritescode: Looks like the PHP community has been at it again [link] [link]
3. » 04 Feb '13, 2pm

   Looks like the PHP community has been at it again [link] [link]
4. » 03 Feb '13, 7am

   Can this RubyGems thing also happen with Maven? [link]
5. » 03 Feb '13, 1am

   RT @matsuu: そういえばちゃんと確認してなかった、[link]がヤラれた件 / “[link] hacked, interrupting Heroku services and p…” [link]
6. » 03 Feb '13, 12am

   そういえばちゃんと確認してなかった、[link]がヤラれた件 / “[link] hacked, interrupting Heroku services and p…” [link]
7. @JeremyEhrhardt » 02 Feb '13, 10pm

   @tissarah this kind of bush league vulnerability is why i'm not sold on Ruby's community [link]
8. » 02 Feb '13, 3pm

   [link] - rubygems hacked
9. @bak2k2 » 02 Feb '13, 1am

   RT @josdirksen: Not a good couple of weeks for Ruby - [link] hacked, [...] putting sites using Rails at risk - [link]
10. » 01 Feb '13, 5pm

    [link] hacked. Interrupts Heroku. Puts sites using Rails at risk [link]
11. @josdirksen » 01 Feb '13, 5pm

    Not a good couple of weeks for Ruby - [link] hacked, [...] putting sites using Rails at risk - [link]
12. » 01 Feb '13, 11am

    RT @frbayart: Rubygems hacked, interrupting Heroku services and putting sites using Rails at risk | [link]
13. » 01 Feb '13, 11am

    RT @htshozawa: RubyGemsにセキュリティ問題。Herokuに影響。ネットってやっぱり100%セキュリティは難しいな。漏洩してもよい情報だけをクラウドに上げるのが賢明かも　[link]
14. » 01 Feb '13, 10am

    RubyGemsにセキュリティ問題。Herokuに影響。ネットってやっぱり100%セキュリティは難しいな。漏洩してもよい情報だけをクラウドに上げるのが賢明かも　[link]
15. » 01 Feb '13, 8am

    [link] hacked [link]
16. » 01 Feb '13, 7am

    XML can be a pain, but you can't eval() it. Writeup of the [link] yaml vulnerability [link] /via @stagr_lee #yam
17. » 01 Feb '13, 6am

    Tiens ça te fais penser à qq chose @julienviet ? :-) RT @stagr_lee: For "gem install" on a production box... [link]
18. » 01 Feb '13, 6am

    [link] fm
19. » 01 Feb '13, 6am

    RT @stagr_lee: For everyone who as been told to run "gem install" on a production box... [link]
20. » 01 Feb '13, 5am

    For everyone who as been told to run "gem install" on a production box... [link]
21. » 01 Feb '13, 1am

    RT @yahihi: RubyGemsがハックされたとは / “[link] hacked, interrupting Heroku services and putting sites using Rails at r…” [link]
22. » 01 Feb '13, 12am

    RubyGemsがハックされたとは / “[link] hacked, interrupting Heroku services and putting sites using Rails at r…” [link]
23. » 01 Feb '13, 12am

    RT @rgaidot: [link] hacked, interrupting Heroku services and putting sites using Rails at risk [link]
24. @breun » 31 Jan '13, 11pm

    Een hoop Ruby web-ellende. :o( [link] [link] [link]
25. » 31 Jan '13, 9pm

    Check your Rails app. Vulnaribilities around: [link]
26. » 31 Jan '13, 9pm

    The dangers of developing in the #cloud: RubyGems hacked, interrupting Heroku services; many sites shutdown [link] #dev
27. » 31 Jan '13, 8pm

    Yikes! MT @VentureBeat: [link] hacked, halting Heroku svcs & putting Rails sites at risk [link] by @johnkoetsier
28. » 31 Jan '13, 8pm

    @xavii Amazon is down and this also happened. [link] come back the internet is crumbling without you!
29. » 31 Jan '13, 4pm

    RT @wildjcrt: [link] hacked, interrupting Heroku services and putting sites using Rails at risk | VentureBeat [link]
30. » 31 Jan '13, 3pm

    RT @WarN4N: Wow @technomancy works at heroku and I just watched his conj talk on lein2 where he warned of such stuff [link] via @prismatic
31. » 31 Jan '13, 3pm

    RT @gslin: [link] hacked, interrupting Heroku services and putting millions of sites using Rails at ri [link] via @zite
32. » 31 Jan '13, 2pm

    Gem install fireball [link] via @prismatic
33. » 31 Jan '13, 2pm

    Wow @technomancy works at heroku and I just watched his conj talk on lein2 where he warned of such stuff [link] via @prismatic
34. » 31 Jan '13, 1pm

    [link] hackeado! ¿Que consecuencias podría tener esto? [link]
35. » 31 Jan '13, 1pm

    RT @ebrandi: [link] hacked, interrupting Heroku services and putting millions of sites using Rails at ri [link] via @zite
36. » 31 Jan '13, 1pm

    RT @gattaca: [link] hacked, interrupting Heroku services and putting sites using Rails at risk [link]
37. @sunnysurya » 31 Jan '13, 1pm

    #Ruby site hacked, interrupting Heroku services and putting sites using Rails at risk: [link] via @venturebeat #oops!
38. » 31 Jan '13, 1pm

    RT @robdiana: [link] hacked, interrupting Heroku services and putting millions of sites using Rails at risk [link]
39. @DocAlev » 31 Jan '13, 12pm

    #Ruby developers take note, [link] hacked: [link]
40. » 31 Jan '13, 11am

    RubyGems hacked, interrupting Heroku services and putting sites using Rails at risk | [link] | WTF is going on lately?
41. » 31 Jan '13, 10am

    RT @PascalOnRails: A company bought for 212 mlln $ is down because of an security exploit at a volunteer-run service. Interesting times. [link]
42. » 31 Jan '13, 10am

    A company bought for 212 mlln $ is down because of an security exploit at a volunteer-run service. Interesting times. [link]
43. » 31 Jan '13, 9am

    RT @unak: 自分でも呟いておこう。えと、この辺? -- [link] hacked, interrupting Heroku services and putting sites using Rails at risk [link]
44. » 31 Jan '13, 9am

    自分でも呟いておこう。えと、この辺? -- [link] hacked, interrupting Heroku services and putting sites using Rails at risk [link]
45. » 31 Jan '13, 9am

    [link] hacked, interrupting Heroku services and putting millions of sites using Rails at ri [link] via @zite
46. » 31 Jan '13, 8am

    [link] hacked, interrupting Heroku & putting sites w/Rails at risk [link]
47. » 31 Jan '13, 8am

    Sure you’ll have seen this but just in case. [link] @bmxbandit
48. » 31 Jan '13, 6am

    RT @Wh1t3Rabbit: For those whose cave doesnt get Internet, Venturebeat is running a story on the [link] exploit... [link]
49. @AstroRabbit » 31 Jan '13, 6am

    [link] Ruby 언어 패키지 배포 사이트 [link]가 해킹당했다고 함.
50. » 31 Jan '13, 5am

    For those whose cave doesnt get Internet, Venturebeat is running a story on the [link] exploit... [link]