Thanks for your response Matias, Unfortunately some things have come in between, but I will definitely take another look at social-auth once I've get some time and let you know about the result!
Regards Leon On 20 mei, 17:52, Matías Aguirre <matiasagui...@gmail.com> wrote: > Excerpts from Leon van der Ree's message of Fri May 20 11:21:15 -0300 2011: > > > Hi all, > > Hi, > > > First a short intro, since this is my first post > > > Last few years I have been working on and with Symfony (Php) a lot, > > but since I am done with the ugly bugs within Php I decided to switch > > to another development environment. I have always been interested in > > other languages and frameworks and Python and Django always looked > > very promising to me. Now that I have a new job I was able to make > > this switch so I dived into Python and Django. I think I now have a > > basic understanding of how to optimally use the dynamic capabilities > > of Python (something that you can't properly meke use of in Php if you > > ask me) and I understand the design of Django. Untill now all seems > > brilliant! > > Welcome! > > > > > > > > > > > My first assignment in Django is to develop a social-media powered > > website, so I started to explore the community plugins but now got a > > bit disappointed. I haven't found anything that is capable to handle > > several different social networks. Am I missing something or isn't it > > there yet? > > > So far I found several social-authorization applications, but most of > > them where tightly coupled with the social networks they can handle so > > there is no easy way of adding different networks from outside the > > application (by E.G. adding an extra application for another network > > and provide it to the generic-app through your project > > configuration). > > Other social media plugins that I found are capable of doing more than > > only authorization, but are build specifically for one social network. > > Django is so nicely organised, and capable of being extended with all > > kind of functionality, so I would have expect social-media apps that > > where designed this way as well? > > You might have foundhttp://github.com/omab/django-social-auth/already, > as you can see it's easy to extend adding more and more authentication > backends, they can be on a separated module even. But, it only take care > of authentication, that's because there are plenty of projects that > handle user data retrieval and each project have different needs. And > I prefer the do-one-single-thing principle. > > Anyway It's easy to extend using the defined signals, there you can > easily retrieve user data from the different social-media sites. > > > My idea of a social media application is that it should be extendable > > and capable of doing more than only handling authorisation. Depending > > on the social network you have more or less functionality that can be > > used. E.G. Facebook and Twitter both support posting messages, but > > only Facebook supports liking things. But you have thinkgs like Orkut > > (and in Holland Hyves) as well, which could make use of the same > > generic interface to support like-ing and sending messages, while > > others, like e.g. gmail only support authorisation. > > This could be a interesting side project, but it should do only that, no > more IMO. > > > > > > > > > > > I think there can be a generic interface with functionality and > > specialised classes per social network that implement this > > functionality. Than in your project settings you should be able to > > simply (configure and) enable these networrks.These specialised > > classes for all the different networks can be provided in different > > apps, so anyone can build new connections without modifying the > > generic social-app. In these specialised apps you can choose how to > > implement the connection to the network yourself (use the entire > > python facebook library, or write a custom facebook authroisation > > module yourself). I think a good base for this is the implementation > > of django-allauth although it currently has some hardcoded > > configuration (urls, templatetags, etc) and is limited to only > > authorisation. > > > Any feedback about this would be greatly appreciated! > > Leon > > Thanks, > Matías > -- > Matías Aguirre <matiasagui...@gmail.com> -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
