FAQS List
TWO MOST IMPORTANT FAQs:
1. There is no baking mistake that can't be fixed. 2. Never panic, never tap.
Generally
What hardware/software is needed in order to bake?
Laptop or desktop (phonefagging hard for newbies & tablets lack power). The bigger the screen, the better. Text editor like Notepad++ (for PCs) or Atom (for Macs).
What other skills are good for a baker?
Patience, persistence, high tolerance for criticism, ability to say no to shills. Good enough typing to more or less keep up the pace.
What shift is good for a new baker?
A slow shift like late night to early morning (also, Q seldom posts then). If you take a faster shift, just tell anons you're new and you'll get support.
Bakers Tools
This is an independent tool that anyone can use, but you don't need it to bake.
Baking in TOR
TOR doesn't allow images but does allow embedded YT vids; use for General (Iwo Jima) image. There's usually a TOR vid in "Baking" section of the /qresearch/ dough. (TOR is currently disabled in QR to prevent shills from posting; may be temporarily reactivated if anons can post only thru TOR.)
Don't change previous baker's notables
Possible exceptions: bad links, spelling errors, when they give specific permission.
Baking everyday vs every so often
Whether you can bake a little or a lot, help is always welcome in the kitchen.
How to reduce baking stress
Practice first, develop routines, be prepared, stay calm, don't fixate on mistakes.
The Dough
The dough = first 1-4 posts in each bread (varies over time). Each post in one document separated by some kind of BREAK markers.
Organization @Feb 2022
post 1 - Q posts/resource links, post 2 - Notables Notables page can be broken into two pages on the fly if notable buns are long (even tho there's no BREAK marker).
Practice Baking
Practice bake in /comms/, established in 2018 by BO Rusty. After getting down the basic steps, try shadow baking (following a real bake to get the timing down).
Green text
In /comms/ practice bakes using Q Research doughs, links don't work and text is green.
Pastebins: ControlC.com & Fullchan.net
What is a pastebin?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account
No, anyone can use either as a GUEST. See
Notables
How to tell what is notable?
A few ideas: look for anon noms, Q decodes, POTUS tweets/retweets, planefag/boatfag reports, relevant news items (for breaking news, check qresear.ch to avoid dups). Usually, memes are not notabled. Unsauced tweets & articles must be sauced first (quality matters).
How to format notables list?
Formats vary, but best to use bold orred text. Examples: 'Early notables', 'Notables @200', 'Notables #11956 @300'. Always link to dough postif ghosting after posting.
How often do you post notables?
Some ideas:
* 200, 400, 600 (plus a FINAL) or * 250, 500, Last Call around 640 (plus a FINAL).
If you take the bake late: Post notes as soon as you catch up, then enough to let anons know you're still there.
Timing Issues
What's the first thing to do after accepting the handoff?
Most bakers start by finding/copying pastebin (check Dough post first); prepping Create a Thread; and doing a quick dough check to make sure everything is ok. Then start collecting notables.
When to post a final list?
Depends on bread speed but usually around 680 - 710.
How to keep up with notables during fast breads?
Depends how fast. When Q posts, priority is on grabbing Q drops, not notes. During fast non-Q breads, focus on skimming off the 'cream' and leaving the rest, may not be possible to check qresear.ch. Always try to include noms but only if they're high quality (from anons not shills). Practice makes perfect.
How long does a New Thread take to show up after I select Create a Thread?
30 - 60 seconds unless there's a severe lag. If lag is bad, let anons know and ask them to wait for new thread.
Prepping the bake
Prepping includes grabbing the dough, filling in Create a Thread, checking the dough (at least the bread number), making room for new Q posts or notables, transferring notables from text editor to dough. See step-by-step instructions for more.
Max number of breads in Previously Collected Notables?
4 - 5 lines. To make room, just delete the bottom line(s).
Handoffs and Baker Comms
Good /comms/ are critical for well-baked breads, so need to be clear & easy to find.
Showing baker or note-taker changes
Easy to forget but useful to showing who's responsible for which notables. Insert "baker change" or "note-taker" at the point when the change occurs when recording notables.
Handoffs: call-and-response protocol
Baker announces he seeks handoff; available baker(s) announce they can bake; baker usually takes the first in line.
Example: B1:baker seeks handoff', B2:can bake, B1:handoff confirmed?, B2:confirmed, bread is mine
When shill activity is high, baker may be asked to produce a recent pastebin or other proof that he's legit.
Ghost bake protocols - ALWAYS TAG THE DOUGH POST!
When baker can't get a replacement, he may have to ghost the bread (leave it bakerless).
Example: B1:baker seeks handoff; will ghost @100, [no response], B1:baker leaving the kitchenghost bake
When another baker picks up the ghost:baker assuming responsibility. Don't forget to TAG THE DOUGH POST so bakers arriving after @600 will know there's a baker (avoids dup bakes).
When there is more than one baker per bread
Two things to note:
1. Ordering of notables (can be more or less "top to bottom" or "bottom to top"): Either use the same order as first baker or change his to match yours; try not to mix them.
2. Use "baker change" to separate your work from first baker's. Don't treat first baker's notables like suggestions, respect them as if they are PB notables.
Making Reports and Global Reports
To report to BO/BVs, find little triangle on upper left of each post, select it, then use menu.
Use Report to ask BO to make bread changes that bakers can't make, e.g. changing a wrong bread number. You may need to do it more than once (or twice).
Use Global Reports for child porn (CP) or other illegal material. Someone is on-duty 24 hours.
Duplicate bakes
Use Report to ask for moldy bread to be locked and provide a link to 'good' bread.
Baking
See step-by-step instructions on page 1 of class dough. E-BAKE steps are there too.
To bake each page….
Divide bread into 4 posts by looking for BREAK markers. (For two-page notables, do it on-the-fly for page 2).
How to bake when the Catalog is down?
Use the Index (8kun.top/qresearch/index.html). You can Create a Thread there. Afterwards, locate your new thread this way: go past the pinned threads and the old thread; new one is usually right after it. To "enter" that thread, click on the OP post number. (Allow at least 30 secs__ for new thread to appear.)
Baking Error Messages
Body too long
Happens when there are too many characters per post (maybe 5000) or too many lines (maybe 200). This seems to vary but gives you an idea).
Flood detected
Happens if you already posted same exact text (most common–if so, add a space somewhere). Can also happen during DDOS or when too many anons post at once.
Server took too long
Usual server response for /qresearch/ bakes (95% of bakes). Solution: WAIT AT LEAST 30-60 secs because it will eventually post in Catalog despite the message. Can be confusing for first-time bakers because it seldom if ever happens in /comms/.
Common Mistakes
Don't be afraid to make mistakes - all bakers make 'em (get used to it newbies!). Easy-to-make mistakes:
* Incomplete copypasta (not grabbing ALL the dough when baking for each post, so that top or bottom isn't there)
* Screwing up content or formatting for bread title (use Report to have BO/BVs correct).
* Not tagging the dough post in comms like handoffs, picking up a ghost bake or posting notes in a ghost bake
'''* Forgetting to use BOLD andred textfor handoffs, Notables posts, and other important comms
* Confusing "Create a Thread" in the Catalog with "Post a Reply" within a bread. (Avoid this by putting Create a Thread tab far away from tab with current bread.)
* Accidentally pressing Create a Thread before end of bread (Solution: report premature thread to BO/BVs, post a link back to real bread, post an alert & apology to anons, then forget it & return to bake).
* Dough errors (Solution: generate new dough & post pastebin link in the bread. First-time bakers: just leave a message for next baker on the problem.)
Q Bakes
Generally: When Q posts, drop everything and get to bottom of bread to pick up Q drops and put them in the dough. Pick up notes from there if you can. Bake EARLY - @630 is not uncommon.
Formatting Q drop LINES
Use existing Q drops to see formatting; copy-pasta the LINES__, don't try to do them yourself.
Cap for baker
Anons will usually post them for you. Search with F3 on the link or 'cap for baker'.
Dealing with Shills
Shills want a bread full of squabbling anons so that anons withdraw and good digs are overlooked. Just the presence of a baker deters them. The regular posting of notables shows anons that the work goes on despite distractions. See also "How To Quickly Spot A Clown" (last line of page 1 in /qr/ dough).
Telling anons from shills
Baker: "you can tell when a reasonable accommodation does not mollify." Posters who kvetch no matter what are shills, not anons.
Responding to shill tactics
Shills always test bakers, pressuring them on notables, dough changes, etc.
If being reasonable does not work (see above), make a decision and stand firm with it.
Common shill tactics for screwing with baker
Purposely leaving out dates on moldy notables; nomming a list of notables at end of bred; nomming hard-to-evaluate Q decodes w/no main point or title; including no sauce or crap sauce; burying bad stuff in the middle of a post (muh joos, etc), moaning about pb notables/asking for changes. Anons do some of these things too but shills are more obvious about it.
Ways to respond when you're sure it's a shill:
* Generic shilling/spam: Generally ignore.
* When shills demand something: Respond calmly, with humor and facts, try funny memes to diffuse an attack (Left still can't meme). Memes also tend to end the conversation. See Baker Tips for examples of how to outlaugh a shill.
* For a personal attack targeting you: If it's major, don't take that shit, fight back, it's war. Make the shill POS sorry he ever took you on with a vicious but meticulously documented, fact-based counterattack. Caps can help. Remember, revenge is a dish best served cold.