Blogmarks.net Blog

In case you have not noticed, we're doing some experiment with advertising on public pages (the green ones).

We're actually working on our (small) business model and this will help us know how we can monetize blogmarks.net.

In the future, we've planned to launch paid accounts for the people who love our service and don't want to be annoyed with this kind of advertising.

end of experiment : Ok, we collected the metrics we wanted. Result : speaking short term, we wont display any ads when the user is connected.

We pushed online yesterday a new layout for marks within blogmarks.net RSS feeds.

What do you think about it ?

Yeah, i think this announce will make lot of people happy, Blog Sync is back :)

At first, when we launched Blogmarks.net v2, we decided to drop it and come back later with a more powerful tool. But, hey, we received *lot* of complains, and then realised the real popularity of this tool. So, we decided to recode it with identical features and here we are.

To enable it in the Tools section, you have to fill your Blog Profile first. This is not heavily tested, feedback welcome, betaaaaaaaaaaaaaaaaaaa !

A little note to let you know that Blogmarks.net is no more a spammer and porn paradise.

• If someone post illegitimate content, we will empty then block the account. We may blacklist the IP too if we detect a lot of abuse from it. Illegitimate content is at our own policy: porn related links, links to SEO dedicated pages, accounts with links pointing only on commercial catalogues, etc.
• Legitimate users, please post illegal, porn and violent content privately. If you don't do this, we'll reserve the right to switch them for you.
• If you see some annoying illegitimate accounts, don't hesitate to contact us.

A little note to let you know that we've just activated the timezone handling. Update your general profile and then all dates displayed on blogmarks.net will be converted on this basis.

Yep, very little but great (we hope !) improvement.

These two parts were launched a little bit ... rough. This is now (almost) fixed.

We are still actively debugging and stabilising the platform. Thank for your great support !

Yesterday, we released blogmarks.net v2. While everything is not polished, we had to move on, blogmarks.net v1 performances were definitely too bad and not sustainable anymore.

So what's new ? New code, new hosting, new design, new everything.

Status ? A little bit "beta" for now, we have some bugs to fix during the next few weeks. You can help us by sending feedback and bug reports.

Big up to Benoît (architecture, coding), Sébastien (design) and everyone involved.

Sorry for this long long outage (2h30 -> 12h30 Paris time) ...

Not related with this problem, we have the pleasure to announce that Blogmarks.net v2 will be launched around the 24 may.

We encourage application developers and users of the web service to contact us this week. We'll give you a preview access to test the new toolkit and the new REST API. It's important because we made some non backward compatible changes.

One year ago, we were releasing Blogmarks.net v1.

Happy blogmarks to you !

Our screenshot facility is currently off. The cause is surely simply electrical but while we are all in holidays, we can't fix anything right now. It will be back up tuesday night if not before. When all will be ok, we'll shoot again all the kind URLs you blogmarked the last few days. Sorry for that, blame christmas :)

A good news, next time i will write on this blog, i will speak about "blogmarks.net 2.0", yep. It's going big !

update : tuesday : train - 19h check-in at our workplace - dsl connection down - fuck - trying to repair - fuck - unplugued the server - snow - taxi - home - replugued - 0H30 back up.

Sorry for the recent server problems and generally for the performances. The fact is that it's more and more difficult to handle the (heavy) load ! We plan to move on a new server infrastructure in the next few weeks.

Until then, please be patient and don't shoot F5 too often :) Thanx for your understanding !

update (07/07/05) : We just reached step 1 of 3 to better performances. Much faster database now ...

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.