³ÉÈË¿ìÊÖ

Very nice. Now can we please have a standard component so that Music Shows such as Get It On can post their playlists to last.fm.

Look: , so the API must already exist...

We do that for some shows like so we should be able to do it for Get It On. I shall try and find out...

Whats with the blatant promotion of Pure

"By machine-tagging these photos you will be helping machines connect things together and create new paths for people to find both ³ÉÈË¿ìÊÖ programmes and your photos."

Wow, what a great way of targeted 'spamming', up load a load of product images and then "machine tag" them to popular programmes, web-sites or what ever!

I don;t think the ³ÉÈË¿ìÊÖ has possibly thought the idea of linking to such machine tags out, even more so if one is going to use the tags to embed content from sites like Flickr, up load a legitimate photo, wait for it to be linked to (it will be a trivial task to monitor when such links have occurred) and once it has then replace the image with your spam or other unwanted content and as long as the image doesn't break Flickr's AUP/T&C Flickr won't do a think as they will be getting the extra click-throughs...

@Boilerplated - agreed, that is a risk if we automatically linked out to those images so we'd probably always have a level of human moderation in there. And although spammers could replace their images, they would have to have tagged a pretty relevant image for it to have been linked in the first place which seems a little unlikely?

#5. At 09:41am on 25 Aug 2009, tristanf wrote:

"And although spammers could replace their images, they would have to have tagged a pretty relevant image for it to have been linked in the first place which seems a little unlikely?"

Not really, and what is more, how are you going to cope with the archiving of your own web pages etc. if the external content could either change or vanish - sorry but whilst I can see why linking to this sort of 'social media' content sounds good in theory, in practise it's a time delayed bomb waiting to explode in the face of the ³ÉÈË¿ìÊÖ, you will have to carry on monitoring (physically checking with human eyes) all pages that carry such content in perpetuity otherwise ³ÉÈË¿ìÊÖ web pages could be carrying anything from the correctly sought image through image-spam to sexually graphic images - hackers will have a field-day in the future seeing who can get the ³ÉÈË¿ìÊÖ to embed the most outrageous content... :~(

Oh, and who is the ³ÉÈË¿ìÊÖ going to know were to send the royalties for the use of someone else's intellectual work?!... ;-0

I found myself thinking along similar lines to Boilerplated.

Tweets are one thing; as far as I am aware they can not be retrospectively edited (though I believe they can be deleted or locked). But photos, videos, etc. can be edited - therefore there is always a risk.

This could be a nice way to create Twitter trends for a particular programme. Unfortunately, the tag's a bit too long for Twitter. How about #bbc:pid=b00lj1nc or even just #bbc:p=b00lj1nc.

Re: spam remarks. I've just looked on Flickr, and I can't see any way to change a photo besides tweaking it. Surely if someone uploaded a new picture, it would have a different identifier? I doubt this new toy is going to have the audience to attract spammers anyway.

#5. At 09:41am on 25 Aug 2009, tristanf wrote:

"@Boilerplated - agreed, that is a risk if we automatically linked out to those images so we'd probably always have a level of human moderation in there."

Yes, and all the time that any such page is extant - one doesn't have look around the ³ÉÈË¿ìÊÖs own blog network to hard to find comments, which have no topical relevance to the subject of the blog (or even any thread-drift) discussion, that have been added to old blogs long after the discussion ceased, some of which is blatant spam or mischief making, to see how people could miss-use 'old' web pages that have embedded content.

"And although spammers could replace their images, they would have to have tagged a pretty relevant image for it to have been linked in the first place which seems a little unlikely?"

The more I think about this the more I think the real problems will come from those with malicious intent (against the ³ÉÈË¿ìÊÖ) or those who 'hack for kicks', it's one thing relying on your own organisations security policy, AUP or T&Cs but what is being suggested here is a complete out-sourcing of such polices.

Relying on some external web sites operational policy (as suggested by "smiler_jerg") of not allowing an existing file to be replaced by another whilst keeping the original file name is very high risk, all it requires is a change in their policy and the ³ÉÈË¿ìÊÖ's relevant security policy has flown clean out the window...

I'm not against the machine tagging, I can see it being really useful for the end user (or even the ³ÉÈË¿ìÊÖ for internal research use etc.), it's the suggestion that someone like the ³ÉÈË¿ìÊÖ could then go on and use embedded content from such external sources.

In april 2008 Radio 4's Broadcasting House asked its listeners to add their flickr photos of their radio to this Radio4BH flickr group

join the group (some policing may be possible here) and you are free to add your photos to the group. it worked for that programme and while it is the smallest sample of one case study there were no issues. Now a ³ÉÈË¿ìÊÖ meta data layer in the cloud could tag items in that group, notice who is doing the tagging, not the end user, this is not only shifting the chance of misuse but also shifting the burden of accuracy to the ³ÉÈË¿ìÊÖ.

So see it as a two step approach, corral the images near the programme and ³ÉÈË¿ìÊÖ sweep in and tag, a bit like the googlebot indexes content, and images can be id'ed as safe or not (note not tagged safe/unsafe but detected).

Having said all this by the time its implemented to scale we will all be able to hear 'radio through the "waves"' like google waves. Trusted islands of collaboration, listeners, corporation, programme guest, staff and the wider community. By then the two step approach becomes one step and the tagging in not auto but implied as images shared are internal.
just my 2cent regardz brian greene

Tristan:

Thanks, for the excellent resource about tagging....

=Dennis Junior=