<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:media="http://search.yahoo.com/mrss/" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
  <title>Discussions of group: ipernity API development</title>
  <link>https://www.ipernity.com/group/api-dev/discuss</link>
  <image>
    <url>https://cdn.ipernity.com/p/101/1E/01/65822.buddy.jpg</url>
    <title>Discussions of group: ipernity API development</title>
    <link>https://www.ipernity.com/group/api-dev/discuss</link>
  </image>
  <description>Let's talk about current and future API developments ;-)  If you want to discuss about using the API,  please join the API users group.  Also see www.ipernity.com/api</description>
  <pubDate>Mon, 17 Aug 2026 06:17:28 +0000</pubDate>
  <lastBuildDate>Mon, 17 Aug 2026 06:17:28 +0000</lastBuildDate>
  <generator>https://www.ipernity.com</generator>
  <item>
    <title>Changes due to HTTPS migration</title>
    <link>https://www.ipernity.com/group/api-dev/discuss/199288</link>
    <guid isPermaLink="false">tag:ipernity.com,2024-05-31,topic-199288</guid>
    <pubDate>Fri, 31 May 2024 08:37:58 +0000</pubDate>
    <author>nobody@ipernity.com (Team)</author>
    <description>&lt;p class="who"&gt;&lt;a href="https://www.ipernity.com/home/team"&gt;Team&lt;/a&gt; has started a discussion:&lt;/p&gt;&lt;div class="description"&gt;Dear developers,&lt;br /&gt;
&lt;br /&gt;
the migration of the website to HTTPS also has some consequences for API usage. The API is now reachable via &lt;strong&gt;https ://​​api.ipernity.com&lt;/strong&gt;, and links returned by API requests will be HTTPS. Please update the links to the Ipernity API.  Authorization links should be given as HTTPS too (&lt;strong&gt;https ://www.ipernity.com/apps/authorize?...&lt;/strong&gt;). The documentation already shows the HTTPS links.&lt;br /&gt;
&lt;br /&gt;
As some API methods require the POST request method which does not allow redirects, and as some API implementations do not follow redirects at all, the HTTPS redirection for http ://api.ipernity.com has been switched off to enable legacy applications to still function, so the API is now reachable by both HTTP and HTTPS. Note that authorization links will still be redirected to HTTPS, but this is unlikely to cause problems as these links generally are processed by the user's browsers.&lt;br /&gt;
&lt;br /&gt;
In the long run, we want API calls to be encrypted, so we will eventually disable the HTTP access to the API. When this will be done is yet to be decided, the date will be announced in the groups &lt;a href="https://www.ipernity.com/group/api-users" target="_blank" rel="nofollow"&gt;API users&lt;/a&gt; and &lt;a href="https://www.ipernity.com/group/api-dev" target="_blank" rel="nofollow"&gt;API development&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
&lt;em&gt;Your ipernity team&lt;/em&gt;&lt;/div&gt;</description>
    <media:title>Changes due to HTTPS migration</media:title>
    <media:text type="html">&lt;p class="who"&gt;&lt;a href="https://www.ipernity.com/home/team"&gt;Team&lt;/a&gt; has started a discussion:&lt;/p&gt;&lt;div class="description"&gt;Dear developers,&lt;br /&gt;
&lt;br /&gt;
the migration of the website to HTTPS also has some consequences for API usage. The API is now reachable via &lt;strong&gt;https ://​​api.ipernity.com&lt;/strong&gt;, and links returned by API requests will be HTTPS. Please update the links to the Ipernity API.  Authorization links should be given as HTTPS too (&lt;strong&gt;https ://www.ipernity.com/apps/authorize?...&lt;/strong&gt;). The documentation already shows the HTTPS links.&lt;br /&gt;
&lt;br /&gt;
As some API methods require the POST request method which does not allow redirects, and as some API implementations do not follow redirects at all, the HTTPS redirection for http ://api.ipernity.com has been switched off to enable legacy applications to still function, so the API is now reachable by both HTTP and HTTPS. Note that authorization links will still be redirected to HTTPS, but this is unlikely to cause problems as these links generally are processed by the user's browsers.&lt;br /&gt;
&lt;br /&gt;
In the long run, we want API calls to be encrypted, so we will eventually disable the HTTP access to the API. When this will be done is yet to be decided, the date will be announced in the groups &lt;a href="https://www.ipernity.com/group/api-users" target="_blank" rel="nofollow"&gt;API users&lt;/a&gt; and &lt;a href="https://www.ipernity.com/group/api-dev" target="_blank" rel="nofollow"&gt;API development&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
&lt;em&gt;Your ipernity team&lt;/em&gt;&lt;/div&gt;</media:text>
    <media:credit role="author">Team</media:credit>
  </item>
  <item>
    <title>New Flickr2Ipernity v1.15 not working properly with Firefox</title>
    <link>https://www.ipernity.com/group/api-dev/discuss/162571</link>
    <guid isPermaLink="false">tag:ipernity.com,2014-04-08,topic-162571</guid>
    <pubDate>Tue, 08 Apr 2014 14:24:52 +0000</pubDate>
    <author>nobody@ipernity.com (François Collard)</author>
    <description>&lt;p class="who"&gt;&lt;a href="https://www.ipernity.com/home/francois_collard"&gt;François Collard&lt;/a&gt; has started a discussion:&lt;/p&gt;&lt;div class="description"&gt;I have been compelled to "upgrade" my Flickr2 Ipernity Greasemonky script from one that worked to a new one that didn't...&lt;br /&gt;
I had to fix this line:&lt;br /&gt;
    div.style.backgroundColor="#111111";&lt;br /&gt;
which does display a black background (guess why?) which does not make black letters very legible, to:&lt;br /&gt;
    div.style.backgroundColor="gray";&lt;br /&gt;
But the previous version was better.&lt;/div&gt;</description>
    <media:title>New Flickr2Ipernity v1.15 not working properly with Firefox</media:title>
    <media:text type="html">&lt;p class="who"&gt;&lt;a href="https://www.ipernity.com/home/francois_collard"&gt;François Collard&lt;/a&gt; has started a discussion:&lt;/p&gt;&lt;div class="description"&gt;I have been compelled to "upgrade" my Flickr2 Ipernity Greasemonky script from one that worked to a new one that didn't...&lt;br /&gt;
I had to fix this line:&lt;br /&gt;
    div.style.backgroundColor="#111111";&lt;br /&gt;
which does display a black background (guess why?) which does not make black letters very legible, to:&lt;br /&gt;
    div.style.backgroundColor="gray";&lt;br /&gt;
But the previous version was better.&lt;/div&gt;</media:text>
    <media:credit role="author">François Collard</media:credit>
  </item>
  <item>
    <title>About Greasemonkey scripts</title>
    <link>https://www.ipernity.com/group/api-dev/discuss/31258</link>
    <guid isPermaLink="false">tag:ipernity.com,2010-07-14,topic-31258</guid>
    <pubDate>Wed, 14 Jul 2010 15:26:32 +0000</pubDate>
    <author>nobody@ipernity.com (François Collard)</author>
    <description>&lt;p class="who"&gt;&lt;a href="https://www.ipernity.com/home/francois_collard"&gt;François Collard&lt;/a&gt; has started a discussion:&lt;/p&gt;&lt;div class="description"&gt;Maybe this is the wrong group to talk about that, but I wanted to say that the Greasemonkey scripts linked to Flickr (Flickr2ipernity...) would no longer work since Flickr changed its API, so that those scripts should be removed or updated.&lt;br /&gt;
Flickr users can still keep the old page layout, but not for long.&lt;/div&gt;</description>
    <media:title>About Greasemonkey scripts</media:title>
    <media:text type="html">&lt;p class="who"&gt;&lt;a href="https://www.ipernity.com/home/francois_collard"&gt;François Collard&lt;/a&gt; has started a discussion:&lt;/p&gt;&lt;div class="description"&gt;Maybe this is the wrong group to talk about that, but I wanted to say that the Greasemonkey scripts linked to Flickr (Flickr2ipernity...) would no longer work since Flickr changed its API, so that those scripts should be removed or updated.&lt;br /&gt;
Flickr users can still keep the old page layout, but not for long.&lt;/div&gt;</media:text>
    <media:credit role="author">François Collard</media:credit>
  </item>
  <item>
    <title>doc.tags.X format changes</title>
    <link>https://www.ipernity.com/group/api-dev/discuss/23678</link>
    <guid isPermaLink="false">tag:ipernity.com,2009-06-12,topic-23678</guid>
    <pubDate>Fri, 12 Jun 2009 15:38:41 +0000</pubDate>
    <author>nobody@ipernity.com (Christophe Ruelle)</author>
    <description>&lt;p class="who"&gt;&lt;a href="https://www.ipernity.com/home/xtof"&gt;Christophe Ruelle&lt;/a&gt; has started a discussion:&lt;/p&gt;&lt;div class="description"&gt;Hi friends,&lt;br /&gt;
&lt;br /&gt;
Just a quick message to inform you we had to modify the API format for tags.&lt;br /&gt;
&lt;br /&gt;
(in fact the format was not mature if you've checked closely).&lt;br /&gt;
&lt;br /&gt;
Please check :&lt;br /&gt;
&lt;br /&gt;
- &lt;a href="https://www.ipernity.com/help/api/method/doc.tags.add"&gt;https://www.ipernity.com/help/api/method/doc.tags.add&lt;/a&gt;&lt;br /&gt;
- &lt;a href="https://www.ipernity.com/help/api/method/doc.tags.getList"&gt;https://www.ipernity.com/help/api/method/doc.tags.getList&lt;/a&gt;&lt;br /&gt;
- &lt;a href="https://www.ipernity.com/help/api/method/doc.tags.edit"&gt;https://www.ipernity.com/help/api/method/doc.tags.edit&lt;/a&gt;&lt;br /&gt;
- &lt;a href="https://www.ipernity.com/help/api/method/doc.tags.remove"&gt;https://www.ipernity.com/help/api/method/doc.tags.remove&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
Of course, if this change was a real problem for some apps, please let me know, I can keep the old format for certain API keys.&lt;br /&gt;
&lt;br /&gt;
Wish you all a great weekend,&lt;br /&gt;
&lt;br /&gt;
Christophe.&lt;/div&gt;</description>
    <media:title>doc.tags.X format changes</media:title>
    <media:text type="html">&lt;p class="who"&gt;&lt;a href="https://www.ipernity.com/home/xtof"&gt;Christophe Ruelle&lt;/a&gt; has started a discussion:&lt;/p&gt;&lt;div class="description"&gt;Hi friends,&lt;br /&gt;
&lt;br /&gt;
Just a quick message to inform you we had to modify the API format for tags.&lt;br /&gt;
&lt;br /&gt;
(in fact the format was not mature if you've checked closely).&lt;br /&gt;
&lt;br /&gt;
Please check :&lt;br /&gt;
&lt;br /&gt;
- &lt;a href="https://www.ipernity.com/help/api/method/doc.tags.add"&gt;https://www.ipernity.com/help/api/method/doc.tags.add&lt;/a&gt;&lt;br /&gt;
- &lt;a href="https://www.ipernity.com/help/api/method/doc.tags.getList"&gt;https://www.ipernity.com/help/api/method/doc.tags.getList&lt;/a&gt;&lt;br /&gt;
- &lt;a href="https://www.ipernity.com/help/api/method/doc.tags.edit"&gt;https://www.ipernity.com/help/api/method/doc.tags.edit&lt;/a&gt;&lt;br /&gt;
- &lt;a href="https://www.ipernity.com/help/api/method/doc.tags.remove"&gt;https://www.ipernity.com/help/api/method/doc.tags.remove&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
Of course, if this change was a real problem for some apps, please let me know, I can keep the old format for certain API keys.&lt;br /&gt;
&lt;br /&gt;
Wish you all a great weekend,&lt;br /&gt;
&lt;br /&gt;
Christophe.&lt;/div&gt;</media:text>
    <media:credit role="author">Christophe Ruelle</media:credit>
  </item>
  <item>
    <title>New group API methods + group suggestion</title>
    <link>https://www.ipernity.com/group/api-dev/discuss/19685</link>
    <guid isPermaLink="false">tag:ipernity.com,2008-10-23,topic-19685</guid>
    <pubDate>Thu, 23 Oct 2008 20:39:09 +0000</pubDate>
    <author>nobody@ipernity.com (Christophe Ruelle)</author>
    <description>&lt;p class="who"&gt;&lt;a href="https://www.ipernity.com/home/xtof"&gt;Christophe Ruelle&lt;/a&gt; has started a discussion:&lt;/p&gt;&lt;div class="description"&gt;Thanks to Tristan who did a terrific work, the API now proposes new methods for groups.&lt;br /&gt;
&lt;br /&gt;
The second good news is about group suggestion.&lt;br /&gt;
Let me explain: actually a member needs to be a member of a group to add docs in. And a group admin/moderator may suggest a member to add a doc in a group by leaving a comment. Not easy...&lt;br /&gt;
This is why we decided to change the way it is and launch a great new feature: group suggestion.&lt;br /&gt;
Now a group admin can suggest to add a doc in a group just like if he was adding a doc in his own group, using the document tools menu "suggest a group".&lt;br /&gt;
What happens then:&lt;br /&gt;
- you see this group in the "Suggested Groups" section.&lt;br /&gt;
- the member gets a notice in his activity page.&lt;br /&gt;
- the member ca approve or refuse from the doc page.&lt;br /&gt;
- the member gets an implicite invitation to the group (even if private or by invitation).&lt;br /&gt;
&lt;br /&gt;
Now with only one click we made all this process much easier.&lt;br /&gt;
&lt;br /&gt;
More soon on the team's blog.&lt;br /&gt;
&lt;br /&gt;
We're off to Barcelona until monday, not sure if we will be able to connect...&lt;br /&gt;
&lt;br /&gt;
Have all a nice and sunny weekend.&lt;/div&gt;</description>
    <media:title>New group API methods + group suggestion</media:title>
    <media:text type="html">&lt;p class="who"&gt;&lt;a href="https://www.ipernity.com/home/xtof"&gt;Christophe Ruelle&lt;/a&gt; has started a discussion:&lt;/p&gt;&lt;div class="description"&gt;Thanks to Tristan who did a terrific work, the API now proposes new methods for groups.&lt;br /&gt;
&lt;br /&gt;
The second good news is about group suggestion.&lt;br /&gt;
Let me explain: actually a member needs to be a member of a group to add docs in. And a group admin/moderator may suggest a member to add a doc in a group by leaving a comment. Not easy...&lt;br /&gt;
This is why we decided to change the way it is and launch a great new feature: group suggestion.&lt;br /&gt;
Now a group admin can suggest to add a doc in a group just like if he was adding a doc in his own group, using the document tools menu "suggest a group".&lt;br /&gt;
What happens then:&lt;br /&gt;
- you see this group in the "Suggested Groups" section.&lt;br /&gt;
- the member gets a notice in his activity page.&lt;br /&gt;
- the member ca approve or refuse from the doc page.&lt;br /&gt;
- the member gets an implicite invitation to the group (even if private or by invitation).&lt;br /&gt;
&lt;br /&gt;
Now with only one click we made all this process much easier.&lt;br /&gt;
&lt;br /&gt;
More soon on the team's blog.&lt;br /&gt;
&lt;br /&gt;
We're off to Barcelona until monday, not sure if we will be able to connect...&lt;br /&gt;
&lt;br /&gt;
Have all a nice and sunny weekend.&lt;/div&gt;</media:text>
    <media:credit role="author">Christophe Ruelle</media:credit>
  </item>
  <item>
    <title>doc.search limit</title>
    <link>https://www.ipernity.com/group/api-dev/discuss/19589</link>
    <guid isPermaLink="false">tag:ipernity.com,2008-10-18,topic-19589</guid>
    <pubDate>Sat, 18 Oct 2008 11:29:54 +0000</pubDate>
    <author>nobody@ipernity.com (Roberto Ballerini - traveling)</author>
    <description>&lt;p class="who"&gt;&lt;a href="https://www.ipernity.com/home/robertoballerini"&gt;Roberto Ballerini - traveling&lt;/a&gt; has started a discussion:&lt;/p&gt;&lt;div class="description"&gt;I don't understand this 3000 items limit.&lt;br /&gt;
If what you want is a limit to the quantity of calls, a 'per hour' calls limit as in Flickr seems to me more effective.&lt;br /&gt;
As it is implemented now, I can always play with the parameters and circumvent it: the result is that the code is more difficult to write, but the server load only slightly decreases...&lt;/div&gt;</description>
    <media:title>doc.search limit</media:title>
    <media:text type="html">&lt;p class="who"&gt;&lt;a href="https://www.ipernity.com/home/robertoballerini"&gt;Roberto Ballerini - traveling&lt;/a&gt; has started a discussion:&lt;/p&gt;&lt;div class="description"&gt;I don't understand this 3000 items limit.&lt;br /&gt;
If what you want is a limit to the quantity of calls, a 'per hour' calls limit as in Flickr seems to me more effective.&lt;br /&gt;
As it is implemented now, I can always play with the parameters and circumvent it: the result is that the code is more difficult to write, but the server load only slightly decreases...&lt;/div&gt;</media:text>
    <media:credit role="author">Roberto Ballerini - traveling</media:credit>
  </item>
  <item>
    <title>[done] User alias and user ID for using in user_id</title>
    <link>https://www.ipernity.com/group/api-dev/discuss/19514</link>
    <guid isPermaLink="false">tag:ipernity.com,2008-10-14,topic-19514</guid>
    <pubDate>Tue, 14 Oct 2008 18:24:00 +0000</pubDate>
    <author>nobody@ipernity.com (Ｄｉｒｋ)</author>
    <description>&lt;p class="who"&gt;&lt;a href="https://www.ipernity.com/home/dirk"&gt;Ｄｉｒｋ&lt;/a&gt; has started a discussion:&lt;/p&gt;&lt;div class="description"&gt;If i do a doc.search call with user_id='dirk', i’ll get an error message “User not found”. But if i call with user_id=19181 it all works fine.&lt;br /&gt;
&lt;br /&gt;
Would be great, if i could pass the user alias directly as user_id, because i can’t find my user ID here at ipernity, i only find my user alias (well, i found my user ID &lt;a href="https://www.ipernity.com/help/faq?q=user+id"&gt;in the help system&lt;/a&gt; here at ipernity), and i don’t want to compel my users to do some research and use some bugs (i don’t know, if the using of the user ID instead of the user alias in the help system is a bug *g*) just for using my stuff :)&lt;br /&gt;
&lt;br /&gt;
Conclusion: user_id should work with the user ID and the user alias in the same way.&lt;br /&gt;
&lt;br /&gt;
Alternative: Make it easy to get the own user ID via ipernity web site.&lt;br /&gt;
Alternative 2: Create a getUserID-function to resolve the user alias to the user ID.&lt;/div&gt;</description>
    <media:title>[done] User alias and user ID for using in user_id</media:title>
    <media:text type="html">&lt;p class="who"&gt;&lt;a href="https://www.ipernity.com/home/dirk"&gt;Ｄｉｒｋ&lt;/a&gt; has started a discussion:&lt;/p&gt;&lt;div class="description"&gt;If i do a doc.search call with user_id='dirk', i’ll get an error message “User not found”. But if i call with user_id=19181 it all works fine.&lt;br /&gt;
&lt;br /&gt;
Would be great, if i could pass the user alias directly as user_id, because i can’t find my user ID here at ipernity, i only find my user alias (well, i found my user ID &lt;a href="https://www.ipernity.com/help/faq?q=user+id"&gt;in the help system&lt;/a&gt; here at ipernity), and i don’t want to compel my users to do some research and use some bugs (i don’t know, if the using of the user ID instead of the user alias in the help system is a bug *g*) just for using my stuff :)&lt;br /&gt;
&lt;br /&gt;
Conclusion: user_id should work with the user ID and the user alias in the same way.&lt;br /&gt;
&lt;br /&gt;
Alternative: Make it easy to get the own user ID via ipernity web site.&lt;br /&gt;
Alternative 2: Create a getUserID-function to resolve the user alias to the user ID.&lt;/div&gt;</media:text>
    <media:credit role="author">Ｄｉｒｋ</media:credit>
  </item>
  <item>
    <title>EXIF</title>
    <link>https://www.ipernity.com/group/api-dev/discuss/19429</link>
    <guid isPermaLink="false">tag:ipernity.com,2008-10-10,topic-19429</guid>
    <pubDate>Fri, 10 Oct 2008 20:54:59 +0000</pubDate>
    <author>nobody@ipernity.com (Roberto Ballerini - traveling)</author>
    <description>&lt;p class="who"&gt;&lt;a href="https://www.ipernity.com/home/robertoballerini"&gt;Roberto Ballerini - traveling&lt;/a&gt; has started a discussion:&lt;/p&gt;&lt;div class="description"&gt;I'd like to have access to the EXIF data of docs&lt;/div&gt;</description>
    <media:title>EXIF</media:title>
    <media:text type="html">&lt;p class="who"&gt;&lt;a href="https://www.ipernity.com/home/robertoballerini"&gt;Roberto Ballerini - traveling&lt;/a&gt; has started a discussion:&lt;/p&gt;&lt;div class="description"&gt;I'd like to have access to the EXIF data of docs&lt;/div&gt;</media:text>
    <media:credit role="author">Roberto Ballerini - traveling</media:credit>
  </item>
  <item>
    <title>PDF version of documentation</title>
    <link>https://www.ipernity.com/group/api-dev/discuss/19428</link>
    <guid isPermaLink="false">tag:ipernity.com,2008-10-10,topic-19428</guid>
    <pubDate>Fri, 10 Oct 2008 20:44:19 +0000</pubDate>
    <author>nobody@ipernity.com (Roberto Ballerini - traveling)</author>
    <description>&lt;p class="who"&gt;&lt;a href="https://www.ipernity.com/home/robertoballerini"&gt;Roberto Ballerini - traveling&lt;/a&gt; has started a discussion:&lt;/p&gt;&lt;div class="description"&gt;I Know, I know: I'm lazy, but how about a downloadable (and printable) pdf version of the documentation?&lt;/div&gt;</description>
    <media:title>PDF version of documentation</media:title>
    <media:text type="html">&lt;p class="who"&gt;&lt;a href="https://www.ipernity.com/home/robertoballerini"&gt;Roberto Ballerini - traveling&lt;/a&gt; has started a discussion:&lt;/p&gt;&lt;div class="description"&gt;I Know, I know: I'm lazy, but how about a downloadable (and printable) pdf version of the documentation?&lt;/div&gt;</media:text>
    <media:credit role="author">Roberto Ballerini - traveling</media:credit>
  </item>
  <item>
    <title>API developers... welcome!</title>
    <link>https://www.ipernity.com/group/api-dev/discuss/19412</link>
    <guid isPermaLink="false">tag:ipernity.com,2008-10-10,topic-19412</guid>
    <pubDate>Fri, 10 Oct 2008 14:23:26 +0000</pubDate>
    <author>nobody@ipernity.com (Christophe Ruelle)</author>
    <description>&lt;p class="who"&gt;&lt;a href="https://www.ipernity.com/home/xtof"&gt;Christophe Ruelle&lt;/a&gt; has started a discussion:&lt;/p&gt;&lt;div class="description"&gt;Hello friends,&lt;br /&gt;
&lt;br /&gt;
We're very proud to launch the ipernity API today. It's in BETA and it's incomplete.&lt;br /&gt;
&lt;br /&gt;
But... it's OPEN ;)&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Let us know what you think:&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
- did you understand everything? (please let us know after carefully read the documentation)&lt;br /&gt;
- did you find any bugs?&lt;br /&gt;
- what are the methods and possibilities you're missing.&lt;br /&gt;
- what software are you planning develop?&lt;br /&gt;
&lt;br /&gt;
Before getting again deeper into our codes, we'll wait a little bit and listen to your needs.&lt;br /&gt;
&lt;br /&gt;
Give us your feedbacks!&lt;/div&gt;</description>
    <media:title>API developers... welcome!</media:title>
    <media:text type="html">&lt;p class="who"&gt;&lt;a href="https://www.ipernity.com/home/xtof"&gt;Christophe Ruelle&lt;/a&gt; has started a discussion:&lt;/p&gt;&lt;div class="description"&gt;Hello friends,&lt;br /&gt;
&lt;br /&gt;
We're very proud to launch the ipernity API today. It's in BETA and it's incomplete.&lt;br /&gt;
&lt;br /&gt;
But... it's OPEN ;)&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Let us know what you think:&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
- did you understand everything? (please let us know after carefully read the documentation)&lt;br /&gt;
- did you find any bugs?&lt;br /&gt;
- what are the methods and possibilities you're missing.&lt;br /&gt;
- what software are you planning develop?&lt;br /&gt;
&lt;br /&gt;
Before getting again deeper into our codes, we'll wait a little bit and listen to your needs.&lt;br /&gt;
&lt;br /&gt;
Give us your feedbacks!&lt;/div&gt;</media:text>
    <media:credit role="author">Christophe Ruelle</media:credit>
  </item>
</channel>
</rss>