Please document use cases and usage of the app

[GoogleCodeExporter]

Please, document the use cases for this application. I was looking for an app 
to add Flickr and 
Picasa photostreams/albums integration to my site and Google suggested me this 
app, but I cann't 
find any information on what's this app for (really, "syncing" is not a use 
case description).

Also, the usage is not clear, but I think my confusion comes from not 
understanding the use case.

Original issue reported on code.google.com by jarek.zg...@gmail.com on 26 Nov 2008 at 7:49

[GoogleCodeExporter]

Hello,

       Well this app makes API calls to various social networks and syncs user data into your database. Thats the 
whole point. We have n't really put a lot of time into documentation rather we 
put a lot of time into coding.

If you are comfortable with django its fairly easy to setup these apps into 
your project. Please post here if you 
need any help...

Original comment by yash...@gmail.com on 1 Dec 2008 at 6:40

[GoogleCodeExporter]

With all due respect, this is still a terrible summary.  Someone really needs 
to at
least explain the basic expected uses here, or the project is useless to most 
of us.
 I mean... all we know is that data of various kinds can be sync'd back and forth. 
Does that mean it downloads images from flickr?  Can upload images to flickr? 
Provides links to flickr?  ID codes for flickr images to make your own links?  
If a
user does 100 things a day on your django app, and you sync that with twitter, 
will
twitter ban you or something?  Or can that sort of stuff even BE sync'd?  Does 
the
twitter sync only support listing what a django user's friends are up to?  None 
of
this is clear.  When we know what basics are supported, we'll have a better 
sense of
where we can go beyond basics to some innovative and interesting use.

Original comment by fallible...@gmail.com on 1 Dec 2008 at 12:28

[GoogleCodeExporter]

@fallibledragon  well a better solution to that is to do a screencast on how to 
use django-syncr with an 
existing project. Hmm may be i'll do that in a week. I have n;t done any 
screencast till date but I a going to try 
it now.

To answer your questions in short:

this app checks a user's flickr account and syncs the image links(small, 
medium, thumbnail etc), date, and 
many more to django backend. We dont upload pics to flickr. Also we dont 
download pics from flickr instead 
we take the hyperlink to the image like 
(http://farm1.static.flickr.com/154/380173157_dd6a416379.jpg)

we also note each photo's flickr id(345009210). 

what do you mean by a user does 100 things on django. We just show the list of 
photos thats it.

similarly we can sync a user's tweet. pass a username as argument to 
GetTweets(username) it will get only the 
tweets of that user. Similarly we can pass another username to get his tweets.

May be screencast can help you get started. Do take a look at docs in the 
repository.

Original comment by yash...@gmail.com on 2 Dec 2008 at 7:02

[GoogleCodeExporter]

Here's the reason I created django-syncr: I wanted custom representation of my 
activities and data from 
various social media sites (ie. Flickr, YouTube, delicious). These were 
originally intended to be rendered on 
my blog in a way that I deemed fit. In other words, I wasn't happy with the 
default "badges" offered by most 
sites.

One example use case is the auto-embedding of YouTube videos from my YouTube 
account's "Favorites" to a 
videos page on my blog. This means when I watch a video on YouTube and hit the 
favorite button, my blog is 
automatically updated to reflect the new addition. Likewise with special 
playlists, etc.

Delicious is another good example use case. I wanted a linklog but I didn't 
want to post links manually. The 
syncing application automatically refreshes my delicious bookmarks to my blog, 
including my comments, and 
redisplays it in the form of a linklog.

Similar use cases exist for Twitter, Flickr, etc. 

Original comment by jesse.l...@gmail.com on 3 Dec 2008 at 4:30

[GoogleCodeExporter]

Thanks guys.  That makes sense now, and I can already envisage some uses for it 
:)

Original comment by fallible...@gmail.com on 3 Dec 2008 at 6:33