Tagged: API Toggle Comment Threads | Keyboard Shortcuts

  • Joe 18:24 on May 31, 2007 Permalink
    Tags: API, , nice photo sharing site, Panoramio.com   

    Google buys Panoramio 

    The Spanish startup Panoramio.com has been acquired by Google. This is not very surprising, as they already were linked very intimately with Google Earth.

    PanoramioFor those who don’t know Panoramio yet, it is a clean, nice photo sharing site. Its specialty is that every photo is geographically marked. Select photos appear on Google Earth and the site itself is organized around Google Maps, where every location marks available photos with an icon or a small thumbnail.

    The announcement in the blog post does not provide many specific details, but for now not much will change:

    For now, our user interface will not change; accounts, urls, features… We will keep working for Panoramio as a team, but this time using Google infrastructure as Panoramio further integrates into Google’s mapping technologies. We will also keep answering e-mails directly as much as possible.

    Oh, and by the way, they also have an API – released just earlier this month…


  • Joe 17:20 on April 17, 2007 Permalink
    Tags: API, CBS, , Robin Berjon, semantic web backend technology   

    Joost Updates 

    Lots of updates around Joost.com, so time for a little blog post again.
    First, version 0.9.2 adds network stability, the video plays almost without any hitches on both of my Macs now. The impressive part is going on behind the scenes: much of the content is coming from the P2P network now many more beta testers are being added. And apparently mixing P2P with traditional streaming has its challenges.

    New content: lots of CBS programs will appear soon. A Dutch proverb says: “if the first sheep passes the bridge, all of them will follow“. Oh well…

    In the mean time, bloggers around the world are getting to the gory details of Joost’s semantic web backend technology. For instance, Joost: It’s The Metadata, Stupid! and Idea: Joost’s missing feature (well, that was in March – the scaffolding for this idea is already in the current betas).

    For me, the next exciting milestone will be the opening of the API for developers. At this time we can only guess what this will look like. But I expect something very similar to the current Firefox plugin architecture, with added SVG goodness (Robin Berjon is working on SVG and Widgets for Joost). In other words: develop your own overlays, with transparency and smooth scalability. Sweet!


    • Lyly 17:37 on April 17, 2007 Permalink

      send me invention to joost to:
      subotaj AT gmail.com

    • Robin Berjon 18:50 on April 17, 2007 Permalink

      As you might expect I cannot commit to an exact feature set (and certainly not a date) at this point, but here is a very rough overview (and subject to change) of what is on the table:

      – yes there will be SVG involved (and XHTML, CSS…), basically you’ll have the capabilities of recent Gecko builds (but with some restrictions)

      – the extension system is “comparable” to that which is found in Firefox, but isn’t the same (largely for security reasons and convenience). Notably, it doesn’t rely on overlays and the extensions are not running with chrome permissions.

      We are still in the early stages but if you have any suggestions as to what you would like to see in there, please don’t hesitate to email me.

    • aleksandar 13:31 on April 21, 2007 Permalink

      I heard about joost but i dont have any friend to sent me an invitation.So can you sent me one please.Thank you buy

    • Agustin 15:47 on May 7, 2007 Permalink

      I also need and invitation to join Joost.

  • Joe 09:56 on April 13, 2007 Permalink
    Tags: API, , ,   

    Google Maps with KML data 

    Some time ago I wrote about the introduction of a new feature for the Google Maps API: you can now use the same definitions file format as with Google Earth (technically speaking this is the KML 2.1 format).

    All cool and neat, so I did a little experiment to try it out. And guess what: it didn’t work! No error messages, just my KML file was completely ignored.

    Well, it appears that KML file must be accessible for Google to read and parse; in other words: it is not the client side API (Javascript) which reads the KML, but the Google service. Apparently what they do is: parse the file, calculate the correct view port and then send over all geo data, back to the client API.

    As I hosted the file on my local computer (http://localhost/), this did not work. Duh!

    This feature was not immediately obvious to me from the API documentation. And it might not be strictly necessary: as long as the KML file is hosted on the same server as the client HTML, the file could just be retrieved through XMLHttpRequest (the same origin policy would be satisfied). Performance might be an issue, though, as XML Parsing in the browser is not very efficient. And setting the viewport for the map would require another round trip and delay.

    Conclusion: be sure to host your KML file such that it is accessible for Google (over http), otherwise it will just not work.

    var geoXml = new GGeoXml('http://www.yourhost.com/geo/map.kml');


  • Joe 11:06 on April 12, 2007 Permalink
    Tags: API, early applications, geeky applications, , , open IM protocol, protypical web   

    Twitter vs Jabber 

    Twitter logoAs you might know, Twitter is the hype of last months. Everybody and their dog are updating their current activities like crazy.

    As a spin off, many secondary purposes are being created on top of the public Twitter API.

    This reminds me of the old days when Jabber was started as an open IM protocol. Lots of geeky applications sprung into life, like monitoring incoming email (headers), keeping an eye on your computer logs and such. Now the Jabber protocol (XMPP) is being used as the basis for a couple of IM platforms, like Google Talk. Many of those early applications are now official a XMPP extension. The platform has matured, but lost its appeal to the geeky crowd.

    Today, these kinds of applications are being built on Twitter by the dozens.
    Without any effort, I found lots and lots of them. I estimate these are less than 5% of all Twitter applications out there, so the list is really getting huge.

    • MoniTwitter (answering one simple question: What’s your website doing?)
    • TwitterIsWeird (displays pairs of twitter quotes in comic balloons)
    • PingTwitter (update Twitter when you publish a new blog post)
    • TwitterChat (2-way live shoutbox-twitter integration)
    • Twitterific (Mac OSX client application)

    And then we have the Twitterforum, an unofficial Twitter related discussions site, listing even more twitter related applications and sites.

    So does the Twitter API popularity have to do with its incredible simplicity? And its pluggability for the protypical web 2.0 platform (yes, it has a JSON interface)?

    I’m not sure, but I hacked togeter my own little contribution to this madness in just half an hour: Browse with Twitter, a Greasemonkey script for Firefox.

    Update your twitter.com status with a message “Browsing: [document.title]” whenever you load a web page.

    Fair warning: don’t install this script if you do value your privacy (or at least restrict it to the sites you explicitly want to show up on twitter).


  • Joe 15:57 on April 2, 2007 Permalink
    Tags: 200 OK;, , API, Baltimore, community vigilance tools, Danny Ayers, Denny Vrandecic, Frank Zappa, front end web application, Green Genes, Hot Rats;, Maryland, Peaches;, , semantic web terminology, web applications   

    Freebase: Life, the Universe, and Everything 

    Just after my post Freebase as productive playground, I recieved an invite (thanks a lot, Ken!) and I have played around a little…

    Now, a lot of relevant things have been said around the ‘net (see my prevous post). And, there have been some in-depth reviews of the model of Freebase, related to the Semantic Web: Denny Vrandecic, Danny Ayers.

    I will not repeat these comments here, rathter give my first impressions as a curious explorer.

    First of all, the Freebase website is very heavy on Ajax, which seems to be almost essential for the functionality provided.
    As a novice user, you are launched at the “User Profile” page. While starting to fill out some profile fields, you are immediately confronted with the Metaweb Object Model (login needed).

    The Freebase Object Model

    The model roughly consists of:

    • Domain (the top level ontology, e.g. ‘music‘ or ‘business‘)
    • Type (a class within a domain, e.g. music/artist)
    • Topic (an individual object, let’s say Frank Zappa as musical artist)
    • Property (attributes, e.g. ‘name’ or ‘date of birth’, or a relation with another Topic)

    So when you start editing your User Profile, you are actually filling out a template of a User Type. Within this type, the attribute “Me as a Freebase Topic” links to an object of class (Type) ‘people/person‘. The distinction is somewhat like the difference between a real world (verifyable) person, and personas this person might use. From the Freebase documentation:

    A person topic is distinct from a user in Metaweb. Users have profiles that can only be edited by the users themselves. A person topic can be edited by anyone and is intended as a factual representation of details about a person.

    A couple of primitive Types exist (e.g. type/intor type/text), but in most cases more complex types are used for attributes. So Place of Birth is not just a text sctring, but an object of type ‘location/location‘. This ensures that all occurrences of ‘Baltimore, Maryland‘ refer to the same object.

    Following the link to this location, you can zoom in further and find that the object is not only of type ‘location/location‘, but also ‘location/citytown‘ and ‘location/us_county‘.

    Queries and results

    Freebase is called a database for a reason: you can run queries against it and get results back. Now being heavily rooted in the semantic web terminology, you might expect to use SPARQL as a query language, and results back in some RDF representation. But this is not the case.

    Both queries and results are expressed in plain JSON, which is becoming the data transport protocol of choice for most Ajax projects and frameworks.
    (More …)

  • Joe 11:45 on March 29, 2007 Permalink
    Tags: access site, , API, Benelux, Bernhard Seefeld, Brandon Badger, CRM, een site, GMaps Utility Library, , , New Foundland and Labrador, open web, Rotterdam, satellite imagery, Sidney Mock, USD, web crawler, web-applicatie te maken, www.nederkaart.nl   

    Google Geo Day 1 

    Google Geo Day, part 1

    Today the google geoday is held in Amsterdam Expo XXI

    The morning programme consisted of three speeches, most about google maps and google earth, focused towards developers who want to create mashups based on the maps API.

    A bunch of quick notes, some in Dutch (with the Dutch speakers mostly)

    (More …)

Compose new post
Next post/Next comment
Previous post/Previous comment
Show/Hide comments
Go to top
Go to login
Show/Hide help
shift + esc

Twitter links powered by Tweet This v1.8.3, a WordPress plugin for Twitter.