It was called CompuServe. If you were a software developer, you had a CompuServe account because that was where the online support, patches, docs and threaded discussions were to be found.
Then the web happened and Compuserve's business model collapsed. All those hardware and software vendors moved their content from Compuserve forums to their own (mostly free) web sites. The user base followed and the Compuserve technical community, which was in some ways more vibrant than anything on the web today, faded away.
CompuServe was not cheap, but at the time it was well worth the money and we paid.
Paying for web content is a much harder sell. As an aggregate, today's web content outweighs yesterday's Compuserve content by orders of magnitude, but web content is very diffuse. It's unordered, unbalanced, of widely varying quality and is served from a kaleidoscope of individual, independent sources, 99.99% of which are free. Compuserve's content was densely packed, uniformly packaged, well indexed and, most tellingly, unrivaled.
It's hard to compete with free, especially if you are selling to this crowd.
--Former CompuServe Internet Publishing Forum Sysop
If you hang your DSL or cable modem off of a linux box and do your NAT there then solutions to these little conundrums become fairly trivial. To accept external connections on a particular port of a machine behind the NAT box, all you need is a generic proxy, like the TIS Firewall Toolkit's plug-gw. And you get packet filtering capability thrown in as part of the bargain.
Naturally, this solution involves tradeoffs. Instead of a sleek little fanless box nestled somewhere in the vicinity of one of your computers, your stuck with a hulking rattle-trap of a 486 beast (in a butt ugly tower case, most likely). But on the bright side, you get to coo over your homemade router's uptime and you can set things up so you can SSH into your home network from the office. Works for me.
Slashdot Mirror
The images accompanying the patent text are TIFF files. My browser informs me that I need a plugin in order to view them.
In order to read the patent, I must violate it.
Not Slackware.
On Slackware, there is no wu_ftp, there is no pam, there is no Vixie crond.
And there are very few security advisories.
Then the web happened and Compuserve's business model collapsed. All those hardware and software vendors moved their content from Compuserve forums to their own (mostly free) web sites. The user base followed and the Compuserve technical community, which was in some ways more vibrant than anything on the web today, faded away.
CompuServe was not cheap, but at the time it was well worth the money and we paid.
Paying for web content is a much harder sell. As an aggregate, today's web content outweighs yesterday's Compuserve content by orders of magnitude, but web content is very diffuse. It's unordered, unbalanced, of widely varying quality and is served from a kaleidoscope of individual, independent sources, 99.99% of which are free. Compuserve's content was densely packed, uniformly packaged, well indexed and, most tellingly, unrivaled.
It's hard to compete with free, especially if you are selling to this crowd.
--Former CompuServe Internet Publishing Forum Sysop
My understanding is that copyright protection has been extended to source code by classifying it as a "literary work".
If this is the case then how can source code be both a literary work and anything less than speech?
It would seem to me that either code is speech or it is not copyrightable.
We're using their InterCall product (a C library that provides full access to UniVerse via RPC) wrapped in a Perl module to do our web interface.
Additionally, there is the UniVerse General Call Interface, which allows calls from Pick Basic to C/C++ programs.
A CTO clearly has a higher ASCII value.
If you hang your DSL or cable modem off of a linux box and do your NAT there then solutions to these little conundrums become fairly trivial. To accept external connections on a particular port of a machine behind the NAT box, all you need is a generic proxy, like the TIS Firewall Toolkit's plug-gw. And you get packet filtering capability thrown in as part of the bargain.
Naturally, this solution involves tradeoffs. Instead of a sleek little fanless box nestled somewhere in the vicinity of one of your computers, your stuck with a hulking rattle-trap of a 486 beast (in a butt ugly tower case, most likely). But on the bright side, you get to coo over your homemade router's uptime and you can set things up so you can SSH into your home network from the office. Works for me.
Every HTTP GET and POST is logged with the full URL. Scripts are commonly employed to generate aggregate data based on TLDs or client machines.
If you removed all the GNU tools from a stock FreeBSD installation...
Then you can't compile it and nothing runs.