bioneural.net site preferences

Accessibility

Toggle width/ text size:

style

Default/Alternate

Suits visual impairment, mobile devices

Styling

Change the theme:

layout

Sorry, this option is not enabled

Link behaviour

Links with an icon are off-site:

links

Right-click any link to optionally open in a new window or tab


Tag archive for 'webdev'

 

Twitter release per-tweet geotagging API

Twitter's geotagging API is official. There is now a checkbox to enable geotagging in your Twitter account settings; enabling this option allows third party applications to annotate individual tweets with location data. Developers could previously integrate only profile location with the Google Maps API as here.

 

Share Twitter locations using Google Maps

With my tweets integrated into WordPress the next challenge was to integrate my Twitter location with my custom Google Map. This recipe uses a WordPress theme functions.php file and the excellent Geo Mashup plug-in for WordPress. One advantage of this method is that you don't need to add custom location tags to each tweet (as you do for example here using Pipes). This method simply reads the location as set in your Twitter profile until you change it (and tweet again).
Continue reading 'Share Twitter locations using Google Maps'

 

Geo Mashup implementation guide

Geo Mashup is one of my favourite WordPress plug-ins (and no, that's not just because it adopted the Geotag Icon). It neatly integrates geographically-relevant blog posts with a custom Google Map displayed within your own site. The Maps API in turn allows those willing to dirty their hands with a little JavaScript the option to pull in geotagged content from external sources, including photos (e.g. from Flickr, Panoramio, Picasa Web Albums), content from other blogs (via GeoRSS feeds), and placemarks from Google Earth (uploaded KML/ KMZ files, even with network links). What follows is an implementation guide, sharing some usage tips and the code used on bioneural.net.
Continue reading 'Geo Mashup implementation guide'

 

Gearing up for SSL to WordPress with Safari

A friend brought an impending WordPress security exploit to my attention, in the form of a CookieMonster. Your data might be at risk if you administer your blog from a public Internet connection (e.g. WiFi in a café). Securing your authentication cookies with Secure Sockets Layer (SSL) provides a defensive countermeasure for your admin loggins, and WordPress.com users now have a checkbox to "Always use HTTPS when visiting administration pages". That checkbox is absent in self-hosted WordPress 2.6.2, but here's how to enable HTTPS and accelerate your admin sessions using Google Gears via Safari.
Continue reading 'Gearing up for SSL to WordPress with Safari'

 

Fire Eagle from Yahoo! aids location sharing

Fire Eagle is a free service from Yahoo! that provides a conduit for updating a centrally-stored current location, permitting delivery of location-aware services by means of an API allowing developers to resolve and share user location across various applications. Care has been taken to address privacy concerns by keeping choice in the hands of users, who can update their location manually or automatically from "anywhere". For example, Fire Updater on your MacBook might put you in a London hotel, while subsequent telemetry from SearchQuest GPS on iPhone tells your mates which pub to find you at; at least one WordPress plug-in is in development.

 

Publicizing WordPress post revisions

WordPress 2.6 introduced post revisions, a form of version control that allows you to review or revert to previous editions of a post or page on your WordPress blog. The value of this feature has generated some debate, largely because it's "on by default" with no easy toggle to disable it. The thing is notification of post revisions is private, within the admin interface. So how do you make the date of last editing public?
Continue reading 'Publicizing WordPress post revisions'