Firefox Extension for Applied Social Networking
wanderingstan writes "Outfoxed is my masters thesis project about trust. (Nutshell overview) The extension uses a social network for personalized searching, phishing/spyware protection, file/process validation and more. It's related to del.icio.us, StumbleUpon, and those Kevin Bacon things, but goes a lot further. Mathematically, it's based on the network behavior of small world networks (pdf). Built with Javascript, Python, SQL, and XSLT. 366 testers so far, but we need the network to grow!"
It's a cool idea, but I'm not sure how many people would bother to set this up, how often this will change the search results, whether the changes will focus your attention on the most relevant result for your search, and whether you can scale a system that accesses data on everyone in your social network on every web search.
What I wonder is this: Yes it does seem like an interesting idea, but how many of your friends run the same software you do? I still have friends that I'm trying to convert from IE, but it's too easy for them use what's already there. I know plenty of cliques that hang together because they all like running BSD/Linux and deal with programming and such, but none of them use the same distro or the same preferences.
My bottom line is this: Look at your best friends computer. Do they have the same extensions that you do? Do they even run Firefox? The network can only be as expansive as the people that decide to jump on board.
Perfecting Discordia
www.stevenvansickle.com
If people used the brains that are supposedly inside their skulls, there would be no need for these not very useful methods of 'protection.' How many people out there would have given a thumbs up to Kazaa? My friends are great to hang out with but tend to spread the computer equivalent of STDs.
This isn't a very good idea for a host of practical reasons, mostly centering around the fact it is too simplistic.
IMHO, you are reaching for a capabilities-based model, which works out at least somewhat better in practice, though it is an open question of whether it works well enough to use. (Link leads to a group trying to build an OS on the idea, and I know it hasn't been completely smooth sailing, but I am not intimately familiar with the project.)
That should give you a springboard for further investigation into the topic, if you like. (Way too big to cover in a Slashdot post, and I am only passingly familiar with it anyhow.)
That's no problem. You just make trust decay. With every hop away from your own directly linked network the trust metric is reduced. So I might give my Dad a trust value of 10/10 (i.e. I would trust this person with my life), but I could assign second-generation hops (those outside of my control) 80% of the trust value that Dad gives them. Allowing users to tweak their own trust decay rates will let them manage the size of their trust pool and reduce the impact of malicious users (i.e. phishers, for example).
Unfortunately, this would just lead to:
Spyware Program [installed by] Spyware Installer [executed by]] KaZaA Installer [trusted by] User [trusted by] Root User
or
Spyware Program [executed by] ActiveX component [executed by] Internet Explorer [trusted by] Windows [trusted by] Root User
Which is exactly what's already happening.
While it would certainly be nice to have this kind of info so you can trace back where files and processes came from, it wouldn't stop malicious programs in the slightest.