Earlier this morning we reported on the AP's new content tracking system and already we're seeing the blogosphere light up with cries of nefarious intent. Nevertheless, just to prove that content tracking may not always be about serving DMCA take down notices, Creative Commons featured the Tynt Tracer tool in a morning blog post.
Sponsor
Tynt Tracer is a few lines of JavaScript that automatically add license and attribution information to a user's clipboard when they copy text. This method of attribution is not mandatory, nor is it really enforceable as re-posters can always remove the 3 lines of code. Nevertheless, this tool certainly makes attribution convenient.
As an additional plus, Tracer adds, "Our data shows that those pages that users engage with most are not necessarily those with the most page views." With Tracer, publishers can find out their most sought after information and increase the relevancy of their resources to readers. Creative Commons is already using Tracer to see what readers are highlighting, copying and redistributing.
As well, Creative Commons' Fred Benenson encourages members to consider using the tool. He says, "As a creator and contributor to the commons, you have the right to attribution (all six of our licenses require it), so why not make it easy for your audience to automatically provide it?"
To test Tracer, members can register at Tynt.
Read more:
http://creativecommons.org/weblog/entry/16060#ixzz0MCiF2lSE
Under Creative Commons License: Attribution
http://tracer.tynt.com/features-and-benefits-of-tracer#ixzz0MCg9SuUl
Under Creative Commons License: Attribution No Derivatives
Discuss
Font faux pas happen all around us. Last night while you slept, someone wrote an entire sentence in Night Sky. While you ate breakfast, a notice about martial arts Shanghaied your inbox. And by the time you started work, thousands of grade school teachers typed their lesson plans in Comic Sans.
Sometimes poor typography is an honest mistake and sometimes it's bad judgement. In the same way that I love cringeworthy headline puns, you should be free to experiment as a web typographer. However, due to the limitation of web-safe fonts, the world might be missing out on your creativity.
Sponsor
The Microsoft and Apple camps simply can't agree on a catalogue of core fonts and Night Sky, Shanghai and Comic Sans do not render across all browsers without the help of a web-native font solution. For those who are unwilling to sacrifice looks for functionality, here's an explanation of 4 solutions to make your serif's sing.
1. sIFR (Scalable Inman Flash Replacement): sIFR is an open source typography solution that uses a combination of JavaScript, CSS and Flash to replace browser text with prettier web-native text. Essentially, you're playing a Flash layer on top of the original web text. SIFR co-creator Mike Davidson blogs about it as being "a method to insert rich typography into web pages without sacrificing accessibility, search engine friendliness, or markup semantics." Critics argue that the option is slow to render in certain browsers. Nevertheless, sIFR is an extremely popular solution amongst designers and the simplified embeddable sIFR-based Font Burner is quickly gaining users.
2. @font-face: @font-face is a CSS rule where web designers reference a hosted typeface. Dave Rosenberg wrote a great piece about Firefox 3.5's addition of the rule. Some designers prefer to use @font-face as it does not require viewers to have Flash installed; however, the solution is not available across older browsers. As well, Rosenberg notes that, "As with any linked asset, there is some level of security risk if a hacker gets their hands on the font file."
3. Cufón: Cufón aims to be a sIFR alternative. Essentially, the solution allows designers to upload fonts, convert them to a proprietary format and render them using JavaScript. This solution overcomes sIFR's speed issues as it is faster to render in Internet Explorer (since it uses VML) and it does not require the use of a plug-in. It also addresses @font-face's security issues because uploaders retain control of the font files.
4. TypeKit: Judging by the fact that Evan Williams, Caterina Fake and Matt Mullenweg just invested in Small Batch Inc's upcoming TypeKit, font designers might just get the recognition (and possibly pay) they deserve. While we're unsure how this project will take shape, thanks to a TypeKit blog post, we do know that Small Batch is "working with foundries to develop a consistent web-only font linking license." Naysayers already speculate that the solution will be slow and costly to website owners, but the legal implications of this tool may open up typeface options for designers.
Discuss
