text:
Talk:Haskell/Category theory

Untitled first section by DavidHouse
This page is getting there. Some stuff I'd still like to do:

 * More exercises
 * Diagrammatic explanations of CT concepts

Monad laws are incorrect
Hi all. I was looking over the monad laws section and noticed some errors in the first and second laws. The first law is incorrect because join cannot be composed with join since it is a function from M^2 to M. The confusion here is on subscripts: the join_x can be lifted to join_{Mx} which will then be ok. It is better to write this as (join M) using the standard monad notion. I.e the first law should read jM.j = j.jM. See the wikipedia article on monads (category theory) for the correct commutative diagrams.

There is a similar abuse of notation problem with the second law. This may be confusing to the inexperienced. I did not change them because of the following example would have to be altered as well. Perhaps a note about the abuse of notation would be sufficient since it will be awkward to explain the haskell code equivalent. -- Marc

 * The trouble comes from the fact that in Haskell,  is of polymorphic type  . The parametrization on the monad   is not important here, but the parametric type variable   is. This makes it a function and a natural transformation at the same time with   being the type argument. The point is that the Haskell compiler will accept the composition   because it can figure out that the first   takes the base type   if the other takes a base type  . In other words, it will infer the subscripts automatically. I'm unsure what to do here, but I suspect that this has to be explained at some point anyway. -- apfeλmus 09:30, 8 March 2007 (UTC)

 * I agree that it is just an abuse of notation and that it doesn't affect the code since the compiler is smart enough to figure out what is going on. This is why I didn't go trampling through the page making changes. I do think that it is worth mentioning that this happens for clarity.

 * Perhaps something like: Notice that the subscript on the second join is actually Mx so that this composition is proper from a category-theoretic standpoint, but since join is of polymorphic type in Haskell the compiler understands which join is meant from context, so in (coding) practice the distinction is not important. -- Marc

 * Actually, I think I should have called it "type inference" instead of "compiler". From the Haskell point of view, "subscript" may be confusing :), it's "type specialization". Maybe something like: "note that the second  is specialized to the type  ".
 * But the issue is more subtle than that: because of polymorphism, the category Hask allows to internalize not only morphisms but natural transformations as well. I'm not well-versed in category theory but I guess there is some construction corresponding to that? In particular, I suspect that the naturality laws 3 and 4 are free theorems (although I don't know whether higher kinded free theormes have been worked out yet). I think that this what makes innocent looking Haskell notation break with the standard category theory notation.
 * Maybe it's best to simply introduce natural transformations explicitely in the article and solve notational and conceptional problems with that. Hiding them is probably more confusing than giving a translation between Cat-speak and Haskell-speak. Actually, I like the $$T\mu$$ notation more than subscripts or type inference because it results in more symmetric monad laws. -- apfeλmus 21:47, 8 March 2007 (UTC)

 * I am well versed in category theory, but fairly new to haskell. I'm using my category theory skills to understand haskell, which is how I ended up here. I think that laws 3 and 4 are ok -- they are just expressing the requirement that unit and join must be natural transformations.

 * I'm not sure if it is worth giving a significant introduction to natural transformations into the article, though a mention and a link to a wikipedia page might be appropriate. My main concern is just that the monad laws be replaced with their correct formulations so that others approaching this in the manner that I have won't have to wrestle with the laws for a while before figuring out that they are not what a category theorist would expect. (Normally I would not be such a stickler, but this is the category theory article after all.) I am, however, willing to help make the article more in-depth from a category-theoretic point of view. Perhaps in conjunction with more concepts we will find that we need to discuss natural transformations. Marc Harper 02:19, 9 March 2007 (UTC)

 * I agree, it's a category theory article, after all :) So, subscripts are important. I'm unsure on how to state the categorially correct monad laws without natural transformations? Concerning the introduction of concepts, the rule of thumb would be that a concept may be introduced as long as there is corresponding Haskell code for it. Of course, it's best introduced if it's also useful. Your additions would be most welcome! -- apfeλmus 09:28, 9 March 2007 (UTC)

I think that we should use the $$T\mu$$ notation and explain that the type system can infer the correct domain for (M join). For the reader that understands functors, this will not be suprising since monads are functors and we are basically just applying fmap to join to lift it to the correct domain. Natural transformations can be viewed as types of the form $$ \forall a, m a \to n a $$ for functors m and n, which should be sufficient for most readers.

Once some more content is added that uses natural transformations and gives interesting examples of them it may be appropriate for a more detailed discussion of natural transformations. There is a lot of categorical content to be added -- even relatively simple constructions such as identifying tuple types at the categorical product. Does anyone know of a good reference for a categorical discussion of the properties of Hask? Marc Harper 21:15, 9 March 2007 (UTC)

 * Agreed.

 * Note that the tuple is (unfortunately) not the categorial product :) This basically comes from the fact that $$\perp \neq (\perp,\perp)$$, i.e. the tuple type has an extra element $$\perp$$ that breaks the universal property. The sum type (coproduct)  has the same problem. For more on $$\perp$$ ("bottom") and the semantics of general recursion, see Haskell/Denotational semantics.

 * AFAIK, there is no concretely worked out category theory behind Hask. In general, Lambda calculi are connected to cartesian closed categories. A quick google suggests Cartesian closed categories and the λ-calculus as trampoline. I don't know where to find a categorial construction of universal quantification $$\forall a$$, but the inventors of the polymorphic lambda calculus System F are Girard and Reynolds and they have semantics for it. Then, there are initial algebra semantics for folds and generic programming in general. The "banana and barbed wires"-paper mentioned on the haskell wiki page is one of the most famous in that direction. There is also the work of Moggi in Categorial semantics, he mostly deals with monads. -- apfeλmus 11:01, 10 March 2007 (UTC)

 * It is disappointing that it is not as elegant as it seems from the surface. Thanks for the references. -- Marc
 * What about restricting our attention to only strict functions in the category Hask? Then we seem to get better categorical properties. Also, if we consider types to be 'pointed' with basepoint $$\perp$$ then we can get properties such as $$\perp = (\perp,\perp)$$ by taking the product in the pointed category (much in analogy with pointed topological spaces). -- Marc 74.139.215.32 01:08, 28 October 2007 (UTC)

 * I don't think that a restriction to strict functions makes things better. While (co)products may work out fine, function types won't:  and   are not isomorphic, the former can be used to simulate call-by-name in a strict language. In other words, ⊥ will still bite when considering function types. Usually, one restricts everything to total functions, thereby kicking out ⊥ completely, and that does give a satisfying category. Partiality ⊥ can then be modeled by a monad (I don't have a good reference for that but maybe  is a start).
 * For an introductory article like this one, I think the most reasonable thing to do is to mention the problem and otherwise declare all functions to be total :-) (The current article "allows" partial functions while ignoring them at the same time, I think that's a bit clumsy.)
 * -- apfeλmus 09:58, 28 October 2007 (UTC)

Strong monads
There is another subtlety, namely the fact that every "monad" in Haskell is also a "strong monad", but not the other way round. See Moggi's paper. This means that there is a natural transformation t :: Monad m => (a, m b) -> m (a,b) t x m = m >>= \b -> return (a,b) = join. fmap (\b -> return (a,b)) $ m Apparently, the category Hask offers quite a lot of objects for free. -- a  p  f  e  l m  u  s  21:47, 8 March 2007 (UTC)

Powerset eq List Monad?
This may be irrelevant from a pedagogical standpoint, but most of the times I've heard category theorists talk about the list monad (in the operads world), they seem to view it as something in a symmetric monoidal category, i.e. tensor products of Thingies; and not using powersets -- the powerset analogy is slightly flawed in that it would disallow things like [2,3,2,2,1,2]. On the other hand, proposing a change that actually works out simple enough for an example to be good is over my own head right now. Michiexile 09:29, 29 January 2007 (UTC)

 * They are not the same. This is because sets are not ordered/indexed by default, i.e. a set would not contain the element 2 twice, but a list could. As far as illustrating the idea though, they are otherwise very similar.

 * To be precise about the distinction, if you consider sets with the monoidal structure introduced by the cartesian product, then you can view lists as element of a product of sets. (This allows the list elements to be of different types though, so it is more properly viewed as a tuple.) So... lists of length n (in Haskell) are really elements of A^n, the product of A with itself n-times. The proper category theoretic way to view this is to generate a category with the product and a set A. Then n-lists can be viewed as a monad. If you wanted to treat all lists similtaneously, you could toss in the element B=A^{\infty}. It still has a product (B x B = B) and you could consider lists of length n to be infinite lists where all terms after the n-th are zero. -- Marc

 * Since you mentioned operads, the connection here is that you can view operads as monoids in the monoidal category of symmetric families of a category... I think that a discussion of operads in the article would be unecessarily complicated at this time, and even though the powerset example is not quite the same I think that it is pedagogically sufficient. -- Marc

Right chapter?
This is in the "Time and space" chapter, but the only connection to time and space (which I understand to mean performance in this context) appears to be the mention of fusion - which is tangential, and doesn't, I think, justify this article's inclusion in this chapter. --Greenrd 21:49, 16 January 2007 (UTC)

 * Would it be reasonable to rename the Program correctness chapter to something more general and move this there? Actually... would program correctness be reasonable as is?  -- Kowey 23:00, 16 January 2007 (UTC)

 * I also think that it belongs to the chapter currently entitled "Program correctness" as this chapter intents to subsume anything about "Formal program manipulation". While "Program correctness" is too narrow for category theory to fit in, I have been reluctant to change the title because "Formal" could (unfortunately) scare people off. Maybe it's good idea to change the title anyway but to bait people with a subchapter "Why is my program correct?" which serves as a hands-on introduction to the "Formal program manipulation" subject? A sneakier version would be "Help, my program doesn't work" because the chapter won't tell anything about debugging, it will tell about "Program derivation from specification" and how to prove your programs do what they should. In short, it will show how to write correct programs in the first place. -- Apfelmus 10:43, 17 January 2007 (UTC)

Category theory wikibook
Have you seen Category theory? -- Kowey 09:55, 13 January 2007 (UTC)

Suggestion
I know what a Set is, but I don't know what a Group is. Perhaps link to the wikipedia pages for these two things - so people can have access to the mathematical definition.

"Functors on Hask" paragraph
Another suggestion.

Maybe it's me, maybe because English is not my first language, maybe because i'm a physicist, maybe because the word "map" has a lot of meanings, maybe a lot of things but...

I've seen and heard "functors represent types that can be mapped over" and it never seems clear to me at all. Not even after i think i understood what they are.

As an intuitive explanation, the "mapped over" has been to me as useful at saying "functors are functors".

Can't it be added something like "functors are the generalization to categories of linear operators"?

Or if i'm wrong, add an explanation of way the comparison doesn't hold. --Dragomang87 (discuss • contribs) 20:16, 14 November 2013 (UTC)

 * The intuition here comes from practical Haskell: "mapped over" there refers to how, for instance,  allows us to apply a function to each element of a list, so that  evaluates to  . If the   type class is unfamiliar to you, check the chapter which introduces it.--Duplode (discuss • contribs) 00:23, 15 November 2013 (UTC)

Review from the Haskell-cafe mailing list
On the 16th Jan 2007, a message was sent regarding this article to the Haskell mailing list, asking for review and comment. This was really helpful, poking holes in my knowledge as well as helping to improve the article manyfold. Most of the changes you can see in the history since that date are tweaks due to that review. Noteable reviewers were Brian Hulley and Yitzchak Gale, whose comments were very encouraging and hopefully had a bit influence on the article's content. DavidHouse 18:32, 19 January 2007 (UTC)

Diagrams
... were done using the Inkscape vector editing program. The original SVG files are available on request, email me (see my talk page). DavidHouse 18:32, 19 January 2007 (UTC)

 * The wikimedia projects (e.g. wikibooks) support .svg diagrams. Have you given it a try?  It works badly on the ones produced by Omnigraffle; perhaps you would have better luck -- Kowey 19:38, 19 January 2007 (UTC)

 * Also, it's highly worth it to move the diagrams to commons. This will make the diagrams transparently shareable across all wikimedia projects, for example, a hypothetical French version of the wikibook -- Kowey 19:40, 19 January 2007 (UTC)

Comment
The first exercise asks 'As was mentioned, any partial order (P, \leq) is a category with objects as the elements of P and a morphism between elements a and b iff a \leq b. Which of the above laws guarantees the transitivity of \leq?' This seems backwards to me. The statement is that a partial order gives rise to a category, not the other way around. Given a paritial order we don't need to gaurantee the transitivity of \leq. That is an axiom. The question should be something along the lines of 'which of the axioms of a poset guarantees the second category theory law?' -- astrolabe

Morphism composition. If the existence of a (unique) f_{a,b} from a to b is equivalent to a \leq b, then: a\leq b and b\leq c means there are f_{a,b} and f_{b,c}, therefore there must be f_{a,c} = f_{b,c}. f_{a,b} --- which amounts to saying a must be \leq c. -- askyle

Another Comment
When explaining functors as they apply to Hask, the list functor is explained as a functor from Hask to Lst. But for a Monad, the underlying functor is from a category to itself: $$M : C \to C$$. So considered as a Monad, is it not the case the list functor should be a functor from Hask to Hask (where its image in Hask is only those objects in the subcategory Lst)? I know this was (perhaps still is!) a point of confusion for me, perhaps a note of clarification would be worthwhile.--Jyossarian (talk) 03:39, 12 January 2010 (UTC)

 * Lst is a (full) subcategory of Hask, i.e. every object in Lst is a Haskell data type. The list functor can be viewed as an endofunctor $$M : \mathbf{Hask} \to \mathbf{Hask}$$ but it can also be interpreted as a functor from Hask to a subcategory Lst. The text simply chose the latter interpretation when introducing the functor.
 * -- apfeλmus 09:52, 15 January 2010 (UTC)

adjoint functors
I read somewhere that monad transformers were really adjoint functors, whatever those are. Could some explanation be added? I like this article a lot and it helped me with the traditional stumbling block of understanding monads (I sort of get them now), but I'm still baffled by monad transformers. Thanks

 * Oh? That would be interesting, I only know that every pair of adjoint functors (like $$S\to\cdot$$ and $$S\times\cdot$$) gives rise to a monad ($$S\to(S\times\cdot)$$). Concerning monad transformers, the wikibook has a chapter on them, but it's not optimal yet. Meanwhile, have a look at . Concerning adjoint functors, this module will hopefully explain them at some point in the future. -- apfeλmus 10:21, 7 December 2007 (UTC)

Convention used for function composition
In the section on Category Laws, we have the following:

 * … if $$f : A \to B$$ and $$g : B \to C$$, then there must be some morphism $$h : A \to C$$ in the category such that $$h = f \circ g$$.

This suggests that $$f \circ g$$ is being used here for the morphism that results from composition of the morphism f preceding the morphism g. However, this conflicts with the Haskell composition notation, in which $$f \circ g$$ (well, f.g) refers to the composition of the morphism f following the morphism g.

The section is also internally inconsistent in that it states that for the category shown in the figure, for which $$f: B \to A$$ and $$g: A \to B$$, $$g \circ f = id_B$$ and $$f \circ g = id_A$$. (This corresponds to the convention used in Haskell.). But for the same category, the text states that $$f \circ id_A = id_B \circ f = f$$ (which uses the opposite – and un-Haskell-like – convention).

Which convention should be adopted here? (I’m no authority on Haskell or on category theory, so I wouldn’t wish to make the choice myself.)

See also the compositions for unit and join, which appear to use the Haskell-like convention.

 * Oh! The "Haskell" convention is correct. In fact, it's the convention used all over mathematics. Fixed. -- apfeλmus 08:16, 10 April 2008 (UTC)

 * Not used ‘all’ over mathematics – but certainly by far the most common convention, I agree. (And my comment on the last relation there was mistaken, as it wasn’t of course referring to the category in the diagram.) Thanks for fixing this. --Axnicho (talk) 09:17, 10 April 2008 (UTC)

-- It would be more instructive, I think, when in the diagram that explains the existence of f o g and g o f, there is for at least one of them another option than just id. Currently, the example is such that both f o g and g o f are the identity, and this might be misleading for the beginner.

Typographical conventions for unit, join
In this article, we have, for example:

 * $$join \circ M(join) = join \circ join$$

Is this really the desired typography? I’d have been inclined to use

 * $$\mbox{join} \circ M(\mbox{join}) = \mbox{join} \circ \mbox{join}$$

But perhaps there is some Haskell convention that I’m unaware of? (The same applies to unit.)

 * Function names in italic (more precisely \mathit{} in LaTeX) have a widespread tradition in papers about functional programming and Haskell, especially when there is some "mathematical" touch to them. A prototypical example is probably the book The Fun of Programming. Some chapters are available online, like Fun with Binary Heap Trees. Naturally, typewriter face is widespread, too. A variable width but upright font is the exception, a prominent example being Chris Okasaki's thesis and corresponding book.
 * In other words, italic is what we want here :-) -- apfeλmus 08:42, 10 April 2008 (UTC)

 * OK – I can accept that italic is used in Haskell and functional-programming papers (though why the standard mathematical convention that I mentioned should be used specifically in papers with ‘some "mathematical" touch to them’ eludes me!). Still, at the very least, we should improve the typography so that it looks more like this (I have made this change):

 * $$\mathit{join} \circ M(\mathit{join}) = \mathit{join} \circ \mathit{join}$$

 * By using math-mode italics (bare $…$) rather than \mathit{…} or \textit{…}, the spacing of the word ‘join’ is pretty awful – and a poor advertisement for TeX. As Lamport notes in the LaTeX 2ε user guide (p. 51):

 * ‘LaTeX normally uses an italic type style for letters in math mode. However, it interprets each letter as a separate mathematical symbol [which is not what we want here], and it produces very different spacing than an ordinary italic typestyle. You should use \mathit for multiletter symbols in formulas.’
 * --Axnicho (talk) 09:35, 10 April 2008 (UTC)

 * Yes, thanks for making the change to \mathit{} :-)
 * Concerning the italic convention, I imagine it as follows: usually, the objects of mathematical discourse have only one-letter names like $$x$$ or $$\zeta$$. This is not practical for programming, so multi-letter names like $$\mathit{map}$$ or $$\mathit{foldr}$$ are used. But since they're almost on "equal footing" with those nice looking italic letters, they gotta be italic, too. I mean, in the papers with "mathematical touch", they're not so much actual code to be typed into the terminal (-> typewriter face), but mathematical entities that obey laws like $$\mathit{map}\,(f\circ g) = \mathit{map}\,f \circ \mathit{map}\,g$$. (Hm, same for $$\sin(x)$$ of course. Must be the higher order functions, i.e. the fact that map can also be argument of a function. Oh well, whatever, it looks good :-)
 * -- apfeλmus 13:15, 11 April 2008 (UTC)

 * That is pretty funny, since in mathmetics the well established convention is to write variables (whether the variable contains a number, a function, or some other object, does not matter) as single letters in italics, and the multi-letter symbols for named functions (whose meaning in known, so they are not variables, for example: sin, max, log, etc.) in upright. And clearly map and foldr etc. are in this category, too; not variables but names for known functions, and no mathematician would write them in italic. So apparently haskell/functional programming papers with "some mathematical touch to them" use a typographical convention that is based on misunderstanding the normal mathematical typography. Whether this wikibook should follow the normal mathematical, or the alternative functional programming convention, is a difficult question. Maybe it depends to which audience this wikibook is targeted: to readers familiar with math but new to functional programming (who'd be less confused with normal math typography), or readers more familiar with functional programming papers and less familiar with normal math (who'd be more confused with the normal math typography).
 * -- Sampo Smolander 10:56, 26 November 2011 (UTC)

Applicative Functors
Should there be a section about applicative functors? It seems to me that a functor F can be made into an applicative functor if it respects exponential objects, where $$ B^A $$ should be the object consisting of functions from A to B. By that I mean that there needs to be a map

$$F(B^A)\to F(B)^{F(A)}$$

Another way to say this is that there is a map

$$ F(B^A)\times F(A)\to F(B)$$

But I haven't quite figured out where the pure requirement fits it (I'm not sure why a map $$A\to F(A)$$ is important to have for this). Possibly, we want the map $$ F(B^A)\times F(A)\to F(B)$$ to be the unique map that makes a diagram commute, where we use $$\text{pure}:B^A\times A\to F(B^A\times A)$$, and map that to $$ F(B) $$ by $$F(f)$$ where $$f:B^A\times A\to B$$ is the evaluation map, and we also map $$B^A\times A$$ to $$ F(B^A)\times F(A)$$ by the product of the two pure maps (sorry if it isn't clear, in the end we have a square we want to commute). I'm not sure if this makes sense/is actually true though.

Taylor561 (talk) 18:43, 26 November 2010 (UTC)

ID remark is incorrect
The article says that: The function  in Haskell is polymorphic - it can take many different types for its domain and range, or, in category-speak, can have many different source and target objects. But morphisms in category theory are by definition monomorphic - each morphism has one specific source object and one specific target object. This is a gross error. A monomorphism is a left-cancellative morphism. The author is confusing the property of a function of sets being single-valued with a monomorphism. (Monomorphisms generalize the notion of an injective function, because they go mono-e-mono...now you'll never forget that!)

Strictly speaking, from the mathematical point of view, the  function can be viewed as an abuse of notation. Thus Hask is a category.

Moreover, with regards to subtyping, one can use a Subobject classifier in a beautiful way...since the objects of Hask are types.

Just thought it might be nice to clarify that from the mathematician's point of view...

Pqnelson (discuss • contribs) 01:09, 10 February 2011 (UTC)

 * Nicely spotted! The funny thing is that two rather different concepts have "monomorph" in their name.
 * monomorphic type vs polymorphic type. That's what the author meant.
 * morphism, monomorphism, epimorphism and friends. That's what you mean and what the author seemed to write.
 * In category-speak, the  function is a natural transformation. The   category has the curious property that a lot of natural transformations can be reified as elements of some objects (which correspond to polymorphic types). This is like a cartesian closed category, where there are power objects $$B^A$$ whose elements correspond to morphisms.
 * I agree that the text needs a small rewrite to make the above distinction more clear.
 * --apfeλmus 09:25, 10 February 2011 (UTC)

[video] Dominic Verity on Category Theory
Maybe it is worth including links to http://vimeo.com/17207564 and http://www.youtube.com/watch?v=yilkBvVDB_w

Dominic Verity presents a gentle introduction to Category Theory, perfect for those who've been playing with Haskell for some time and wanted to know what it's all about. Yrogirg (discuss • contribs) 10:13, 18 August 2011 (UTC)

What the heck is a morphism?
I applaud the initiative to give an overview of category theory, and its relationship to Haskell. And it's encouraging that the discussion starts with the basic: "a category is a collection with three components".

But the article immediately heads off into the weeds by explaining everything in terms of "morphisms", a word which appears over fifty times. Yet never is any clue provided as to what the morphism word actually delineates (although we are told that they are sometimes called arrows, no wait, ignore that, and they may not be functions, yet correspond to functions in the Haskell sense).

Just from the context of this article, morphisms appear to be functions, or something very like functions. But the fact that this article studiously avoids calling them functions suggests that anyone assuming they are functions would be on the wrong track. So basically, if the reader doesn't already understand what morphism refers to in this neighborhood of mathematics they are going to be out of luck.

If someone takes on the task of adding a description introducing the word "morphism", before it is used, telling what "morphism" encompasses, could they please also comment on how it relates (or doesn't) to the polymorphism, monomorphism and any other morphisms we're likely to encounter.

Thanks! Gwideman (discuss • contribs) 09:16, 30 December 2012 (UTC)

 * Pretty good question! The underlying issue is that there is nothing else we can say about what a morphism is in general; the concept, just like that of object, is entirely abstract. There are things called objects, and things called morphisms which have one object as source and one object as target, and so forth. Category Theory abstracts from what those things actually consist of.

 * What we can do to clarify things is providing examples of categories. Then it is not surprising that morphisms appear to be "something very like functions", given that in the very familiar example of the Set category functions are the morphisms, and in the no less familiar example of Hask Haskell functions are the morphisms. But it needn't be so. For an arbitrary example, you can make a category out of the integer numbers by taking a single object (and it doesn't even matter what it is), the integers as morphisms, addition as composition and zero as identity. For a different sort of example, when Gabriel Gonzalez talks in the pipes documentation about "the category of Unix pipes" he refers to the fact that a  is a morphism in a category with   as composition and   (the forward-as-is pipe) as identity (a neat presentation of the underlying ideas is provided by "The category design pattern" in Gabriel's blog).

 * As for the relation to monomorphism and polymorphism with respect to types, they are different things. This question, and Apfelmus' answer to it, may shed some light on the distinction.

 * Duplode (discuss • contribs) 21:48, 12 April 2014 (UTC)

Defintion of composition unclear
"A notion of composition of these morphisms. If h is the composition of morphisms f and g, we write $$h=f\circ g$$."

It is very unclear what the exact requirements are. Is this "notion of composition" the same for all pairs of objects / morphisms? Does it have to exist between all morphisms?

E.g. the Set category does not work if composition between all $$f : A \to B$$ and $$g : C \to D$$ is required even if $$B \neq C$$, but from the "definition" given above, it is not clear why only specific morphisms have to be composable. How about this (copied from http://en.wikibooks.org/wiki/Category_Theory/Categories#Data )

"For each ordered triple of objects A, B, C in $$\mathcal C$$, there is a law of composition: If $$f:A\to B$$ and $$g:B\to C$$, then the composite of f and g is a morphism $$g\circ f:A\to C$$"

I personally don't know any category theory, so I don't know if that is correct: It would mean that the composition is allowed to follow different laws for different ordered triples of objects.

 * Well spotted - $$f\circ g$$ is only defined if the target of $$f$$ is the source of $$g$$, and the text didn't make that clear enough. I rewrote the passage to show sources and targets explicitly.Duplode (discuss • contribs) 20:24, 12 April 2014 (UTC)

Second monad law
In discussing the equation: join. fmap return = join. return = id

the = id at the end is ignored, but in fact it's the whole point of the equation, namely that both join. fmap return and join. return are nops (i.e. join undoes fmap return and just return by itself, so composing them produces an id of the appropriate type. I leave it to the author to amend the text. 2602:306:CD38:1040:F8A5:67E8:E2DA:1569 (discuss) 10:07, 17 July 2015 (UTC)

 * Well, the original authors are long gone :) Fortunately, this is Wikibooks, and so we have carte blanche to fix things. I agree with your remark, and will try to improve the text later. In fact, I find the treatment of the so-called "third and fourth laws" (justified in footnote 2) presented here somewhat distasteful. If the reader has gone all the way to find out about Category Theory this kind of lies-to-children aren't very useful. Furthermore, in more recently written chapters about various type classes the book talks about "laws" and "bonus laws" (the latter being naturality properties, which always hold in Haskell thanks to parametricity), so there is background to mention natural transformations in passing. Fixing this issue should lead to the improvement you suggest, as we would then be able to talk about the actual three monad laws.--Duplode (discuss • contribs) 18:15, 17 July 2015 (UTC)

The second exercise in the "Introduction to Categories" section
From the little and brittle knowledge I have about category theory, the diagram does seem like a category to me, and it really bugs me to be told it's not. I'm no expert in pedagogy, but I can feel as a beginner that, that exercise is doing more harm than good, unless the answer is given within reach. I'm trying to form an understanding around these very abstract concepts, and the exercise tells me that the picture I've been forming so far is wrong, without telling me why. So I question everything in the picture and it weakens my understanding. (This would actually make it a great exercise, if the answer were also given) Thanks for the great wikibook :) Enisbayramoglu (discuss • contribs) 04:14, 25 January 2016 (UTC)

 * If you follow the diagram, you will see that we can compose $$f$$, $$g$$ and $$h$$, like so: $$f \circ g \circ h$$. The associative law states that the following must hold true: $$f \circ (g \circ h) = (f \circ g) \circ h$$. From the diagram, we can see that $$g \circ h = id_B$$ and $$f \circ g = id_A$$. Thus, we can replace into the expression for the associative law: $$f \circ id_B = id_A \circ h$$. By the definition of identity, this means that $$f = h$$, which is not true. Thus, the diagram's description does not hold up to the category laws, and cannot be a category. (Disclaimer: I am a complete beginner at this. Please correct me if I did any mistakes.) --Insipido (discuss • contribs) 16:36, 11 September 2016 (UTC)

 * Your solution is correct. I do think has a point: beyond the emptiness of the solutions page, something about this exercise strikes me the wrong way. Perhaps the presentation is a little brusque, or the background assumption that the drawn arrows correspond to all distinct morphisms (which e.g. is what allows saying that $$g \circ h = id_B$$) is not obvious enough. One more thing to consider in a future cleanup of this chapter... --Duplode (discuss • contribs) 04:36, 6 October 2016 (UTC)

the do-block section has the numbering of the laws all confused ?
For example 'return x >>= f = f x' is bullet-listed as (1), whereas it is in fact the 3rd law n the earlier section.

title: Talk:Haskell/Category theory


text:
Blender 3D: Noob to Pro/Creating a jewel in Blender

In this tutorial we will create a jewel in Blender. It is fairly simple. I recommend you do this tutorial if you are a noob, because it explains some basic features, but I suggest you read the tutorial syntax and the pages at the very beginning of this Wikibook first.

Modeling the jewel
Start up Blender if you haven't already. There is a cube in top view (it looks like a square because it is in top view.) Delete it by pressing the X key. Then, to begin modeling, add a circle by pressing SPACE→Add→Mesh→Circle. Set the vertices to 10 and make sure it is not filled in. Then press OK.

Next, we will extrude the vertices down. First enter side view by pressing Numpad 3 on your keyboard. As you can see, the circle is flat and not filled in. We will give it some depth. Switch to Edit Mode (TAB) and extrude the circle by pressing the E key and selecting "Only Edges". Move the mouse down and click to confirm the position (you may want to limit to Z axis by pressing the Z key).

OK, what we just did is turn the circle into a hollow cylinder by extruding. But we don't want a cylinder. We want the bottom to be a nice tip. To do this, press Alt-M. This creates a Merging menu. Select "At Center". Now the bottom is a nice tip, like we want it!

Now we will edit the top of the jewel. Press A to deselect everything and press the B key. This enters Box-Select Mode. Drag a box over the top vertices to select them.

Now extrude the vertices upwards a bit (again: E key and "Only Edges"). Next, we will scale down these vertices to look a bit more like a jewel. Make sure the ring of vertices are selected and press the S key. This enters Scale Mode. Scale down the top vertices a bit and click to confirm.

To look around your jewel model use the Middle Mouse Button or Alt-Left Click. Your jewel is looking fantastic! But there's a big gaping hole at the top. We'll fix that. First, enter side view (Numpad 3). Now extrude the topmost ring of vertices but don't move them anywhere with the mouse. If you are feeling doubtful, just press 0 and then Enter (or just click right mouse button). This makes a duplicate of rings placed over the original. Next merge this new ring with Alt-M -> At Center. This merges the duplicate ring, thus filling up your hole.

At last! Your jewel is finished! Feel free to rotate around it and make further adjustments if you are more advanced with using Blender.

Shading
Switch back to Object Mode (TAB) and show the Shading Panel (F5). Enable the Material Buttons (click on the button with a red ball). Add new material by clicking on "Add New" button in the "Links and Pipeline" tab. Copy the settings in the screenshot below. If you are having trouble setting the precise value to a slider, just click on the number. This allows a manual type-in. First, make it green by setting R to 0, G to 1, and B to 0. Next set the alpha slider to 0.458 (it looks like an A). Now press "Ray Mirror" (raytracing reflection) to turn it on and set it to 0.13. Now press "Ray Transparency" and set the IOR value to set 1.44. When you're done it should look like this:

The finishing touch
To improve the effect, add a plane underneath the jewel. In the Object Mode (TAB) press SPACE>>ADD>>MESH>>PLANE. Scale it 5 times using the S key. Then move it down a bit using the G key (press the Z key to restrict movement to the Z axis).

You may try to render your jewel now. Press the F12 key. You may find that camera doesn't see whole jewel. Move and rotate the camera (using the G and R keys) to set it in the right position. You may want to switch to "Camera View" (Numpad 0) and try out "Camera Fly Mode" (SHIFT F). Try also moving the lamp and see what happens.

I've found that the jewel looks best with Ambient Occlusion on. So go to the Shading window, then the World buttons, click the Amb Occ tab and click the Ambient Occlusion button.

Here is an example of what you can do:

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


text:
Talk:AppleScript Programming/Sample Programs/Run QuickTime in full screen

As the earlier "script" was like this:

Run this AppleScript after playback of a movie has begun.

tell application "QuickTime Player" to present movie 1

I decided to make an actual script. --F-3000 19:59, 12 January 2007 (UTC)


text:
User talk:207.157.69.190

Xania talk 20:04, 12 January 2007 (UTC)

title: User talk:207.157.69.190


text:
User talk:Mrchrishunt

Great input at Magic/Basic Card Magic......keep it coming......I did a few very minor clean-ups, but your stuff is good.....keep going! Buddpaul 21:18, 12 January 2007 (UTC)

title: User talk:Mrchrishunt


text:
Talk:AppleScript Programming/Sample Programs/Converter for temperatures

I tried to re-craft the program so that it would have been simplier to use, yet I faced such problem that  from a dialog with input-prompt cannot be used twice. If you make line " ", followed by " ", result is that both myVar1 and myVar2 got same data, from " ". If the two lines are placed opposite, the data will be from "button returned of result". I didn't actually test this as a program, but in Scripteditor it didn't work. --F-3000 22:37, 12 January 2007 (UTC)


text: Template:Species id

title: Template:Species id


text:
Adventist Youth Honors Answer Book/Insect list

Lepidoptera
|


text:
Blender 3D: Noob to Pro/Team/Mission Statement and Vision

Mission Statement
Blender 3D: Noob to Pro aims to provide the best freely available Blender 3D instruction on the internet. Hmm... "best" is so ambiguous... we better clarify a bit:

 * Funnest
 * Most efficient
 * Most inspiring

There, much better.

Vision
In order to satisfy the stringent requirements brought by the aforementioned Mission Statement, Blender 3D: Noob to Pro shall:

 * have fun tutorials
 * with fun page names
 * that build on the principles taught in previous tutorials
 * that prefer pictures to words for instruction
 * that are littered with beautiful screenshots and renders
 * that are organized smartly in the Table of Contents

Mission Statement and Vision


text:
User talk:Dc105

Hello and welcome to Wikibooks!

Here are some tips to help you get started:
 * You should sign your name on Talk and vote pages using four tildes, like this: ~~~~.
 * Remember to conduct any editing experiments in the sandbox.
 * If you're a Wikipedian, see Wikibooks for Wikipedians for a primer on how things work here (it's a little different).
 * If you want to base your work here on materials from Wikipedia, please use WB:RFI to bring the material over in compliance with the GFDL.
 * If you're an instructor and plan on using wikibooks for a class project, see Guidelines for class projects
 * Please say hello at the Staff Lounge with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Please take a look at Naming policy before starting a new book.
 * Remember to maintain a Neutral point of view.
 * Explore, be bold in editing pages, and have fun!

You will find more resources in Community Portal. If you want to ask a question, visit the Study help desk, the Staff lounge, IRC channel or ask me personally on my talk page. For site news, see the Bulletin board. It might be an idea if you add this page to your "watchlist" so that you can see when any new information is posted there.

Good luck! -- SB_Johnny | talk 00:55, 13 January 2007 (UTC)

title: User talk:Dc105


text: Abnormal Sexual Psychology/Paraphilia and Health


text:
Cookbook talk:Vegetarian cuisine

Dawn's Fish and Eggplant Curry Curry Sauce: 2 tablespoons of butter 2 tablespoons of flour 1 tablespoon of lemon juice 4oz. of vegetable broth 3oz. of half and half 2 teaspoons of curry

Melt butter in small sauce pan. Once melted, add flour while stirring it in. Add other ingredients and mix.

Fish and Eggplant: olive oil desired amount of fish fillets desired amount of peeled and diced eggplant salt to taste lemon pepper to taste fresh parsley to taste minced garlic to taste

In a frying pan, saute the eggplant, lemon pepper, parsley, minced garlic, and salt in olive oil until brown. Remove from pan. In the same pan, add fish fillets. Add eggplant and then curry sauce. Cover until ready to eat. Fish and Eggplant Curry goes wonderful with rice.

This recipe doesn't say at what temperture to saute, and has no numbers at all. It's all either "desired amount" or "to taste". Also, no picture. I know that definitions of vegetarianism vary around the world, but in the US vegetarians don't eat fish. This dish would count as pescetarian, I think. JonathanHopeThisIsUnique (discuss • contribs) 19:14, 26 July 2014 (UTC)

Para removed from bread
>, but unless they have a filling such as peanut butter or tofu slices, they provide inadequate protein on their own.

For some reason this criticism is often leveled at vegetarian foods, yet not leveled at meat eater diet foods, despite the fact that for both diets it is true but of no importance. Any healthy balanced diet does not mean eating only one food, and variation of protein intake from one meal to another is a non-issue.

> Eating in public places, like having lunch at work, can be a challenge.

I cant work out if this is a personal issue or a claim that being vegetarian is problematic. If the first, a textbook is probably not the ideal place for such things, and if the 2nd I've been to several countries and not found vegetarian eating out a challenge. This is especially so in the wealthier countries where such great variety is available.

> A bread rich in protein is always a good choice

Not so. Soy bread is usually a poor choice for a few reasons, which is why so few people eat it. Tabby 20:40, 27 August 2007 (UTC)

Suggestion
Maybe we could turn this into an actual book? The organization is really good. Just have a chapter for each of these sections, with each page being a recipe. Of course, we could try to make all the recipes as good as possible too. Pictures are important. Perhaps organize each chapter (section) by how hard the recipe is? Or just alphabetically. Breads probably shouldn't be here though, since as the article notes, most breads are vegetarian. I hope that this idea isn't too hard, boring or just plain silly. :) Thanks for reading! JonathanHopeThisIsUnique (discuss • contribs) 17:45, 26 July 2014 (UTC)

title: Cookbook talk:Vegetarian cuisine


text:
Cookbook:Fish Sauce

| Southeast Asian cuisines

Fish Sauce, also nước mắm (Vietnam), nam pla (น้ำปลา - Thailand), jeotgal (Korea), patis (Philippines), is a sauce made by fermenting various types of fish (usually anchovies) and pressing to extract the liquid.

Fish sauce is very salty and has a strong flavour, not just of fish (due to the fermentation process). It is an essential ingredient in many South-East Asian recipes. It is also used as a basis for many other sauces.

When using fish sauce in a recipe, additional salt is generally unnecessary. Quantities of salt vary from country to country and from brand to brand, with Vietnamese fish sauces generally being saltier than those from Thailand. Additionally, some brands of fish sauce are more pungent and primarily for cooking, while others are more delicate and used mostly for salads as a dressing and to finish a dish.

title: Cookbook:Fish Sauce


text:
Talk:Islam Way of Life/The Success

yeah for proper reading and concentraion on the same tehme both should be merged

title: Talk:Islam Way of Life/The Success


text:
Template:B3D:N2P/VTT1

Usage
This template is used to overlay as many as nine textboxes or rectangles on top of an image. You must provide an image to the template using the  argument, although you can (optionally) provide an image width (via  ). If left unspecified, the width will default to.

Each item overlayed on the image must be one of two types: either a "textbox" or a "drawbox". Both have their own arguments. Each argument (apart from the  and   arguments) must belong to a item numbered 1-9. This "item number" will be appended to each argument of the item. For example, see the following: The first item is item number 1. Therefore, we add a "1" at the end of every argument for item 1. Similarly, the next item is item number 2, so we add "2" at the end of its arguments.

For a detailed list of arguments, see the below

Shared arguments
These are the arguments that are shared between textboxes and drawboxes. Most of these arguments work similarly to CSS properties of the same name. To see a list of all of them, visit https://developer.mozilla.org/en-US/docs/Web/CSS.

 *  ,  ,  , and  : These arguments position the box relative to the image. They behave similarly to their corresponding CSS properties, for example, you can set  to position the box 10 pixels away from the left border of the image, or you can set   to position the top of the box at the center of the image (i.e., the midway point). All of these are optional (if left unspecified, both   and   will default to  )
 *  : This specifies the width of the box. It works similarly to the  CSS property. For example,   will set the width to take up 50% of the image. It is an optional argument, and it will be set to   if left unspecified.
 *  : This argument allows you to style the border of the box. You can customize the color, the width, and the line style. It works similarly to the  CSS property. For example,   will create a 2-pixel-wide blue border with dashed lines. It is an optional argument, however, its default value depends on the type of box used (typically  ).

Textboxes
Textboxes have the following exclusive arguments, which can't be used for drawboxes:
 *  : This can either be set to,  ,  ,  , or  . These themes change various textbox colors, for example,   will set the background color to red, and change the border color and the text color to match accordingly. It is an optional argument. By default, its value is  , which simply displays a white background.
 *  : This argument sets the text color of the textbox. It behaves similarly to the  CSS property. You can specify a color in many formats, including using a named color (e.g.  ), using hexadecimal notation (e.g.  ) or   notation (e.g.  ), using   notation (e.g.  ), among other methods. You can use a color picker to get these values, or pick from a list of named colors. It is an optional argument, but its default value depends on the   (typically  )
 *  : This argument styles the background of the textbox. It behaves similarly to the  CSS property. Its main use is to specify a background color, although it can be used to specify other background properties. It is an optional argument, but its defaultt value depends on the.
 *  : This argument specifies an optional label for the textbox. For example,  will display "Example label" at the top of the textbox. Any label text will always use white for its text color, and black for its background color, completely ignoring the   and   arguments. It is an optional argument.
 *  : This argument specifies the text to be displayed inside the textbox. For example,  will display "Example text" at the top of the textbox.

Textboxes look like the following:

Drawboxes
Drawboxes also have their own exclusive arguments, which can't be used for textboxes:
 *  : This argument, like the  argument, specifies the height of the box. It behaves similarly to the   CSS property. It is an optional argument, defaulting to   if unspecified.

Drawboxes look like the following:

Example
becomes

VTT1

title: Template:B3D:N2P/VTT1


text:
User talk:Akhilvira

Hello and welcome to Wikibooks!

Here are some tips to help you get started:
 * You should sign your name on Talk and vote pages using four tildes, like this: ~~~~.
 * Remember to conduct any editing experiments in the sandbox.
 * If you're a Wikipedian, see Wikibooks for Wikipedians for a primer on how things work here (it's a little different).
 * If you want to base your work here on materials from Wikipedia, please use WB:RFI to bring the material over in compliance with the GFDL.
 * If you're an instructor and plan on using wikibooks for a class project, see Guidelines for class projects
 * Please say hello at the Staff Lounge with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Please take a look at Naming policy before starting a new book.
 * Remember to maintain a Neutral point of view.
 * Explore, be bold in editing pages, and have fun!

You will find more resources in Community Portal. If you want to ask a question, visit the Study help desk, the Staff lounge, IRC channel or ask me personally on my talk page. For site news, see the Bulletin board. It might be an idea if you add this page to your "watchlist" so that you can see when any new information is posted there.

Good luck! -- Herby talk thyme 08:10, 13 January 2007 (UTC)

New pages
Hi - you appear to have created two pretty similar pages - could you explain what book they fit into and whether one is created in error - thanks -- Herby talk thyme 08:10, 13 January 2007 (UTC)

title: User talk:Akhilvira


text:
Wikibooks:Requests for deletion/Programming/LearnByExample

Programming/LearnByExample
This book and (presumably) all subpages were nominated by the author for speedy, but at least some have had minor tweaking since then. Seemed worth a look here before deleting, in case any of it's useful. -- SB_Johnny | talk 13:26, 28 December 2006 (UTC)
 * Comment - I almost said that there was nothing there but structure; in fact, the author has wiped content from the top level pages to leave only the speedy delete tag. See Category:Programming/LearnByExample for the pages that have actual content. I'll reserve my vote for the moment, until I can check this out further. Webaware 22:13, 28 December 2006 (UTC)
 * Keep - Looks like quite a bit of work when viewing the category. If someone took maybe an hour to revamp the structure a bit, I think this could be used. However, we could also just chop this book up and put its work in the other languages here. -within focus 19:50, 30 December 2006 (UTC)
 * Delete . Move the salvageable contents to their respective languages if needed. The (seemingly) only substatial contributor cited "I did this a while ago, and it's not very useful" as the reason for delete. I've emailed the author about this VfD. --Swift 16:41, 2 January 2007 (UTC)
 * Author replied and I may have misunderstood his delete reason. In his email the author stated that the reason for delete was that he wasn't going to complete it himself. The content may still be useful (I'm not wasting my time going through the history). I'm suspending my vote till I hear from the author again. --Swift 05:02, 4 January 2007 (UTC)
 * Delete. Author wants this deleted. --Swift 06:07, 4 January 2007 (UTC)
 * Delete. I agree with User:Swift --Panic 19:45, 2 January 2007 (UTC)
 * Delete per author. Kellen T 08:05, 3 January 2007 (UTC)
 * Delete - might be worth keeping if it had more commentary, otherwise is probably too terse for those not already familiar with the various languages. Webaware 13:19, 3 January 2007 (UTC)
 * Comment. I agree with User:Swift --User:Billsix
 * Delete - per Swift. --Az1568(Talk) 06:12, 4 January 2007 (UTC)
 * I know the decision's been made.........but I vote keep.....maybe just a bit longer?? Buddpaul 02:05, 5 January 2007 (UTC)

 * I held back on deleting for about a week because a Wikibooks user wanted to work on it. Nothing materialised so this book has now been deleted. Xania [[Image:Flag_of_Poland_2.svg|15px]]talk 14:57, 12 January 2007 (UTC)


text:
Cookbook:Beef Curry

| Curry

This is a beef curry that can be made out of ingredients which you might find in your fridge normally, so no need to buy extra ones.

Ingredients

 * 1 lb (450 g) minced (ground) beef
 * 1 onion
 * 1 bell pepper or 1 cup (200 g) frozen mixed bell peppers
 * Curry powder to taste
 * 1 beef stock cube, crumbled
 * 2 Tbsp tomato purée
 * 1.5 cups rice
 * 2.75 cups water
 * 1 lemon, juiced

Optional

 * 1 Tbsp mango chutney
 * 1 teaspoon paprika

Procedure

 * 1) Peel and chop the onion and pepper.
 * 2) Brown the ground beef in a pan and add the curry powder.
 * 3) Add the chopped onion and pepper to the pan, and fry this for one minute.
 * 4) Add the crumbled stock cube, tomato purée, mango chutney and paprika to the pan and stir.
 * 5) Add water into the pan till it covers the mixture.
 * 6) Bring to a boil and simmer for 1 hour stirring every 10 minutes.
 * 7) Meanwhile, bring the rice to a boil in the 2.75 cups of water.
 * 8) If you would like the rice to be yellow, add a small amount of tumeric.
 * 9) Immediately cover and reduce heat to a minimum and allow to cook for 10 minutes.
 * 10) Turn off heat and allow to rest for 10 minutes.
 * 11) Add lemon juice to the rice.
 * 12) Fluff with a spoon or fork.
 * 13) Put the rice on a plate with the curry on top. You may wish to mold the rice for a nicer presentation.

title: Cookbook:Beef Curry


text:
User talk:81.152.188.188

Welcome!
Welcome to Wikibooks, a collection of open-content textbooks! You don't have to log in to read or edit articles on Wikibooks, but creating an account is quick, free and non-intrusive, requires no personal information, and gives you many benefits, including:
 * The use of a username of your choice
 * The ability to view all your contributions via a "My contributions" link
 * Your own user page
 * Your own talk page which, if you choose, also allows users to send you messages without knowing your e-mail address
 * The use of your own personal watchlist to which you can add articles that interest you
 * The ability to rename pages.
 * The ability to upload images
 * The ability to customize the appearance and behavior of the website
 * The eligibility to become an administrator
 * The right to be heard in votes and elections
 * Your IP address will no longer be visible to other users.

We hope that you choose to become a Wikibookian and create an account. Feel free to ask me any questions you may have on my talk page. By the way, make sure to sign your posts and comments with four tildes (~~~~), which will let others know who left it.

-- Herby talk thyme 10:01, 13 January 2007 (UTC)

title: User talk:81.152.188.188


text:
User talk:70.95.101.29

Welcome!
Welcome to Wikibooks, a collection of open-content textbooks! You don't have to log in to read or edit articles on Wikibooks, but creating an account is quick, free and non-intrusive, requires no personal information, and gives you many benefits, including:
 * The use of a username of your choice
 * The ability to view all your contributions via a "My contributions" link
 * Your own user page
 * Your own talk page which, if you choose, also allows users to send you messages without knowing your e-mail address
 * The use of your own personal watchlist to which you can add articles that interest you
 * The ability to rename pages.
 * The ability to upload images
 * The ability to customize the appearance and behavior of the website
 * The eligibility to become an administrator
 * The right to be heard in votes and elections
 * Your IP address will no longer be visible to other users.

We hope that you choose to become a Wikibookian and create an account. Feel free to ask me any questions you may have on my talk page. By the way, make sure to sign your posts and comments with four tildes (~~~~), which will let others know who left it.

-- Herby talk thyme 10:51, 13 January 2007 (UTC)

title: User talk:70.95.101.29


text:
Wikibooks:Arbitration/Panic2k4 vs. SBJohnny/Plaintiff Rebuttal

From SB_Johnny
I'm not going to make a lengthy rebuttal here: I think Panic's tone and the things he's said in response to the various "charges" speak for themselves only too well. Panic has a long history of disruptive behavior on Wikibooks, beginning with the troubles with Paddu and the moderators who got involved there, later with darklama, James Dennet, and finally with me.

The issue with Panic is not edit warring... in fact he seems to see "reverting" to be an aggressive act. What he does instead is act uncivilly on talk pages, in such a way as to exert control of the conversation and in turn the editing process.

His inability to work with others was inherent in the decision to make his "fork" early on. When his fork was disallowed, he returned to the main book, and apparently just kept arguing with Paddu until his "opponent" finally left the project and he could go ahead and do what he wanted.

Paddu objected to the fork at least in part because these forks were in part copy-pastes of Paddu's work, and so weren't properly attributing in the history page. My guess is that this is where the idea of "using the GFDL as a weapon" came in, and Panic has since been using the GFDL as a justification for editorial control of the book.

In his response to Darklama, Panic seems to have taken the tactic of just saying "well, too bad. Same thing happened to me a while ago, but now I'm the guy in charge, so now you'll have to deal with me." It's clear that he probably thinks this is actually the "proper way", since he provides this link in his "defendant's reply".

In summary, what we have in Panic is someone who doesn't (or won't) work well with others, but or some reason insists on working on wikibooks, which is by it's very nature a collaborative project. He's very careful not to "violate policies" (though he has a hard time with WB:CIVIL), but continually violates the spirit of the project. His potential as a good contributor is undermined by his unwillingness to collaborate in a collegial manner.

The three blocks were for the following reasons:
 * Block 1: Bossing around a new user on talk pages (violating WB:CIVIL). This was a very short block, intended as a warning (previous written warnings were not being heeded).
 * Block 2: Shortly after the first one, when Panic claimed that it was his "right" to do that, and would continue doing so (using a rather uncivil tone, on darklama's talk page). This block was longer, in part to give Panic some time to reconsider his behavior here, and in part to allow the other two users interested in contributing to discuss the book and how to improve it.
 * Block 3: Another 2 week block, this time for rearranging talk pages again. The talk pages were reorganized during his "absence" because Panic had apparently been moving them around and reorganizing them (see Paddu's comments on the "Charges" page). He may also have done this because I was no longer interested in arguing with him ad infinitum. Regardless of whether his intent was to push my buttons or to reassert his authority over the C++ book, it was time to stop him (and hopefully get him to try again to take a civil approach to all involved).

In conclusion, I think my actions were perfectly reasonable. I had tried cajoling, discussion, and explanation... all fruitless, as Panic is interested only in making others see things from his point of view, rather than trying to understand theirs. Both James and Paddu made it clear from the beginning that they would not be willing to contribute to the book if it meant being harassed by Panic. Panic has all along been impossible to work with (either intentionally or unintentionally), has not been willing to budge an inch, and has ignored warnings. There was no option left but to block him for a cooling off.

I still hope Panic can become a good contributor, but he's going to need a moderator working with him for this to happen. As I have mentioned before, I am no longer willing to do it, in part because Panic's hostility is now directed at me as much as at anyone else, and in part because I'm just tired of doing it.

From darklama
I agree with what SB_Johnny said above and including most importantly this isn't about any edit warring. My inviting Paddu was due my belief it is as important part as recent events are in regard to Panic having trouble working together cooperatively. The only part I disagree with is SB_Johnny's suggestion that Panic needs moderation, because that has already been tried for about 5 months without any progress or change. I believe its unreasonable for anyone to need to moderate someone endlessly on working together and being civil.


text:
User talk:89.242.112.114

Welcome to Wikibooks. We invite everyone to contribute constructively to our collection. Take a look at the welcome page if you would like to learn more about contributing. However, unconstructive edits are considered vandalism, and if you continue in this manner you may be blocked from editing without further warning. Please stop, and consider improving rather than damaging the hard work of others. Thanks. -- Herby talk thyme 11:49, 13 January 2007 (UTC)

title: User talk:89.242.112.114


text:
Horticulture/Maggots

A maggot is the larval stage of the fly life cycle, though sometimes "maggot" is used to refer to the larval stage of any insect. Many maggots feed on carrion and other wastes, but some are crop pests and others are predators and parasites.

Description
Maggots are generally 4 to 12 mm in length depending on their stage of growth. Most maggots range from an off-white color to a light brown, though some can be a yellow or reddish color. Maggots have one pair of tiny hook-like parts to aid in feeding and have no legs.

The adults are easily recognized since this is the only order of insects that has only one pair of wings ("Diptera" meaning 2 wings). They be scary.

Symptoms and Signs
Pest maggots can be leaf or root feeders, borers, or leaf miners.

Ecology
The fly life cycle is composed of four stages: egg, larva (commonly known as a maggot), pupa, and adult. Most feeding is done in the maggot stage.

title: Horticulture/Maggots


text:
Horticulture/Mites

Mites, together with ../Ticks/, belong to the subclass Acarina (also known as Acari) and the class Arachnida. Mites are among the most diverse and successful of all the invertebrate groups. They have exploited an incredible array of habitats, and because of their small size (some are microscopic) most go totally unnoticed. Many live freely in the soil or water, but many species live as parasites on plants or animals and some feed on mold.

Insects may also have parasitic mites. Examples are ../Varroa destructor/ which attaches to the body of the honeybee, and ../Acarapis woodi/, which lives in the tracheae of honeybees. There are hundreds of species of mites associated with other bee species, and most are poorly described and understood. Some are thought to be parasites, while others beneficial symbionts.

There are over 45,000 described species of mites. Scientists believe that we have only found 5% of the total diversity of mites. Mites have existed for around 400 million years.

Most mites in the garden are pests, but some mites are predatory on other mites.

Description
Mites are very small arthropods, with eight legs and two body segments. They have piercing-sucking mouthparts.

Symptoms and Signs
Mite damage includes stippling, discoloration, distorted foliage, and in the case of spider mites webbing.

title: Horticulture/Mites


text:
Wikibooks:Requests for deletion/Algebra I in Simple English/Systems of Linear Equations/Using Matricies to Solve Linear Systems

Algebra I in Simple English/Systems of Linear Equations/Using Matricies to Solve Linear Systems
This topic is completely out of place in an Algebra I curriculum, especially because it is empty. The topic should be deleted because it would require the editor to teach the basics and some of the more advanced aspects of matrices in order to simply solve a linear equation. If I am not mistaken, it is the only reference to matrices in the entire wikibook. It would be much better suited in an Algebra II curriculum or other higher level math. Thylacine222 04:30, 6 January 2007 (UTC)

 * Speedy Delete - As it has no content and is not suited to the book I see no problems. Xania [[Image:Flag_of_Poland_2.svg|15px]]talk 12:58, 6 January 2007 (UTC)
 * Delete - Webaware 21:14, 6 January 2007 (UTC)
 * Keep - This is something for the book authors to discuss on their own pages. VfD should not decide what Algebra I consists of and for all we know there could be many pages in that book that might not fit. The book is relatively new (with many structure-only pages) and I suggest we don't interfere with this for now. Once the book authors discuss this, they can give an admin a list of pages to immediately delete if necessary. -within focus 21:23, 6 January 2007 (UTC)

 * But there's nothing whatsoever on the page. So there's nothing factual that can be deleted except for the subject headings.  This page has existed since July with no content at all and someone has requested that the page be removed because a) it has no content and b) if it did have content it would not be relevent for the 'Algebra I' book (mainly because it's from a higher level).  Xania [[Image:Flag_of_Poland_2.svg|15px]]talk 00:13, 8 January 2007 (UTC)

 * Keep - On the same conditions that was mentioned by Wthinfocus. I've been quite upset when a user pushed a content dispute into a VfD in order to flame the issue, and this appears on the surface to be a similar kind of problem.  There are other means to deal with this problem, and rasing a VfD is not the best approach.  This should be decided upon by those who are participating with the development of the Algebra I book, or seem moderation of some sort to attempt to resolve the issue.  --Rob Horning 23:33, 7 January 2007 (UTC)

 * Keep - Agree with Withinfocus. Unlike Wikipedia, wikibooks is more personal about projects. Books have authors and author lists here and as long as policy allows the book, whatever goes in it should be (in 99% of the cases) fine. That other 1% is reserved for vandalism and maybe for useless dangerous stuff (like that chemstry thing that made bombs and supposedly not useful in any class). Depends on how useless and how dangerous. --Dragontamer 00:06, 8 January 2007 (UTC)
 * Keep. As a matter of precident, I think this page should be deleted, but I dont believe that it should be deleted via VfD discussion. The authors of this book (of which I've played a small part) should discuss the matter internally to the book and make a decision in that way. With that said, I am going to be bold and remove the VfD notice from that page, replace it with a delete, and possibly start a discussion about it on the main talk page of the book in an effort to get in touch with the other authors of that book. Because I am essentially moving the discussion away from VfD, I am going to declare this matter closed. --Whiteknight (talk) (projects) 15:32, 8 January 2007 (UTC)

Closed. As per my comment above. --Whiteknight (talk) (projects) 15:32, 8 January 2007 (UTC)


text:
User:Sebastian Huber~enwikibooks

Welcome Sebastian. It is great to have you in Wikispace. Have fun and let me know if I can help, ciao, bob

 * thank you, Sebastian Huber

Welcome
Hello and welcome to Wikibooks!

Here are some tips to help you get started:
 * You should sign your name on Talk and vote pages using four tildes, like this: ~~~~.
 * Remember to conduct any editing experiments in the sandbox.
 * If you're a Wikipedian, see Wikibooks for Wikipedians for a primer on how things work here (it's a little different).
 * If you want to base your work here on materials from Wikipedia, please use WB:RFI to bring the material over in compliance with the GFDL.
 * If you're an instructor and plan on using wikibooks for a class project, see Guidelines for class projects
 * Please say hello at the Staff Lounge with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Please take a look at Naming policy before starting a new book.
 * Remember to maintain a Neutral point of view.
 * Explore, be bold in editing pages, and have fun!

You will find more resources in Community Portal. If you want to ask a question, visit the Study help desk, the Staff lounge, IRC channel or ask me personally on my talk page. For site news, see the Bulletin board. It might be an idea if you add this page to your "watchlist" so that you can see when any new information is posted there.

Good luck! -- Herby talk thyme 14:45, 13 January 2007 (UTC)

 * hi herby, thanks Sebastian Huber

title: User:Sebastian Huber~enwikibooks


text:
User talk:65.26.126.222

Xania talk 15:16, 13 January 2007 (UTC)

title: User talk:65.26.126.222


text:
User talk:Willem Bol

Thanks for experimenting with Wikibooks. Your test worked, and has now been removed. Please use Sandbox for any other tests you want to do, since testing material in modules will normally be removed quickly. Please see the welcome page if you would like to learn more about contributing to our project. Thanks. -- MichaelFrey 15:30, 13 January 2007 (UTC)

Image copyright problem with Image:At class waves.jpg
Thanks for uploading Image:At class waves.jpg. However, the image may soon be deleted unless we can determine the copyright holder and copyright status. The Wikimedia Foundation is very careful about the images included in Wikibooks because of copyright law (see Wikibooks' Copyright policy).

The copyright holder is usually the creator, the creator's employer, or the last person who was transferred ownership rights. Copyright information on images is signified using copyright templates. The three basic license types on Wikibooks are open content, public domain, and fair use. Find the appropriate template in Image copyright tags and place it on the image page like this:.

Please signify the copyright information on any other images you have uploaded or will upload. Remember that images without this important information or giving false information can be deleted by an administrator. If you have any questions, feel free to contact me, or ask them at the Study help desk. Thank you. Iamunknown 03:50, 31 January 2007 (UTC)

Tags
Willem, I noticed that you uploaded the image two more times after I left the above message here. If you were trying to tag the image but found it at all confusing, I am totally willing to help out. Do you have any questions? Also, let me leave you our standard welcome message. It is very helpful. Hello and welcome to Wikibooks!

Here are some tips to help you get started:
 * You should sign your name on Talk and vote pages using four tildes, like this: ~~~~.
 * Remember to conduct any editing experiments in the sandbox.
 * If you're a Wikipedian, see Wikibooks for Wikipedians for a primer on how things work here (it's a little different).
 * If you want to base your work here on materials from Wikipedia, please use WB:RFI to bring the material over in compliance with the GFDL.
 * If you're an instructor and plan on using wikibooks for a class project, see Guidelines for class projects
 * Please say hello at the Staff Lounge with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Please take a look at Naming policy before starting a new book.
 * Remember to maintain a Neutral point of view.
 * Explore, be bold in editing pages, and have fun!

You will find more resources in Community Portal. If you want to ask a question, visit the Study help desk, the Staff lounge, IRC channel or ask me personally on my talk page. For site news, see the Bulletin board. It might be an idea if you add this page to your "watchlist" so that you can see when any new information is posted there.

Good luck! Iamunknown 23:06, 1 February 2007 (UTC)

PROBEREN
Hi - no idea where this should be but this page really must be part of a book and so named Book title/PROBEREN. You can use the "move" tab to rename it - thanks -- Herby talk thyme 15:14, 16 April 2007 (UTC)

title: User talk:Willem Bol


text:
User:Gouchi~enwikibooks

My user page.

title: User:Gouchi~enwikibooks


text:
AppleScript Programming/Advanced Code List/Say

With command  you can cause the computer to "say" things with spoken text.

Its basic format is this:

Which would cause the computer to say "Support Wikibooks".

Information about how to control the speech itself can be found from here: developer.apple.com


text:
User talk:141.70.120.2

Please do not replace Wikibooks pages with blank content. Blank pages are harmful to Wikibooks because they have a tendency to confuse readers. If it is a duplicate article, please redirect it to an appropriate existing page. If the page has been vandalised, please revert it to the last legitimate version. If you feel that the content of a page is inappropriate, please edit the page and replace it with appropriate content. If you believe there is no hope for the page, please see the deletion policy for how to proceed. If page is no longer useful, insert delete to its top. Thanks for contributing to Wikibooks!

Xania talk 21:36, 13 January 2007 (UTC)

title: User talk:141.70.120.2


text:
Cookbook:Focaccia (Genovese)

| American cuisine | Italian cuisine | Vegetarian Cuisine | Bread

Procedure

 * 1) In a 4-quart bowl (or the bowl of an electric mixer), combine flour, salt, yeast and water.
 * 2) With a large metal spoon, stir together until all the flour is absorbed. If you are mixing by hand, repeatedly dip one of your hands or the spoon in cold water and use it, much like a dough hook, to work the dough vigorously into a smooth mass while rotating the bowl in a circular motion with the other hand.
 * 3) When the dough sets up, wash and dry your hands and let the dough rest for 5 minutes. Then add ¼ cup olive and dip your hand or spoon again in water and continue to work the dough for another 5 minutes until it is smooth and stretchy. The dough should be very sticky, but it should also have some texture and structure. Even if mixed with the wet hands method, it should still pass the windowpane test (snip off a small piece of dough and gently stretch it until it forms a paper-thin, translucent membrane).
 * 4) If the dough seems like a batter and does not have enough structure, work in some more flour.
 * 5) Transfer the dough to an oiled bowl, turn it to coat the dough with the oil, cover it with plastic wrap and refrigerate overnight. The next day, the dough should have nearly doubled in size. If not, allow it to sit at room temperature for about 2 hours or until it doubles in size.
 * 6) Line a 12-by-17-inch sheet pan (technically called a "half sheet pan") with either baking parchment or a silicon baking pad (Silpat).
 * 7) Drizzle about 2 tablespoons of olive oil on the parchment or pad and spread it over the surface. Using a plastic bowl scraper dipped in water, gently transfer the dough from the bowl to the pan, taking care to de-gas the dough as little as possible.
 * 8) Drizzle the remaining ¼ cup olive oil on the surface of the dough.
 * 9) Using only your fingertips, press down on the dough, creating dimples and pockets all over the surface for the oil to fill. Do not press the dough outward toward the edges of the pan; instead simply press downward at only a slight angle toward the edges. When the dough fills the pan a little more than half full and springs back toward the center, stop pressing and let the dough relax at room temperature for about 15 minutes.
 * 10) Repeat the dimpling process, beginning at the center and gradually working out toward the edges of the pan. This time the dough will nearly fill the pan. Again let the dough relax at room temperature for about 15 minutes.
 * 11) Repeat the dimpling. This time the dough should fill the pan. Let the dough rise for approximately 2 to 3 hours at room temperature or until it fills the pan.
 * 12) Your dough is now ready for topping and baking.

Notes, tips, and variations

 * Makes enough dough for 1 (12-by-17-inch) half sheet pan.
 * This bread spends more time in the pizza oven than most crusts, so it requires special toppings that can withstand the heat:
 * Caramelized Sweet and Sour Onion Marmalade
 * Paper-thin slices of potatoes and onions, seasoned with rosemary
 * Marinara Sauce
 * Pesto Sauce
 * Roasted peppers and olives
 * Genoa style: just sprinkle with salt

title: Cookbook:Focaccia (Genovese)


text:
Template talk:Template doc page viewed directly

Page history from Wikipedia:

--Az1568(Talk) 22:16, 13 January 2007 (UTC)
 * 15:32, 12 January 2007 MrDolomite (Talk | contribs) m (added See also to companion template Template:Template doc page transcluded and moved line above tag)
 * (cur) (last) 13:47, 29 December 2006 81.15.30.3 (Talk)
 * (cur) (last) 13:46, 29 December 2006 81.15.30.3 (Talk)
 * (cur) (last) 09:29, 20 November 2006 Ligulem (Talk | contribs) ("the" is more appropriate than "a". See Wikipedia:Template doc page pattern)
 * (cur) (last) 06:27, 20 November 2006 Down10 (Talk | contribs) m (cleanup)
 * (cur) (last) 22:05, 16 November 2006 Freakofnurture (Talk | contribs)
 * (cur) (last) 16:54, 15 November 2006 Ligulem (Talk | contribs) (link, cat)
 * (cur) (last) 00:47, 15 November 2006 Flamurai (Talk | contribs) m (moved User:Flamurai/Template doc page viewed directly to Template:Template doc page viewed directly: moving from user space to template space)
 * (cur) (last) 20:48, 11 November 2006 Flamurai (Talk | contribs) m (width)
 * (cur) (last) 20:48, 11 November 2006 Flamurai (Talk | contribs) m
 * (cur) (last) 20:16, 11 November 2006 Flamurai (Talk | contribs)


text:
User talk:Coelacan~enwikibooks

I don't check this page. Talk to me at Wikipedia:User talk:Coelacan.

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called Coelacan. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Coelacan~enwikibooks that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 23:06, 17 March 2015 (UTC)

Renamed
 This account has been renamed as part of single-user login finalisation. If you own this account you can |log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: . -- Keegan (WMF) (talk) 04:48, 19 April 2015 (UTC)

title: User talk:Coelacan~enwikibooks


text:
User:Coelacan~enwikibooks

Wikipedia:User:Coelacan

title: User:Coelacan~enwikibooks


text:
User talk:88.105.161.116

Cookbook:Frappé Coffee
Thanks for experimenting with Wikibooks. Your test worked, and has now been removed. Please use Sandbox for any other tests you want to do, since testing material in modules will normally be removed quickly. Please see the welcome page if you would like to learn more about contributing to our project. Thanks. Webaware talk 23:51, 13 January 2007 (UTC)

title: User talk:88.105.161.116


text:
Template:B3D:N2P/VTT1/TEXTBOX

VTT1/TEXTBOX

title: Template:B3D:N2P/VTT1/TEXTBOX


text:
User talk:Thard012

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally.

Also please make sure that when signing up for a project you need to sign up on the 'talk' page and not the main 'module' page as the instructions say. Xania talk 00:37, 14 January 2007 (UTC)

title: User talk:Thard012


text:
User talk:Goodman.m.w

Hello and welcome to Wikibooks!

Here are some tips to help you get started:
 * You should sign your name on Talk and vote pages using four tildes, like this: ~~~~.
 * Remember to conduct any editing experiments in the sandbox.
 * If you're a Wikipedian, see Wikibooks for Wikipedians for a primer on how things work here (it's a little different).
 * If you want to base your work here on materials from Wikipedia, please use WB:RFI to bring the material over in compliance with the GFDL.
 * If you're an instructor and plan on using wikibooks for a class project, see Guidelines for class projects
 * Please say hello at the Staff Lounge with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Please take a look at Naming policy before starting a new book.
 * Remember to maintain a Neutral point of view.
 * Explore, be bold in editing pages, and have fun!

You will find more resources in Community Portal. If you want to ask a question, visit the Study help desk, the Staff lounge, IRC channel or ask me personally on my talk page. For site news, see the Bulletin board. It might be an idea if you add this page to your "watchlist" so that you can see when any new information is posted there.

Good luck! User:Iamunknown 00:55, 14 January 2007 (UTC)

title: User talk:Goodman.m.w


text:
MediaWiki talk:Recentchangestext

A few minor changes
I have to suggestions. Cheers, User:Iamunknown 01:12, 14 January 2007 (UTC)
 * 1) Add a link in the form   or something other pithy phrase immediately after the list of wikibookses by ISO language code.
 * 2) Change the "edit" link. First off, it should use the domain "en.wikibooks.org" not "www.wikibooks.org." Secondly, it should use "/w/index.php?title=" not "/w/wiki.phtml?title=." Also, I would suggest moving it to the bottom-right of the table.
 * Done. : ) --Az1568(Talk) 09:14, 8 February 2007 (UTC)

Other languages
Isn't the "other languages" link useless because on interwikis ? J.M. Tavernier 00:42, 20 February 2007 (UTC)
 * Arguably. Sometimes redundancy is warranted.  --Iamunknown 23:36, 1 April 2007 (UTCHelder)

 * Please, add the interwikis that are missing. If you want, you can use the list that I made at pt.wikibooks, only removing the comment tags around pt:Special:Recentchanges and putting them around your language interwiki. Helder 14:09, 17 June 2008 (UTC)

Minor change
"M = minor edit, N = new" should be changed to "m = minor edit, N = new" but it is locked so I can't edit it. Could someone with higher clearance please fix this? Storeye 11:31, 16 May 2007 (UTC)
 * Correct & done - thanks -- Herby talk thyme 11:35, 16 May 2007 (UTC)

Browse categories
The link to browse by category goes to Category:Main page when it should go to Category:Books by subject or even Category:Categories for the very top level.. -- Adrignola talk contribs 14:59, 27 May 2009 (UTC)
 * ✅ — Mike.lifeguard | talk 18:01, 27 May 2009 (UTC)

Interwikies
editprotected Please update the interwiki links with the list below. This is to remove a few closed projects (Asturian, Corsican, Latvian, Nauru, Low German, Swahili, Turkmen, Zulu) and to add the missing Tajik Wikibooks. Thanks, Jafeluv (discuss • contribs) 07:41, 23 April 2012 (UTC)

 * done, thanks QU TalkQu 09:33, 23 April 2012 (UTC)

Edit request
Can someone add Wikidata and Wikivoyage to the sister projects bar? Thanks. --Jakob (talk) 13:49, 4 March 2014 (UTC)
 * Done. --ЗAНИA [[Image:Flag_of_Estonia.svg|15px]]talk 11:42, 10 March 2014 (UTC)

Edit request - newbies
Please remove

- [ New users' contributions]

since the functionality was removed. Thanks, --DannyS712 (discuss • contribs) 02:05, 24 September 2019 (UTC)
 * Done, thanks - QuiteUnusual (discuss • contribs) 10:48, 24 September 2019 (UTC)
 * can you also remove the extra space at the end? Its " Logs]] ". Thanks, --DannyS712 (discuss • contribs) 17:51, 24 September 2019 (UTC)
 * Sure, done - thanks for pointing it out. QuiteUnusual (discuss • contribs) 08:32, 25 September 2019 (UTC)

title: MediaWiki talk:Recentchangestext


text:
User talk:Arminius~enwikibooks

Welcome
Hello and welcome to Wikibooks!

Here are some tips to help you get started:
 * You should sign your name on Talk and vote pages using four tildes, like this: ~~~~.
 * Remember to conduct any editing experiments in the sandbox.
 * If you're a Wikipedian, see Wikibooks for Wikipedians for a primer on how things work here (it's a little different).
 * If you want to base your work here on materials from Wikipedia, please use WB:RFI to bring the material over in compliance with the GFDL.
 * If you're an instructor and plan on using wikibooks for a class project, see Guidelines for class projects
 * Please say hello at the Staff Lounge with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Please take a look at Naming policy before starting a new book.
 * Remember to maintain a Neutral point of view.
 * Explore, be bold in editing pages, and have fun!

You will find more resources in Community Portal. If you want to ask a question, visit the Study help desk, the Staff lounge, IRC channel or ask me personally on my talk page. For site news, see the Bulletin board. It might be an idea if you add this page to your "watchlist" so that you can see when any new information is posted there.

Good luck! User:Iamunknown 01:59, 14 January 2007 (UTC)

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called Arminius. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Arminius~enwikibooks that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 22:59, 17 March 2015 (UTC)

Renamed
 This account has been renamed as part of single-user login finalisation. If you own this account you can |log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: . -- Keegan (WMF) (talk) 04:34, 19 April 2015 (UTC)

title: User talk:Arminius~enwikibooks


text:
Cookbook:Socca (Italian Chickpea Flatbread)

| Cuisine of France | Cuisine of Italy

Socca (French), torta di ceci or farinata (Italian), is a type of flatbread made from chickpea flour.

See also: Calentita

Ingredients

 * 300 g (2 cups) chickpea flour
 * 500 ml (2 cups) water
 * 2 tbsp olive oil
 * 1 tsp salt
 * Black pepper to taste; 2–3 decent grinds of a grinder should do

Equipment

 * Oven
 * Something to cook the socca on; traditionally, a 50cm (20 inch) copper plaque is used as it spreads the heat evenly to all parts of the socca, but a good cast iron pan will suffice if preheated in the oven first.

Procedure

 * 1) Heat oven as high as it can go—around 300°C / 570°F is traditional, but do whatever your oven can manage that gets close to this. If using a cast-iron pan, get it into the oven at the start so that it is hot when the batter goes into it.
 * 2) Whisk all the ingredients together well, ensuring there are no lumps. This should make a very thin, easy-to-pour batter.
 * 3) Once the oven is up to temperature, pour some of the batter into the hot pan or onto the plaque, and put into the oven for 8–9 minutes at 300°C / 570°F, or 13–15 minutes at 250°C / 480°F. With a 50 cm plaque or pan, cook half the batter at a time—the batter should cover the plaque or pan very thinly.
 * 4) Remove from the oven and cut into triangular wedges. Serve hot.
 * 5) Repeat for the rest of the batter.


text:
User talk:67.86.28.140

Regarding edits made during January 14 2007
Welcome, and thank you for experimenting with Wikibooks! Your test worked, and thank you for reverting or removing it yourself. The best way to do tests in the future would be to use the sandbox. You can look at these pages as well: how to edit a page, editing Wikibooks, and Manual of Style. All of these pages are good places to start. Again, welcome, and I hope that you will like Wikibooks. If this is an IP address, and it is shared by multiple users, ignore this warning if you did not make any unconstructive edits. Az1568(Talk) 04:11, 14 January 2007 (UTC)

title: User talk:67.86.28.140


text:
Wikijunior:New Title Policy/Unstable

The Wikijunior community has adopted some restrictions on what titles can be created within Wikijunior.

Suggesting a title
To suggest a title, visit the New Title Suggestions page and add the title to a list of proposed Wikijunior books. Regular Wikijunior contributors will be able to view this title and make suggestions.

Please try to follow the format when suggesting a new title. Include a list of possible articles that would be within the book. Talk about the audience and scope of the title. Provide a list of questions that will be addressed by the articles.

Voting on new titles
One way that new books are added to Wikijunior is that they have passed through the New Book of the Quarter voting process. This process is designed to make sure that a new book is launched once a quarter and that the book has a high level of community support.

Other ways of adding books
Voting is not the only way to add a book to Wikijunior. In unusual circumstances when trying to meet a contractual obligation such as what has happened with the Beck Foundation when Wikijunior was started, specific book projects can be created by the community independently of the voting process.

If an individual author would like to start a new book on Wikijunior and is willing to contribute substantial content, the author can create the book, suggest it in New Title Suggestions, and add it to the list of all books.

Sometimes a suitable book with substantial appropriate content can be adopted by community consensus into the group of recognized Wikijunior titles without going through the New Book of the Quarter voting process.

Additional notes
This is a Wikijunior specific policy, and not something that pertains to Wikibooks in general. If in the future, there is increased activity on Wikijunior, this whole policy may be substantially revised or done away with, but for now this will give us a chance to gradually expand without being overwhelmed with a bunch of book stubs that don't go anywhere.

Adding a new Wikijunior book is not a huge thing. Even a brand-new contributors are encouraged to suggest a new title. If you want to write a book and are willing to put the hard work into developing substantial content yourself, we encourage you to do so. Have fun and enjoy working with Wikijunior. We are glad that you are here.

title: Wikijunior:New Title Policy/Unstable


text:
Wikijunior talk:New Title Policy/Unstable

I think that this document badly needs to be updated and revised. So I'm being bold and doing so. --xixtas 05:54, 14 January 2007 (UTC)

Motion to adopt
If there are no objections I will make this policy active on the grounds that:
 * 1) It is a heckuva lot better than what is already there.
 * 2) No-one has spoken against it.
 * 3) Misunderstandings that this document address are damaging to Wikijunior and stifling its development.
 * 4) This document has been up for review for three weeks, and has been well publicized in the staff lounge and on various users talk pages.

-- xixtas 17:18, 5 February 2007 (UTC)

 * Keep in mind that I wrote the original "policy" in an attempt to change the eariler "policy" for Wikijunior: That no other books other than the "original three" Wikijunior books could be written.  I felt that a better solution could happen to allow some new Wikijunior books, but continue the original philosophy of generally slow growth and encouraging a "polishing" of Wikijunior books rather than a huge expansion of titles.  I'll leave the results of this effort to others to try and determine for themselves.
 * BTW, I am supportive of the current changes and would suggest that this be moved to become "official policy". --Rob Horning 14:12, 6 February 2007 (UTC)

 * I appreciate that the existing new title policy was an effective problem solving step that helped Wikijunior grow. I'm glad that you find the revised policy to be acceptable. --xixtas 16:34, 8 February 2007 (UTC)


text:
Chess/Variants/Chinese Chess

Xiangqi, or Chinese Chess, is an extremely popular game in the Eastern Hemisphere. It is currently played by millions (or tens of millions) in China, Taiwan, Thailand, Singapore, Vietnam, Hong Kong and other Asian countries. Xiangqi has remained in its present form for centuries. It is believed that both Xiangqi and Western Chess derive from the original Indian game of Chanturanga.

Xiang Character (xiáng) Qi Character (qí ) translates to Elephant Game. In Mandarin it is written as either Xiangqi, Xiang Qi or Hsiang-Ch`i and pronounced "Shiang-Chi". In Cantonese it is written as Jeuhng Keih and pronounced "Junk Kay".

The name Xiangqi has an interesting origin. Of China's four traditional arts—qin (music), hua (brush painting), shu (calligraphy) and qí (strategy games) -- the latter term, qi, provides the final syllable of Xiangqi. There is much literature on Xiangqi, most of it in Chinese. There are, however, a few books available in English and other languages.

Xiangqi sets can be procured from a number of sources. The most obvious of these are shops in the Chinese districts of large cities. Often, such sets are quite cheap, consisting of a paper board and flat wooden counters inscribed with red and black pictograms. These traditional Chinese symbols may appear strange to the western eye, but can easily be recognized with a minimum of practice. (For more sophisticated sets, see below.)

The board
The Xiangqi board is made up of ten horizontal lines and nine vertical lines. The verticals are interrupted by a central-horizontal void called a river. Two palaces are positioned at opposite sides of the board. Each is distinguished by a cross connecting its four corner points.

http://www.chessvariants.org/xiangqi.dir/xiangqi1.gif

The above board shows various L-shaped markings in order to distinguish the setup points of Pawns and Cannons. These markings are not present on all commercial boards.

title: Chess/Variants/Chinese Chess


text:
Cookbook:Chorizo

Chorizo is a type of pork sausage made in Spain and other Hispanic cultures. A similar sausage, chouriço, comes from Portugal.

Characteristics
Chorizo comes in several different varieties. Spanish chorizo varieties are cured dry sausages made from chopped pork. They tend to include smoked paprika and garlic as well as regional spices and are not particularly hot. On the other hand, Mexican-style chorizo is a fresh sausage typically consisting of ground pork meat or offal, vinegar, chiles, and other spices —they are spicy and tangy.

Selection and storage
Make sure to purchase the correct variety of chorizo called for by your recipe. Both fresh and cured chorizos should be stored in the fridge. Cured chorizo will have a longer lifespan if kept away from moisture.

Use
Spanish cured chorizos can be eaten raw in much the same way as other cured dry meats like salami or pepperoni—it is excellent on charcuterie plates. However, it can also be added to soups and stews. Mexican chorizo and other fresh chorizo varieties must be cooked before consumption—the filling is often removed and cooked much like ground beef.

title: Cookbook:Chorizo