I just discovered something I'm not sure I like.
Whenever I post something to slashdot, slashdot connects back to port 80 on the machine I post from, looking for an open proxy on port 80.
This isn't behavior I really like to see. It's unsolicited, and more to the point, it takes advantage of a local firewall possibly being temporarily open for traffic FROM an address for a short while after connecting TO it.
There might be a "good cause", like collecting a list of open proxies for the poor guy behind the Great Firewall of China or something similar, but it's still unsolicted, clandestine and not documented.
Here are a couple of web log entries showing this:
188.8.131.52 - - [10/Sep/2008:15:47:47 -0400] "GET http://news.slashdot.org/ok.txt HTTP/1.0" 404 271 "-" "libwww-perl/5.812"
184.108.40.206 - - [10/Sep/2008:20:32:18 -0400] "GET http://mobile.slashdot.org/ok.txt HTTP/1.0" 404 273 "-" "libwww-perl/5.812"
Big brother is at it again. The Department of Homeland Security is issuing new regulations requiring reporting on, and guarding of, hundreds of common chemicals with "terrorist applications" (such as propane, hydrogen peroxide, chlorine,
A thread in the Slashdot article The 700MHz Question drifted into a discussion between me and rcw-home/rcw-work on using multiple antennas to synthesyze multiple patterns. This allows a particular hunk of bandwidth to be reused to generate several full-bandwidth links simultaneously - either between a base station and several remote stations or even between the base station and a single remote station that itself has multiple antennas.
The thread is beginning to horzon out on my user info history. So this journal entry is a new venue for its continuation after rcw-*'s most recent post.
I'll respond to that after he posts here to indicate that he's also making the move.
A number of stories have recently surfaced asking where Mozilla is going as a platform and whether it risks being outflanked by proprietary rivals. Chris Messina, a former Flock developer and SpreadFirefox volunteer, posted a 50-minute vlog enumerating his concerns about Mozilla. His discussion centered around Mozilla 2 potentially missing the forest for the trees, becoming overly focused on the short-term successes that Firefox has enjoyed, while failing to outrun the proprietary flanking actions being undertaken by Adobe and Microsoft for the next generation internet technologies.
Richard McManus at Read/WriteWeb expands the discussion of Mozilla's direction. His central concern is the adoption of microformats and what that will mean for Mozilla's position. He comments that microformats are already a step in the direction that Messina is pointing toward--a web that remains open.
Mike Shaver, technology strategist for Mozilla, has posted his own discussion of Adobe and Microsoft's proprietary tools intended to close off the web--Apollo and Silverlight--and what this means for Mozilla, if anything.
Finally, concerning Mozilla missing the forest for the trees, Ben Goodger, lead Firefox developer, reports on a Mozilla Corp board member, Brendan Eich, essentially writing off the non-Firefox products offered by Mozilla. Goodger wonders whether it would be a better strategic move for non-Firefox developers to begin seeking greater autonomy from Mozilla Corp, a speculation that Mike Pinkerton, lead developer of Camino, caught flack for a couple months ago when he opened the possibility of dropping Gecko for WebKit.
In a slashdot posting titled "Hollywood vs. Sealand" on April 2 2007, I:
- Made a movie proposal,
- Asserted copyright,
- Offered to license it,
- Threatened possible infringement suits if such a movie is made sans license, and
- Directed anyone wishing to license it to contact me by leaving a message in my journal. B-)
This journal entry is to receive such messages.