After reading this article, I'm wondering if metadata is really going to be as effective as the author thinks it is. The author points out that, "the computer makes us do the work of a filing clerk". In other words, when you place a files on your computer, you normally place them into a folders to organize them, which is, "not fun". The author implicitly claims that metadata will solve this situation.
But that's the problem! If it's not fun to organize items into folders, how is it anymore fun to add metadata to a file? I'm not talking about text files. Text files are easy, because you can pull the metadata out of them automatically (in fact, you can do this now with search tools). I'm talking about files that have to be explicitly tagged with metadata, like pictures. How is adding metadata to each picture file to categorize your vacation pictures any less laborious than placing the vaction pictures into their own directory?
That's the problem as I see it. You still end up being a filing clerk! If people don't even organize their folders now, are people going to use metadata when it's available? Will improved search capabilities make users want to be clerks?
Because the device being crontrolled exposes not only its API, but its user interface. Therefore, your universal remote control is really universal, because the UI is being provided by the device being controlled.
If companies just bothered to spend a little more time on the remotes, rather than skimping on them in favor of the tv/stereo, we'd have no need of jini.
That isn't the problem. I have no issues with any of the remotes that I have for any of my devices. The trouble arises when you want one remote to control several devices. The upshot of Jini is that it can be used to control *any* device that is Jini enabled, because the controller doesn't need to know how to control the specific device (i.e. the interface is provided by the device being controlled).
More generic buttons, a learning feature, or hell, maybe industry standard IR codes.
Which doesn't help you control the special features of a device. With Jini, this isn't an issue, because the device provides the interface.
Or, we could just overengineer it, put little arm7 cpu's in everything, and release new software versions every 3 weeks, so that nothing you have ever quite interoperates.
I don't understand where this came from. There's NO standard now, and nothing interoperates. How is this better than a standard where everything is made to interoperate?
Using Jini, two devices running Java will be able to understand each other. The idea is that devices that need to be controlled expose not only their API, but their user interface. Thus, if you had a Jini-enabled remote, and it found a stereo on your bluetooth network, it would download the UI for the stereo from the stereo and display it on the remote. Since the UI would be made by the stereo manufacturer, it would allow you to control all its features. Java's security model allows this to be done in a secure fashion.
Now if only the companies who manufacture digital players would take a look and see that there is life beyond MP3. Nice that a few are starting to offer Ogg Vobis, but they are few and far between.
What does this have to do with the article? Digital players don't use low-bandwidth encodings like the listening test is for.
Oh, wait, the article mentions Ogg Vorbis. Nevermind...
Of course, there is a simple solution for all the html crap that goes on. Make the mail server, whatever it is, convert everything to plaintext.
Outright banning html content is being lazy. It's like closing port 80 because you don't want exposure. If it is a required service then you take the time to secure it rather than just banning it.
I'm not sure where I got the above advice from, but it seemed appropriate.
It's a shame that people still resort to posting FreeCache links, in situations where it will not work. From the FreeCache FAQ:
What files are being served by FreeCache?
FreeCache can only serve files that are on a web site. If the link to a file on that web site goes away, so will the file in the FreeCaches. Also, there is a minimum size requirement. We don't bother with files smaller than 5MB, as the saved bandwidth does not outweight the protocol overhead in those cases.
It's a fact! The projectionist who turned in the bootlegger also had on beer goggles, and thought the bootlegger was a lot hotter than he turned out to be after the arrest was made.
1. GM crop protestors attempting to destroy your crops whilst wearing fake biohazard suits (do you get these people in the US?)
2. Travellers setting up their caravans on your land, leaving rubbish around & allowing their dogs to attack your livestock. (is this another UK thing?)
Farmers in the U.S. generally have weapons and dogs. Furthermore, local law enforcement tends to be friendly towards farmers, and tresspassing is a serious crime.
Draft Standard is a Standards Track Maturity Level. RFC is a document type.
You were probably thinking of Internet-Drafts, which are not the same thing as RFCs. RFCs must first be published as Internet Drafts. Internet-Drafts are removed after 6 months if they are not approved by the IESG for publication. RFCs are archived.
The zeroconf documents are Internet-Drafts. They are not RFCs.
Slashdot Mirror
Shit. You figured out that I used an enthymeme. Now I'll never retain the Funny modifier. :)
Seriously the pipeline goes Address Book --> Mail Merge --> Group Mailer.
WTF?
You were right. See here.
Trees are graphs. A tree is a connected acyclic simple graph (i.e. any two vertices are connected by exactly one path).
What mrchaotica has done is add edges to the tree so that it has more than one path between some vertices. This makes the tree into just a graph.
But that's the problem! If it's not fun to organize items into folders, how is it anymore fun to add metadata to a file? I'm not talking about text files. Text files are easy, because you can pull the metadata out of them automatically (in fact, you can do this now with search tools). I'm talking about files that have to be explicitly tagged with metadata, like pictures. How is adding metadata to each picture file to categorize your vacation pictures any less laborious than placing the vaction pictures into their own directory?
That's the problem as I see it. You still end up being a filing clerk! If people don't even organize their folders now, are people going to use metadata when it's available? Will improved search capabilities make users want to be clerks?
In a nutshell, isn't it the same problem?
Oh for the love of...
And that solves any of our problems, how exactly?
Because the device being crontrolled exposes not only its API, but its user interface. Therefore, your universal remote control is really universal, because the UI is being provided by the device being controlled.
If companies just bothered to spend a little more time on the remotes, rather than skimping on them in favor of the tv/stereo, we'd have no need of jini.
That isn't the problem. I have no issues with any of the remotes that I have for any of my devices. The trouble arises when you want one remote to control several devices. The upshot of Jini is that it can be used to control *any* device that is Jini enabled, because the controller doesn't need to know how to control the specific device (i.e. the interface is provided by the device being controlled).
More generic buttons, a learning feature, or hell, maybe industry standard IR codes.
Which doesn't help you control the special features of a device. With Jini, this isn't an issue, because the device provides the interface.
Or, we could just overengineer it, put little arm7 cpu's in everything, and release new software versions every 3 weeks, so that nothing you have ever quite interoperates.
I don't understand where this came from. There's NO standard now, and nothing interoperates. How is this better than a standard where everything is made to interoperate?
Using Jini, two devices running Java will be able to understand each other. The idea is that devices that need to be controlled expose not only their API, but their user interface. Thus, if you had a Jini-enabled remote, and it found a stereo on your bluetooth network, it would download the UI for the stereo from the stereo and display it on the remote. Since the UI would be made by the stereo manufacturer, it would allow you to control all its features. Java's security model allows this to be done in a secure fashion.
Check this out before you embarass yourself.
You still need a password for single user mode in most modern operating systems.
Ahhhh, but what he failed to mention is that it's one character of the unicode character set!
It was a joke, so the latter one is probably correct.
The simple solution is inherently the lazy one because you are breaking functionality to achieve security.
Like converting HTML to plain text? :)
What does this have to do with the article? Digital players don't use low-bandwidth encodings like the listening test is for.
Oh, wait, the article mentions Ogg Vorbis. Nevermind...
Outright banning html content is being lazy. It's like closing port 80 because you don't want exposure. If it is a required service then you take the time to secure it rather than just banning it.
I'm not sure where I got the above advice from, but it seemed appropriate.
The Tu-4 is probably the most famous considering it's a B-29.
I didn't realize that there was lack of WAV support. Jeez, I think even my ancient Archos has that.
It's a fact! The projectionist who turned in the bootlegger also had on beer goggles, and thought the bootlegger was a lot hotter than he turned out to be after the arrest was made.
Hey, watch the language, pal.
No we don't. It's illegal.
and that there was a reasonable chance the Canadian cow came from a US herd, right?
And no other cows in the herd had mad cow, IIRC.
2. Travellers setting up their caravans on your land, leaving rubbish around & allowing their dogs to attack your livestock. (is this another UK thing?)
Farmers in the U.S. generally have weapons and dogs. Furthermore, local law enforcement tends to be friendly towards farmers, and tresspassing is a serious crime.
Oh wait, it's probably just down again.
I just love how you got modded "Insightful".
Please add this one to your journal for posterity and to augment the tale already there!
You are completely wrong.
Draft Standard is a Standards Track Maturity Level. RFC is a document type.
You were probably thinking of Internet-Drafts, which are not the same thing as RFCs. RFCs must first be published as Internet Drafts. Internet-Drafts are removed after 6 months if they are not approved by the IESG for publication. RFCs are archived.
The zeroconf documents are Internet-Drafts. They are not RFCs.