[geeklog-devel] geeklog-devel Digest, Vol 38, Issue 21
moulyg at gmail.com
Fri Feb 19 10:09:10 EST 2010
facebook has their own web services we can acess them... its like twitter i
I have worked on twitter....
so we can get username and the password of the facebook when they are
registetring or after.......
@ Dirk I am also thinking about security.......it should bevery important
point and the other one is will user give their passwrod to a 3rd party web
I think if they have advantages they will
On Thu, Feb 18, 2010 at 8:30 PM, <geeklog-devel-request at lists.geeklog.net>wrote:
> Send geeklog-devel mailing list submissions to
> geeklog-devel at lists.geeklog.net
> To subscribe or unsubscribe via the World Wide Web, visit
> or, via email, send a message with subject or body 'help' to
> geeklog-devel-request at lists.geeklog.net
> You can reach the person managing the list at
> geeklog-devel-owner at lists.geeklog.net
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of geeklog-devel digest..."
> Today's Topics:
> 1. SOCnet -- was GSoC 2010 (Randy Kolenko)
> 2. Re: GSoC 2010 is on (Dirk Haun)
> 3. SOCNET (Joe Mucchiello)
> Message: 1
> Date: Wed, 17 Feb 2010 11:18:54 -0500
> From: "Randy Kolenko" <Randy.Kolenko at nextide.ca>
> Subject: [geeklog-devel] SOCnet -- was GSoC 2010
> To: "Geeklog Development" <geeklog-devel at lists.geeklog.net>
> <063B8B70CB9DA141B2FC1DB483561B9F1122A4 at nex-pluto.nextide.ca>
> Content-Type: text/plain; charset="us-ascii"
> By the way, finally, we're getting discussion on moving GL forward. This
> is a good thing regardless of what your opinion is towards ideas. This
> is how good products are developed.
> So, just further to this whole plugin (and socnet) concept:
> 1. I honestly could care less if socnet is part of core or a plugin. I
> strongly suggest the plugin route in order to decouple add-on
> functionality from core in order to have faster development cycles and
> some independence of design.
> 2. Based on Joe's proposal (and Joe, don't take this the wrong way), we
> have to start thinking about this a bit more. I think what's been
> discussed here is far too simplistic.
> How do we handle requests to join a group? (That would include requests
> FROM a group owner to a user and vice versa.)
> How do we handle blacklisting people? How do we handle a user removing
> themselves from a group for which they are not owner of? How do we
> handle administration of all of this? How do we manage privacy? How do
> I manage receiving email alerts for content added for groups I am a part
> All of that extra "stuff" would have to be part of core.
> 3. Up to this point in the GL world, plugins are mostly self-sufficient
> entities. There is next to zero collaborative abilities between them.
> What if I want comments on my ABC plugin page? Well, I have to write
> comment functionality myself. Comments on XYZ plugin? Well, I have to
> write that too. Why not have a comment plugin that can expose itself to
> other plugins via a hook based API controlled by core? Some form of PLG_
> hook functionality to signal which plugin and the plugin's unique
> identifier is saving, editing, inserting or deleting content that other
> hooked plugins can listen for.
> Turn on/off hooked plugin functionality for your product through the
> online configuration for your plugin. It's a subscription of sorts.
> So, why not have a base socnet plugin and build your apps around that
> dependency? Just food for thought.
> Flame/critique away, but think architecturally and how to move GL
> forward that would intrigue other developers to write code for GL.
> Having 8-10 month development cycles for core would stagnate socnet and
> any other plugins out there. Socnet could easily race ahead to meet the
> needs of the community without hacking core.
> Message: 2
> Date: Wed, 17 Feb 2010 17:35:56 +0100
> From: "Dirk Haun" <dirk at haun-online.de>
> Subject: Re: [geeklog-devel] GSoC 2010 is on
> To: geeklog-devel <geeklog-devel at lists.geeklog.net>
> Message-ID: <20100217163556.658983271 at smtp.haun-online.de>
> Content-Type: text/plain; charset=ISO-8859-1
> Tom wrote:
> >I haven't really looking into how
> >Openid was implemented but I assumed Facebook Connect would be done in a
> >similar manner. Maybe this process needs to be changed? I don't know as I
> >haven't done any real research yet on how Facebook Connect is implemented
> >and how Geeklog handles its different login procedures.
> There's an API for remote authentication modules which are then simply
> dropped into system/classes/authentication
> The LDAP, LiveJournal, and the now defunct Blogger authentication
> modules were implemented that way.
> The OpenID login process, however, was too different from what that API
> allows and had to be hard-coded.
> I have never even used Facebook and have no idea how their login process
> works and whether or not it could use the remote authentication API ...
> bye, Dirk
> Message: 3
> Date: Wed, 17 Feb 2010 12:21:30 -0800 (PST)
> From: Joe Mucchiello <jmucchiello at yahoo.com>
> Subject: [geeklog-devel] SOCNET
> To: geeklog-devel at lists.geeklog.net
> Message-ID: <664844.73425.qm at web31403.mail.mud.yahoo.com>
> Content-Type: text/plain; charset=us-ascii
> I'm away from my main email....
> Randy wrote:
> > How do we handle requests to join a group? (That would include requests
> > FROM a group owner to a user and vice versa.)
> > How do we handle blacklisting people? How do we handle a user removing
> > themselves from a group for which they are not owner of? How do we
> > handle administration of all of this? How do we manage privacy? How do
> > I manage receiving email alerts for content added for groups I am a part
> > of?
> > All of that extra "stuff" would have to be part of core.
> No, none of it has to be in core. Since it sounds like a socnet plugin is
> desired, once my patch is made, core never has to care about social
> networking ever again. The socnet plugin would handle the friendship
> handshake, group management, etc. All that core has to do is treat group
> type "2" as something invisible to the administrators. (The socnet plugin
> can provide the ability to peak inside a group if needed since that is
> something a socnet admin would do.)
> Now you do bring up something that would nice to have in core: bulk email
> handling, queuing and throttling. But email features are useful outside of
> social networking. There is a feature request and I think a GSOC project for
> this as well. I've written many messages about email throttling in the past.
> Dirk wrote:
> > I have never even used Facebook and have no idea how their login process
> > works and whether or not it could use the remote authentication API ...
> I believe the Facebook Connect login works like OpenID does. Think about it
> from security: You do not provide your Facebook password to some random
> website so they can log you in to Facebook. Geeklog probably needs to
> overhaul this feature since the OpenID (and Facebook) model where you never,
> ever type your password into a 3rd party website makes a lot more sense from
> a security point of view than the Geeklog assumption that users will gladly
> provide some random Geeklog site with their livejournal login and password.
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> End of geeklog-devel Digest, Vol 38, Issue 21
Department of Computer Engineering
University of Peradeniya
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the geeklog-devel