It looks like Apple and Cisco have decided to ’share’ the iPhone brand. I think this is a bit odd and possibly silly.

Whether Cisco like it or not, Apple’s useage of the brandname will be always ‘mentally connected’ (that’s kind of what brand awareness is, right?) with their forthcoming Apple phone – not a cordless VOIP Skype handset (which I must say are very good – I have one)

There’s got to be some crazy deal going on under all this, or Cisco’s lawyers are in awe of Apple’s.

Is there such a thing as an ‘Apple Lawyer Fanboy’?

Tara and Chris take the mic
posted by kosso using NOKLOG : [permalink]

Wow! There seems to be no stopping me now! I’m on a roll!

Another podcast for ye.

Today I talk about OPML PLUS RSS TO THE POWER OF USERS and what I am trying to do to make life easier. Also thoughts on the perfect podcast device and mobiles in podcasting.

[audio=http://media.libsyn.com/media/agentkosso/kozcast3.mp3]

DOWNLOAD PODCAST MP3 HERE

Subscribe here

OK. So I have recently been working to support the new Blogger / Google logins to post to Blogger blogs. I was easily able to register my app to remove the warning on the login page, but they offer no support of how to actually ’sign’ the request to keep them secure.

I have posted to both the Blogger Data API Group and the Google Accounts API Group but it seems like I am dealing with some kind of ‘dark art’.

I think it’s a good idea to make connection for secure for people, but they are about to ‘force’ their bloggers to the new system, yet offer no support on how application developers like myself are to support this new ’secureness’.

Even the Zend GData framework, which is available does not appear to handle the secure method required. I also cannot use this without upgrading my PHP and installing some more stuff. But there is no need, as PHP and Curl can do the job required just fine.

For those who may be able to help, here are the docs for the signing I am on about. But there’s just not enough info there on how to do it.

When I get this working, I’ll be happy to share how I did it.

Anyone got any ideas? I have the insecure method working fine.

Argh!

Check it out, Ev Williams has posted that Odeo, their podcasting system is up for sale/partnership.

I think this is great. I wonder how many users Odeo has?

Podcast.com is doing about a tenth of the traffic they state over there, [Uniques: 66,765 Page views: 294,867 over the last 30 days at podcast.com] which I think is not bad considering there are only 4 or five registered users of podcast.com so far, for testing – and three of them are me!

This is encouraging for when we open the doors to sign up. Odeo has some great technology behind their system. In fact I am off out not to see a friend’s company who have just developed something similar – using Open Source

It’s way past time that I met Ev and had a ‘createc’ chat

I’m also interested on how that list of post below his was generated. At first I thought it was a blogger.com thing onlw. Now as I see techment and tailrack in there I know it’s now.  But it is more then simple trackback, as far as I can see. I could be wrong – please correct me. ta.

Dave on Scripting News and Mike over on Techcrunch post their views of OPML used for ‘reading lists’.

This is an important discussion and one close my heart. I commented over on Dave’s (wordpress) blog , but I thought I’d add to it over here:

Re: OPML lists and ‘trees’ – etc expect some along these lines soon:

The system developed behind podcast.com enables just that, it’s just that naturally with podcast.com we are only interested in feeds with audio or video enclosures.

So, podcast.com is a ‘client’ of this larger system which will be able to support all types of ‘types’ – all supporting OPML inclusion.

I don’t think you should call them ‘lists’ – I think ‘trees’ is more descriptive. ‘Reading trees’. People can either ‘climb’ up then to find the ‘fruit’ (content) they want, or they could wait for the most popular to drop into their lap. Also through looking through ‘leaves’ (tags) they can be sure of following the right branches, as they ‘climb’ up the tree, deep and deeper into the directory/tree. (’directree’? )

OPML is the tree
FEEDS are the vines
TAGS are the leaves
ITEMS/ENCLOSURES are the fruit.

The coolest thing about OPML inclusion, is you could think of it like climbing up a tree, going along a branch, and then ‘zap’, you’re in another tree. Like magic. Painless. Rewarding.

Telepordata?

Semantics. Taxonomy. Folksonomy.

Now that’s what I call a ’social media network’

I hope to be able to let some users in to try out the system in the next 4 weeks.

Then people could create something like : http://my.podcast.com/kosso , which is my ‘listening tree’/ podcast folders/ ‘tree of sound’

One reason why I think there are more OPML ‘lists’ than ‘trees’ out there is that there are too few tools out there to effectively manage an OPML file. Your apps have been the best to date (once we got the rss attributes sorted)

I mean managing OPML folders/nodes effectively, over import/export of ‘flat’ lists. So many systems eith dont ‘do’ folders or destroy them on import/export.

Also, I think we really need to evangelise the concept of ‘OPML subscription’ .
OPML files are so often used as static files to import/export bunches of feeds. It is indeed great for backup in that sense. But I believe that ‘OPML Subscription CONNECTS’ all these trees/branches out there. When one branch changes on one tree – if there is an ‘inclusion’ (think of it like a shortcut/symbolic link to a folder) then the other will be able to reflect that if one was to climb that branch.

The trees are ALIVE! So subscribe to them! Watch them grow Feed them, prune them and ‘graft’ ‘cuttings’ to their branches.

We like to call it ‘treedia‘

Clearly for this to work, we also need well defined standards to make sure the data out there is well-formed – or we’re screwed but let’s not make the same mistake the web browsers did, by just displaying html if it was broken or not.

I feel like doing another podcast