https://github.com/ujihisa/twi1

https://github.com/ujihisa/twi1

Last synced: about 1 month ago
JSON representation

• Host: GitHub
• URL: https://github.com/ujihisa/twi1
• Owner: ujihisa
• Created: 2010-05-27T23:12:41.000Z (over 14 years ago)
• Default Branch: master
• Last Pushed: 2010-05-28T06:00:51.000Z (over 14 years ago)
• Last Synced: 2024-05-01T23:19:46.450Z (7 months ago)
• Language: Ruby
• Homepage: http://ujihisa.blogspot.com/2010/05/experimental-twitter-clone-with-rails.html
• Size: 167 KB
• Stars: 1
• Watchers: 2
• Forks: 4
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# An Experimental Twitter Clone with Rails

Let's make an experimental Twitter clone web app by Ruby on Rails version 3.

The minimum features of Twitter clone app are below:

* A visitor can sign up and get an account to become a user

* A user can post tweets

* A visitor and a user can see another user's one single tweet or a sequence of tweets

* A visitor and a user can see public timeline

* A user can follow another user

* A user can see "timeline" of the followings' tweets

I cut the following features for ease:

* A user can see "mentions"

* A user can leave (unfollow) others

* A user can send or receive direct messages

But I also would want to add the following internal feature which the real Twitter seems to be using:

* A timeline is not created just in time, but created when a user of the participants posted a tweet

This feature reduces the load time of reading a timeline.

## So what's the difference?

* It doesn't use any special software but just use Rails3

* It doesn't use a relational DB for storing tweets

* It is fast and scales (hopefully)

## The Product "twi1"

I named it "twi1" without thinking anything. That's here. 

Note that currently it doesn't work because heroku doesn't support writing a file. I should look for another way if I use heroku.

The below screenshots are on my local server.

![User's timeline](http://gyazo.com/481d6caa9e0ce814d93acc76941eadc9.png)

![Public timeline](http://gyazo.com/6b1ace898ac7dac063339f06785b488d.png)

The public/user timeline is stored as the below.

    timeline([

    ,{user: 'ayden', text: 'test'}

    ,{user: 'ayden', text: 'adsfjklasdf'}

    ,{user: "ayden", text: "newest"}

    ,{user: "brian", text: "asdfasdfasd"}

    ,{user: "brian", text: "<script>test</script>"}

    ,{user: "jjjjjj", text: "asdfads"}

    ,{user: "ujm", text: "Hello, world!"}

    ]);

When a user posted a tweet, the following code runs.

    # in model/tweet

    def add_a_tweet_on_timeline_to(username)

      add_a_tweet_on_the_file("#{RAILS_ROOT}/public/#{username}.js")

    end

    def add_a_tweet_on_the_file(file)

      File.open(file, 'r+') {|io|

        finale = "]);\n"

        io.seek(-finale.size, IO::SEEK_END)

        io.puts %|,{user: "#{@owner.username}", text: "#{@text}"}|

        io.write finale

      }

    end

That just removed the last line and add two lines.

To show the static timeline json file, I used the following short javascript codes.

    function timeline(xs) {

      var t = new Template("
#{user}: #{text}
")

      $('timeline').innerHTML =

        xs.compact().map(function(x) {

          return t.evaluate(x);

        }).reverse().join("\n");

    }


and in the HTML view file,

    

      Event.observe(window, 'load', function() {

        var username = '<%= @user.username %>';

        var url = '/' + username + '.js?' + (new Date()).valueOf();

        var script = document.createElement('script');

        script.setAttribute('src', url);

        document.getElementsByTagName('head')[0].appendChild(script); 

      });

    

## Actually

The current `twi1` doesn't have the "follow" feature.

## References

* 

*  (to run authlogin on heroku)

*  (for jsonp)