Not exactly new, and will probably work itself out over the years. In Ye Olden Times (like five years ago), search for anyone who had ever authored an RFC would return 10.000 mirror sites with the same RFC. These have now been "collapsed" somehow, so that only one hit gets back. I expect that if the problem gets intense enough, the same thing will somehow happen with Wikipedia articles.
My rule of thumb is that perhaps 1 out of 200 Linux users register with the counter - but there doesn't seem to be a reason for Australians to register in larger droves than the Americans.
Guess they just don't tell their bosses about it....
What is written above is just a short story of everything that went on during last year. I also do not want to give out too much information, since it wouldn't be wise.
In the US, this would probably have said "after taking advice from my lawyer, I have decided not to say anything more".
1W = the amount of power required to heat 1g of water 1 degree celsius in 1 second (1 J/sec). 1 cup of coffee: 0.2 litres (200g) heated from 10 to 100 degrees celsius (90 degrees) = 18 KJ. 250 KW: 14 cups of coffee per second.
The answer to "where do we put these puppies"? Next to Starbucks.
if you look carefully at the picture of the ROAD "linux clamshell" linked from the article, you will see the top left hand of the window saying something like "Win.... ROAD" - and the GUI is clearly a Windows (clone?). talk about reimplementing the dominant paradigm.....
I've used Mulberry for years - it's one of the few clients that I can use in a sensible way to handle hundreds of emails per day. What I'll miss is the multi-pane mode. Every mail client (including Mulberry in later versions) supports the 3-pane mode where the list of folders is to the left, the list of messages is on the top and the message you're previewing/reading is on the bottom. But with Mulberry, I can have a window with my folders on the left side of my screen, open up 4 folders at the same time, open up 7 different messages and cut/paste between them, start replying to one and go back and look through archives to find the point I wanted to make.... all in DIFFERENT windows.
What other client can offer me that (and disconnected IMAP, too)?
I discovered the other day that some people, when they talk about "responsible disclosure guidelines", actually have a specific document in mind - but can't be bothered to include the URL. The document's title is "National Infrastructure Advisory Council - Vulnerability Disclosure Framework - FINAL REPORT AND RECOMMENDATIONS". Here it is: http://www.dhs.gov/interweb/assetlibrary/vdwgrepor t.pdf
a simiar project has been going on at the Linux Counter for years - not every 10 minutes, and not specifically for beta kernels, but still, it's fun to watch the report once in a while.
Tidbit: Linux 2.6 is now running on more than half the computers tracked.
This document describes the Atom format for syndication. It is XML-based and is considered to be the successor to the earlier RSS formats. Its primary use is for web-based content, but is expected to be used for non-web content as well, such as personal news feeds.
Working Group Summary:
Some members of the working group remain unenthusiastic about some sections of the document, but the chairs strongly believe that there is rough (or better) consensus in support of the document as a whole. For some of the parts with the most contention, there cannot be more than very rough consensus due to basic differences in the way people would design parts of the format, particularly given that we have many models in existence with the different flavors of RSS. For some parts of the document, there is contention about whether or not a particular item should or should not be in the Atom core versus being an extension. For some parts, there is contention whether there should be MUST/SHOULD/MAY leeway for content creators in the presence or absence of an element, or the semantic content of an element; the group really pushed RFC 2119 around during the past few months.
Protocol Quality
Scott Hollenbeck and the XML Directorate have reviewed the specification for the IESG. Test implementations have confirmed basic protocol soundness.
Being a frequent participant in transatlantic phone conferences, I've always dreaded the Week Of Confusion in March where the US has changed its clock and Europe hasn't (or was it the other way around?). Half the participants late (or early) by one hour, almost every time. Now I understand that's going to be 2 months of confusion a year. THANK YOU, Mr. Bush!
Political statement in what it does NOT do
on
.tel Coming Soon
·
· Score: 4, Interesting
If ICANN has accepted this request, it is a very subtle political statement. Check out section 15.1.1 of the application - "Avoiding established addressing systems and regulations" - it promises NOT to try to put phone numbers in the.tel domain. Other.tel proposals have suggested exactly that, and this has had ITU in a tizzy. By registering this utterly useless.tel TLD, ICANN is making a statement that it will not create TLDs that say up front that they're out to upset the ITU national regulators' club and its telephone numbers fun-and-games. I'm neither surprised nor unhappy..tel as described is utterly useless, but the other proposed usages of.tel had a potential to cause damage in addition to being useless.
I've got a web page with the greylisting database stats for my mail server at my webserver. It shows on the low side of a thousand messages being held by SQLgrey's block at any given time - which translates to less than a thousand spams per day blocked. It's a significant decrease in spam getting through, but no panacea.
Periodically there are proposals to mandate the use of a special top
level name or an IP address bit to flag "adult" or "unsafe" material
or the like. This document explains why this is an ill considered
idea from the legal, philosophical, and particularly, the technical
points of view.
Of course, RFCs have no force. But I think he argued the point well. Oh well. The fact that something's stupid has never prevented people from doing it. Especially where sex is concerned.
For the isolated question of what the split of work between IETF and ICANN *is*, see RFC 2860, "Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority". The bigger question of what it *should be*.... is a bigger question.....
What? And deny Verisign the right to be the Domain Provider To The World?..... and believe me, quite a few of those people who designed IDN have not only glanced at, but READ the Unicode book......
SIGH. And convince the Russians that when they write text in Russian, they need to write the "C" character in the Latin character set because it looks too much like a Latin C, despite the fact that it's pronounced "S". And convince the Greeks that they need to rewrite their upper/lowercase conversion to make sure the uppercase Alpha is represented by a Latin uppercase A, but the lowercase alpha gets represented by a greek alpha, because it doesn't look like a Latin lowercase a. Get real. Homographs are here to stay.
in the Museum of Modern Art in San Francisco. The most bizarre part of the visit was standing behind a group of "cultured" people discussing whether the inclination of the piece served to detach it from its function so that its true beuty of form could be seen.... to me, it was obvious that Duchamp's main purpose in creating the piece was to create the controversy around it.... as such, one should regard the descriptions of the controversy on the wall of the museum as at least as much a part of the "art" than the urinal itself.
He succeeded. Brilliantly. The shape of the object had (IMHO) very little to do with it. And the comments (apparently completely serious) I overheard show that we still need that kind of challenge.
"Joke" foot on article: check.t mp ace
Suspicious URLs:
http://www.rebelscience.org/Crackpots/notorious.h
http://www.rebelscience.org/Crackpots/nasty.htm#S
Check.
Comments taking the article 100% seriously: check.
This must be Slashdot.
Not exactly new, and will probably work itself out over the years.
In Ye Olden Times (like five years ago), search for anyone who had ever authored an RFC would return 10.000 mirror sites with the same RFC. These have now been "collapsed" somehow, so that only one hit gets back.
I expect that if the problem gets intense enough, the same thing will somehow happen with Wikipedia articles.
United States of America: 24797 registered users, 86.73 users/Mpop
Australia: 2338 registered users, 120.90 users/Mpop
New Zealand: 687 registered users, 177.06 users/Mpop
A lot more Linux users per capita Down Under than Out West.
The Linux Counter has more.
My rule of thumb is that perhaps 1 out of 200 Linux users register with the counter - but there doesn't seem to be a reason for Australians to register in larger droves than the Americans.
Guess they just don't tell their bosses about it....
Get Counted!
From video.google.com Help Center:
How can I tell if a video is copy-protected?
You can determine whether a video is copy-protected during the purchase process: if a video is only available for Windows, it's copy-protected.
depends on what things you choose as facts....
DOGMA, THEREFORE TRUE: Information wants to be free
SAID, THEREFORE TRUE: Mythbusters doesn't want to be free
FROM THESE TWO FOLLOW: Mythbusters is not information
The conclusion makes me suspect that one of the premises may be invalid....
In the US, this would probably have said "after taking advice from my lawyer, I have decided not to say anything more".
I wish him luck.
1W = the amount of power required to heat 1g of water 1 degree celsius in 1 second (1 J/sec).
1 cup of coffee: 0.2 litres (200g) heated from 10 to 100 degrees celsius (90 degrees) = 18 KJ.
250 KW: 14 cups of coffee per second.
The answer to "where do we put these puppies"?
Next to Starbucks.
if you look carefully at the picture of the ROAD "linux clamshell" linked from the article, you will see the top left hand of the window saying something like "Win.... ROAD" - and the GUI is clearly a Windows (clone?).
talk about reimplementing the dominant paradigm.....
I've used Mulberry for years - it's one of the few clients that I can use in a sensible way to handle hundreds of emails per day.
What I'll miss is the multi-pane mode.
Every mail client (including Mulberry in later versions) supports the 3-pane mode where the list of folders is to the left, the list of messages is on the top and the message you're previewing/reading is on the bottom.
But with Mulberry, I can have a window with my folders on the left side of my screen, open up 4 folders at the same time, open up 7 different messages and cut/paste between them, start replying to one and go back and look through archives to find the point I wanted to make.... all in DIFFERENT windows.
What other client can offer me that (and disconnected IMAP, too)?
Guess we've managed to test the scalability of the implementations already.... cute names, though!
I discovered the other day that some people, when they talk about "responsible disclosure guidelines", actually have a specific document in mind - but can't be bothered to include the URL.r t.pdf
The document's title is "National Infrastructure Advisory Council - Vulnerability Disclosure Framework - FINAL REPORT AND RECOMMENDATIONS".
Here it is: http://www.dhs.gov/interweb/assetlibrary/vdwgrepo
Tidbit: Linux 2.6 is now running on more than half the computers tracked.
does anyone have real info on which version numbers of RSS (and according to whose spec) works with the Microsoft implementation?
Sounds like the ideal box for an IETF plenary - 800 geeks in one room, all with their laptops out....
that this happens on the day after the IETF announces that it's approved the ATOM syndication format?
o mpub-format-11.txt
Announcement reproduced below:
The IESG has approved the following document:
- 'The Atom Syndication Format' as a Proposed Standard
This document is the product of the Atom Publishing Format and Protocol Working Group.
The IESG contact persons are Scott Hollenbeck and Ted Hardie.
A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-at
Technical Summary:
This document describes the Atom format for syndication. It is XML-based and is considered to be the successor to the earlier RSS formats. Its primary use is for web-based content, but is expected to be used for non-web content as well, such as personal news feeds.
Working Group Summary:
Some members of the working group remain unenthusiastic about some sections of the document, but the chairs strongly believe that there is rough (or better) consensus in support of the document as a whole.
For some of the parts with the most contention, there cannot be more than very rough consensus due to basic differences in the way people would design parts of the format, particularly given that we have many models in existence with the different flavors of RSS. For some parts of the document, there is contention about whether or not a particular item should or should not be in the Atom core versus being an extension. For some parts, there is contention whether there should be MUST/SHOULD/MAY leeway for content creators in the presence or absence of an element, or the semantic content of an element; the
group really pushed RFC 2119 around during the past few months.
Protocol Quality
Scott Hollenbeck and the XML Directorate have reviewed the specification for the IESG. Test implementations have confirmed basic protocol soundness.
Being a frequent participant in transatlantic phone conferences, I've always dreaded the Week Of Confusion in March where the US has changed its clock and Europe hasn't (or was it the other way around?). Half the participants late (or early) by one hour, almost every time.
Now I understand that's going to be 2 months of confusion a year.
THANK YOU, Mr. Bush!
If ICANN has accepted this request, it is a very subtle political statement. Check out section 15.1.1 of the application - "Avoiding established addressing systems and regulations" - it promises NOT to try to put phone numbers in the .tel domain. .tel proposals have suggested exactly that, and this has had ITU in a tizzy. .tel TLD, ICANN is making a statement that it will not create TLDs that say up front that they're out to upset the ITU national regulators' club and its telephone numbers fun-and-games. .tel as described is utterly useless, but the other proposed usages of .tel had a potential to cause damage in addition to being useless.
Other
By registering this utterly useless
I'm neither surprised nor unhappy.
I've got a web page with the greylisting database stats for my mail server at my webserver. It shows on the low side of a thousand messages being held by SQLgrey's block at any given time - which translates to less than a thousand spams per day blocked.
It's a significant decrease in spam getting through, but no panacea.
RFC 3675, ".sex Considered Dangerous".
Abstract
Periodically there are proposals to mandate the use of a special top
level name or an IP address bit to flag "adult" or "unsafe" material
or the like. This document explains why this is an ill considered
idea from the legal, philosophical, and particularly, the technical
points of view.
Of course, RFCs have no force. But I think he argued the point well.
Oh well. The fact that something's stupid has never prevented people from doing it. Especially where sex is concerned.
Sigh.
Orkut worked fine for me for a few months, but I've not been able to log in with anything but IE for the last 6 months.
Not that I miss it much.
For the isolated question of what the split of work between IETF and ICANN *is*, see RFC 2860, "Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority".
The bigger question of what it *should be*.... is a bigger question.....
What? And deny Verisign the right to be the Domain Provider To The World? ..... and believe me, quite a few of those people who designed IDN have not only glanced at, but READ the Unicode book......
SIGH.
And convince the Russians that when they write text in Russian, they need to write the "C" character in the Latin character set because it looks too much like a Latin C, despite the fact that it's pronounced "S".
And convince the Greeks that they need to rewrite their upper/lowercase conversion to make sure the uppercase Alpha is represented by a Latin uppercase A, but the lowercase alpha gets represented by a greek alpha, because it doesn't look like a Latin lowercase a.
Get real. Homographs are here to stay.
in the Museum of Modern Art in San Francisco. .... as such, one should regard the descriptions of the controversy on the wall of the museum as at least as much a part of the "art" than the urinal itself.
The most bizarre part of the visit was standing behind a group of "cultured" people discussing whether the inclination of the piece served to detach it from its function so that its true beuty of form could be seen.... to me, it was obvious that Duchamp's main purpose in creating the piece was to create the controversy around it
He succeeded. Brilliantly. The shape of the object had (IMHO) very little to do with it.
And the comments (apparently completely serious) I overheard show that we still need that kind of challenge.
That would be a relief. Currently I have to start up IE to get Orkut to work properly - which means I rarely visit Orkut these days.