Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
User Journal

Journal Journal: CLTD 15

Time for my Crazy Late-night Thought of the Day:

Much as the GPL turns copyright against itself, could trusted computing be turned against itself by creating a class of software that doesn't run on computers where trusted computing is turned on?

Food for thought.... perhaps....

User Journal

Journal Journal: Travesties of moderation 8

Much as the oh-so-superior K5 crowd might malign Slashdot, it is still a hell of a lot more interesting and fresh than K5's offerings of bland introspection and home-brew beer HOWTOs.

Of course, it is far from perfect, and one thing that really annoys me are the increasingly frequent misuse of moderation, whether deliberate or simply as a result of an overactive sense of political correctness.

Now, this might seem like whining, ok, it is whining, but how could anyone justify moderating this down as flamebait?! I mean, who seriously thinks that the British need to be protected from such racist insults? It is reminiscent of LA County recently asking their suppliers not to use terms such as "master" and "slave" when referring to equipment. Perhaps on /. we should moderate down anyone who refers to male and female cable connectors lest it offend Wayne Bobbett?

Anyway, I am going to keep this story around and post examples of moderator abuse in the comments afterwards, others are free to do the same.

User Journal

Journal Journal: Latest threat to P2P comes from within 1

Altnet, the company most responsible for the proliferation of spyware, recently acquired a patent which allows easy identification of files on a P2P network. In the words of Derek Broes, Altnet's executive vice president of worldwide operations, Altnet will "...focus on protecting and commercializing our patented technology and realizing the potential it offers content owners by commercializing peer-to-peer networks". Just another day in the world of little-league software companies you think. Not so.

Unfortunately, there are a few problems with this picture. The so-called "Truenames" patent, filed in 1997, is little-more than a marketspeak-friendly name slapped on a decades old and widely known technique in computer science called "hashing". A hashing algorithm takes a file, and produces a "signature" for that file, a short set of letters and numbers that, for any two identical files, will always be the same. This technique has often been used to detect identical files, or to verify the integrity of software downloaded over the Internet. Clearly, it requires very little imagination to suppose that hashing might also prove useful when verifying the integrity of files on a P2P network.

This, of course, puts Mr Broes' quote in a somewhat sinister new light. In a classic example of P.R "doublespeak", what he refers to as protection, most would see as an anti-competitive offensive, and what he refers to as commercialization, most would refer to as extortion. Yes, the implication of recent public statements from Altnet is that they plan to use their government granted monopoly on an obvious idea to force other P2P companies, through threat of litigation, into cooperating with whatever scheme they are cooking up.

It is hard to overstate the bitter irony of a company, their main innovation being the loathed spyware, threatening real innovators in the P2P space for using a technique that Altnet made no contribution toward but which they now claim as their property. Altnet's initial targets seem to be designed to place them on the moral high-ground, as most are companies trying to track down copyright infringers on P2P networks. It may only be a matter of time, however, before they attack Shareaza, BitTorrent, eDonkey or others.

Fortunately, all is not lost. Firstly, given the facts I have just outlined, this patent should be overturned if anyone fights it, it obviously fails the non-obviousness requirement for patents, and there is plenty of prior art out there.

Secondly, the Federal Trade Commission recently published a report acknowledging the problems with the US patent system and making a number of recommendations which will make it harder for Truenames-style patents to be granted in the future, and easier to challenge those that have already been granted.

In the EU, concerned citizens and subjects mounted a spirited opposition to the attempted introduction of US-style software patents, and were successful in getting the European Parliament to amend the proposal such that software patents were not permitted. The battle in the EU is far from over, but it is heartening to see rank and file computer enthusiasts and small businesses raise their voice and be heard over the paid lobbyists of big software.

So, danger on the horizon, but also hope. With luck Altnet will renounce patent-blackmail as a business model. With even more luck the FTC's recommendations will be implemented, and the EU will listen to the voice of their citizenry with respect to software patents. In the mean time, those threatened by Altnet must stand firm or risk emboldening them and those like them even further.

User Journal

Journal Journal: PHP project needs new owner

A few months ago I wrote QuickCMS. It is designed to be a simple, minimalist, and tidy PHP-based alternative to Wikis that can "eat its own dogfood". This means that you can edit the QuickCMS source code through QuickCMS itself.

Anyway, the project lay dormant for a while, but now I want to find someone to take it over - anyone interested should email me at ian@locut.us.

User Journal

Journal Journal: Welcome to the world of Puba! 5

Puba Health Concepts Inc
"Your life in our hands"

Congratulations on becoming one of the many healthy consumers that enjoy the Puba PaceMaker 3! We at Puba Health Concepts Inc would like to thank you or your employer for choosing a Puba affiliated physician to address your Cardiac care needs. Your new Puba PaceMaker 3 is equipped with state-of-the-art remote monitoring and control technology allowing us to modify your treatment as needed. We would like you to take a moment to read through the terms and conditions of use of your new Puba PaceMaker 3.

Terms and Conditions

1) By using the Puba PaceMaker 3 service you indicate your acceptance of the following terms. If this agreement is unacceptable to you, immediately discontinue use of the Puba PaceMaker 3. Violation of any of these terms will result in immediate remote termination of the Puba PaceMaker 3 service.

2) Your initial subscription payment is due immediately and must be paid within 7 days of installation of the Puba PaceMaker 3. Subsequent subscription payments are due monthly within 5 working days. Failure to pay within these time periods will result in immediate termination of service.

3) The Puba PaceMaker 3 contains proprietary intellectual property of Puba Health Concepts Inc. Any attempt to reverse engineer the Puba PaceMaker 3 or to circumvent our Technology Rights Management system will result in immediate termination of service. Additionally, under the terms of the New Century Treason and Theft Prevention Act, your body will become the automatic property of Puba Health Concepts Inc.

5) This document is the intellectual property of Puba Health Systems and any disclosure of the contents of this document to a third party will result in immediate termination of service. Additionally, under the terms of the New Century Treason and Theft Prevention Act, your body will become the automatic property of Puba Health Technology.

6) You may not make any statement, written or verbal, referring to Puba Health Technology in a derogatory, or defamatory manner, or otherwise damage the reputation of Puba Health Technology. Any attempt to pursue alternatives to the Puba PaceMaker 3 will be viewed as defamation of Puba Health Technology. Failure to comply with this term will result in immediate termination of service.

User Journal

Journal Journal: Package Management in the untimate operating system 5

I have frequently thought about how to put together the next iteration of the operating system, and a recent discovery on SweetCode reminded me of this.

Zero Install is designed to make the process of installing new software completely transparent. It achieves this by mapping a filesystem to HTTP. for example, if you wanted to install The Gimp, you would simply run it from /uri/0install/www.gimp.org/bin/gimp. This would transparently download the gimp software, and any libraries on which it depends. Once downloaded such applications are cached such that the next time you run the gimp it is just as fast as if you ran it from your local filesystem (because you would be running it from your local filesystem!).

This idea, of breaking down the barriers between the local filesystem and the Internet to effectively eliminate the notion of installation definitely seems like the way forward. This is the kind of convenience that tools such as Debian's apt-get begin to provide - however 0Install takes it to its ultimate conclusion.

The next step, then, would be to build an entire Linux distribution around the 0Install principal. This would also benefit from upcoming filesystem innovations which allow set operations on directories (for example, having two directories and creating a new virtual directory that contains everything the two real directories do). At the simplest level this would eliminate things like the $PATH variable.

Creating a new Linux distribution that isn't afraid to make bold advances such as those outlined above will be the true next step in the evolution of operating systems - it won't be brain surgery, just elegantly combine a number of technologies (such as Linux, 0Install, and the new Reiser FS) that are already out there or in development.

User Journal

Journal Journal: Collaborative document editing 7

I am been interested in the area of collaborative document editing for a while, and for the last few days have been working on something to allow this. I just put up an alpha-quality version of it at http://3D17.org, please let me know what you think.
User Journal

Journal Journal: Locutus 0.5

Just released a new version of Locutus. Locutus offers collaborative spam filtering and employs some novel algorithms to avoid getting fooled by spammers that try to evade collaborative filters. It also does fast local and remote keyword searching for documents using a scalable search algorithm inspired by Freenet but generalized for fuzzy searching. Locutus isn't free as in speech, but it is free as in beer. If you run Outlook or Outlook Express on Windows please check it out - the more people that use it the better it gets.
User Journal

Journal Journal: News about me. Stuff that matters. 4

It is getting a little bit silly how frequently I and/or one of my projects is appearing on /. these days. I am not complaining, it is great when stuff you are doing attracts attention. Nor do I take it for granted, I am amazed that people are still willing to hear about my crazy ideas. Having said that, the latest story is something I never wanted or intended to enter the public arena.

There are those that have accused me of being a self-publicist (you know who you are), but I think this latest episode demonstrates that not everyone that gets some publicity for something did it through shameless self-promotion.

I was following a debate on Slashdot about an Intel engineer who had admitted (under considerable duress) that he was a terrorist. Many people took this to imply that he was actually guilty. In an attempt to wake people up to the seriousness of what was going on I posted a comment under my slashdot nickname (but making no further attempt to identify myself) explaining that I was leaving the US, and how concerned I was about the direction this country was going. Admittedly, I used somewhat hyperbolic language, and gave fans of Godwin's Law the opportunity to indulge in the meta-arguments that they enjoy so much, but it was just a throwaway comment on /. after all...

...or so I thought. It didn't take long for someone to post this to InfoAnarchy, and with that my throwaway comment had graduated to an "announcement". It didn't take long to go from there to a story on BoingBoing.net by Cory Doctorow where by now my throwaway comment was a "goodbye letter".

As a result of this I got one phonecall from the Canadian Broadcasting Company, and an article in the Irish Times, followed by a request from GrepLaw to do an interview. As always, I accepted these requests to discuss what I had said - I learned long ago that whether you talk to them or not, journalists will write a story - and it is far better that you have the opportunity to inject your perspective than to leave it up to them and their editors.

Bottom line - it might make people feel better to imagine that the amount of coverage someone gets is directly proportional to the size of their inflated egos, but it isn't always true. Of course, sometimes it is ;-)

User Journal

Journal Journal: Godwin's Law - "law" or cop-out? 24

I have always been uncomfortable with Godwin's Law. For those unfamiliar with it, it states that "As a Usenet discussion grows longer, the probability of a comparison involving Nazis or Hitler approaches one." Many people infer from this that whoever, during a debate, makes a comparison with Hitler or Nazis, loses the argument automatically.

It wasn't until a recent email conversation with Cory Doctorow, started by a /. comment of mine, that I was forced to introspect and find the reason for my discomfort.

Here, I outline a fictional debate between Cory and I, using various extracts from our conversations and comments, which I hope gives a fair indication of Cory's viewpoint:

Me: As an Irish citizen living in the US - I have decided that it is time to leave this country - it is starting to look, smell, and act as Germany did during the 1930s.

Cory: It's a shame that [you] violated Godwin's Law, as it gives those who would distract us from the real issue here a handy red herring to toss into the fray, i.e., pointless arguments about the appropriateness of a comparison to Nazi Germany.

Me: I think the comparison with *1930s* Germany is apt, although a comparison with 1940s Germany would not be, you can't invoke Godwin's law when the conversation *really is* about Nazi Germany ;-)

Cory: The point for me of G's law is not its aptness -- I happen to agree that it is an apt analogy, and I speak as someone who lost a significant fraction of his family in the death camps.

The point of G's law is that comparisons to Nazi Germany immediately end all discussion about the subject at hand and instead divert the whole debate to an argument about the aptness of the comparison.

Me: In some cases, however, a discussion about the aptness of the comparison is actually useful, and gets to the core of the issue.

Cory: My point is that Doctorow's Corollary To Godwin's Law is that anyone who wishes to be an effective rhetorician should completely expunge the notion of Nazi comparisons from his bag of tricks, because it creates a vulnerability to an attack that is otherwise neutralized ("My opponent is of such poor judgement and callous insensitivity that he believes it's appropriate to make comparisons to Nazi Germany!").

Me: Well, I am not so sure I agree with you there. *If* a comparison to Nazi Germany is pertinent then an effective rhetorician will be sufficiently skilled to counter this kind of ad hominem attack. They say that those who forget history are doomed to repeat it, and what more important lesson for society than the events in Germany during the Nazi period.

Refusing to use such an important lesson of history in debate for fear of exposure to fallacious arguments seems like an unfortunate surrender of a powerful tool for those who wish to fight against fascism. For this reason - I have never been entirely comfortable with Godwin's Law.

Unfortunately this is where the debate must end as I still await Cory's response to my last comment.

I would be curious to hear some third-party opinions on this, since Godwin's Law is one of the Internet debate doctrines that never rang true for me.

Anyway, bottom line is that I now propose:

Clarke's Law: Anyone that invokes Godwin's Law in an argument automatically loses the meta-argument

User Journal

Journal Journal: Unified configuration mechanism 11

One of the biggest problems with Linux (and I am certainly not the first to observe this), is the vast number of configuration files, many with completely different - and often nonsensical layouts, and most of which must be edited manually. It is a mess.

I would propose that someone come up with a unified Linux daemon which handled all configuration information - keeping it all in a well-ordered datastructure, perhaps based on XML. The idea would not be dissimilar to the Windows registry, although it could incorporate a number of features to make it even better:

  • Security
    Different parts of the configuration tree could be given read and write security permissions on a per-user basis
  • Backwards compatability
    Through the use of pipes, older software which doesn't directly support the configuration mechanism can read their configs from a file that is actually a pipe to the config daemon
  • Network support
    Access to the config daemon could be handled over a network, or the local config daemon could be configured to "fall back" to a remote daemon - allowing centralized configuration for software, but still letting the user modify user-specific stuff
  • Cross-configuration
    Often - software needs to base its settings on the settings of another piece of software in the system. This approach would make it easy for one piece of software to check the configuration of some other software.

I think such a mechanism would be one of a variety of necessary stages to creating a new environment which can be built around a Linux kernel to bring it closer to the kind of unified integrated approach we see in OSX.

User Journal

Journal Journal: A WhittleBit of extra intelligence 2

After a long delay I finally have a reasonably reliable implementation of my "learning" web search engine up at WhittleBit.com.

Yeah - weird name, I know. All other comments welcome.

Addendum 8/1/03: Sorry for those that tried this and found it to be down - the problem was that I use a Java daemon to do the donkey-work but I couldn't find a VM that would run on the server I was using (which has a weird setup). Finally I got it working using Kaffe - hopefully it will prove to be stable.

User Journal

Journal Journal: Removing bias in collaborative editing systems 28

A few weeks ago a friend of mine that had been thinking about reader-edited forums (like K5) posed an interesting question. He was concerned about how people's bias would influence their voting decisions and wondered whether there could be any way to identify and filter out the effects of such bias. Of course, in some situations bias is expected, such as political elections, however in other situations, such as when a jury must vote on someone's guilt or innocence, or when a Slashdot moderator must vote on a comment, bias is undesirable. After some thought, I came up with a proposal for such a system.

First, what do we mean by "bias"? It is a difficult question to answer exactly; examples would include political left or right-wing bias, nationalist bias, anti-Microsoft bias, and bias based on race. The dictionary definition is "A preference or an inclination, especially one that inhibits impartial judgment." Implicit in the mechanism I am about to describe is a more precise definition of bias; it is the aptness of this definition that will determine the effectiveness of this approach.

Visitors to websites such as Amazon and users of tools like StumbleUpon will be familiar with a mechanism known as "Automatic Collaborative Filtering" or ACF. Amazon's recommendations are based on what other people with similar tastes also liked, this is an example of collaborative filtering in action. There are a wide variety of collaborative filtering algorithms, which range widely in terms of sophistication and processor requirements, but all are designed to do more or less the same thing: anticipate how much you will like something based on how much similar people liked it. One way to look at it is that collaborative filtering tries to learn your biases and anticipate how they will influence how much you like something.

My idea was to use ACF to determine someone's bias towards or against a particular article, and then attempt to remove the effect of that bias from their vote. The effect of their bias is assumed to be the difference between their anticipated vote based on ACF, and the global average vote for that article. Having determined this, we can then take their vote, and remove the effect of their bias from it.

Let's look at how this might work in practice. Joe is a right-wing Bill O'Reilly fan who isn't very good at setting aside his personal views when rating stories. Joe has just found an article discussing human rights abuses against illegal Mexican immigrants. Joe, not particularly sympathetic to illegal Mexican immigrants, gives the article a score of 2 out of 5. On receiving Joe's rating, our mechanism uses ACF to determine what it might have expected Joe's score to be. It notices that many of the people who tend to vote similarly to Joe (presumably also O'Reilly fans) also gave this article a low score - meaning that according to our ACF algorithm - Joe's expected vote was 1.5. Now we look at the average (pre-adjusted) vote for the story and see that it is 3 - we then assume that Joe's anticipated bias for this story is 1.5 minus 3 or -1.5. We use this to adjust Joe's vote of 2 to make it an actual vote of 3.5 - which means that Joe's adjusted vote for this story is actually above average once his personal bias has been disregarded!

So, how well will this system work in practice - and what is it really doing? What are the implications of this mechanism for determining someone's bias? Is it fair?

I don't pretend to have the answers to these questions, but it might be useful to think of it in terms of punishment: when your vote is adjusted by a large amount, then you are being punished by the system as your vote will have an effect different from that which you intended.

The way to minimize this punishment is for your votes as predicted by the ACF algorithm to be as close to what the average vote is likely to be as possible. The worst thing you can do is to align yourself with a group of people who consistently vote in a manner in opposition to the majority.

I have been trying to think of scenarios where it might be bad for people to do the former, or bad for them to do the latter, but so far I haven't come up with anything. What kind of collective editor would such a system be? What kind of negative side effects might it have? I am curious to hear your opinions.

Privacy

Journal Journal: A draft of a new Freenet article 4

I have been working on an article describing Freenet's "Next Generation Routing" algorithm. You can find my working draft here - comments appreciated, but remember that it is still a draft so please don't link to it except through my blog.

When complete I will probably submit it to /. among other places to get some wider peer review.

Slashdot Top Deals

1 + 1 = 3, for large values of 1.

Working...