Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×
Music

Journal Journal: Tallie Stubbs Counter-Sues RIAA and its Lawyers 1

In a new case in Oklahoma,Warner v. Stubbs, the defendant Tallie Stubbs has countersued the RIAA and its lawyers for her attorneys fees, charging that "Plaintiffs' only evidence to support their claims against Tallie is her status as an account holder with Cox Communications..... " and that she "denies that she had any knowledge of KaZaa...." and "is and continues to be without knowledge of how to download music off of the internet.....Despite being placed on notice that Tallie did not download any songs, the Plaintiffs filed this action against Tallie. Plaintiffs impugn Tallie's character and subject her to demands which are closely akin to extortion....." She also claimed that the RIAA has "a pattern and practice" of bringing similar actions. Ms. Stubbs is represented by Marilyn Barringer-Thomson, of Oklahoma City, Oklahoma, the same lawyer who represents Deborah Foster in Capitol v. Foster.
User Journal

Journal Journal: Information for good log messages

This is a commonly reinvented wheel, and the version Stefan (metze) Metzmacher suggested in samba-technical is the round one (;-))

A maximally useful log message contains a number of fixed items, usually in a fixed-format header of some sort, and text for the human reader to use to understand the implications of the problem.

From memory, the fixed information includes enough to allow for mechanical sorting by nastiness and occasionally mechanical processing:

- date/time
- origin, meaning machine- or domain-name
- source, in some detail,, including the executable name and process id as a minimum, if applicable, and optionally the file, function and line, it is good to make this one token, for ease of parsing and resilience when one line has "sendmail:parse.c:parse_it:332:1948" and another has only "mconnect:1293"
- pre-classification, meaning the application type, error type and severity. DFAs can switch on this, and should.

The old ARPA format was error type source and severity as three decimal digits, which you still see when smtp says "250 ok". The 2 was permanent success, the 5 meant "the app", in this case smtp, and 0 was the severity. I prefer ascii, not numbers (;-))
- then the text for the human, saying the meaning of the error, the same way you're supposed to write the **meaning** of code in comments, not just say what the code does.

Syslog does about half of this, metze's did most of it.

User Journal

Journal Journal: ARPA result codes 1

Alas, many folks don't know the old ARPAnet tricks and have to reinvent them. Often inelegantly.

One very handy pair was the ARPA command and return-code standard.

A command was four letters or less at the beginning of a line (record, packet), often monocase, so it could be treated as a 4-byte integer and switched on.

For example, smtp starts ups with
helo localhost
250 froggy Hello localhost [127.0.0.1], pleased to meet you

The "HELO" is the command, and the next line the response.

the first character is an ascii digit, where
1 means "informational message", and is rare
2 means permanent success
3 means partial success, as in a series of steps.
4 means temporary failure, such as "no space", and
5 means permanent failure

The second digit is 5 for "this app" and 9 for "the OS"

The third digit is the severity, so
599 I must close down, my CPU is on fire
is a very sever and permanent error (:-))

The fourth character is an ascii blank if the reply is complete on this line, a "-" if it continues to additional lines. For example, smtp has a help command:
help
214-2.0.0 This is sendmail version 8.12.8+Sun
214-2.0.0 Topics:
214-2.0.0 HELO EHLO MAIL RCPT DATA
214-2.0.0 RSET NOOP QUIT HELP VRFY
214-2.0.0 EXPN VERB ETRN DSN
214-2.0.0 For more info use "HELP ".
214-2.0.0 To report bugs in the implementation contact Sun Microsystems
214-2.0.0 Technical Support.
214-2.0.0 For local information send email to Postmaster at your site.
214 2.0.0 End of HELP info

The three digits and the "-" for continuation allows one to write as simple or as complex a DFA as you like, by doing trivial masking on fixed-length strings.

User Journal

Journal Journal: Anyone a subscriber? Do me a favor if so ... 2

Does anyone actually subscribe to /.?

I actually had a prospective employer ask me to list the best threads I've been a part of (my job is technical marketing and one of the things I do is look around for things related to my current job to clear up when they are misstated).

I have something like 750 posts, but non-subscribers only get to see a 25 comment history. If you are a subscriber, I would love it if you could page through my comment history and mail me the results.

Yeah, you don't owe me anything, but if you're reading this you probably got here because you either very much agreed or very much disagreed with my comments. If you're in the former category and are a subscriber, maybe you'll take pity.

If not, maybe I'll do it some day :)

User Journal

Journal Journal: My New Vocation 1

Ok, so I finally figured out what my next job should be ... Slashdot Analogy Critic.

Come on ... if you're going to make an analogy, examine it for 10 seconds before posting it. Make sure it actually holds up. Is it as close to "apples to apples" as can be, or is it "Apple to Coors"?

Seriously, is it just /. or are bad analogies everywhere? Most weeks I find I've torn apart some seriously bad analogies. Sure, I've probably posted a couple with holes, but these were really bad.

Think it though a bit more, everyone will thank you.

User Journal

Journal Journal: Big boys need to have cache!

A quick thread that pretty well sums up how I feel about the way /. and Google and like can really abuse their best participants ...

http://slashdot.org/comments.pl?sid=101442&cid=8655929

...
Pasted here in case the above link ever dies but I may miss parts of the discussion because of it

...

Re:Yeesh (Score:1)
by thesaur (681425) on Wed Mar 24, '04 08:57 AM (#8655929)

However, that cannot prevent an attack by Google. You wouldn't want to block requests referred by google.com, because you do want people to find your site, right?

As reported in a previous story [slashdot.org], Google linked their main logo graphic to an information academic site and brought it down [swin.edu.au]. Subsequently, Slashdot hit [swin.edu.au], but it didn't hold a candle to Google. Fortunately, such attacks by Google are rare. Of course, there is no way to determine your risk for a Google attack, unlike slashdot attacks.

The best idea is to always keep your server ready to handle any load.

I'll probably get modded down for this, but so be it.
[ Reply to This | Parent ]


Re:Yeesh by thesaur (Score:1)
Re:Yeesh (Score:1)
by Jahf (21968) on Wed Mar 24, '04 10:59 AM (#8657449)
(Last Journal: Wed Oct 29, '03 04:29 AM)
Depends on if you care if people see your site ... I know one guy who takes all traffic referred by Google, /. and a couple of other sites (he occasionally publishes tech goodness) to the Google cached version of his page.

Most people can't afford to keep their personal servers ready to handle 1% of the load that Google's image fiasco or 10% of a popular article on /. can throw at them.

Should those people be penalized by not being able to have their own site (rather than surrendering control to a bunch of web farm monkeys)? No, sites like /. and Google, which espouse the idea of being good net citizens on principle should realize that often they are some of the worst net citizens out there.

Wow ... wasn't expecting it to turn into a rant, oh well :)

And who cares about being modded down? *laugh*
        [ Reply to This | Parent ]


Re:Yeesh (Score:1)
by Jahf (21968) on Wed Mar 24, '04 11:05 AM (#8657551)
(Last Journal: Wed Oct 29, '03 04:29 AM)
btw I doubt even the referer->GoogleCache mechanism would save most sites from the inadvertant DDOS that Google provided by that image link. Just more argument to Google and /. being better citizens.

Perhaps /. could wait to publish a story until Google had it cached and then give the -option- in a user pref to allow links to be rewritten to the Google cache ...

Perhaps Google could add a new piece to the stale robots.txt standard like "cache-link-only" so that Google would know the author was only interested in being in the Google engine if Google directed all links to it's own cache for that particular site.

Both are opt-in programs that allow the rest of us to have good conscience when viewing tiny sites via links from beasts like Google and /.

BTW, I don't want people to get me wrong ... I might not have a -job- without /. or Google since I use them for research and learning every day along with a host of other sites. I don't want them -gone- I just want them to be a bit more responsible for their actions. To paraphrase J. Depp, they're "something like big dumb pupp"ies ... in this case we like to pet them and they're usually sweet but sometimes they can bite the hand that pets them when they get overzealous.

User Journal

Journal Journal: Debate on my signature ...

Tonight mcrbids commented on my signature ("It is more productive to voice thoughtful opinions (reply) than to judge (moderate) others.") being a "crock" ...

A semi-lively debate ensued between mcrbids, Darth and myself. Maybe this journal entry will be useful to someone who is confused by the signature. I don't know who would be confused by it's meaning unless they are -looking- to twist it's meaning (even taken purely literally it does not have the extra nuances they implied and in my opinion a literal interpretation actual refutes their view of it), but hey, it's already happened twice in one night.

See this offtopic mini-thread for the clarification. If you care ... which you shouldn't ... but I'll save it just for my own future reference in case this comes up again.

The Courts

Journal Journal: Eldred Thoughts: One Week After

This being the one-week "anniversary" of Eldred v. Ashcroft in the Supreme Court, I am going to post the various thoughts I've gone over in the week since. I'm feeling rather secure that Lessig covered his arguments well, so my take on the copyright clause here is going to be quite different.

First, to lay the groundwork of the discussion. The Copyright clause grants Congress the power "To promote the progress of science and useful arts, by securing for limited times to authors and inventors the exclusive right to their respective writings and discoveries". Any law passed that exceeds this grant of power is unconstutionioal.

Lessig stood before the Supremes and made a very convincing argument for "limited times" being a limit on congress' power. No doubt, he indeed was sucessful in prosecuting that vein; however, in reading the Constituition again last week it was a different word-- "exclusive"-- that lept at me. I realize that the Eldred case cannot address both issues; however I would imagine that this is the single word in the copyright clause that will overturn the DMCA.

Now, (an excerpted) reading the clause without that single word forms "...securing for limited times to authors ... the right to their respective writings...".

"Wait a minute," you may ask, "How does that make things any different?" The answer, I'm afraid, is dreadfully simple and one that seems to be in conflict with all of the US' copyright history. If the clause must establish exclusivity for authors, then it implies that the rest of the population has right to the same writings. (Most simply put, this one word is the link between the copyright clause and the first amendment: what good is free speech if there is nothing to be said?)

Now, examine the effects of the DMCA in the light of whole-populace rights to a work. Either it is illegal because it attempts to extend copyrights for an unlimited time (by not having a exemptive clause for public domain works), or it is illegal because it attempts to secure exclusive rights via mechanisms outside of the grant of power contained in the copyright clause.

Damn, I just had another thought. That single word, "exclusive", also seems to veto / trump the line of reasoning that states computer programs require an EULA because the computer will copy the data in the process of executing it (thus violating copyright). After all, if the rights of the author in nature are not exclusive (and are made so only by the acts of congress), then such a requirement is (depending on the exact wording of the fair use clauses) nonexistent.
User Journal

Journal Journal: For Openness Not of Source 2

This isn't what I expected my first journal entry would be like. While the whole time I knew this would be the place where I put my opinions out to /.'s readership for further examination (rather than make this a personal diary), I didn't think the first entry would be cut and paste.

That just goes to show you how much I don't know about myself.

A nice thread today on the topic of LinuxWorld led me to make a statement- in which I declared I'd post to my journal.
Well, here it is.

I mailed my letter to the DOJ a little too quickly. Rereading it, I would have liked to have made one more editorial pass; however it must lie in the record as I mailed it. So for your viewing pleasure, my Tunney comments to the DOJ on how Microsoft ought to be punished (and afterward, refreshments and light commentary.)

------- To Whom It May Concern:

I am opposed to the proposed settlement in the Microsoft antitrust trial. I feel that,while covering many vital aspects of the case, the current proposed settlement does not fully redress the actions committed by Microsoft in the past, nor inhibit their ability to commit similar Sherman violations in the future.

In the past, the people most hurt by Microsoft were not the hardware distributors or the existing middleware vendors, but the developers of new applications. With each new version of Windows, it has become increasingly impossible for any vendor outside of Microsoft to introduce a new feature -- such as Plug and Play or USB support -- to the market without Microsoft's collaboration. The potential new technologies that have been stifled by Microsoft's vice-like grip on innovation has done the market far more damage than could ever be measured in a dollar amount.

To this end, there is only one possible remedy.

Microsoft, as a software vendor, lives on its' intellectual property. That property does not only include the copyrights it holds on the source code to Windows and the other softwares it sells, but also the patents and trade secrets that Microsoft has, over the years, added to its' code to hinder competition. The copyright and or patent of code, while in some circles of dubious quality, is never categorized in the same manner as trade secrets. The computing sector has an interdependence of intellectual works never before seen in any industry, and the use of trade secrets is the greatest possible artificial barrier Microsoft has erected in its' illegal actions.

Furthermore, this action is in direct opposition of the actions of other software vendors. There are several standards bodies in the computing world, including the International Standards Organization [iso.org] who define standards in many fields, the Institute of Electronic and Electrical Engineers [ieee.org] who help define standards in hardware peripheral design, and the World Wide Web Consortium [w3c.org] devoted solely to Internet standards. The standards are open for public inspection and independent review, and encourage further development in the fields they cover.

I would suggest a single remedy appropriate to this problem: Microsoft must be forbidden to declare any portion of their product a trade secret, and as a result make available to public examination and independent re-implementation (for interoperability, educational and testing purposes only) technical specifications for all of their system APIs, file formats, media codecs, and any other method of system interaction not covered by a patent. The information could be, at little cost, be added to Microsoft's Developer Network, found at msdn.microsoft.com.

The benefits of this action far outweigh the apparent dangers. First, this action is not as invasive as it may seem, still allowing Microsoft to protect its' current patents or copyrights, and no limit is levied against Microsoft for patenting further technologies. Second, this action does not greatly affect Microsoft's competition: most or all of the information to be disclosed has either been disclosed on the Microsoft Developer's Network or has been repeatedly legally reverse-engineered. Third, this completely removes the artificial barrier raised against the developers of new technologies.

While it may be noted that Microsoft is a member of many standards bodies, too numerous to mention in a short letter, as a developer in the computing industry I have noted a distinct trend on the part of Microsoft to abandon widely-held standards in favor of their own protocols and methods, often of similar or identical name to the official standard, and generally a trade secret. While I shall withhold judgment of such actions, it must be noted that they lead to an inevitable destruction of competition. The current settlement does not cover such actions; I therefore submit my solution to be considered as a part of additional action to prevent this violation of anti-trust law from being repeated.

I believe this action is the best possible remedy applicable to Microsoft. As shown by the antitrust trial, Microsoft has historically used the trade secrets cocooned into the products it sells to stifle competition and hamper entrance of new technologies into the market. The most direct and least intrusive method to end such practices would, of course, to remove the possibility of the same circumstances arising again. To this end, I suggest that measures be added to the settlement that would forbid further development of technologies within Microsoft to be declared a trade secret, for they are clearly only used in a violation of the law.

-------

Whew. Let me cool off after rereading that- the whole Microsoft thing makes me really mad and I don't post that clearly for a while afterward.

That's better. Now, if you came here from my comment link, you might wonder why I don't talk just about protocols. Well, to me the whole think stinks just as bad, and if you're going to attack a small portion of the sh*t MS put out as "standards", then go ahead and throw the whole lot out- bathwater and baby (can't do too much harm, other options exist). Needless to say, I will be writing the W3C on the topic of standards very soon, with a similar point.

The floor is open to comments. And I will respond as quickly and often as possible- provided you put down your cookie and glass of punch to post in a reasonably friendly manner.

Slashdot Top Deals

I think there's a world market for about five computers. -- attr. Thomas J. Watson (Chairman of the Board, IBM), 1943

Working...