philwilson.org :: foaflicious

FOAFlicious offline

Phil Wilson — Mon, 20 Nov 2006 20:36:00 +0000

If you hadn't already noticed, FOAFlicious has been down for some time due to problems with Java on my server. I'll probably try and rewrite this in JRuby or Python sometime soon.

IFP added

Phil Wilson — Tue, 06 Sep 2005 22:47:07 +0000

I've added in a foaf:homepage to each user that you foaf:know pointing to that user's del.icio.us page (in addition to any other detected) so that now graphing tools might actually work.

I'll also try and update it to do some better caching and expiry and try to actually use the del.icio.us API rather than the painful screenscraping that I'm currently doing.

FOAFlicious now doesn't use a stupid port number

Phil Wilson — Tue, 15 Mar 2005 12:55:10 +0000

I've tidied up my settings slightly so that now when you enter your name in the FOAFlicious form and submit it, it no longer points at port 8180 on my server. This should help anyone who would otherwise have to open a port on their firewall to be able to use FOAFlicious.

http://philwilson.org/foaflicious/foaflicious.groovy?user=pip is the newer syntax, although the old one with the port number will still (currently) work.

FOAFgen supports FOAFlicious

Phil Wilson — Mon, 07 Mar 2005 16:19:32 +0000

The excellent FOAFgen now provides a rdfs:seeAlso to FOAFlicious if you provide a del.icio.us username. Cool!

foaflicious 0.2

Phil Wilson — Mon, 21 Feb 2005 19:31:57 +0000

The source for FOAFlicious 0.2 is available on http://philwilson.org/projects/foaflicious/code/foaflicious-0.2.groovy.

This version of FOAFlicious relies on Groovy 1.0-beta 9 or above.

There are two major changes between 0.2 and 0.1:

You can now pass in a del.icio.us username as a parameter
It no longer looks for FOAF files linked from users' homepages (because it was killing performance stone dead).

FOAFlicious now has a home page

Phil Wilson — Mon, 07 Feb 2005 12:54:38 +0000

As part of my efforts to tidy up my website and projects, FOAFlicious now has a home page with an easy access form for generating your FOAF file, and protects you slightly from having to remember that dreadful URL :)

FOAFlicious now generates FOAF for any del.icio.us user

Phil Wilson — Fri, 04 Feb 2005 22:47:30 +0000

You can now get the del.icio.us inbox for any user in FOAF format like so: http://philwilson.org:8180/foaflicious/foaflicious.groovy?user=pip - just substitute the username you want at the end of the URL

This functionality was always there, but broken in Groovy 1.0-beta-6. I've just upgraded to beta 9 and it works just fine.

In other news, I wanted to play with a new toy, so there's now an "upcoming features" list for FOAFlicious hosted on tadalist.com.

I'll try and actually fix all the things on the list over the weekend.

FOAFlicious 0.1

Phil Wilson — Fri, 07 Jan 2005 14:47:10 +0000

FOAFlicious is an application for generating a FOAF file from your del.icio.us inbox.

FOAFlicious is written in Groovy, and can be seen in action on http://philwilson.org:8180/foaflicious/foaflicious.groovy (hopefully this URL will become better in time).

This is the first time I've ever used Groovy and so far I've not been able to configure it to accept URL parameters (answers on a postcard please) so it's currently hardcoded to return a FOAF file based on my del.icio.us inbox, here's looking at v0.2 :)

The del.icio.us inbox facility is currently turned off except for the list of subscriptions so it currently works by masses of screen-scraping. As soon as the inbox comes back it should be able to switch to using the del.icio.us API (probably using David Czarnecki's delicious-java API).

Currently it uses the del.icio.us page for each user listed in your inbox to extract a user's real name and homepage, then looks at their homepage to see if they have a FOAF autodiscovery link, and if so includes it in a <rdfs:seeAlso rdf:resource="blah"/> block.

The (terrible) code is available on http://philwilson.org/projects/foaflicious/foaflicious-0.1.groovy. it was only written in a couple of hours, so no abuse please :) In order to run it you'll need the Groovy libraries, commons-httpclient, commons-logging and JTidy.

If you want to stay notified about this project, it has its own feed.