|
||||
|
Tuesday, September 30
[09:25AM EDT]
The great thing is that if voters type in the wrong vote, Verisign has the technology to point them in the right direction.
[via Boing Boing Blog]
C (2) |
T (82) |
#
Monday, September 29
[05:59PM EDT]
For reasons that I can't go into, Joey "AccordionGuy" deVilla and I have decided that this coming Friday, October 3, 2003 is "First Annual 'Post A Picture of A Cat to your Blog' Day" aka "BlogACatMas".
The celebration is very simple - just post a picture of a cat in your life to your blog. You can even caption the photograph with some kitty-centric witticisms (kittycisms?) if you want. It doesn't have to be your cat or a real cat (but it could be a KitKat) but it does have to be a picture that you, or someone you know, took. Bonus points for pictures of wet cats or cats in hats, negative points for kittens. Send me your links and I'll start a "CatRoll" here on Random Bytes. C (16) | T (215) | # Friday, September 26
[09:17AM EDT]
Scott Mace wonders where Elliot's RSS is.
There are a couple of ways to find out where any specific Blogware feed might be - first, all of the default blogware templates have a Syndication link in the header bar of each page. The default one links to the root RSS feed (in the format of the publisher's choosing) that sits in the root directory of the blog. ie http://www.byte.org/blog/index.xml Publishers can also choose to add a link to this header bar that point to their category RSS feeds - I've done this on byte.org, Elliot hasn't on e-Land. We turn it off by default because it can be a little bit confusing for the average bear. The trick in finding this is pretty straightforward - they are predictably found at http://blognhostname/blog/directoryname/index.xml - or - If you really want to get fancy, you can grab a directory of all of a blog's available feeds by parsing http://bloghostname/blog/ocs.xml We've got a few more surprises in store, RSS-wise - I'll definitely blog about them as we release the new functionality. C (1) | T (83) | #
[08:26AM EDT]
NewzCrawler v1.5 final is out. If you are using an aggregator you should be using this one. If you're not using an aggregator, you should be. And it should be this one ;)
[via NewzCrawler]
C (4) |
T (51) |
#
Thursday, September 25
[06:29PM EDT]
John Robb and Dennis Kennedy are blogging back and forth about John's viewpoint that aggregators are more important than weblog tools.
They are both half right. The really important tool is the one that does both. The fact that they are typically found in different apps right now is just silly. Like a video camera that requires an external monitor with no builtin viewscreen to allow you to "create" and "consume". Every single killer internet app that I can think of off the top of my head has allowed users to create and consume - except the web. I submit that the only reason that weblogs and aggregators aren't usually found under the same hood is because they are usually web apps. If Blogger had started out on the desktop, it would probably allow for some really cool two-way interactions. Like Radio. C | T (23) | # Wednesday, September 24
[08:36AM EDT]
Elliot is blogging again. I don't think he could have had a better "coming out".
C (2) |
T (62) |
#
Tuesday, September 23
[03:04PM EDT]
Verisign claims that Sitefinder doesn't violate any technical standards and therefore, there is no cause for concern. But, the question that they are avoiding is whether or not they feel that they have violated the trust relationship with the community that they have been appointed to serve. In most respects, RFC 1591 has been obsoleted by service contracts and zone delegation agreements. It no longer defines how these types of relationships work. But, it did define community expectations when Network Solutions received their original grant to operate .com and .net - do we still feel this way today? What follows is a digest version of the relevant parts of 1591 that I still expect a registry operator to follow when operating the zone that we have entrusted them with. ...excerpts from 1591 C | T (361) | #
[09:14AM EDT]
As Darryl pointed out here first on a Tucows internal blog, this Eliyon thing just doesn't work at that well - unless I somehow missed the period of time that Kobe Bryant and Mac Astronomica were on Tucows' board of directors.
"To stupidity and beyond!" Indeedy. [via John Robb's Weblog]
C (1) |
T (20) |
#
[08:34AM EDT]
In a move that has fooled no one, VeriSign refuses to budge on redirection bodge, but has committed to creating a technical review board that will consult with, not make recommendations to, Verisign regarding Sitefinder. Verisign, despite having some of the finest minds in the business on their payroll, seems intent on making a fool of the internet community and themselves before everything is said and done. In a letter to ICANN, Rusty Lewis, the head honcho in Verisign's registry operations (and quite a nice guy actually), stated that "...all indications are that users, important members of the Internet community we all serve, are benefiting from the improved Web navigation offered by Site Finder... As to your call for us to suspend the service, I would respectfully suggest that it would be premature to decide on any course of action until we first have had an opportunity to collect and review the available data. After completing an assessment of an it would be premature to decide on any course of action until we first have had an opportunity to collect and review the available data." Rusty needs to hear two things. First, users being confused by the service - end users, developer users, operator users and registrar users. EVERY single internet user is somehow being negatively affected by the implementation of this "service". Putting a dress on it and calling it "an enhanced navigation service" doesn't means that its benefits outweigh its drawbacks. Rusty also needs to hear is that Verisign has absolutely no right to arbitrarily change the way that the internet's core infrastructure works before *we*, the community, "first have had an opportunity to collect and review the available data" prior to the introduction of any service that monkey's with the way that my internet works. None. This isn't about what the contracts or the RFCs say, rather, its about the moral obligation that Verisign has to the community to provide the service that we expect. ICANN's solution can be very simple. Require that DNS resolution be run separately by a not-for profit entity that receives its policy directly from ICANN. In this environment, the registry protocol interface could be modified in such a way that the registry operator becomes an unnecessary artifact. I've discussed this option with other registrars - we believe that it could technically work. Will Verisign push the community far enough that consensus would view this as a viable alternative to the current regulated monopoly infrastructure? [via Moreover - ZDNet]
C |
T (61) |
#
|
Blogroll 2.0
Make a Donation to the Tour For Kids!
Search
![]() "Random Bytes" is a produced for and by Ross Rader. Everything else is just a happy byproduct. The views expressed here belong to me and not my employer.. Contact Me
Feel free to use my contact information to get in touch for work related items. email: ross@tucows.com tel. +1.4165385492 cel. +1.4168288783 MSN. ross@tucows.com Local Topics
Recent Articles
Recent Comments
Recent Visitors
jamessmithforum - Tue 15 Dec 2009 03:21 AM EST
ahmed100 - Tue 08 Dec 2009 06:49 AM EST
Andrew C - Fri 04 Dec 2009 09:57 PM EST
maxvoice - Mon 30 Nov 2009 06:33 AM EST
ahmed1212 - Thu 19 Nov 2009 09:20 PM EST
Login
|
|||
|
||||


