text:
User talk:Matt Crypto/archive1

Greets
Hi Nikki ,

You've been doing some excellent work over the last couple of days on the crypto related articles. Welcome to Wikipedia! -- Arvindn 15:13, 11 Mar 2004 (UTC)
 * Thanks Arvindn! Do you do much work on the crypto articles yourself? Nice to meet you anyway. (P.S. I've sent you a somewhat garbled email about your Javascript Email Obfuscator, sorry about that)...Matt 17:10, 11 Mar 2004 (UTC)

Great work on block cipher! Lunkwill 07:30, 14 Mar 2004 (UTC)

Alan Turing
Excellent work over at Alan Turing. Keep it up. →Raul654 06:01, Mar 15, 2004 (UTC)
 * Cheers! BTW, does the → in your signature mean anything? Matt 06:35, 15 Mar 2004 (UTC)
 * Nothing special about the right arrow - I just wanted something to differentiate my sig from other people. Others (*cough*Cyp*cough*) have had some sigs that were over the top, so I wanted to keep it subtle. →Raul654 06:41, Mar 15, 2004 (UTC)

 * I see ;-) Can you set a different signature for ~, or do you have to manually insert each time? Matt 06:51, 15 Mar 2004 (UTC)
 * It's an option in your preferences. Log in to Wikipedia, and go to the top right. There should be a link there. →Raul654 07:13, Mar 15, 2004 (UTC)

Matt, Have just stumbled on your work on TEA and XTEA. Superb! Congratulations. Let's see if we can get all the crypto related articles to this standard of quality. ww 16:08, 17 Mar 2004 (UTC)

Likewise Lucifer. ww

And ,see my note at Talk:List of crypto... ww 15:43, 25 Mar 2004 (UTC)

CRYPTREC
Matt, On the CRYPTREC article, thanks for the comments on my Talk page. Those of us who don't read Japanese do have some problems with the Web site since much of the material (slide presentations, etc) are in Japanese. It is indeed hard to follow.

As best I can make out, the project is ongoing. They seem to expect to produce approximately yearly reports. It being (apparently) the official government project on these issues (akin to CSEG in the UK or one division of NIST in the US), there is I think a more or less permanent committment. Here and there there are statements about the necessity for keeping on top of new developments (new attacks, new mathematics, ...) which imply a sensible and responsible approach to recommending (approving, endorsing, ...) crypto algorithms/protocols/etc., including extension in time.

I, on the other hand, remain uncertain whether NESSIE is likewise. As nearly as I can tell most of their stuff is output in English (of which I can, more or less, make sense) and I've trolled through most (all?) of it, but I still can't tell. I haven't sent mail to them asking as I haven't wanted to contribute to their overhead load. The RIPE project (NESSIE's predecessor involving many of the same personnel) was self limiting. Will NESSIE terminate, has it already done so? Can you enlighten me? ww 17:46, 25 Mar 2004 (UTC)

 * I think NESSIE's done, e.g. talks about finalists and winners (like in AES process), and  gives a clear time schedule that ended March 2003. I can't find anything similar at CRYPTREC, but I've just assumed that it was hidden away somewhere in Japanese... — Matt 18:06, 25 Mar 2004 (UTC)

Matt, Two extended sessions at CRYPTREC have produced (finally!) something that's actually useful. At least as a first pass. There is more to be done, but I'm CRYPTREC'd. I'm going to take a break from it for a few days. Take a look if you would and put together some improvement ideas if you have time. I've not come up with a better way to include the qualifications from CRYTPREC about this or that algorithm. I want to avoid footnotes on the grounds that nobody ever looks at them. Ideas? ww 19:59, 29 Mar 2004 (UTC)

Encyclopedia of Cryptography and Security
Matt, Nope. Haven't heard about the Ency of Cryp and Sec. It's a reputable technical publisher (published some of Galileo's stuff, if memory serves) and if the contributors are good enough (and the editing is good enough -- an vital but very different matter) it might be expected to be worth the reading. Thanks for the heads up.

I've left a message at T:padding for you. The dropped penny may be important vis a vis our interaction. I'd be interested in hearing your response.

ww 20:38, 12 Apr 2004 (UTC)

Thanks
Thanks for your message, as well as your good edits and creations on the subject of crypto. I feel like I am slacking a bit now, but maybe when I get done with my thesis I'll have more time to dedicate to the mathematical side of things. CryptoDerk 23:13, Apr 12, 2004 (UTC)

oops
Matt,

Oops on --. Will try to remember.

ww 23:44, 12 Apr 2004 (UTC)

Admin Nomination
Hello, I would appreciate your help by earning your vote as an admin. I have been here about 5 months now and have been nominated. I have made many contributions and have improved on my editing and behavior. I take this seriously, that is why I have gotten into it with Anthony so much. You can look at my user page yourself and see my contribtions. I would appreciate a vote in the yes column if you agree. Again, thanks for your time and help. ChrisDJackson 02:34, 13 Apr 2004 (UTC)

edit conflict, & thanks
Matt,

First off, thanks for chiming in on the admin nomination business. Given our persistent divergence on stylistic points (though I must agree it's been pleasantly civil, though unresolved, unlike some I;ve seen traces of), I wouldn't have expected so warm an endorsement. Thanks again.

I know about the inuse flag, and thanks for suggesting it, but having concentrated on crypto and similarly other obscure stuff, I've only encountered one or two instances. Mostly at Attack on Pearl Harbor. We, on the other hand, have been tripping all over each other like puppies. I may have to go to it.

I trust I've begun to get my -- and my alphabetics better in line of late? I will suggest, however, that names ought to be in alphabetical places at list....Discussion moved to Talk:List of cryptography topics.

ww 16:24, 16 Apr 2004 (UTC)

formatting
Matt, I notice that we are tripping over each other again. Am I doing something against the regs in the formatting of see also. You have been busily correcting them after me. If they are wrong to begin with, perhaps I could get it right the first time and save you the trouble? What's the rule, or is this a convention for crypto stuff that you've adopted?

ww 17:22, 17 Apr 2004 (UTC)

 * For Hagelin, I removed the "See also" because the section is apparently meant for additional topics not yet referenced in the text. I don't think there's a problem with your formatting; there are a couple of acceptable styles for WP - have a quick look at the Manual of Style. I tend to reflexively edit to the longer version whenever there's also an "External links" section, but that's just my whim, I think. — Matt 17:38, 17 Apr 2004 (UTC)

 * Alright. I won't worry about it further. ww 17:40, 17 Apr 2004 (UTC)

Discussion with ww over "ought to"-style
(Moved from Talk:CRYPTREC)

Matt, Not sure why you deleted sentence recommending consultation. Can you say? ww 19:33, 17 Apr 2004 (UTC)

 * Simply — I don't think Wikipedia articles should include recommendations. — Matt 19:38, 17 Apr 2004 (UTC)

 * Matt, Ahhh.. Now some things become clear. We should discuss this, I think. Perhaps off line to avoid clogging talk pages? Since we two are the most active in the crypto corner, we should have an agreed policy else there will be repeated re-edits whose only point will be time waste.
 * You can send Wiki email to me as I have provided an email address. If that's acceptable. ww 19:44, 17 Apr 2004 (UTC)

 * I'm happy to host the discussion on my talk area, if you like; my thesis is that, since Wikipedia seeks to collect and report facts, articles should describe facts, and not tell the reader what they "ought" to do. The latter (prescriptive) is a textbook style; the former (descriptive) is an encyclopedia style. I appreciate that you are motivated by a concern for being as helpful to the reader as possible, but I think we can be more subtle about how we do this. Consider this quote about NPOV and opinions about creative works:

Characterizing opinions of people's work
A special case is the expression of aesthetic opinions. Wikipedia articles about art, artists, and other creative topics (e.g., musicians, actors, books, etc.) have tended toward the effusive. This is out of place in an encyclopedia; we might not be able to agree that so-and-so is the greatest guitar player in history. But it is important indeed how some artist or some work has been received by the general public or by prominent experts. Providing an overview of the common interpretations of a creative work, preferably with citations or references to notable individuals holding that interpretation, is appropriate. For instance, that Shakespeare is one of the greatest authors of the English language is a bit of knowledge that one should learn from an encyclopedia. Notice, determining how some artist or work has been received publicly or critically might require research; but that reception, unlike the idiosyncratic opinion of the Wikipedia article writer, is an opinion that really matters.

 * — Matt 21:09, 17 Apr 2004 (UTC)

 * Matt, You will find a thread lossage response to the reply you didn't make at Talk:Certificate Revocation List. It's hereby incorporated by reference and incoherence.

 * I recognize this concern on the part of WP 'standards', but argue that it doesn't apply in this case. I am not suggesting that you or I or anyone should endorse this or that algorithm over all others -- or protocols or books. That's not my position. It is my position that readers are disserved if a salient, nay, dominant fact of life in crypto is not made clear to them as it becomes possible to do so. This is not POV, unless one argues that facts of life are somehow a particular viewpoint. One does not disparage any product, any crypto technique review committee, or any algortihm/protocol/system design/... by noting there are tricky bits in crypto about which users should take especial care lest they get into trouble.

 * It is also, in my view, not POV to note that one's data is subject to attack by assorted miscreants (or corporations in the US where the Wild West of legend has returned in the electronic data arena). Jet Blue airlines has recently released to the Defense Department the account details of some hundreds of thousands of their customers. It is describable reality which those in the (assorted) 'businesses' would characterize, and do, as no problem. Only ignorance, which WP surely should not support, could maintain a state of public acquiesence in this.
 * Public education should include something on this, and WP is an educative medium. Not only the data exploiters' position should be, by silence in appropriate places in WP, let stand in the 'marketplace of knowledge'.

 * It is certainly true that this fact of crypto and data life has policy implications, but I would oppose including policy recommendations in WP. That I find anyone knowing the facts who doesn't reach certain policy conclusions to be numb in a significant sense isn't very relevant.

 * I agree that we should be subtle, but not so subtle as to leave only the data collection interception folks' position the only one on the field. Silence in this case is POV, in my view.

 * As for taking it to your talk page (or mine) if you don't want to take it off line to email, that's fine with me. Since you have mastered more of WP internals than I have in the month or so you've been editing, I suggest it be yours, unless you want to bring me up to speed in that area of WP operations.

 * Enough for now.

 * ww 16:40, 18 Apr 2004 (UTC)

 * I don't disagree with your aims, but one problem I have with an "ought" statement is that they tend not to be easily verifiable facts. Alternatively, a strong presentation of "is" facts will usually suffice to give a reader the gist of what they "ought" to do anyway. If not, an "ought" statement from a cryptographic expert might be quoted. (See also Is-ought problem). — Matt 17:46, 18 Apr 2004 (UTC)

 * Matt, :! I don't think we have an instance of Hume's problem here. I'll come back when I have more time and will add to this. ww 18:46, 18 Apr 2004 (UTC) Back now. Readers ought not to be told what action to take about this or that problem, certainly, but they should be told about the problem, surely. I don't think -- but have impressions both ways -- that we disagree about this. Am I correct?

 * What we disagree about, it seems is where and when to (and quite how) to make such information available. Is this about right?

 * If so, it wouldn't seem to be a Humeian problem of prescription v description. ww 18:56, 18 Apr 2004 (UTC)

Hi Matt and Ww,

While I'm obviously not as active as either of you in crypto, I see you're having the same old, same old discussion once again, and so I thought I'd get a word in.

What I feel is that the content of the warnings is by-and-large ok as long as it is not worded that way. To use an example I've used before, rather than saying "If you want to work in crypto you'd better watch out for the NSA!!!", you can say "prominent cryptographer Adi Shamir has revealed that his early work in cryptography led to threats to his person by certain U.S government agencies", achieving largely the same effect. If the reader gets the message, that's fine; if not, its not our problem.

 * OK, it's essentially the wordings that I have concerns with. I don't think we should have phrasing that plainly says that a user X should do Y; I'd prefer either a factual example (as you suggest), or a quote from someone. — Matt 17:59, 18 Apr 2004 (UTC)

I feel that if at all there is a compromise to be reached then it has to be something like this, so I urge you to consider it.

More concretely,
 * there are some articles where we want a mathematical exposition. WW, don't go adding warnings to those articles.
 * there are others that more related to cryptosystems. Matt, lots of warnings is fine in these articles, as long as you make sure they are worded objectively, in an encyclopedic rather than textbook manner.
 * for articles that fall in between these two cases, such as the main cryptography article, adopt a middle ground. Cut down on the length of warnings and also phrase them objectively.

I'm sorry I haven't read all that you guys have had to say on this issue, or even the entirety of the discussion on this page (sorry... no time), so I might have missed something, or a lot.

 * Thanks for your comments (and yes, there's a lot of discussion!); it's good to have some other remarks. Your compromise suggestion here seems to chiefly be about the volume of warnings (and looks to be a sensible guideline to me), but (I think!) we were mainly disagreeing over the style of saying what "ought" to be, or what's "obligatory", and so forth. — Matt 18:09, 18 Apr 2004 (UTC)

On a vaguely related note, please see my comment on talk:password. Thanks. Arvindn 17:43, 18 Apr 2004 (UTC)

 * Arvindn and Matt, We were (asymptotically) approaching some such position in our discussions of some time ago (along with much else). What you outline is sensible in my view, and acceptable to me in my attempt to act on behalf of Our Reader. This is clearer than anything we had reached back when and is therefore progress in my view. Thanks. ww 18:46, 18 Apr 2004 (UTC)

on adding new articles to List of C and Topics in C
Matt, I'd be willing to add stuff, and have done so once or twice, but have been generally hesitant as your classification criteria are unclear and I didn't want to stumble over them with other things left hanging. eg, cleartext, FISH v Fish, cryto system or cryptosystem, alpha ordering of names, IV at padding, the cryptography article itself, ...

If you can get me in sync with your plans, criteria, and so on, I'll be glad to do the entry myself. And maybe even get it right (you know the --, and such).

ww 15:48, 19 Apr 2004 (UTC)

 * OK, the List of cryptography topics page lists every page with its current location, not a redirect — it's "canonical name" or whatever term. So, basically, I propose that we add every page that's not a redirect, whether its title (or existence) is controversial or not, to the list; that way editors can track all the changes to crypto without having to rely (necessarily) on their watchlists, even to pages with questions remaining about their exact title.

 * Whenever a page gets moved or turned into a redirect, hopefully the list will be updated too, but that's not quite so important — I'm happy to maintain that part. It's just hard to notice new pages added without tracking "New Pages" or laboriously keeping tabs on other editor's "User Contributions". — Matt 16:11, 19 Apr 2004 (UTC)

 * Matt, I'm not sure I've got this. Purple is a redirect to the (misnamed) purple code, but we shouldn't list the redirect? Have I got this right?

 * Yep; the List of cryptography topics is just to describe what's currently "out there", and not any kind of comment or endorsement of it. (Of course, in a reader-targeted list, like Topics in cryptography, it should be whatever name / redirect is most helpful to the reader). If you really wanted a list of redirects as well one could, in theory, use the current list — and a moderate amount of technical wrangling — to automatically generate them. — Matt 21:55, 19 Apr 2004 (UTC)
 * Matt, Wouldn't what's out there include redirect pages? Some will be sensible, others (like 'magic cryptography') either blunders or awkward, but in either case, should not all be included? I only dimly sense the consequences of this and am groping in the dark really. You're likely to have thought more on this. ww 14:12, 20 Apr 2004 (UTC)

 * Such as...User:Matt_Crypto/Crypto_redirects — Matt 00:57, 20 Apr 2004 (UTC)

 * Matt, More on this under separate rubric below. ww

 * (Actually getting purple code renamed has been on my 'backburner irritation and do something about' list for a while. Any thoughts?)

 * We could move it to PURPLE?. Some writers capitalise it, e.g. Bauer's "Decrypted Secrets". — Matt 21:55, 19 Apr 2004 (UTC)

 * Matt, No. The issue I had in mind is that it's not a code. Should be named Purple (cypher) with whatever redirects as exist changed to reflect. this has stuck me as so much effort that I've kept the whole thing far on the backburner. Ticks me off, though, every time I see it. ww 14:12, 20 Apr 2004 (UTC)

 * I doubt it since I can see that some topics are best handled as redirects. For instance, I noticed that there was no article 'foo', but there was an article on 'metasyntactic variable'. NO ONE is going to go looking for that article unless they already know about foo and bar and ..., so for the reader baffled by this foo business, I started the page. It's not much and refers to metasysyntactic variable, but it serves the not already_aware_reader. And evoked a prompt let's merge this msg on the page! So I would think a list might include both 'foo' (even if a redirect) and 'metasyntactic variable'. Do you see my uncertainty here? I can't think of an example in the crypto corner though.

 * I think I understand what you're trying to say here, but, again, List of cryptography topics isn't meant to be any kind of glossary or index for the reader. We have Topics in cryptography and the "Find" box for that. — Matt 21:55, 19 Apr 2004 (UTC)

 * Matt, I understand the point about not for the average reader. But, see above for my 'groping around' comment for a reply to the rest of yours. ww

 * Just thought of one. Should we have entries for Alice and Bob, though perhaps not for 'anyone' else save perhaps Mallory, even though the articles (now nonexistent) are actually redirects to characters in...?

 * Let's we two agree on this one before either of us goes off and does something. I think we need the practice.

 * ww 19:03, 19 Apr 2004 (UTC)

 * OK, I'm be willing to discuss this above stuff, but I see it as being entirely different topic from the "list" thing we've been discussing; I thought we'd better make sure we've got the latter sorted first! — Matt 21:55, 19 Apr 2004 (UTC)
 * Matt, Good. Agreed. This example is hardly of earthshking importance, but can serve, I think for deciding the policy. Which I think is what you're suggesting here. ww 14:12, 20 Apr 2004 (UTC)

article view count page
Matt, I didn't know that could be done! Unless I've missed something, the 'technical wrangling bit' is most impressive! I've noted (elsewhere) that you've learned more about Wiki innards in around a month than I have the entire time I've been here. Most impressive, and perhaps useful.

 * In case you weren't aware, article counts are at http://wikimedia.org/stats/en.wikipedia.org/url_200403.html Arvindn 18:03, 20 Apr 2004 (UTC)
 * Arvindn, I wasn't aware, and I've just found an anonymous edit (at Enigma) which puts my first known activity here 15 Dec 01. And 'that' makes my unawareness (of this and other things) even more chagrining. ww 18:27, 21 Apr 2004 (UTC)

 * Yep, and it's quite amusing to see just how popular Wikipedia's sexual content is...note, though, that there the counts for an article exclude those from its redirects (I think). The "crypto counts" are aggregated, but the difference is usually minor. — Matt 18:22, 20 Apr 2004 (UTC)
 * Hadn't noticed that either. sigh... ww 18:27, 21 Apr 2004 (UTC)

 * Not long back, goatse.cx was the most visited non-special article! With the tragic demise of that charming website, the article has fallen in popularity as well. Still, seven dirty words is not an entirely unworthy successor to the crown ;^) Arvindn 18:35, 20 Apr 2004 (UTC)
 * Or any of this ..... ww 18:27, 21 Apr 2004 (UTC)

Now that we can see that no one else except we two is reading anything... our problem becomes catching folks' attention. I'm thinking about streaking across the main page periodically, or perhaps staging a sit in. What do you think?

 * I think I'm going to take to squinting at cryptography out of the corner of my eye in future, just in case...— Matt 16:48, 20 Apr 2004 (UTC)

 * Oh, I thought Ww meant the wikipedia main page. Its just cryptography? Then I'll just avoid that page :)
 * Thanks to you both, the interest in crypto will decrease still further. I suspect you would both advise against?? ww

Fantastic info. Clearly, some of my expectations about which stuff is being read were well off the mark. I'll have to ponder this to see what result it should have for my editing. Perhaps we should try to get one or more articles featured?

 * Yes, there were a few surprises for me too; I guess it does help to know what is worth spending large amounts of time polishing. For featuring, how about Enigma? — Matt 16:48, 20 Apr 2004 (UTC)
 * Matt, Working on it. jwr's invited comment in Talk got me off the dime a bit in re that. Wait until I get a bit further on in the rework.
 * I'm still considering your attractive bait in re bombe. Perhaps you can entice me further? ww 18:27, 21 Apr 2004 (UTC)

What is the wrangling involved? Is it regularly repeatable? This could be a very useful tool if we can figure out the informational content for policy in the crypto corner. Very impressive! Thanks for the wrangling.

 * A bit of hacky one-off Python / shell / Emacs automation; next time I can make it a little more repeatable, but it's dependent on infrequently posted Wikipedia stats. — Matt 16:48, 20 Apr 2004 (UTC)

 * Yay for python! How about

import string a=open("crypto.list").readlines for l in open("url_200403.html"): title = l.split("/wiki/")[-1] if title in a: print "%s\t%s" % (l.split[0], title)
 * although this doesn't add up redirect counts. Arvindn 18:58, 20 Apr 2004 (UTC)

 * Matt, Suspected it was something like that. Well done! Arvindn, Second the python praise. ww 18:27, 21 Apr 2004 (UTC)

And thanks for the congrats. We'll see if, like editing did, this turns into something I didn't intend. ww 14:12, 20 Apr 2004 (UTC)

Wikiproject crypto
Matt, YATIHN. Sounds good to me, and it will provide a discussion arena for broader topics of policy in crypto corner. My only thought prior to this was the sort of separate page Arvindn created for our now OBE discussion. Or perhaps the new wikibbs. How about you, Arvindn? What do yo think about a wikiproject?

Again, you've found someThing I Hadn't Noticed. I'm not sure how to go about starting it and all, but I'm sure you and Arvindn can dope that out without help from me. Obviously, I never look up from editing! ww 18:27, 21 Apr 2004 (UTC)

WikiMagic
So, I might need to rephrase that... What I meant with as little exposure as possible is that I wouldn't like to expose 'the secret' for every single trick in the WikiPedia. If someone is really interested I feel they should be helped with finding stuff out on their own instead of just being told. I'm not opposed to some secrets being revealed. I'm just saying 'we' -whoever we is- should be selective in what we tell. (As semi-professional I'm protective over the art).

 * OK, though, as a "test case", what would you do if a contributor put in secrets to tricks that might seem to be "too revealing"? Would you advocate removing the secret? (Presuming the "secrets" were otherwise verifiable, of course...).

Hope that was clear :) If you have any suggestions on how to find more magicians on WikiPedia, please let me know. -- MGM 19:22, Apr 21, 2004 (UTC)

 * Maybe you could scan the edit histories for contributors who've added more than just typo fixes, and drop them a line on their talk pages?

P.S. How did you end up on my WikiMagic page anyway?

 * Announcements. By the way, I've been hacking up a proposal for a Wikiproject Cryptography that's inspired by your WikiMagic page, thanks! — Matt 19:52, 21 Apr 2004 (UTC)

apologies
Matt, It appears that a digraph substitution cypher (or plain ignorance) has inhabited my fingers. I refer to the multiple edits you've made correcting del to dle. If you'd told me (or I'd noticed!), I would have been glad (well embarrassed) to correct them myself. I think it's the neuropathy myslef... Thanks. ww 15:09, 27 Apr 2004 (UTC)

sha-1 q?
could you talk about slideability and updateability as applied to Sha1 or maybe just Message_digests in general Hfastedge 21:39, 9 May 2004 (UTC)

 * Sorry, I don't know what "slideability" and "updateability" are, and Google doesn't seem to be of much help; where did you encounter these terms? — Matt 10:31, 10 May 2004 (UTC)

Well for updateability, i see an update func in python's shamodule.c User:Hfastedge/sha1code. and someone said that slideability lets you take  some sum from x[a:b] (maybe not something designed  as sha1), and easily get the sum for x[a+1:b+1]   AND since i suck at groking C code, im wondering if all this update is doing is going from the sha1 for x[a:b]  and updating to x[a:b+N]     dunno. all a mess to me. just curopis Hfastedge 21:09, 10 May 2004 (UTC)

Re: Prospero Alpini
Hey, Matt. I saw that you reverted my entry on Prospero Alpini earlier today. I know it seems kind of outlandish, but that entry is based on interdisciplinary research we've been doing here at Brown University. For the past year, I've been supervising a number of undergraduates concentrating in History, Queer Theory, and Latin who are pouring over manuscripts from the Renaissance period. In particular, we've come across several codices (De Amatoria Virili and Remedia Incesti Amoris, as I mentioned in the entry) which are really significant if they're authentic (and they appear to be). It seems like this relatively obscure figure in botany may be one of the earliest sexual theorists!

Anyway, I know the Wikipedia gets hit with a lot of vandalism (most of it relating in some way to homosexuality), so I just thought I'd clear the air. We're asking several outside professors to come in and verify the authenticity of the documents, so, if it turns out that they're just really good fakes, I'll revert the entry myself.

Thanks! Gillo

 * Regarding your reply: that's entirely understandable. Everyone here at Brown has the 128.148.* prefix on their IP address. In fact, I'm fairly sure that the spurious revision that you mentioned ("Gaykin") was the work of a friend of mine who initially linked me to the Wikipedia. Sorry for the inconvenience.

 * I'm not sure if there's any existing research on the subject available online; frankly, there's barely any in print. Most of our work is based entirely on primary source material in the collection of the University. The manuscripts which I mentioned in the article were a small part of a donation from the Getty Trust that also consisted of a number of texts related to the sciences. Somehow the Classics department didn't get around to translating them until last year; apparently, they don't have any sense of urgency regarding texts that are only a mere 400 years old.

 * Anyway, the point of all this is that almost nothing has been published on Prospero Alpini's interests outside of botany, which is an oversight I intend to rectify when I've completed the corresponding chapter of my thesis. It will definitely be available online, and I'll make sure to post a link here if you're interested. We're also trying to put together a web site about the project, where we'll post the text and images of the manuscripts. I'll keep you posted. Gillo

your PGP comment
Matt, Your reluctant oppostion to PGP as featured concerned several styple points as I understand it. Will you address them, should I, jon, or ...? Since this is now a 'public' issue, it would be quickest if you were to make those changes you feel necessary.

The following may help. l'affaire Z is the criminal investigation by US Customs of Z for violation of US munitions export regulations. It was launched as a result of a patent licensing complaint against PGP filed with Customs (they enforce patent and trademark stuff in re import/export). The awkward sent you quote was mine and was deliberately so, to avoid eye glaze by the reader. It is the topic sentence of that paragraph as I recall.

If there's anything else I can do to help, don't hesitate to ask. I'm sure jon will be willing to do so as well, but of course can't speak for him directly. ww 18:15, 13 May 2004 (UTC)
 * Matt, I remain uncertain how you wish to handle this. Should I go and attempt to edit to meet your objections? Or not? ww 19:38, 17 May 2004 (UTC)
 * Matt, Between the edits Isomorphic and I made on the 19th, and yours earlier, it looks as though all the concerns you had have been addressed. Is this so? If not..., more needs to be done. On the other hand, if so, it would appear that there remain no objections to the article going on the FA list. I take it that you'd be willing to 'revise and extend' your comment to suit? Thanks, ww 13:59, 20 May 2004 (UTC)
 * Erk, sorry, but I'm afraid I still think there's need for improvement in this article; a few things pop to mind as examples (==PGP as an Internet standard== is an entire section that consists of just three sentences; the article could be helped by some with overview information -- something like a timeline of PGP, or a table of versions -- to help make the detail more accessible; I think someone else mentioned screen shots.) I'll try and commit some time to editing it (though I'm going to be away this weekend), but I think it needs a reasonable amount of work still. — Matt 11:00, 21 May 2004 (UTC)

subheading caps
Thanks for the heads up about the 'standard'. It's dumb and I'll probably leave a note somewhere about it, but I'll go along (gritttted teeth). ww 13:35, 14 May 2004 (UTC)

Politeness
Thank you! That made my morning. Hope to see you around elsewhere. Yours, Meelar 12:47, 27 May 2004 (UTC)

Virgil Exner
Thanks so much for your suggestions re: Virgil Exner - I've expanded the section on the "Forward Look." What I was trying to get across was the difference between the cars of 1947, 1949, 1951, and Exner's 1958 1957 & 58] models, such as the one displayed on the page. It was a rather drastic change, but hard to put into words :) I also haven't really talked about his long-lerm effect on the design industry, but I really don't know much about this topic. Exner piqued my interest just enough for me to do all this research on something I know nothing about, which is why I feel it needs a lot of peer review.

Again, thanks! -PlatinumX 07:26, 4 Jun 2004 (UTC)

Lock and auto diagrams
Thanks for the compliments on the lock and auto diagrams. Since I created all of them, the licensing status is GFDL. Nice diagrams on your user page too, by the way! I actually sort of understand them, since I took a course on cryptography a while back. -- Wapcaplet 21:22, 5 Jun 2004 (UTC)

 * It might be worthwhile to stick a GFDL notice on my diagrams. Many of them were uploaded before we had a nice mechanism for adding such a notice, so I sort of just relied on the assumption that unless otherwise stated, all submitted content is GFDL. I've had a couple questions about their licensing, though, so it's probably a good idea to do that now... I think it'd be fun to model an Enigma machine, provided I can find some good diagrams to work from, but I suspect that the workings of that might be better illustrated with this kind of diagram; I am not sure what a 3D representation would add to that. Any suggestions? -- Wapcaplet 23:22, 5 Jun 2004 (UTC)

re: Featured article candidate Fanny Blankers-Koen
Matt, thanks for your note on Fanny Blankers-Koen at the featured article candidates page. I think I've now eliminated all problems with past/present tense ; I also posted a reply to your other remark. Could you take another look at it? Thanks, Jeronimo 12:49, 8 Jun 2004 (UTC)

rply to mc
Matt, On my talk page, under your comment. ww 16:50, 9 Jun 2004 (UTC)

Thanks for WikiProject Crypto invite
Matt, thanks for telling me about WikiProject Cryptography; I never knew it existed, unbelievably enough. I've joined it and I've started work. Thanks!

Thanks for WikiProject Crypto invite
Matt, thanks for telling me about WikiProject Cryptography; I never knew it existed, unbelievably enough. I've joined it and I've started work. Thanks! --Decrypt3 19:53, Jun 10, 2004 (UTC)

confusion about confusion
Hello,

this is one of my first visits on Wikipedia, and if my editing experience is very scarce yet, I duly apologize.

OK, now to the discussion: I have recently been editing the article "confusion and diffusion" because I became aware of a statement in the article which simply is not true in my opinion.

Unfortunately my changes have been un-done so I wanted to take a chance to argue in favour of what I think is correct.

The point is that confusion and diffusion are -- at least in some lecture notes and books -- explained just in a self-respective way: confusing.

But if you happen to have read Shannon's original paper, which should be taken as the origin of any citations, the terms are made rather clear:

There are two "inputs" which lead to a ciphertext. One is the plaintext, the other one is the key. Diffusion leads to an elimination of a statistical relation between changes in single plaintext bits and changes in single ciphertext bits. If you change a plaintext bits, a cipher with good diffusion should lead to a 50 pc chance for _any_ ciphertext bit to change.

Confusion, on the other hand, does the same for the key<->ciphertext relation.

As I stated, I did the changes the day before yesterday, but they have been un-done.

Please read the original paper to get the terms correct, and then please re-do my changes. The current explanation is simply incorrect.

A link:

http://www.cs.ucla.edu/~jkong/research/security/shannon1949.pdf

Shannon and chess
Matt, The justification of including chess as link at Shannon is that he was, with Turing, one of the first to think about chess playing programs on computers. In fact, he built one (a machine, I think) if memory serves. As such he belongs with (was it Newell and Simon?) as one of those who very early proposed using computers to perform as a game player. In the grand tradition (if without the fraud) of The Turk. ww 18:06, 11 Jun 2004 (UTC)

 * Ah, that's quite interesting; would you be able to add that to the article? — Matt 01:52, 12 Jun 2004 (UTC)

 * Much of my own stuff is inaccessible just now, so whatever it is that I could check of my own is out of reach for the moment. I'll look around the Net to see if I can scare up something. ww 16:30, 22 Jun 2004 (UTC)

Main WikiProject page
Matt, since you're basically the father of WikiProject Cryptography, I wanted to tell you about the main WikiProject page. WP Crypto isn't listed on there. I would list it myself, but I'm not sure what category it falls under. I would lean toward creating a separate subcategory of Science. --Decrypt3 13:44, Jun 12, 2004 (UTC)

 * Yes, I think I wasn't sure about that at the time, and then forgot all about it! Cryptography seems to fall under several categories, but perhaps we could stick it under both Mathematics and Computing? I'm not convinced it fits well under Science, as it's not so much about describing the physical world. Feel free to go ahead, though, even if you're unsure; I'd hate to think that, just because I started WikiProject Cryptography, I had any more say so than anyone else about what happens with it ;-) — Matt 18:44, 12 Jun 2004 (UTC)

 * I went and put it under Mathematics - after all, it's not all about computing. --Decrypt3 20:56, Jun 12, 2004 (UTC)
 * But it does fit under Engineering. Is there a WikiProject of that sort? ww 15:24, 21 Jun 2004 (UTC)

Quick question
Just a quick question: what software do you use to make the diagrams you have on your user page? --Decrypt3 18:36, Jun 12, 2004 (UTC)

 * I've been using Dia on a Linux machine; it's quite nice for some things, the only annoyance is not being able to include mathematical symbols and the like. — Matt 18:38, 12 Jun 2004 (UTC)

About Duplicate Links
Just read your comment about the Billboard featured article nomination. So are you not supposed to have links both in the content of the article and at the end? I'm used to offline articles putting a footnote like (1) and then putting the reference next to the (1) at the bottom, but that doesn't happen in Wikipedia AFAICT. I'm new here :) Jkeiser 22:24, 12 Jun 2004 (UTC)

 * I think so, though it's not explicit in the Manual of style. — Matt 22:41, 12 Jun 2004 (UTC)

Another World
I still don't understand what's so horrible about my article. Can you explain it to me again? TheCustomOfLife 01:15, 13 Jun 2004 (UTC)
 * I don't think it's a horrible article; remember that Featured Articles are the very best of Wikipedia, so they have to be pretty good. Just because I object, doesn't mean that it's not a decent article, just that I think it could be improved to be excellent. The problem I have is that I think the article contains too much "trivial" information, as in a discussion of the exact ordering of the credits at the end of each episode, and each individual variation of how the programme is announced. — Matt 01:25, 13 Jun 2004 (UTC)

 * A technical history was needed. I think those sections are nice in that they illustrate the "behind the scenes", things viewers never knew, or in some cases, never saw.

 * If you don't like them, honestly, please give me a suggestion as to what needs to be done. If you don't suggest anything, I won't change it. TheCustomOfLife 00:53, 14 Jun 2004 (UTC)

 * OK. My objection is based on my opinion that there's too much detail in the "Technical History" section; assuming this is generally agreed upon, it could be fixed simply by trimming it down. In particular:
 * * Trim the "The Announcer" section down to one paragraph, mentioning Bill Wolff and giving a single example of a typical introduction and conclusion.
 * * Lose the "Closing credits" section entirely, perhaps moving the fact about Denise Alexander's crediting stipulation to her article page (might not be a bad idea to copy this fact there in any event).
 * An alternative might be to move sections to separate pages, e.g. History of the announcements of Another World or The closing credits of Another World.
 * However, I'd prefer some more community comment on how we can judge whether facts are too trivial to include or not for a particular article. I'm convinced there is a limit (I mentioned an extreme example on the Featured Article's page — the number of thes spoken in the dialog), but I don't have guidelines (that's why I talk about a "gut feeling"). — Matt 01:27, 14 Jun 2004 (UTC)
 * Closing credits and announcements moved to separate pages. Links are given at the end of the opening credits section. TheCustomOfLife 01:42, 14 Jun 2004 (UTC)
 * I'm now supporting this. — Matt 02:02, 14 Jun 2004 (UTC)

 * I've replied to my newest peril/dilemma on my talk page. TheCustomOfLife 21:08, 14 Jun 2004 (UTC)

Academia FAC status
Hi, see that talk page for my response to your helpful objection. Does that balance point get at what you were looking for? Thanks - Taxman 18:05, Jun 15, 2004 (UTC)
 * I was just going to mention that. I wanted to let you know I took the liberty of moving 'academia' from objections to no-objections. →Raul654 03:01, Jun 16, 2004 (UTC)

Bible atrocities
Matt, excellent work on the Bible atrocities article. It has been improved quite a bit.

One of my main sources (as well as D. Friedman) on the subject who may interest you is:
 * Mendenhall, George E. The Tenth Generation: The Origins of the Biblical Tradition, The Johns Hopkins University Press, 1973.
 * Mendenhall, George E. Ancient Israel's Faith and History: An Introduction to the Bible in Context, Westminster John Knox Press, 2001.

He was a Navy cryptographer during WWII, one of the guys who kept successfully breaking Japanese military codes in the Pacific theater. After the war, he turned his cryptographic skills (and exhaustive skills with ancient Near Eastern languages and scripts) to the Old Testament as a professor and scholar at the University of Michigan.

Cheers, Fire Star 19:46, 16 Jun 2004 (UTC)

Bombe
Prepare to be jealous.:) I had the pleasure of visiting the National Cryptologic Museum on Thursday. Source for the believed existence of another US bombe was Jack Ingram, Curator of the Museum, during a tour of the museum (the rest of the group appeared to be NSA, no surprise - I was just tagging along, with permission, of course). He told of searching for it and not finding it whole, but noted that they can be broken down into many smaller pieces and thought that it may be buried in storage somewhere which just hasn't yet been discovered. I forget who he mentioned as his source for the statement that there should be two of them. The Bombe at the NCM is now enclosed in a plastic or glass enclosure, to protect it from more of the damaging contacts and parts thefts it experienced while it was at the Smithsonian. Jamesday 20:13, 18 Jun 2004 (UTC)

Yes, some caution is needed for stories in this area, particularly anything within the last few decades, since secrecy and deception are tools of the trade! I'll be back in the UK in a few months, so I'll probably arrange a visit to Bletchley Park to complete the visit set.:) Jamesday 02:24, 21 Jun 2004 (UTC)

Polybius Square
Thanx for the suggestion, just got it as I was marking it up

Engima images
Matt, Nice images. Worth adding. Thanks. They need some more illuminating captions and I'll look into that as time permits.

What's the meaning of the cryptic initials following the English language caption? The PD I can guess at, I suppose. ww 15:32, 21 Jun 2004 (UTC)

 * The initials of Greg V. Goebel, and Public Domain. — Matt 15:41, 21 Jun 2004 (UTC)

Category alterations
I understood we were trying to organise the cryptography category, and I believe by piping some of the entries this would alphabetise those articles. I'm currently looking at C, and some of those articles didn't belong under C, and by sorting the category using the pipe, it replaces the item under the correct letter. That's how I understand it anyway. --TonyW 15:43, Jun 21, 2004 (UTC)

 * Thanks for your response, and I'm only too happy to help where I can. I'm still fairly new to categorisation, and I discovered by piping you can alphabetise articles, esp those involving names. As for Torus, for some reason that entry was under C, and rather than paste the whole name I entered just the first part, and it has indeed sorted it under T. Technically, I think we're supposed to enter the whole title when sorting, but got away with it on this occasion. X is a different matter tho - I notice they are not strictly in order, so that's probably a case of making show the whole name is entered or something. --TonyW 16:08, Jun 21, 2004 (UTC)

 * Oh, my apologies for getting that wrong! I'll get there in the end. -TonyW 20:17, Jun 21, 2004 (UTC)

 * I've now realised some entries I've done contain one or more of the sub-categories e.g. . Are we saying those only need to be in the one category because a sub-cat is available? If so, I'll happily just run through them all, and check them out. --TonyW 20:26, Jun 21, 2004 (UTC)

Ok. Here's a question: should 3-Way be in seeing as it's a block cipher? --TonyW 20:36, Jun 21, 2004 (UTC)

Glad to have been of help. I completed the remaining letters in 'Help wanted', and have since gone through each letter, one by one, to ensure each article is categorised in the way we've discussed. --TonyW 12:36, Jun 22, 2004 (UTC)

Edits
I have added some of what made AW unique to the front page but not all of it. Review and see if it's enough. TheCustomOfLife 22:39, 21 Jun 2004 (UTC)

rply re PR
Matt, "Grin!" is exactly the attitude I think we should be taking towards that TT. Look, that TT will provide more than a grin (perhaps even a few guffaws) to onlookers. I say let's let anyone look on! At least they won't think us cryptiacs so dull after reading about all that! The thing that bothers me is my typos, which may convince folks that I'm some kind of spasmodic. Well, one doesn't quite control the views others have of one if one does anything publicly visible, does one?

On another topic altogether, I've discovered a clearly identifiable downside to your efforts to be bold in extirpating the satanic 'y'. When you changed Great cypher to Great cipher, my watchlist lost track of it. Clearly a bug in MediaWiki, I think. Or is it....

How are you proposing to do this PR evolution, anyway?

ww 20:08, 24 Jun 2004 (UTC)

 * "Great Cypher" -> "Great Cipher": That is a bug, I thought the software now tracked moves? (btw, that was because "Great Cipher's" a name for a specific cipher, rather than being a descriptive title). re PR; just dropping a note at the Village Pump, and probably the Talk: pages of everyone listed at WikiProject Cryptography. — Matt 20:13, 24 Jun 2004 (UTC)
 * So, specific cipher's names must be spelled w/ i? I think I'm lost here. Yet another attack on we virtuous fans of wyverns and kyngs entangled with them.
 * No - just that if a name has a certain spelling, we should write it as such — I was under the impression that "Great Cipher" was the name.
 * Matt, The name was French of course (grand chyffre or something), and French spellings are hardly binding on English speakers/writers, nor pronounciations either -- to the eternal agnst and fury of the French. The usual English versions I've seen (at least those remembered) are spelled with y for no reason I can make out. I wonder what the original French spelling was... Might there have been an attempt to retain some of it? It might fit with the effective policy in English of keeping just enough to make it clear it came from French, but to muck it up enough to raise Continental BPs. Maybe it's good they drink so much wine over there. They need the French paradox just to cope with the cardiovascular effects of those darned English and their wycked ways.
 * I just went with what I'd seen. No attempt to coerce the world to the virtues of y. ww 13:45, 25 Jun 2004 (UTC)
 * Oh, OK, sorry, must have had an over-keen moment! Feel free to move it back if you like. — Matt 15:08, 25 Jun 2004 (UTC)
 * Anyway, I had hoped you had an in with Fleet Street or something. Sigh... Have you tried the BBC reporter, Reynolds? He'd probably be interested in an open content book, and would find the German progress of some EU interest. They're always looking for story ideas... ww 20:19, 24 Jun 2004 (UTC)
 * Maybe when we're finished; certainly, we should post the finished "Reader" around various NG's and the like. — Matt 20:30, 24 Jun 2004 (UTC)
 * Matt, NGs? On another point, I was assuming from (your?) example that comments were intended to be anonymous along some line of reasoning like a corporate work. But are we thus to be credited/blamed and so on? Do you want shared cover as editor? How is this supposed to work? ww 13:45, 25 Jun 2004 (UTC)
 * Oh sorry, I try and avoid acronyms for just this reason...I meant "newsgroups" (NG) and other internet forums. Regarding signing, it was just because it's a discussion section, and it can get very confusing (once conversations start) if noone has signed their messages! As regards blame and credit, I'm hoping it just comes across as "the work of Wikipedia" — a collaborative effort. The convention for WikiReader is (apparently) to run a script that extracts the user-names of contributers from the page histories, and list them somewhere. — Matt 15:08, 25 Jun 2004 (UTC)
 * Matt, OK. You'll remain the sole editor (and get all the blame/credit).
 * Eh? "I'm hoping it just comes across as "the work of Wikipedia" — a collaborative effort." (previous comment); I only hope to coordinate a WikiReader, not take credit for work of which I'll have only contributed a fraction. — Matt 13:20, 28 Jun 2004 (UTC)
 * As for comments, none were signed. Are they then supposed to be? I'm still not clear on this. As for your comment about the summary table, I thought you were summarizing the collective view. Are we to enter our own evaluations in this shorthand format? I'll change Great Cipher back to Great Cypher when I get a round tuit. They've been in short supply. Sorry about missing NG, I should have caught it. Chagrined again! ww 14:57, 26 Jun 2004 (UTC)
 * I think it would be useful for comments to be signed, as is normal in Wikipedia discussions. I was hoping people (other than me) would enter their own evaluations in the summary table, and that we'd thereby have several scores for each article. — Matt 13:20, 28 Jun 2004 (UTC)

<=== eschew too many ':'
 * Matt, Oh. I guess I'll have to figure out how the table thing works, in that case. It wasn't clear that was how it was supposed to go. As for deleting names of contributors in the resulting Reader, I didn't have any thought the page histories would be included anyway. I guess I figured there would be a title page with Reader edited by x or alternatively, x, y, and z.
 * There'll probably be a "contributors" box somewhere; see page 42 of http://tkarcher.gmxhome.de/WikiReader_Schweden.pdf for an example. — Matt 14:59, 28 Jun 2004 (UTC)
 * On another page history question altogether, I just looked at the summaries in the page history for Talk:James Ellis. You once suggested that my comments on Talk pages are a bit obscure. I can now return the compliment in re edit summaries. Alice Cooper???? You've lost me again. ww 14:50, 28 Jun 2004 (UTC)
 * Ah, sorry, I meant to link it: Alice Cooper (a man) — I concede it was a not very helpful edit summary! — Matt 14:59, 28 Jun 2004 (UTC)
 * Matt, Yes I understood Alice Cooper is really a man. And I understand about Culture Club (I think -- though I don't particularly enjoy either's music). My problem was with Cooper's connection to James Ellis. Is there any?
 * Not that I'm aware of, but (if I recall correctly) the edit was correcting wrong-gender references to Alice (he / his). The not-so-witty edit summary was that if Alice was a "he", then he was probably Alice Cooper. — Matt 16:21, 1 Jul 2004 (UTC)
 * Matt, Ah, wet squib humour. Now I get it. You would not believe the hyphotheses I entertained about that... Thanks. ww 16:30, 1 Jul 2004 (UTC)
 * On another point altogether, you have changed case on both (?) of the only two category tag edits I did. I wrestled with that and left it in the only case that actually worked. It seems I've missed something yet again. Can you enlighten me? ww 16:11, 1 Jul 2004 (UTC)
 * Yes, there were 25 pages linking to Category:Cryptographic Protocols; category style is to use lowercase for second and subsequent words, I believe, and this is certainly the case with the other crypto categories. Accordingly, I changed all 25 pages to Category:Cryptographic protocols. — Matt 16:21, 1 Jul 2004 (UTC)
 * Matt, I tried it both ways and only the UC for P worked. I expected there was some convention that I didn't know about that I was traducing with a lc P. Thus the UC P. But ... ww 16:30, 1 Jul 2004 (UTC)

Last words of Jesus
Yeah, I left a couple comments at Talk:Last words of Jesus.Stevertigo

Traditional counties of England
I've made changes to the article per your objections. I haven't tried to pull the abbreviations into the main list because I that would make it look messy and not fit properly. Morwen - Talk 17:09, 1 Jul 2004 (UTC)

I've now turned it from a (rather boring) list into an interesting paragraph. How does that look? Thanks, Morwen - Talk 14:33, 2 Jul 2004 (UTC)

Thanks!
For taking the time to recapitalize Category:Cryptographic protocols.

Re: Coca-Cola's nomination as a featured article
I have refactored the article to accomodate your suggestions on WP:FAC. I hope you could provide input on the article as it is now and where it could use work. Thanks. Johnleemk | Talk 12:58, 5 Jul 2004 (UTC)

Laika
Your concerns have been addressed in the last few revisions. Thanks. --Zerbey 19:49, 5 Jul 2004 (UTC)

Other concerns about Blok A cores and famous dogs have been addressed. I'm not overly keen on the famous dogs section it doesn't seem to fit somehow. If you have an MSN/Yahoo/ICQ id please let me know via IRC today --Zerbey 17:58, 7 Jul 2004 (UTC)

Charles Graner

 * Please do not flag Charles Graner as "contested" on featured article candidates. Please notice the content of the heading at the FAC page; "If you are the only remaining objector, change "Contested" back to "Uncontested." Thanks and regards, Neutrality 04:36, 7 Jul 2004 (UTC)
 * You misunderstand; the clause you quote begins with the predicate, "If you withdraw your objection..." — Matt 04:32, 7 Jul 2004 (UTC)
 * Everything objection cleaned out was either not actionable or solved (with the exception of yours). I acted on behalf of the objectors. If they wish, or if they do not feel their objections were solved, then they can take proper action (added/replacing/rewording objections or listing the entry on Featured article removal candidates). Thanks. Neutrality 04:36, 7 Jul 2004 (UTC)

Mount St. Helens
Could you take a look at that article again and comment at Featured article candidates? --mav 08:03, 8 Jul 2004 (UTC)

Guitar Solo
Your rewrite blew me away! The article is so much better now! Thanks a million. Two Halves, who should not try to do two things at once!

Middle-earth
Is that lead section OK? Morwen - Talk 19:45, 11 Jul 2004 (UTC)

FAC
Thanks for the observations on FAC regarding Russian constitutional crisis of 1993. I noticed and fixed the problems you brought to light 172 17:05, 13 Jul 2004 (UTC)
 * More headings were added . Thanks for the advice. 172 02:00, 14 Jul 2004 (UTC)

Privacy policy
Good evening. You recently weighed in with an opinion on the discussion at Wikipedia:Votes for deletion/User:Tim Starling/Password matches. On the basis of that discussion, I have proposed some changes to our privacy policy at Draft privacy policy. I would appreciate your thoughts if you have time. Rossami 22:18, 13 Jul 2004 (UTC)

XSL Attack FAC status
Hi Matt, XSL has stalled a bit. I'd like to support it, but I think it really needs more details on the attack itself. You seem well qualified to do that. - Taxman 21:07, Jul 23, 2004 (UTC)
 * Sadly, I can't remember how the nitty-gritty parts of the attack worked! It'll take me a while to reread the papers and understand well enough to cook up an example, too long for the FAC process I'm afraid :( Maybe I can renominate it in a month or so... — Matt 02:16, 26 Jul 2004 (UTC)

title: User talk:Matt Crypto/archive1


text:
McArthur

McArthur may refer to:

People

 * McArthur (surname)

Geography

 * McArthur, Arkansas, an unincorporated town in Desha County
 * McArthur, California, in Shasta County
 * McArthur, Modoc County, California
 * McArthur, Ohio
 * McArthur Basin, a large intracratonic sedimentary basin in northern Australia
 * McArthur Lake (disambiguation)
 * McArthur River, Northern Territory, Australia
 * McArthur River uranium mine, Saskatchewan, Canada
 * McArthur River zinc mine, Northern Territory, Australia
 * McArthur Township, Logan County, Ohio

Ships

 * USC&GS McArthur (1874)
 * NOAAS McArthur (S 330) (formerly USC&GS McArthur)
 * NOAAS McArthur II (R 330)
 * MV McArthur, a private maritime security ship in service since 2007

Other uses

 * McArthur Court, an arena at the University of Oregon campus in Eugene
 * McArthur Glen Designer Outlet Wales, a commercial development consisting of around 90 different stores

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: McArthur


text:
McBee

McBee is a surname. Notable people with the surname include:

 * Cecil McBee (born 1935), American jazz musician
 * Deron McBee (born 1961), American actor
 * Lee McBee (1951–2014), American blues musician and singer
 * Pryor McBee (1901–1963), American baseball player
 * Rives McBee (1938–2023), American golfer
 * Thomas Page McBee (born 1981), American author
 * Vardry McBee (1775–1864), American businessman, philanthropist and city founder

title: McBee


text:
McBride

McBride may refer to:
 * McBride (surname), the Irish surname held by many notable individuals

Places

 * Sebree, Kentucky, United States, originally known as McBride
 * McBride, Michigan, United States
 * McBride, Mississippi, United States
 * McBride, Missouri, United States
 * McBride, Oklahoma, United States
 * McBride, British Columbia, Canada
 * McBride Branch, a stream in Indiana, United States
 * McBride Range, a mountain range in British Columbia, Canada

Media

 * McBride (film series), a 2005 series starring John Larroquette
 * McBride's Magazine related to Lippincott's Monthly Magazine and Scribner's Magazine
 * Amelia McBride, lead character of the American comic book series Amelia Rules!

Other

 * McBride & the Ride, a former country music band from Nashville
 * McBride plc, British manufacturer of personal care products
 * McBride Secondary School, a high school in British Columbia
 * Don McBride Stadium, a baseball ballpark in Richmond, Indiana
 * No Man's Land (Eric Bogle song), also known as "Willie McBride"

title: McBride


text:
McCall

McCall is a Gaelic surname, of Irish and Scottish origin.

Notable people with this surname include:
 * Andy McCall (footballer, born 1911) (1911–1979), Scottish footballer and manager
 * Andy McCall (footballer, born 1925) (1925–2014), Scottish footballer, father of Stuart McCall
 * Annie McCall (1859–1949), English doctor
 * Archie McCall (1867–1936), Scottish footballer
 * Bruce McCall (born 1935), Canadian author
 * Carl McCall (born 1935), U.S. politician
 * Christina McCall (1935–2005), Canadian political writer
 * Daniel T. McCall Jr. (1909–2000), justice of the Supreme Court of Alabama
 * David McCall (bishop) (1940–2021), Australian Anglican bishop, husband of Marion
 * Davina McCall (born 1967), British television presenter
 * Duke Kimbrough McCall (1914–2013), U.S. religious leader
 * Edward McCall (1790–1853), U.S. Navy officer
 * Frederick McCall (1896–1949), Canadian aviator, World War I ace, businessman
 * George A. McCall (1802–1868), U.S. Army general and amateur naturalist
 * Grayson McCall (born 2000), American football player
 * Guadalupe Garcia McCall, a Mexican-American poet and novelist
 * Helen McCall (1899–1956), Canadian photographer
 * Ian McCall (footballer) (born 1965), Scottish footballer
 * Jack McCall (1850s–1877), U.S. outlaw
 * James McCall (footballer) (1865–1925), Scottish footballer
 * James McCall (politician) (1774–1856), American merchant and politician from New York
 * James McCall (veterinary surgeon) (1834–1915), founder and the first principal of Glasgow Veterinary College
 * John E. McCall (1859–1920), judge and politician from Tennessee
 * John T. McCall (1863–1950), New York politician
 * Kevin McCall (born 1985), American rapper
 * Louis A. McCall Sr. (1951–1997), American singer, songwriter, drummer and co-founder of the funk/R&B band Con Funk Shun
 * Marion McCall (born 1943), Australian pilot, wife of David
 * Marquan McCall (born 1999), American football player
 * Matt McCall (racing driver) (born 1981), American stock car racing driver and crew chief
 * Oliver McCall (born 1965), U.S. boxer
 * P. J. McCall, songwriting pseudonym of Peter Dawson (bass-baritone)
 * Patrick Joseph McCall (1861–1919), Irish songwriter (also known as P. J. McCall)
 * Phil McCall (1925–2002), Scottish actor
 * Robert McCall (disambiguation), multiple people
 * Robin McCall (born 1964), American stock car racing driver
 * Roz McCall, Scottish politician
 * Samuel W. McCall (1851–1923), U.S. politician
 * Steve McCall (born 1960), English footballer
 * Stuart McCall (born 1964), Scottish footballer
 * Tahjere McCall (born 1994), American basketball player
 * Ted McCall (1901–1975), Canadian journalist and comic strip writer
 * Thomas McCall (disambiguation), several people
 * Tom McCall (1913–1983), U.S. politician
 * William McCall (disambiguation), several people
 * Willie McCall (footballer, born 1898) (1898–1966), Scottish footballer
 * Willie McCall (footballer born 1920) (1920–1985), Scottish footballer

Fictional characters include:
 * the title character of Cash McCall, a 1960 film starring James Garner
 * Robert McCall, star of The Equalizer, a 1980s American television series; The Equalizer, a 2014 film loosely based on the television series; The Equalizer 2, a 2018 sequel; and The Equalizer, a 2020 television series
 * Scott McCall, protagonist of the television series Teen Wolf
 * Sgt. Dee Dee McCall, co-star of the 1980's detective television series Hunter

title: McCall


text:
Talk:Abu Shusha massacre

From VfD:

Re: Abu Shusha massacre This page is a stub and has not changed since December 2003. Due to lack of easily available information, it is likely to stay this way. There are many similar pages linked from List of massacres committed during the 1948 Arab-Israeli war, List of villages destroyed during the 1948 Arab-Israeli war, List of massacres committed during the Al-Aqsa Intifada and probably similar pages that I was so far lucky enough to not have run into. I chose Abu-Shusha as an example. Gadykozma 01:22, 10 Aug 2004 (UTC)
 * Keep, unless no useful information can be found. I don't think it is appropriate to list stubs on this page just because they are stubs.  Cleanup would be a more appropriate place. --Zero 09:53, 10 Aug 2004 (UTC)  I changed my vote, see below.
 * I assumed all votes would appear on the subpage, but this one doesn't. Is that a bug, or just something I don't understand? Gadykozma 17:45, 10 Aug 2004 (UTC)
 * Your entry and the one above it, which were part of the VfD page, have now been moved to this one. (There, only users reading the VfD page saw them along with the others; here they are seen by users using either method of reading this discussion.) You made the small, easy, and often harmless mistake of clicking on "[edit]" instead of "Add to this discussion". If you again click on "[edit]" in the section of Votes for deletion where you posted, and read the whole edit pane, you'll find the following:
 * which is the markup for a Wiki comment. (Since it is a comment, you don't see it when you read the page, but only when you read the edit pane.)  No one expects you to read all the markup in the edit pane, but usually people notice it when they are about to edit right next to it, and go back and use the other link.  You were the victim of the person who edited it before you, and didn't notice and follow the link as we hope editors will do; once there was  an existing entry between the comment and the bottom of the page (where you added your entry), it was almost inevitable you'd also not take the opportunity to go back and use the other link, so don't feel too bad. [smile]--Jerzy(t) 03:53, 2004 Aug 11 (UTC)

 * Keep: A stub by itself doesnt meet the criteria for deletion. Nor does it mean much that you can supernaturally predict that it will remain that way unto perpetuity. It may make sense to merge these into a single list, but then you have to accept the possibility that these will develop in to articles, sometimes slowly and at the author's pace. -SV 18:27, 10 Aug 2004 (UTC)
 * Merge & Delete: I have no interest in the factuality of the entry. Rather, I think what stub information there is here should be merged back into a page that covers the whole list.  (N.b. I'm in favor of allowing the NPOV information, but not having a series of stubs that don't reward clicking on them from the list. (E.g. If you're at "List of Intifada Battles" and click on "The Big Battle" and get text saying, "The big battle was a battle in the Intifada,"  there wasn't much point.))  SV and I are using the very same logic, I know, to reach opposite conclusions: I'd rather they stayed as paragraphs on a list until they needed to break out. Geogre 18:54, 10 Aug 2004 (UTC)
 * Keep. I agree that the information should be merged, but I also think that the stub should remain. If a Wikipedian comes along who knows more about the subject, I think they will be much more inclined to expand on the stub due to the fact that it is a stub than undertake the (sometimes daunting) task of creating a new article. The stub has value. I think it should remain. Skyler 01:37, Aug 11, 2004 (UTC)
 * Merge and delete. Cutler 23:05, Aug 10, 2004 (UTC)
 * I change my vote to Merge and redirect Gadykozma 06:17, 11 Aug 2004 (UTC)
 * I changed my vote to delete after looking in the standard sources (Morris, Khalidi) for information on this subject. Abu Shusha was an Arab village of about 1000 people in Palestine until it was depopulated and partly destroyed in May 1948 by the Zionist/Israeli forces.  A Jewish village was then established at that place.  This much of the story makes it about the same as a couple of hundred other Arab villages. There were some reports that a massacre of Arabs took place there at the time of depopulation, but there doesn't seem to be the solid evidence that is required before one could definitely say that it happened.  Therefore this page does not deserve to exist with this title. --Zero 11:53, 11 Aug 2004 (UTC)
 * In this case I'll change my vote again. Its either plain delete, or rewrite to reflect that these are rumors, merge with the list, and then delete. Gadykozma 15:08, 11 Aug 2004 (UTC)

 * Keep. Controversy involves historically and culturally significant events. It is our job to keep its content NPOV through editing. Davodd 20:25, Aug 11, 2004 (UTC)
 * Keep. Agree with Davodd. --Dittaeva 21:58, 14 Aug 2004 (UTC)
 * Delete. To someone coming to this topic with no knowledge, this articles offers no enlightenment whatsoever. To someone familiar with the incident, this article offers no new perspectives. Unless it does more than say "on this date, some (unspecified) event happened", I don't believe it merits space. Denni ☯ 20:19, 2004 Aug 15 (UTC)

end moved discussion

action to be taken
Since the attempt at deletion failed, I propose to replace this article by one called just "Abu Shusha" with a mention of the claims about a massacre. The present name can remain as a redirect. I'll write a first draft today or tomorrow. If anyone has objections, please speak up now. --Zero 23:51, 18 Aug 2004 (UTC)

 * You should somehow handle the link from List of massacres committed during the 1948 Arab-Israeli war too. And the link from List of villages destroyed during the 1948 Arab-Israeli war. Gadykozma 05:56, 19 Aug 2004 (UTC)

title: Talk:Abu Shusha massacre


text:
HP 3000

The HP 3000 series is a family of 16-bit and 32-bit minicomputers from Hewlett-Packard. It was designed to be the first minicomputer with full support for time-sharing in the hardware and the operating system, features that had mostly been limited to mainframes, or retrofitted to existing systems like Digital's PDP-11, on which Unix was implemented. First introduced in 1972, the last models reached end-of-life in 2010, making it among the longest-lived machines of its generation.

The original HP 3000 hardware was withdrawn from the market in 1973 to address performance problems and OS stability. After reintroduction in 1974, it went on to become a reliable and powerful business system, one that regularly won HP business from companies that had been using IBM's mainframes. Hewlett-Packard's initial naming referred to the computer as the System/3000, and then called it the HP 3000.

The HP 3000 originally used a 16-bit CISC stack machine processor architecture, first implemented with Transistor-transistor logic, and later with Silicon on Sapphire chips beginning with the Series 33 in 1979. In the early 1980s, HP began development of a new RISC processor, which emerged as the PA-RISC platform. The HP 3000 CPU was reimplemented as an emulator running on PA-RISC and a recompiled version of the MPE operating system. The RISC-based systems were known as the "XL" versions, while the earlier CISC models retroactively became the "Classic" series. The two sold in tandem for a short period, but the XL series largely took over in 1988. Identical machines running HP-UX instead of MPE XL were known as the HP 9000.

HP later renamed the computer the HP e3000 to emphasize the system's compatibility with internet and web uses. HP initially announced the systems would be designated to be at end-of-life at HP in 2006, but extended that several times to 2010. The systems are no longer built or supported by the manufacturer, although independent companies support the systems.

HP 2000
While looking for a computer system to control ever-more-complex test equipment, HP briefly considered buying Digital Equipment Corporation (DEC). They were ultimately unimpressed with Ken Olsen's demands and did not attempt a deal. They later found a small company, DSI, working for Union Carbide, that had essentially "stretched" DEC's PDP-8 from 12 to 16-bits. HP purchased DSI and merged it into its Dymec division. The DSI design became the basis for the HP 2100, introduced in 1966, initially marketed as a "test and instrumentation computer".

To their surprise, HP found that the machine was selling well in the business market and other non-lab uses. This led to a series of updated versions with better input/output to handle business workflows while removing some of the expansion capability needed only in the lab setting. The much smaller 2114 was particularly popular in non-lab settings. All of the 211x models were later updated to use semiconductor memory instead of core memory, leading to the 2100 line of 1971.

In 1968, the line was expanded with the HP 2000, a series of machines that were made up of collections of parts from the HP 211x lines, with most systems using a low-end 2114 CPU as a terminal controller and high-end CPU like the 2116 as the main processor. The systems ran HP Time-Shared BASIC and could support between 16 and 32 users simultaneously depending on the model. The machines were an immediate success, quickly becoming one of the best-selling systems in the timesharing market, and propelling HP to become the 3rd largest minicomputer vendor.

Alpha and Omega
As the success of the HP 2000 series became clear, in 1969 the designers in Cupertino Lab decided to begin the development of machines dedicated to the office role, as opposed to the HP 2000, which was made up of various bits and pieces never originally designed for the task. Two basic systems were outlined, the "Alpha" was essentially an HP 2100 built using newer components and improved memory handling, while "Omega" was a much larger 32-bit design that would support large numbers of users.

Initially, the two systems were to be released at about the same time. However, almost all development took place within Omega, and few, if any, engineers were active on Alpha during 1969. In contrast to the 16-bit Alpha, Omega would be a 32-bit computer with up to 4 MB of main memory shared among up to four central processing units (CPUs). The CPUs were designed to be programmed in a high level language, like the successful models from Burroughs that were programmed in a custom systems programming language rather than assembler. Support for multiprogramming and memory protection would be built in.

As development continued, the project appeared to be too large for HP to complete using internal funding. This would require the company to take on external debt, which management considered too risky. In the fall of 1970, Tom Perkins was promoted to Corporate Development and decided to cancel the Omega project. This resulted in several employees wearing black-velvet armbands to mourn the death of the project, and some dismay over being reassigned to "just another 16-bit machine."

By this time the small amount of development on Alpha had changed the nature of the project significantly. Originally conceived as an updated HP 2100, it had become essentially a small Omega, adopting its virtual memory and stack machine design that supported high level languages, but limited to a 16-bit design with a maximum of 64 kWord main memory (128 kB), only a single accumulator, and lacking Omega's powerful input/output systems.

When the plan to continue the development of Alpha was presented, George Newman, who replaced Perkins as the General Manager of the computer division, was concerned that the team was once again designing a machine that could not be delivered. Management was eventually convinced of the merits of the design, and the External Reference Specifications were published in July 1970.

MPE
Prior minicomputers were generally used in a fashion similar to modern microcomputers, used by a single user, and often dedicated to a single particular task like operating machinery. This was true for many contemporary designs like the PDP-8 and Data General Nova. It was the HP 2000's ability to perform timesharing that made it a success in a market filled with otherwise similar machines. The ability to support multiple users running different programs was previously limited to mainframe computers, and a further expansion of this capability was a key design concept for the original Omega.

When Alpha emerged as an Omega-like design, it initially followed the same model of multi-user support, which was in turn based on the HP 2000 concept. In this model, the main CPU does not handle user interaction, which is the task of the front-end processor. This allows the main operating system to be greatly simplified, simply loading up user programs as they appear from the front-end, running them in a round-robin fashion with other users' programs, and then delivering the results. In most respects, this was a batch processing system, much of the complexity of multi-user support was isolated in the separate front-end processor.

As development re-started on Alpha, this concept was re-examined and the decision was made to expand the operating system to support multiprogramming directly. This resulted in the system becoming three-in-one, with the main portion being dedicated to timesharing but also offering real-time support and batch mode. The resulting system, ultimately known as Multi-Programming Executive (MPE), would be among the most advanced of its era. When the ten groups within the operating system team came together to describe their section of the system, they found that it was too large to fit in memory, let alone have room for user programs. To make it fit, the programmers began a marathon effort to shrink the system requirements.

Announcement and initial marketing
The system was announced at the Fall Joint Computer Conference in November 1971. By early 1972 the system was up and running with three prototype machines completed. However, MPE development was by this time far behind schedule. This led to a February 1972 memo outlining the development schedule with various features being delivered over time. Ultimately the realtime support was dropped, and none of the dates on the memo were met.

Meanwhile, a turf war had broken out between the engineering lab and the marketing department, who were actively trying to sell the system. It got to the point where "People from marketing were banned from the lab." Engineers continued to provide performance estimates to marketing, which would pass these along to customers, even though the engineers were aware they were inaccurate.

Increasing concern among upper management led to the May 1972 formation of the Systems Management Group, who would work within the engineering labs as an internal marketing team and drive the development according to customer needs. Among the changes implemented, Jim Peachy was hired to do performance testing on the system. Peachy had previously worked on the first timesharing systems at Dartmouth College, and had since worked at General Electric and Memorex. After only three days he pronounced that there was "absolutely no way" the machine would meet the performance requirements being quoted by sales.

First deliveries, recall
As a result of the MPE delays, the ship date was pushed back from August to November 1972, and MPE was reduced solely to timesharing support, with additional features slated to arrive through 1973.

The November date was held firm, and eventually, someone put up posters claiming "November is a happening", referring to the contemporary "happening" movement in performance art. The first machine was shipped to the Lawrence Hall of Science in Berkeley on November 1, although as one engineer, Frank Hublou, noted, "they should have put it on the truck, drove it around the block, and brought the machine back."

After setup, it was found the machine would only support one or two users before slowing to a crawl, and it crashed every 10 to 20 minutes. Hublou's statement came true when the machine was "immediately returned." In a training session that December, a new version of MPE was able to run four users and crashed only once every two hours. The system was continually patched to keep it running as new bugs were found. Machines continued to be shipped, both to customers as well as companies that were considering purchases. These invariably ended poorly, unable to support more than four users. The schedule for MPE features continued to be pushed back, and the estimated number of machine sales continued to be reduced.

By this time, the development of an HP 2000 replacement had been underway for 5 years and had cost the company $20 million. The problems were not going unnoticed and ultimately ended up with Bill Hewlett. Hewlett asked Barney Oliver to take over the division, but he refused, and Paul Ely was sent instead in his place. Ely quickly ended production of the machines and, in a move still mentioned in historical works to this day, recalled all of the machines that had been shipped out. Dave Packard sent a memo to everyone on the team, today known simply as the "Wow Ouch memo".

Ed McCracken went back to the customers and told them point-blank that the machines would not be available until the fall of 1973, and that the machines would only support four to six users. Some accepted the offer of an HP 2000 in place of their orders, while others broke down and cried. One customer threatened to sue the company, but were put off by the personal intervention of Hewlett who stated he would do everything in his power to fix the problems.

Re-release
The system then entered a six-month period of redevelopment of both MPE and the hardware. MPE emerged as MPE-8, officially ending real-time support. The hardware improved to run about 30% faster than the original model and was priced 20% less. As a result of these changes, the new system was able to run eight users. Shipping re-started in November, a year after the original date.

After another year, an updated version shipped. This new "CX" model replaced core memory with semiconductor memory and replaced the wire wrapped CPU boards with surface mounted components. MPE-C added COBOL and RPG languages, perhaps the first mini to offer the former. As part of the CX release, HP shipped IMAGE, a $10,000 database system written to the CODASYL standards. This was later bundled with the systems for free. IMAGE is the primary reason the HP 3000 eventually became a success.

Overview
Early 3000 models had large cabinets with front panels, while later models were made that fit into desks using only terminal consoles for diagnostics, with bootstrap routines in ROM. By 1984 HP introduced the HP3000 Series 37, the first model that ran in offices without special cooling or flooring requirements. Models ranged from a system sometimes used by a single user, to models that supported over 2,000 users.

The HP 3000 was one of the last proprietary minicomputer systems whose manufacture was curtailed by its vendor, outlasting the PDP-11-descended Digital Equipment Corporation VAX, which was acquired by Compaq and then ultimately by Hewlett-Packard. After almost 30 years, a five-year phase-out period for the now-named HP e3000 series servers was originally announced in November 2001. HP then extended this phase-out period twice. No more new e3000s are being sold by HP, although used systems continue to be sold for upgrades on a third-party reseller market. Support from HP to customers for the HP 3000 continued through December 31, 2010. Many third party firms continue to support the system for customers throughout the world. Some customers continue to use the HP 3000 in companies worldwide, especially in manufacturing and e-commerce industries, while others have migrated to business server systems made by HP and others.

For those unable or unwilling to migrate, a homesteading strategy emerged immediately after HP's announcement of the end of system sales. In 2012, the Stromasys company released a product doing full HP3000 hardware emulation on x86-64 servers running Red Hat Linux or CentOS. That product operates as a virtualized instance of the HP 3000 server hardware. Starting in 2003, HP began a plan to sell a license for the 3000's operating system, which can let 3000 customers run their software on this Stromasys product, known as the HPA/3000.

Software pioneering
The key development that led to the tremendous success of the HP 3000 was the bundling of the HP-developed network database management system (DBMS) called IMAGE (now called TurboIMAGE/SQL) that was reputedly inspired by the TOTAL DBMS developed by Cincom Systems, Inc. IMAGE was an award-winning database anointed by Datamation within two years of the database's introduction. It was the first database management system included with a business-class minicomputer. By bundling IMAGE with the server, HP created an ecosystem of applications and development utilities that could rely upon IMAGE as a data repository in any HP 3000.

Classic memory segments and 64K barrier
Code (reentrant) and data reside in separate variable-length segments, which are 32,768 "halfwords" (16-bit words) (or, 65,536 bytes). The operating system, known as MPE (for Multi-Programming Executive), loads code segments from program files and segmented Library (SL) files as needed, up to 256 segments in one process.

There could be as much as 64KB of memory in a code segment, but calling a routine was based on segment number and routine number within a segment, so a program could theoretically have about 32,385 routines. With 8 bits to specify segment, and 16 bits within a segment a program could have effectively have a 24 bit address or 16MB. This was compared to most 16 bit computers like the PDP-11 or IBM System/34 that had 64KB of address space for code and data. The bigger limitation was the data segment and stack segment, which were also 64KB. Shared library routines did not permit cross-process global data since each process had its own data segment. Some procedures worked around this by requiring the caller to pass in an array from their own stack or data segment to hold all state information, similar to modern object-oriented languages where methods are applied to objects passed and allocated by the caller.

A process could allocate and use multiple extra data segments (XDS) of up to 64KB each. While the Classic architecture imposed a limit of 65,535 extra data segments system-wide, other limitations would usually restrict that to a somewhat smaller limit.

Systems programming was done in SPL (System Programming Language), an ALGOL-like language, but allowing inline assembler, and other direct access to the instruction set. The standard terminals for the HP 3000 were the HP 2640 series, which supported block mode data entry from forms (like IBM's mainframe-based CICS), as well as character mode. By the 1980s the computer had gained the ability to use both PCs and Macs as system terminals.

Classic and PA-RISC 3000 hardware
The HP 3000 family's generations were divided into the "Classic" (16-bit) and then "XL" (later IX – 32-bit) families following the introduction of systems based on HP's PA-RISC chips for 3000s in early 1987. These newer XL systems were not binary compatible with the Classics, but would transparently run Classic code via an emulator, one that HP integrated into the MPE XL operating system. (Classic code could optionally be translated to native PA-RISC code via OCTCOMP, the Object Code Translator/COMPiler ... such code ran at native speed, but was still subject to Classic stack and memory size limitations).

The earlier "Classic" machines were based on a custom CISC processor. From about 1988 onward, HP 3000s using PA-RISC processors began shipping in volume. By 1995 these PA-RISC systems effectively displaced the older family of machines from use. As with all technology shifts, there remained a significant residue of older machines in service. Even today, original Classic 3000s work in production in a few locations.

HP 3000 and many HP 9000 machines used the HP Precision Bus.

The PA-RISC based HP 3000's operating system was written primarily in Modcal, HP's extended version of Pascal. Large portions of the earlier MPE V operating system, written in SPL, are still used as part of MPE XL and MPE/iX on PA-RISC. A few subsystems (e.g., TurboIMAGE) are written in PSPL (Portable SPL). A small portion of MPE XL and MPE/iX is written in PA-RISC assembly language.

The 3000 series operating system was originally styled the Multi-Programming Executive, MPE (later called MPE XL and then, after POSIX compliance was added in versions 5.0-5.5, MPE/iX). The earliest versions of the system used only HP's proprietary SPL systems programming language and BASIC. These System 3000s used a command-line interpreter, with a three-level hierarchical file system, and utilities such as compilers would resemble "run fortran.pub.sys" rather than allowing programs to be run as keyword commands. Later the systems gained a wide range of languages including COBOL and FORTRAN, Pascal, C, and even a version of RPG to assist in winning business away from IBM.

People who used the HP 3000 noticed from the 1970s onward that machines were more reliable compared to other mainframe and minicomputers of the time. The ability to recover from power failures - automatically and seamlessly when power was restored - was a notable feature that sold many systems versus IBM computers. At times the HP 3000 suffered from peripheral support delays or gaps caused by HP's decision to delay supporting, or not support at all, some peripherals on the HP 3000 platform—some of which were supported on the identical HP 9000 hardware.

Use of stack instead of registers
Most current computer instruction sets are based on a general-purpose register model. The processor and memory architecture of the classic HP 3000 were based on a stack machine model, like HP's well-known line of RPN calculators. It was said to be inspired by the famous stack-based Burroughs large systems. Rather than having a small number of registers, for example only an AX and BX register in the case of the HP 1000, operands would be pushed on the same stack used to store local variables and return addresses. So rather than

you would have

The 16-bit microcoded machines (Series I, II, III, 30, 33, 39, 40, 42, 44, 48, 52, 58, 64, 68, 70, 37, ...) implement a 16-bit word addressed, byte-addressable, segmented, Harvard, Stack Instruction Set Architecture (ISA). Most of the ~214 instructions are 16 bits wide. Stack operations pack 2 per 16-bit word and the remaining few are 32 bits wide.

CISC Implementations
 * III: 4 Top of stack registers, 175 ns microinstruction cycle time → 5.7 MHz
 * 30, 33: Silicon on sapphire, 2 Top of stack registers, 90 ns microinstruction cycle time → 11 MHz, instructions take 3-7 cycles
 * 40, 42, 44, 48: Schottky TTL, 4 Top of stack registers, 105 ns microinstruction cycle time → 9.5 MHz
 * 64, 68: ECL, 8 Top of Stack registers, 75 ns microinstruction cycle time → 13 MHz, 8KB cache, 60KB WCS, 2 16-bit ALUs
 * 37: ~8,000-gate CMOS gate array, 4 Top of Stack registers

Later 32-bit models used HP's PA-RISC general register-based RISC architecture.

PA-RISC Implementations
 * PA-RISC 1.0 Series 925, 930, 935, 949, 950, 955, 960, 980
 * PA-RISC 1.1 Series 917, 920, 922, 927, 937, 947, 948, 957, 958, 967, 977sx, 987, 990, 991, 992, 995, 918, 928, 968, 978, 988
 * PA-RISC 2.0 Series 996, A and N class and the 9x9 series

HP's exit from the 3000 ecosystem
After the enterprise computing market shifted toward commodity Unix systems from a wide range of vendors—systems that HP had also been promoting—in November 2001 Hewlett-Packard announced that a period it called the end-of-life for the HP 3000 would wrap up at the end of 2006, and that no new systems would be sold by HP after 2003. In early 2006, Hewlett-Packard announced that limited vendor support for the HP 3000 would be extended by two years for certain clients or geographic regions. In September 2007, HP once more extended its support for the systems, offering Mature Product Support without Sustaining Engineering (ending its creation of software patches). Some patches had been built and tested inside HP, but lacked customer base testing by the end of 2008. HP made these patches available after the end of 2010. By 2011, HP had extended a special provision to 3000 customers that granted them free access to patches, unlike the rest of HP enterprise line, which was forced in 2010 to adopt a "pay for patching" support program instead of free patches.

Independent support
A group of independent vendors has assumed systems and software support for existing customers who have left the ranks of HP's 3000 support business. Several have pledged to continue support for their own software until customers stop using the server. Others, offering comprehensive support, are citing 2016 and later as their end of support dates. A consultants directory is maintained by Robelle Software, and other independent consultants are available through a listing at the OpenMPE website. Open source software resources, including commodity tools, for the 3000's MPE/iX operating system are maintained in a website by Applied Technologies.

The HP 3000 has enjoyed one of the longest lifetimes for any business computer system. These enterprise-grade computers have outlasted the highly regarded PDP-11 and VAX series, although OpenVMS operating system is still being offered on Alpha, IA-64, and x86-64 based systems.

In January 2012, Stromasys announced the development of Charon/HPA-3000, which enables secure transfer of HP3000 systems to a state-of-the-art environment. Stromasys's solution virtualizes the hardware of an existing HP3000 system, and enables the MPE/iX operating system, third-party applications, and user-developed software to run without any modification whatsoever, on industry-standard Intel servers. Their offering includes a two-user evaluation copy delivered in a VMWare package.

Multiple independent vendors have purchased HP3000's Operating System Source Code, MPE/iX and are committed to supporting both hardware and software solutions for HP3000 systems.

Beechglen Development, Inc. began hosting HP3000 systems in 2002. In 2012 Beechglen introduced HP3000 compatible custom fibre channel disc arrays using current technology SSD and SATA hard drives, effectively replacing SCSI tape and SCSI disc devices. As of January 2020, Beechglen is the only vendor that has developed and offers 2028 MPE CALENDAR intrinsic patches for the MPE/iX Operating system allowing intrinsic dates beyond December 31, 2027. They continue evaluating and testing third-party applications for compatibility.

Pictures

 * Picture of HP 3000 series 48
 * Picture of HP 3000 series 70
 * HP 3000 series 42, 52, 70

title: HP 3000


text:
User:Sesse

Yawn. Why are you reading this, anyway? :-) Norwegian Wikipedian (medium to low activity), hoping to do some (non-PHP) Wikimedia programming from time to time. (Perhaps I'll write something useful here one day, but it will stay in the history anyhow...)

title: User:Sesse


text:
Talk:Bad Boy Records

Stub?
Why do you two just go back and forth between making this a stub and a substub? One of you changed it from a stub to a substub, then the other changed it right back, now it has been changed to a substub again.

How much does it truly matter?

Merge

 * I agree.  Lajbi  Holla @ me   Who's the boss?  20:52, 2 August 2006 (UTC)
 * Agreed. --Darkneonflame 21:20, 2 August 2006 (UTC)
 * Im confused about the sstub thing but i think they should be merged, and i dont theink the neptunes are part of the bad boy family --t_heinvisibleman 15:54 BST 03 Sept 2006

Fair use rationale for Image:Notoriousbi bornagain 101b.jpg
Image:Notoriousbi bornagain 101b.jpg is being used on this article. I notice the image page specifies that the image is being used under fair use but there is no explanation or rationale as to why its use in this Wikipedia article constitutes fair use. In addition to the boilerplate fair use template, you must also write out on the image description page a specific explanation or rationale for why using this image in each article is consistent with fair use.

Please go to the image description page and edit it to include a fair use rationale. Using one of the templates at Fair use rationale guideline is an easy way to insure that your image is in compliance with Wikipedia policy, but remember that you must complete the template. Do not simply insert a blank template on an image page.

If there is other fair use media, consider checking that you have specified the fair use rationale on the other images used on this page. Note that any fair use images uploaded after 4 May, 2006, and lacking such an explanation will be deleted one week after they have been uploaded, as described on criteria for speedy deletion. If you have any questions please ask them at the Media copyright questions page. Thank you.

BetacommandBot 23:37, 1 July 2007 (UTC)

BIG
shouldn't BIG be moved to the former artists section? —Preceding unsigned comment added by Gegorg (talk • contribs) 07:01, 12 February 2008 (UTC)

February 2008
The last 50 or so edits to this article are by User:Badboyonline. Is User:Badboyonline an employee of Bad Boy Records, or is this account operated by employees or associates of Bad Boy Records? Newbyguesses - Talk 22:47, 18 February 2008 (UTC)

Discography
This should have its own page IMO.... Nathan86 (talk) 11:03, 21 August 2008 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 3 external links on Bad Boy Records. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20131022042254/http://nobel.osd.wednet.edu/wiki/pages/69D8c3R9r/Sean_Combs_Legacy_in_Hip_Hop.html to http://nobel.osd.wednet.edu/wiki/pages/69D8c3R9r/Sean_Combs_Legacy_in_Hip_Hop.html
 * Added archive https://web.archive.org/web/20150402101711/http://ruthlessblogs.com/2011/04/11/tyler-the-creator-speaks-on-odd-future-bidding-war/ to http://ruthlessblogs.com/2011/04/11/tyler-the-creator-speaks-on-odd-future-bidding-war/
 * Added archive https://web.archive.org/web/20110727155617/http://yodonbleekraps.com/2011/03/21/is-lil-b-signing-to-diddys-bad-boy-records/ to http://yodonbleekraps.com/2011/03/21/is-lil-b-signing-to-diddys-bad-boy-records/

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 12:44, 9 December 2017 (UTC)

Page name
Everywhere I go on bad boy's official accounts, it reads Bad Boy Entertainment as the name. Yet on here it's Bad Boy Records. Could some one change it? — Preceding unsigned comment added by Bring back WWWF (talk • contribs) 02:29, 15 February 2022 (UTC)

title: Talk:Bad Boy Records


text:
Colby

Colby most often refers to:
 * Colby (given name), a list of people
 * Colby (surname), a list of people
 * Colby cheese (originally 'Colby Cheddar'), a type of cheese made from cow's milk
 * Colby-Jack, a mixture of Colby and Monterey Jack cheeses

Colby may also refer to:

British Isles

 * Colby, Cumbria, UK
 * Colby, Norfolk, UK
 * Colby Woodland Garden, Pembrokeshire, UK
 * Colby, Isle of Man

United States

 * Colby, Kansas, a city in Kansas
 * Colby, Ohio, an unincorporated community
 * Colby, Wisconsin, a city in Wisconsin
 * Colby (town), Wisconsin, a town in Clark County
 * South Colby, Washington, an unincorporated community
 * Colby College, a liberal arts college located in Waterville, Maine

Geography

 * Colby Lake (Chisago County, Minnesota)
 * Colby Lake (Washington County, Minnesota)
 * Colby Mountain (Tuolumne County, California)

Culture

 * Colby, a Franco-Belgian comic series from Michel Blanc-Dumont and Greg

Television

 * The Colbys, the TV series, aired from 1985 until 1987 on ABC
 * Colby's Clubhouse, the Christian TV series, aired from 1984 until 2000 on Trinity Broadcasting Network

Other uses

 * Colby, the ball in Bando (sport)
 * Colby Nolan, a cat
 * The Colby meteorite of 1917, which fell in Wisconsin, United States (see meteorite falls)

title: Colby