Blogmarks.net Blog

Due to a crash on our server, blogmarks.net was down from 9pm to 9am (paris time). Sorry for the convenience.

Suite à un problème sur notre serveur, blogmarks.net a été coupé de 21h à 9h (heure de paris). Desolé pour le dérangement.

update : Not related with the last issue, we're actually moving the screenshot engine on a new location. It will come back in a few hours. DONE.

We just released a PEAR Class which connect to the blogmarks.net API. There are 5 methods for the moment : addMark(), updateMark(), deleteMark(), getMark(), getMarksList(), getTagsList(). We started a documentation page about it on our wiki.

If you have an interest in PHP, Atom or blogmarks.net have a look !

• Download class Services_Blogmarks
• Download the bundle with all PEAR dependencies

Just a little howto for those of you who would like to add a nice Add to blogmarks.net link to the articles published on their blog (or anything else).

The URL for the service is : http://blogmarks.net/my/new.php

Just throw a GET request to this URL, with the following parameters :

• title : Title of the mark
• url : URL of the ressource
• summary : Description of the ressource
• via : Referer
• tags : a list of tags, separated by spaces

title and summary are mandatory.

title, summary and tags needs to be utf8 encoded, then urlencoded :

<?php $var = urlencode( utf8_encode($raw_var) ); ?>

BONUS :

Here is a javascript snippet to capture text highlited by user (we use it to fill in the summary in the bookmarklet) :

   var q='';
   if (window.getSelection) { q=window.getSelection(); } 
   else if (document.getSelection) { q=document.getSelection(); } 
   else if (document.selection) { q=document.selection.createRange().text; }

Easy ! What are you waiting for ??!

The original blogmarks.net BlogSync feature was a little bit bugged. Sorry for all the problems you eventually had with it.

Here is the good news, BlogSync must now work as expected. If it is not the case please email us (dev at blogmarks.net) or leave a comment on this post.

We started a documentation effort about it on our Wiki.