foxfirefey: A series of interconnected dots in the shape of an M. (memewidth)
[personal profile] foxfirefey2009-10-27 07:10 am

Some changes made to the edges file

* Now, the username and account number are available, as "name" and "account_id" values.
* OpenID accounts now use their username forms (ext_12345) to simplify spidering (some OpenID URLs are tricky to fetch as a URL parameter), and have "display_name" values for their edges.
foxfirefey: Fox stealing an egg. (Default)
[personal profile] foxfirefey2009-09-09 05:19 pm
Entry tags:

Edges patch is committed!

After some further refinements by [staff profile] mark, edge patches have been committed! That means they're going out in the next code push! Exciting!

You can see the format here (I recommend JSONView) for viewing):

Names have been replaced with userids, which are then defined with username/type in a different struct.
foxfirefey: Fox stealing an egg. (Default)
[personal profile] foxfirefey2009-08-20 10:10 am
Entry tags:

Turn data/interests into JSON?

Now that fdata.bml is in JSON, would it be expedient to make interests.bml into JSON?

Pros: would be easier for Javascript mashups to load, is a standard format for parsing
Cons: would break compatibility with older LJ-based tools, would take up a bit more space than the current file.
foxfirefey: A series of interconnected dots in the shape of an M. (memewidth)
[personal profile] foxfirefey2009-08-18 06:09 pm
Entry tags:

Let's talk about FOAF

All users have a FOAF file, like so:

There's a lot of useful data here, but I think it could be expanded to have some more data. Onward and out! )
foxfirefey: A series of interconnected dots in the shape of an M. (memewidth)
[personal profile] foxfirefey2009-08-17 06:56 pm
Entry tags:

Upcoming fdata replacement: edges

So far Dreamwidth has been sorely lacking an equivalent to LJ's fdata, the data file that told you the relationships of a user with other users. Our new equivalent to that will be called edges. Because of the new complexity of DW's relationship structure, and due to a desire to use more standards, this data file will be in the JSON format. The bug for it is Bug 857.

I currently have my proposed patch in. It's not committed yet, or live on the site, but I think it probably will be within the next month. If you want a chance to prepare, I have my patch applied on my development server. It's possible that details will change with feedback, though, so be forewarned! My server has open registration, so you can feel free to create accounts and play around, but I've made a small set of test accounts such as this one. You can view an example edge data file here:

Here is an example of a community's edges file:

The data is in one big hash. There is an "account_type" variable, set to the type of the account. That makes it easy to determine what kind of account you are fetching data for. The other base variables are relationship types, such as "watched", "watched_by", or "member_of", that are a hash of arrays--all the accounts with a given relationship are split up into account types.

Any commentary on this planned data file? Problems you want to fix now, before it's implemented? Any plans for it you want to share?