IceRocket is a pretty neat search engine. I think it’s still pretty new. It’s got some pretty neat features. My favorite is the ability to search blogs. Caribbean Free Radio had a little to say about it:
Having fun with IceRocket, a search engine which allows you to search blogs. Especially like the fact that it can list results in chronological order and create RSS feeds of searches.
I haven’t seen the icerocket bot crawling any of my pages, but I have gotten a few referrals from the engine somehow. The IceSpy feature is pretty neat too. It lets you see in real time what other IceRocket users are searching for.
Popularity: 1% [?]
This site was experiencing some DNS issues lastnight that made it unavailble for most of the night. These problems have since been resolved and it should all be working again. Not really sure what caused the problems in the first place. I think EveryDNS might have been having some problems that caused it. EveryDNS is where I host my DNS. They have an awesome setup! I wish hosting providers would let you manage your own DNS like EveryDNS does. EveryDNS should try selling their interface to hosting companes, I bet they could make a killing. They even have dynamic DNS.
Popularity: 1% [?]
This is a pretty neat item in the Google Labs right now. It’s basically a personalized Google homepage. So now when I go to http://www.google.com/ig, see something like this. I had to re-arrange the items to fit.
Here’s some of what Search Views had to say about it:
Search Engine Journal has coverage of the Google Personalized Homepage, the beta version of which was revealed at the Google Factory Tour today. The personalized homepage is scheduled to be listed in Google Labs, but we’re not showing it just yet.
In addition to being a competitor for the personalized services of Jeeves, MSN, etc. the service is a way for Google to tie all of its subscription services into one offering, though no RSS aggregation yet (boooooo).
It’s nice to have all that right there. My gmail, weather, and news. Barry @ Search Engine Roundtable also points out this is being discussed on many forums.
Popularity: 1% [?]
WordPress 1.5.1.1 stable is out. I think this release was prompted by the trackback/pingback bug I mentioned earlier. It does indeed seem to be fixed now. After I deactivated the BlogTimes plugin, I could send trackbacks no problem. Here’s what’s said on the WP dev blog about the update:
Update: In our effort to optimize we made two mistakes in 1.5.1, one related to feeds and one related to trackbacks and pingbacks. We’ve updated the download with 1.5.1.1 which corrects these bugs and a few others.
So I guess I don’t really know if my problem was related to that bug or not. I’m just glad I can send trackbacks again. It was announced in the same post as the 1.5.1 announcement on the WP development blog.
Popularity: 1% [?]
Saw this via the Broadband Blog this morning. I downloaded the new beta bittorrent client yesterday, compiled it, and it failed horribly. Dunno know why as I didn’t research it much.
Anyway, here’s the news as reported by Om Malik.
itTorrent’s new version is easier, better and well simpler. In other words, it is trackerless which essentially means “that anyone with a website and an Internet connection can host a BitTorrent download.” The torrent tracking tasks instead of the server, are now off loaded to the client. Downside, well not for users, for MPAA maybe. Many times downloads can kill you with high bandwidth bills. However with the new version, well website operators can simply use the efficient download paradigm of Bit Torrent and can get “broadcast TV” economics working for them.
This looks pretty neat. Previously, you’d have to use a tracker to distribute your files, which was kinda confusing to users. This new trackerless BT is more confusing to me than the previous tracker versions. Trackers are still supported in the newer versions. You can get new releases of BitTorrent from BitTorrent.com.
Popularity: 2% [?]
I’ve been experiencing some issues with sending trackbacks in WordPress 1.5.1.1-beta as of this afternoon. I did an “svn update” to update my local wordpress folder and I was updated to revision 2612 from subversion. There’s a bug report here that relates to what I’m experiencing. It seems the latest revision, 2612 has fixed the problem for some users. Unforunately, the problem started with rev. 2612 for me, which doesn’t make much sense.
If I don’t see something new in subversion by tomorrow afternoon to fix it I’ll probably just revert back to a stable 1.5.1 install.
Popularity: 1% [?]
