The NYTimes and LinkedIn are announcing a partnership this evening that will bring tailored headlines in the NYTimes Business and Technology sections to users based on some of their profile information. The example the NYTimes uses: LinkedIn members who work in the energy sector will see Times stories that cover the energy business. Users can also share stories with other LinkedIn users (this feature adds LinkedIn to the list of other bookmarking services like Facebook, Mixx, etc.).

Very interesting. We met with Matt Mullenweg and Toni Schneider earlier this spring, and one thing they talked about is how large publishers are moving to implement customization without logins… So this is a really interesting way to accomplish that: allow users to your news portal to customize their experience based on preferences at their preferred social networking site… I.e. help your users leverage their time investment elsewhere and re-use that investment at other sites. That’s a real win-win: it helps a user to have a better experience at multiple sites on the web based on their time investment at another site. You as a news provider maybe gain a returning visitor and they get better experiences on your web site.

So if you are Fox News, maybe your foxnews.com home page can be customized based on some preferences of your myspace… Or your CNN home page might be customized based on your Facebook prefs…

Update: Note to self - how can this tie in with the OpenID stuff that I can not get out of my brain? And just noted today as well (myspace becoming an OpenID provider)… Seems the user customization/personalization bit is right there… Tie prefs back into OpenID and allow other services to consume it. Social networks like Facebook, myspace, Linkedin etc. become OpenID providers and expose user prefs. Users can then login to NYT, foxnews.com etc. with their social network OpenID and their home page is already personalized according to their existing profile…

Another update: The above already exists… Less than a month ago MySpace released their MySpace Data Availability tools:

Developers can access any publicly available profile data from a MySpace user and integrate it into their site. This includes a user’s name, picture, bio, social graph (list of friends), and other information. Users authorize the data transfer via a one-time secure OAuth login to MySpace from the third party service. The service is then allowed to access the data.

That’s really something… OpenID + OAuth …

So first there was the online creation of pretty simple items like business cards and T-shirts - businesses which cut out the old middle-man way of doings things. Soon there will be a way to create and “print” objects in 3D on a mass scale, and the first of these is starting to arrive. Netherlands-based Shapeways is launching a private beta of a community for consumers wanting to create real objects. Eventually you’ll be able to share and co-create online as well.

Cool.

MySpace will announce support for the OpenID single sign-on framework sometime this week, we’ve heard from multiple sources. This will be the second largest implementation ever and will bring the total number of OpenID-enabled accounts to over half a billion. MySpace’s 200 million user IDs join Yahoo’s 250 million or so accounts, plus accounts from a number of other large providers.

This is pretty big, assuming it’s true. MySpace will initially only become an OpenID Provider the article says, but not a consumer of OpenID. So you will be able to use your MySpace login to access other sites which support OpenID, but not use your OpenID to create or login to a myspace account.

I was checking yum for updates on one of my Plesk servers and did yum update caching-nameserver … Bad move. It blew away the Plesk named.conf file and killed named on the box.

Here’s what you need to do to get it back:

1. First remove the rpms: yum remove caching-nameserver

2. Next, re-install the default file: cp /var/named/run-root/etc/named.conf.default /var/named/run-root/etc/named.conf

3. Now create a little shell script (found the info here and here), call it dns_rebuild.sh and run that script.
4. Lastly restart named with service named restart and you should be good to go.

Sounds easy now but that took 2 hours… Hopefully this note will save someone an hour!