Big things:
1) Fixed issue #5
2) Fixed issue #13
3) Added a way of displaying the list (shown at
<http://singpolyma.net/contacts>) -- if one contact has multiple links
it puts them is a sublist
4) WP admin page code made more valid (no raw >, use >)
Looking at:
I still dislike the way it detects if an entry matches a user. Should
go into the wp-openid guts like getting an openid for a userid does.
There really should be a function added to the wp-openid plugin to get
OpenID for userid and userid for OpenID so that things like this can
be done without relying on the table structure.
is_friend and similar for logged in user.
--
- Stephen Paul Weber, Amateur Writer
<http://www.awriterz.org>
MSN/GTalk/Jabber: singp...@gmail.com
ICQ/AIM: 103332966
BLOG: http://singpolyma.net/
For example, once we're able to publish or list your entire blogroll
as hcards publicly, how can we begin to segment/group that list
(categories of course, but would WordPress' new tags infrastructure be
applicable?), how can we provide better internal management tools? And
is it conceivable to allow a blog's users to friend each other and
have that reflected either on the site (/author/authorname/contacts)
or in the backend?
Just ideas for now, and maybe even opportunities for secondary
plugins, since very quickly, once we have this portable list of
contacts for one person, it becomes interesting to think about how we
can begin to make use of it to solve some real problems!
Chris
--
Chris Messina
Citizen-Participant &
Open Source Advocate-at-Large
Work: http://citizenagency.com
Blog: http://factoryjoe.com/blog
Cell: 412.225.1051
IM: factoryjoe
This email is: [ ] bloggable [X] ask first [ ] private
--
XFN is another option -- maybe let one list only family members or something.
Users friending each other sounds... odd... unless you're on MU.
--
Not sure, other than the way that they're stored and accessed in
WordPress seems different. Tags also seem somewhat easier and more
flexible to create on the fly, and, should someone feel so bold, allow
us to synchronize with external CRM-type systems like Highrise or
Blinksale, which use tags throughout.
> XFN is another option -- maybe let one list only family members or something.
Certainly. XFN is the start and should be the basis for any
relationship connections. That said, you might have "WoW friends" or
"Favorite Photographers" and so on that don't fit those semantics, or
at least are important enough that someone might want a way to call
out those groups in their personal settings. Furthermore, we should
again look at Facebook's or Gmails' approach to friend grouping for
prior art:
http://www.readwriteweb.com/archives/facebook_launches_friend_lists.php
> Users friending each other sounds... odd... unless you're on MU.
Well, what about being able to pull in a remote XFN list and match the
remote identifiers with the local identifiers to see where your
friends have commented on the blog you're currently reading? Seems to
me that rather than think about this from a "friending" perspective,
we should look at this from a functionality perspective... IF there
are overlaps in friends lists between two people (or on two blogs),
then what kind of information can we reveal that might be of greater
interest to the visiting person? Think about the functionality that
MyBlogLog offers and then distribute it off the central server... and
think about what's possible. That's what should drive this plugin.
Actually, since we have openid login code and hcard importing code,
all that would be needed is a plugin to add the most recent visitor
user IDs to a list somewhere internally and render as a widget.
Stephen, I like the work you're doing on the contacts. I've made you a
member (ie, committer) on the repository, and if you visit
diso.googlecode.com and view the source tab, it will give you
instructions for checking out the repo over https.
Also, I've added an experimental branch under wp-diso-contactlist. Go
ahead and commit your changes to the experimental branch and we can
all review them.
Cheers,
--Steve
--
Steve Ivy
http://redmonk.net // http://diso-project.org
This email is: [ ] bloggable [x] ask first [ ] private
<repo>/wordpress/wp-diso-contactlist/branches/experimental
--Steve
I have also reimplemented user_from_uri to query the OpenID tables
directly, so they cannot be spoofed. This function (along with
openid_for_user) should definitely be moved into wp-openid (so one
plugin does not rely on the table structure of another, and so other
plugins could use it).
This whole thing could maybe be abstracted a bit though, so that other
plugins can somehow be worked in. For example, people can log into my
blog with Facebook accounts. It wold be neat if the plugin detected
those who are also on my contact list and noted that as well -- but it
would suck to have to build detection code for every login type into
this plugin. Not sure how abstraction would look yet -- ideas?
--
Something like you now see in the sidebar of my blog, maybe?
--
This update includes the option to display contacts grouped by category.
The code for generating the list now contains no SQL (yay!) but I
think it will only work on WP 2.1+
It is also easy for the code to generate the list for just one
category now, although the UI does not allow for this yet.