tripcode test
tripcode test 2
Q & A
ββββ Class #1 (2/13/20)
>>6237 How often do you post a notables list? >>6244, >>6248, >>6266, >>6251, >>6278
>>6253, >>6471 What is "body too long"? How to fix? >>6253, >>6275
>>6252 When do you post next bread link to hit 751 (sniping)? >>6263
>>6283 Last notable post: any special formatting? >>6296, >>6297
>>6302 Better to make the updated pastebin before baking or after (and then post the dough)? >>6304
ββββ Class #2 (2/20/20)
>>6406 How to deal with "server too long" message? >>6423
>>6672 How to put my text editor notables in pastebin? >>6673
>>6432 How to tell what is notable and what is not? >>6432, >>6434, >>6436, >>6450, >>6466
>>6513 Do real anons actually love the bewbs (or are they just a distraction)? >>6521, >>6523, >>6526, >>6532
>>6533 How do you make a new pastebin? >>6543, >>6537
>>6549 How much practice do I need? >>6550, >>6559
>>6570 How do you format a Q post? >>6573, >>6588, >>6597, >>6598
>>6630 How great is the need for bakers? >>6635
>>6693 What are the //// BREAK \\ in the pastebin [page breaks]? >>6694
>>6732 Do notables go directly in the dough/pastebin file or in a separate Notable file? >>6691, >>6732
>>6833 How to bake: Index vs Catalog? >>6834, >>6839
>>6779 What shifts need bakers? >>6781, >>6802, >>6806, >>6811, >>6822 [rt 6802], >>6824,
>>6845 Feedback on a new bake rt >>6842
ββββ Class #3 (2/27/20)
>>6908 How do you 'grab the dough'? 10 steps: >>6910, >>6924, >>6928, >>6949, >>6955, >>7042, >>7045, >>7049, >>7055, >>7070
>>6934, >>6938 What is "baker's tools" app & where to find it? >>6943, >>6950, >>6951
>>7073 Anon request for feedback on bake: >>7081, >>7086
>>6966 How does a baker keep up with notables (day, night, Q)? >>6982
>>6983 I got "body too long" - what to do? >>6998, >>7007, >>7015, >>7024, >>7040
>>6984 Anon: plz check my work? >>6994
>>7028 Do I need a pastebin login account? [no!]
>>6995 Max no. of breads in "Previously Collected Notables"? >>7033
>>7033 Can you avoid two-page notables by placing oldest breads in "previously collected notables? [yes!]
>>7025 Body too long: what's the limit? [~4500 chars or 100 lines]
>>7030 Why are links in practice bakes green? >>7030, >>7035
ββββ Class #4 (3/5/20)
>>7193 Baking possible on a cell phone? >>7010, >>7205
>>7210 How do you know who is baking? >>7215, >>7218, >>7222
>>7236 I know I would choke if things got too hectic >>7240
>>7315 How do i get notable bun linked under previously collected notables? >>7319
ββββ Class #5 (3/12/20)
>>7735 What about sniping? >>7739, >>7752
>>7779 How can you tell a real baker from a shill baker? >>7781, >>7790, >>7803, >>7807, >>7821, >>7861
>>7833 How do i know which baker is baking? >>7838, >>7849, >>7851, >>7866, >>7884, >>7885, >>7906
>>7830 How do bakers delete posts? [they don't] >>7834, >>7837, >>7839, >>7842
>>7853 Should I get a pastebin account? >>7870, >>7875
>>8003 What is the "flood detected" message when baking? >>8011, >>8016
>>8024 Does baker include only anon noms in notables? >>8029
ββββ Class #6 (3/19/20)
>>8421 Notes: how do you keep up in a fast bred? >>8432, >>8440
>>8500 What is "shadowing the bread"? >>8546
>>8679 Am I too slow to bake? No! >>8679, >>8698, >>8696, >>8700
>>9258 How do you insert General Image in TOR bakes? >>9278
ββββ Class #7(3/26/20) & Class #8''' (4/02/20)
>>9258 How do TOR bakers use the Iwo Jima video? (7)
>>9135 Can we recap? (7)
>>9397 /comms/ with anons from bakersβok or not? >>9382, >>9397, >>9407, >>9410. >>9411, >>9418 (8)
>>9530 How often does BO log in? (8)
>>9918 Bred titles: What's ok & how to format? >>9932, >>9936 (8)
ββββ Class #9 (4/09/20)
>>10020 Why are my notables green? >>10026, >>10041
>>10032 Q about images: when png, TOR, mp4? >>10067
>>9999 When to postbaking? >>10010, >>10079, >>10092
>>10162 How many practice baker b4 a real bake? >>10168, >>10174
ββββ Class #10 (4/16/20)
>>10641 What do when Q posts? >>10645
>>10762 Would like to bake but have no regular schedule >>10763, >>10765
ββββ Class #11 (4/23/20)
>>11376 Why use both pastebin.com and notepad++? >>11312, >>11321, >>11325
>>11306 How to keep up in fast breads? >>11309, >>11314, >>11320
ββββ Class #14 (5/13/20)
>>13633 Thought on long notable buns
What's you best tip, bakers?
>>13653 Baking from the index
>>13740 Keeping your place in the thread as you move around
>>13782 What do do if your new thread freezes when posting
>>13795 Handoff comms - call & response
>>13820 Numbering threads & notables
=Baker Tips, Tricks & Traps==
ββββ Class #1 (2/13/20)
>>6329, >>6400, >>6468 /comms/ BO Rusty checks in
ββββ Class #2 (2/20/20)
>>6431 What is "pastebin"?
>>6449 Shill tactic of omitting dateβwhy dates matter,other advice on notabling >>6477
>>6480 Even the worst mistakes are fixable
>>6501, >>6477 How to deal with Q proofs & other anon analyses
>>6525 How to post off-bred links
>>6543 Take care to copypaste entire dough to pastebin - easy to miss top or bottom
>>6658, >>6656 Use Control-F (F3) to search within each bread
>>6665 Every new baker freaks out when when Q posts
>>6676 Never feel dumb
>>6734 When to make a new thread [to prep it, not bake it!]
>>6683, >>6687 Cloning the dough in case pastebin.com goes down
>>6695, >>6735, >>6752, >>6754, >>6769, >>6822 Bakers on nick-names, icons, pastebins
>>6848 Baking trick (what to do while waiting for thread to drop)
ββββ Class #3 (2/27/20)
>>7340, >>7072 Baking Steps 1 - 9 (slides only)
>>6998 One- vs two-page notables (more: >>7007, >>7015, >>7024, >>7040)
>>7019, >>7027, >>7030, >>7069 Bakers never panic, never tap
>>7051 Advantages of a non-guest pastebin account [no captcha]
>>7054 You don't have to pull marathons to bake
>>7106, >>7177 Baker pleased to see 2 late gy bakers vying for the bread
>>7116 Eight tips for creating notables posts (to help bakers)
>>7175 End-of-bread issues
ββββ Class #4 (3/5/20)
>>7189 Summary of Baking Steps (eight)
>>7209 "Create a Thread" versus "Post a Reply" >>7212, >>7220
>>7231 Only the first post in baking uses "Create a thread"
>>7216 Laptop is fine for baking
>>7224 The two parts of baking: actual baking & note-taking
>>7252 Funny meme: baker's perspective on baking
>>7287, >>7294 Dough posts with breaks marked /////BREAK\\\
>>7298, >>7303, >>7311 Two-page notables (discussion)
>>7321 How to create a new dough paste
ββββ Class #5 (3/12/20)
>>7573, >>7575, >>7582 In response to "I suck at baking": How to reduce baking stress
>>7731 Pastebin.com works with Mac OS
>>7642 Text editor for a Mac: Atom >>7643, >>7651, >>7729
>>7768 Bakers need detachment >>7770, >>7773
>>7780 Plz don't edit another baker's notables >>7780, >>7784, >>7798, >>7804, >>7809, >>7811, >>7815, >>7817
>>7896, >>7898 Bakers don't want to be ID'd by number
>>8039 Baker school is attracting shillsβmust be over the target
>>8139 Q Bakes: when to bake & late-minute Q posts
>>8237 Tell anons to plz state the main point when posting Q proofs, etc.
ββββ Class #6 (3/19/20)
>>8352 Note-taking wo/baking, baker's assist controversy >>8365, >>8385, >>8413, >>8419, >>8433
>>8544, >>8562 When to drop note-taker notables
>>8788 "8chan" baking vs "WWG1WGA" baking, cooperation w/anons
>>8373 Who's responsible for checking notables (bakers or anons)? >>8388
ββββ Class #7 (3/26/20)
>>8885 The perfect bake: composition, timing, snipe >>8887, >>8888 (You), >>8889
>>8911 Role of bakers on the board plus bakers/BOs >>8915 (You), >>8923 (You)
>>9127 Baking thread a continuing resource
>>9136 Taking notables/baking for a baker
>>9186 (You), >>9193 (You) New bakers coming online, anon encouragement
>>9181 New baker's dough & notes plus feedback >>9188 (You), >>9191 (You), >>9195
>>9191 How to handle notables when there is more than one baker per bread
ββββ Class #8 (4/02/20)
>>9411 Differing ideas about baker demeanor >>9375, >>9382, >>9404, >>9411, >>9418
>>9431 Current relationship with /qr/ BO @fj
>>9337 Bread titleβput colon AFTER the bread number
>>9373 Qs after @600 - don't let shills distract
>>9375 Notable posting, timing 200-400-600
>>9386 Bakers message to anons
>>9380 Notables post after the bake
ββββ Class #9 (4/09/20)
>>9970, >>9981, >>10011, >>10017 Formatting bun numbers, notables page
>>10083, >>10106 Tell anons of needed baker changes in advance; timing issues
>>10081 Note-taker steps to bake for first time
>>10087, >>9993 Formatting issues
>>10075 Importance of tagging the dough post
>>10078, >>10101 Ideas for streamlining notables; what to include/exclude?
>>10106, >>10119, >>10116, >>10167 "Last call crew" (anons/shills who call out problems at end of bake)
>>10101, >>10111 Telling anons from shills
>>10132, >>10148, >>10163 Ignore shills when baking
>>10133 Creating a pastebin early
>>10226 Can't make it to class? Suggestions
ββββ Class #10 (4/16/20)
>>10547, >>6892 Baker handoffs
>>10555, >>10815 Max post length: 4700-5000 characters, ~200 lines (results vary).
>>10581 Good comms with anons
>>10696 How to report a thread or post
>>10763 Team baking (baker plus note collector) >>10765, >>10764
ββββ Classes #11 & 12 (4/23/20 & 4/30/20)
>>12690 Take baking policy q's to new bakers Meta thread
Q & A
ββββ Class #1 (2/13/20)
>>6237 How often do you post a notables list? >>6244, >>6248, >>6266, >>6251, >>6278
>>6253, >>6471 What is "body too long"? How to fix? >>6253, >>6275
>>6252 When do you post next bread link to hit 751 (sniping)? >>6263
>>6283 Last notable post: any special formatting? >>6296, >>6297
>>6302 Better to make the updated pastebin before baking or after (and then post the dough)? >>6304
ββββ Class #2 (2/20/20)
>>6406 How to deal with "server too long" message? >>6423
>>6672 How to put my text editor notables in pastebin? >>6673
>>6432 How to tell what is notable and what is not? >>6432, >>6434, >>6436, >>6450, >>6466
>>6513 Do real anons actually love the bewbs (or are they just a distraction)? >>6521, >>6523, >>6526, >>6532
>>6533 How do you make a new pastebin? >>6543, >>6537
>>6549 How much practice do I need? >>6550, >>6559
>>6570 How do you format a Q post? >>6573, >>6588, >>6597, >>6598
>>6630 How great is the need for bakers? >>6635
>>6693 What are the //// BREAK \\ in the pastebin [page breaks]? >>6694
>>6732 Do notables go directly in the dough/pastebin file or in a separate Notable file? >>6691, >>6732
>>6833 How to bake: Index vs Catalog? >>6834, >>6839
>>6779 What shifts need bakers? >>6781, >>6802, >>6806, >>6811, >>6822 [rt 6802], >>6824,
>>6845 Feedback on a new bake rt >>6842
ββββ Class #3 (2/27/20)
>>6908 How do you 'grab the dough'? 10 steps: >>6910, >>6924, >>6928, >>6949, >>6955, >>7042, >>7045, >>7049, >>7055, >>7070
>>6934, >>6938 What is "baker's tools" app & where to find it? >>6943, >>6950, >>6951
>>7073 Anon request for feedback on bake: >>7081, >>7086
>>6966 How does a baker keep up with notables (day, night, Q)? >>6982
>>6983 I got "body too long" - what to do? >>6998, >>7007, >>7015, >>7024, >>7040
>>6984 Anon: plz check my work? >>6994
>>7028 Do I need a pastebin login account? [no!]
>>6995 Max no. of breads in "Previously Collected Notables"? >>7033
>>7033 Can you avoid two-page notables by placing oldest breads in "previously collected notables? [yes!]
>>7025 Body too long: what's the limit? [~4500 chars or 100 lines]
>>7030 Why are links in practice bakes green? >>7030, >>7035
ββββ Class #4 (3/5/20)
>>7193 Baking possible on a cell phone? >>7010, >>7205
>>7210 How do you know who is baking? >>7215, >>7218, >>7222
>>7236 I know I would choke if things got too hectic >>7240
>>7315 How do i get notable bun linked under previously collected notables? >>7319
ββββ Class #5 (3/12/20)
>>7735 What about sniping? >>7739, >>7752
>>7779 How can you tell a real baker from a shill baker? >>7781, >>7790, >>7803, >>7807, >>7821, >>7861
>>7833 How do i know which baker is baking? >>7838, >>7849, >>7851, >>7866, >>7884, >>7885, >>7906
>>7830 How do bakers delete posts? [they don't] >>7834, >>7837, >>7839, >>7842
>>7853 Should I get a pastebin account? >>7870, >>7875
>>8003 What is the "flood detected" message when baking? >>8011, >>8016
>>8024 Does baker include only anon noms in notables? >>8029
ββββ Class #6 (3/19/20)
>>8421 Notes: how do you keep up in a fast bred? >>8432, >>8440
>>8500 What is "shadowing the bread"? >>8546
>>8679 Am I too slow to bake? No! >>8679, >>8698, >>8696, >>8700
>>9258 How do you insert General Image in TOR bakes? >>9278
ββββ Class #7(3/26/20) & Class #8''' (4/02/20)
>>9258 How do TOR bakers use the Iwo Jima video? (7)
>>9135 Can we recap? (7)
>>9397 /comms/ with anons from bakersβok or not? >>9382, >>9397, >>9407, >>9410. >>9411, >>9418 (8)
>>9530 How often does BO log in? (8)
>>9918 Bred titles: What's ok & how to format? >>9932, >>9936 (8)
ββββ Class #9 (4/09/20)
>>10020 Why are my notables green? >>10026, >>10041
>>10032 Q about images: when png, TOR, mp4? >>10067
>>9999 When to postbaking? >>10010, >>10079, >>10092
>>10162 How many practice baker b4 a real bake? >>10168, >>10174
ββββ Class #10 (4/16/20)
>>10641 What do when Q posts? >>10645
>>10762 Would like to bake but have no regular schedule >>10763, >>10765
ββββ Class #11 (4/23/20)
>>11376 Why use both pastebin.com and notepad++? >>11312, >>11321, >>11325
>>11306 How to keep up in fast breads? >>11309, >>11314, >>11320
ββββ Class #14 (5/13/20)
>>13633 Thought on long notable buns
>>13653 Baking from the index
>>13740 Keeping your place in the thread as you move around
>>13782 What do do if your new thread freezes when posting
>>13795 Handoff comms - call & response
>>13820 Numbering threads & notables
LIVE Baking Seminar
5/14/2020
We in here
Welcome To LIVE Baking Classes in the Q Research Utility Kitchen
We hold these truths to be self-evident: that all men are created equal; that they are endowed by their Creator with certain unalienable rights; that among these are life, liberty, and the pursuit of happiness.
We are the bakers who provide the breads for those anons who post Qresearch's open-sourced information, reasoned argument, and dank memes. We do battle in the sphere of baking ideas and baking ideas only. We neither need nor condone the use of force in our work here.
VINCIT OMNIA VERITAS
SEMPER FIDELIS
WWG1WGA
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
General Announcements
* Baking Class in /comms/ every Thursday @7pm ET: practice baking, Q&A, all are welcome
* Baking class plan by Teach: >>11969, https://pastebin.com/gqfunWCR
Past Class links & archives
>>6125 #1 (2/13/20), >>6368 #2 (2/20/20), >>6885 #3 (2/27/20), >>7185 #4 (3/05/20), #5 >>7568 (3/12/20), >>8274 #6 (3/19/20), >>8872 #7 (3/26/20), >>9320 #8 (4/02/20), >>9787 #9 (4/09/20), >>10510 #10 (4/16/20), #11 >>11086 (4/23/20), #12 >>11733 (4/30/20), #13 >>13041 (5/07/20)
Archives for classes #1 - #12: >>13498
Step by Step Baking Instructions
Simpler version on the left; more detailed version on the right.
>>11792 PREPARATION
>>11815 STEP 1 - Find the Current Dough
>>11833 STEP 2 - Copy the Current Dough
>>11838 STEP 3 - Paste The Dough Into Text Editor
>>11204 STEP 3a - Trim The Notables Section
>>11857 STEP 3b - Make space for your new notables.
>>11860 STEP 4 - Create A New Thread >>11216
>>11869 STEP 5 - Enter Thread Info And Post Thread
>>11896 STEP 7 - Make A New Pastebin & Make The Dough Post
>>11905 STEP 8 - Post Your New Thread Link
Overview & Extras
>>11161 Modules 1 & II:
Timing the Bake
>>11917 Linking between Boards
>>11922 Archiving & teaching files (screenshot; almost current)
E-BAKE Instructions
LIVE Baking Seminar
5/14/2020
We in here
Welcome To LIVE Baking Classes in the Q Research Utility Kitchen
We hold these truths to be self-evident: that all men are created equal; that they are endowed by their Creator with certain unalienable rights; that among these are life, liberty, and the pursuit of happiness.
We are the bakers who provide the breads for those anons who post Qresearch's open-sourced information, reasoned argument, and dank memes. We do battle in the sphere of baking ideas and baking ideas only. We neither need nor condone the use of force in our work here.
VINCIT OMNIA VERITAS
SEMPER FIDELIS
WWG1WGA
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
General Announcements
* Baking Class in /comms/ every Thursday @7pm ET: practice baking, Q&A, all are welcome
* Baking class plan by Teach: >>11969, https://pastebin.com/gqfunWCR
Past Class links & archives
>>6125 #1 (2/13/20), >>6368 #2 (2/20/20), >>6885 #3 (2/27/20), >>7185 #4 (3/05/20), #5 >>7568 (3/12/20), >>8274 #6 (3/19/20), >>8872 #7 (3/26/20), >>9320 #8 (4/02/20), >>9787 #9 (4/09/20), >>10510 #10 (4/16/20), #11 >>11086 (4/23/20), #12 >>11733 (4/30/20), #13 >>13041 (5/07/20)
Archives for classes #1 - #12: >>13498
Step by Step Baking Instructions
Simpler version on the left; more detailed version on the right.
>>11792 STEP 1 - Preparation
>>11815 STEP 1a - Find the Current Dough
>>11833 STEP 2 - Copy the Current Dough
>>11838 STEP 3 - Paste The Dough Into Text Editor
>>11204 STEP 3a - Trim The Notables Section
>>11857 STEP 3b - Make space for your New Notables
>>11860 STEP 4 - Create A New Thread >>11216
>>11869 STEP 5 - Enter Thread Info And Post Thread
>>11896 STEP 7 - Make A New Pastebin & Make The Dough Post
>>11905 STEP 8 - Post Your New Thread Link
Overview & Extras
>>11161 Modules 1 & II: Timing the Bake
>>11917 Linking between Boards
>>11922 Archiving & Teaching Files (screenshot; almost current)
E-BAKE Instructions
Baking FAQs
Draft 1.0, still many placeholders, mockup at this point.
Some things have one standard answer but many have more than one. Tried to be brief but allow for diverse ideas.
General stuff
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++.
What other skills are good for a baker?
Patience, persistence, high tolerance for criticism, ability to say no to shills. Good enough typing to 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 if needed.
Practice Baking
Making Reports and Global Reports
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
Notables - see also Timing
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 (sauce quality also matters).
How to format notables list?
Formats vary, but best to use bold orred text; can include "notables", bread #, and bred 'location' (@200 or "Early notables", etc,). Link to d'oh if ghosting after posting. Example: Notables #11956 @300)
How often do you post notables?
Some ideas: 200, 400, 600 (plus a FINAL); 250, 500, Last Call after 600 (plus a FINAL); if you take the bake late: Post as soon as you catch up, then enough to let anons know you are 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 posts, 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.
Error Messages
'body too long'?
Happens when there are too many characters per post (4700 or 4800) or too many lines (maybe 200?).
Flood detected
Prepping the bake see also Timing Issues
This 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 (see step-by-step baking), transferring notables from notepad++ to dough.
Handoffs and Baker Comms
Ghost bake protocols
Working with a note-taker
Importance of tagging the dough post
Baking
Baking, step by step
See page 1 of class dough. E-BAKE steps are there too.
How to bake when the catalog is down?
Use the index: 8kun.top/qresearch/index.html. You can Create a Thread there. Afterwards, you can find your new thread this way: go past the Pinned threads and the old thread; new one is usually right after it. To "enter" the thread, click on the OP post number. Remember to allow at least 30 secs for new thread creation.
Common Beginner Mistakes
Not copying the entire dough when baking (leaving off tops and bottoms of posts)
Avoiding bold andred textin handoffs/comms with anons
Being afraid to make mistakes (all bakers make 'em, get used to it newbies!)
Confusing "Create a Thread" with "Post a Reply"
Your First Q Bake
Important to emphasize incompleteness at this point:
This is not even complete as a mockup but gives sort of an idea of the approach so far (feedback welcome). First draft may be mine (just to provide some 'shape' and org) but by the time the FAQ is through, should reflect the experience of many bakers.
Baking FAQs
draft 1.1
Some things have one standard answer but many have more than one. Tried to be brief but allow for diverse ideas.
TWO MOST IMPORTANT FAQs:
-
There is no baking mistake that can't be fixed!
-
Bakers 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 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 if needed.
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; there's usually a TOR vid in "Baking" section of the dough.
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 worry about mistakes.
The Dough
The dough = first 4-5 posts in each bread. Each post in one document separated by /////BREAK\\\ markers.
'Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. 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
You can 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.
Making Reports and Global Reports
Use Reports 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.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
Notables - see also Timing
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 (sauce quality matters).
How to format notables list?
Formats vary, but best to use bold orred text; can include "notables", bread #, and bred 'location' (@200 or "Early notables", etc,). Link to d'oh if ghosting after posting. Example: Notables #11956 @300)
How often do you post notables?
Some ideas: 200, 400, 600 (plus a FINAL); 250, 500, Last Call after 600 (plus a FINAL); if you take the bake late: Post as soon as you catch up, then enough to let anons know you are 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 posts, 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
This 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.
Max number of breads in Previously Collected Notables?
about 4 lines. To make room, just delete the bottom line(s).
Handoffs and Baker Comms
Indicate baker or note-taker changes
Easy to forget but useful to showing who's responsible for what. insert "baker change" or "note-taker" in the bun.
with baker change in notables on page 2 of doug
Clear handoffs are very important so it's clear who's baking.
Call and response approach
Baker announces he seeks handoff; available baker(s) announce they can bake; baker usually takes the first in line.
Example:baker seeks handoff',can bake,handoff confirmed?,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:baker seeks handoff; will ghost @100, [no response],baker leaving the kitchenghost bake
When another baker picks up the ghost:baker assuming responsibility
When there is more than one baker per bread
two things to note: first baker's org of notables (top to bottom or bottom to top) and baker change notification.
Either use the same order as first baker or change his to match yours; don't mix them. 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 were PB notables.
Working with a note-taker
'''When there
Importance of tagging the dough post
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, you can find 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. (When baking, remember to allow at least 30 secs for new thread creation.)
Baking Error Messages
'body too long'?
Happens when there are too many characters per post (4700 or 4800) or too many lines (maybe 200? unclear because it sometimes varies).
Flood detected
Happens if you already posted same exact text (most common); can also happen during DDOS or when too many anons post at once.
Server took too long
Often/usually happens when bakingβin that case, WAIT AT LEAST 30-60 secs because it will eventually post in Catalog despite the message. Can be confusing for first-time bakes 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!)
But here are some of the 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 selecting 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 about accidental new thread, get back to the bake.).
-
Formatting errors in Notables page in dough (Solution: generate new dough and post pastebin link in the bread; if that's too much, post needed dough change for next baker.)
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 it; __copy-pasta the LINES, don't try to do them yourself.
Cap for baker
Don't try to get the caps, anons will post them. Search with F3 on 'cap for baker'.
Dealing with Shills
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 pressures
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.
Baking FAQs
draft 1.1
For step-by-step baking instructions, see page one of current baking seminar dough; it's also in baking section of /qresearch/ dough.
TWO MOST IMPORTANT FAQs:
-
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; there's usually a TOR vid in "Baking" section of the /qresearch/ dough.
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 worry about mistakes.
The Dough
The dough = first 4-5 posts in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. 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
You can 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.
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.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 (sauce quality matters).
How to format notables list?
Formats vary, but best to use bold orred text; can include "notables", bread #, and bred 'location' (@200 or "Early notables", etc,). Link to d'oh if ghosting after posting. Example: Notables #11956 @300)
How often do you post notables?
Some ideas: 200, 400, 600 (plus a FINAL); 250, 500, Last Call after 600 (plus a FINAL); if you take the bake late: Post as soon as you catch up, then enough to let anons know you are 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 posts, 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.
Max number of breads in Previously Collected Notables?
about 4 lines. To make room, just delete the bottom line(s).
Handoffs and Baker Comms
Indicate baker or note-taker changes
Easy to forget but useful to showing who's responsible for what. insert "baker change" or "note-taker" in the bun.
with baker change in notables on page 2 of dough.
Clear handoffs are very important so it's clear who's baking.
Call and response approach
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
When there is more than one baker per bread
two things to note: first baker's org of notables (top to bottom or bottom to top) and baker change notification.
Either use the same order as first baker or change his to match yours; don't mix them. 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.
Working with a note-taker
'''When there
Importance of tagging the dough post
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. (When baking, remember to allow at least 30 secs for new thread to appear in index.)
Baking Error Messages
'body too long'?
Happens when there are too many characters per post (4700 or 4800) or too many lines (maybe 200? unclear because it sometimes varies).
Flood detected
Happens if you already posted same exact text (most common); can also happen during DDOS or when too many anons post at once.
Server took too long
Often/usually happens when bakingβin that case, WAIT AT LEAST 30-60 secs because it will eventually post in Catalog despite the message. Can be confusing for first-time bakes 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!)
But here are some of the 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 selecting 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 about accidental new thread, get back to the bake.).
* Formatting errors in Notables page in dough (Solution: generate new dough and post pastebin link in the bread; if that's too much, post needed dough change for next baker.)
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 it; __copy-pasta the LINES, don't try to do them yourself.
Cap for baker
Don't try to get the caps, anons will post them. Search with F3 on 'cap for baker'.
Dealing with Shills
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 pressure 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.
Baking FAQs
draft 1.1
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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; there's usually a TOR vid in "Baking" section of the /qresearch/ dough.
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 worry about mistakes.
The Dough
The dough = first 4-5 posts in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. 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
You can 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.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 (sauce quality matters).
How to format notables list?
Formats vary, but best to use bold orred text; can include "notables", bread #, and bred 'location' (@200 or "Early notables", etc,). Link to d'oh if ghosting after posting. Example: Notables #11956 @300)
How often do you post notables?
Some ideas: 200, 400, 600 (plus a FINAL); 250, 500, Last Call after 600 (plus a FINAL); if you take the bake late: Post as soon as you catch up, then enough to let anons know you are 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 posts, 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.
Max number of breads in Previously Collected Notables?
about 4 lines. To make room, just delete the bottom line(s).
Handoffs and Baker Comms
Indicate baker or note-taker changes
Easy to forget but useful to showing who's responsible for what. insert "baker change" or "note-taker" in the bun.
with baker change in notables on page 2 of dough.
Clear handoffs are very important so it's clear who's baking.
Call and response approach
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
When there is more than one baker per bread
two things to note: first baker's org of notables (top to bottom or bottom to top) and baker change notification.
Either use the same order as first baker or change his to match yours; don't mix them. 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. (When baking, remember to allow at least 30 secs for new thread to appear in index.)
Baking Error Messages
'body too long'?
Happens when there are too many characters per post (4700 or 4800) or too many lines (maybe 200? unclear because it sometimes varies).
Flood detected
Happens if you already posted same exact text (most common); can also happen during DDOS or when too many anons post at once.
Server took too long
Often/usually happens when bakingβin that case, WAIT AT LEAST 30-60 secs because it will eventually post in Catalog despite the message. Can be confusing for first-time bakes 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!)
But here are some of the 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 selecting 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 about accidental new thread, get back to the bake.).
* Formatting errors in Notables page in dough (Solution: generate new dough and post pastebin link in the bread; if that's too much, post needed dough change for next baker.)
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 it; __copy-pasta the LINES, don't try to do them yourself.
Cap for baker
Don't try to get the caps, anons will post them. Search with F3 on 'cap for baker'.
Dealing with Shills
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 pressure 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.
Baking FAQs
draft 1.1
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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; there's usually a TOR vid in "Baking" section of the /qresearch/ dough.
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 worry about mistakes.
The Dough
The dough = first 4-5 posts in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. 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
You can 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.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 (sauce quality matters).
How to format notables list?
Formats vary, but best to use bold orred text; can include "notables", bread #, and bred 'location' (@200 or "Early notables", etc,). Link to d'oh if ghosting after posting. Example: Notables #11956 @300)
How often do you post notables?
Some ideas: 200, 400, 600 (plus a FINAL); 250, 500, Last Call after 600 (plus a FINAL); if you take the bake late: Post as soon as you catch up, then enough to let anons know you are 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 posts, 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.
Max number of breads in Previously Collected Notables?
about 4 lines. To make room, just delete the bottom line(s).
Handoffs and Baker Comms
Indicate baker or note-taker changes
Easy to forget but useful to showing who's responsible for what. insert "baker change" or "note-taker" in the bun.
with baker change in notables on page 2 of dough.
Clear handoffs are very important so it's clear who's baking.
Call and response approach
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
When there is more than one baker per bread
two things to note: first baker's org of notables (top to bottom or bottom to top) and baker change notification.
Either use the same order as first baker or change his to match yours; don't mix them. 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. (When baking, remember to allow at least 30 secs for new thread to appear in index.)
Baking Error Messages
'body too long'?
Happens when there are too many characters per post (4700 or 4800) or too many lines (maybe 200? unclear because it sometimes varies).
Flood detected
Happens if you already posted same exact text (most common); can also happen during DDOS or when too many anons post at once.
Server took too long
Often/usually happens when bakingβin that case, WAIT AT LEAST 30-60 secs because it will eventually post in Catalog despite the message. Can be confusing for first-time bakes 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 selecting 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 about accidental new thread, get back to the bake.).
* Formatting errors in Notables page in dough (Solution: generate new dough and post pastebin link in the bread; if that's too much, post needed dough change for next baker.)
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 it; __copy-pasta the LINES, don't try to do them yourself.
Cap for baker
Don't try to get the caps, anons will post them. Search with F3 on 'cap for baker'.
Dealing with Shills
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 pressure 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.
Baking FAQs
draft 1.1 https://pastebin.com/uY58Twkp
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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; there's usually a TOR vid in "Baking" section of the /qresearch/ dough.
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 4-5 posts in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. 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
You can 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.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 (sauce quality matters).
How to format notables list?
Formats vary, but best to use bold orred text; can include "notables", bread #, and bred 'location' (@200 or "Early notables", etc,). Link to d'oh if ghosting after posting. Example: Notables #11956 @300)
How often do you post notables?
Some ideas: 200, 400, 600 (plus a FINAL); 250, 500, Last Call after 600 (plus a FINAL); if you take the bake late: Post as soon as you catch up, then enough to let anons know you are 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.
Max number of breads in Previously Collected Notables?
about 4 lines. To make room, just delete the bottom line(s).
Handoffs and Baker Comms
Indicate baker or note-taker changes
Easy to forget but useful to showing who's responsible for what. insert "baker change" or "note-taker" in the bun.
with baker change in notables on page 2 of dough.
Clear handoffs are very important so it's clear who's baking.
Call and response approach
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
When there is more than one baker per bread
two things to note: first baker's org of notables (top to bottom or bottom to top) and baker change notification.
Either use the same order as first baker or change his to match yours; don't mix them. 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. (When baking, remember to allow at least 30 secs for new thread to appear in index.)
Baking Error Messages
'body too long'?
Happens when there are too many characters per post (4700 or 4800) or too many lines (maybe 200? unclear because it sometimes varies).
Flood detected
Happens if you already posted same exact text (most common); can also happen during DDOS or when too many anons post at once.
Server took too long
Often/usually happens when bakingβin that case, WAIT AT LEAST 30-60 secs because it will eventually post in Catalog despite the message. Can be confusing for first-time bakes 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 selecting 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 about accidental new thread, get back to the bake.).
* Formatting errors in Notables page in dough (Solution: generate new dough and post pastebin link in the bread; if that's too much, post needed dough change for next baker.)
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 it; __copy-pasta the LINES, don't try to do them yourself.
Cap for baker
Don't try to get the caps, anons will post them. Search with F3 on '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
-
Ignore generic shilling/spam
-
When shills demand something: Respond calmly, with humor and facts, try funny memes for diffusing an attack (Left still can't meme). See Baker Tips for real-life examples.
-
For an attack aimed at you, the baker: While every situation is different, there are times when you need to explain the situation. Your audience is not the shill but anons. Don't get triggered, just use factsand if possible HUMORto deter the shill and diffuse the tension.You'll know you've won when shills stop arguing and just throw epithets ("Shill baker, anons check notables!")
Baking FAQs
draft 1.1 https://pastebin.com/uY58Twkp
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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; there's usually a TOR vid in "Baking" section of the /qresearch/ dough.
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 4-5 posts in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. 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
You can 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.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 (sauce quality matters).
How to format notables list?
Formats vary, but best to use bold orred text; can include "notables", bread #, and bred 'location' (@200 or "Early notables", etc,). Link to d'oh if ghosting after posting. Example: Notables #11956 @300)
How often do you post notables?
Some ideas: 200, 400, 600 (plus a FINAL); 250, 500, Last Call after 600 (plus a FINAL); if you take the bake late: Post as soon as you catch up, then enough to let anons know you are 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.
Max number of breads in Previously Collected Notables?
about 4 lines. To make room, just delete the bottom line(s).
Handoffs and Baker Comms
Indicate baker or note-taker changes
Easy to forget but useful to showing who's responsible for what. insert "baker change" or "note-taker" in the bun.
with baker change in notables on page 2 of dough.
Clear handoffs are very important so it's clear who's baking.
Call and response approach
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
When there is more than one baker per bread
two things to note: first baker's org of notables (top to bottom or bottom to top) and baker change notification.
Either use the same order as first baker or change his to match yours; don't mix them. 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. (When baking, remember to allow at least 30 secs for new thread to appear in index.)
Baking Error Messages
'body too long'?
Happens when there are too many characters per post (4700 or 4800) or too many lines (maybe 200? unclear because it sometimes varies).
Flood detected
Happens if you already posted same exact text (most common); can also happen during DDOS or when too many anons post at once.
Server took too long
Often/usually happens when bakingβin that case, WAIT AT LEAST 30-60 secs because it will eventually post in Catalog despite the message. Can be confusing for first-time bakes 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 selecting 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 about accidental new thread, get back to the bake.).
* Formatting errors in Notables page in dough (Solution: generate new dough and post pastebin link in the bread; if that's too much, post needed dough change for next baker.)
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 it; __copy-pasta the LINES, don't try to do them yourself.
Cap for baker
Don't try to get the caps, anons will post them. Search with F3 on '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
-
Ignore generic shilling/spam
-
When shills demand something: Respond calmly, with humor and facts, try funny memes for diffusing an attack (Left still can't meme). See Baker Tips for real-life examples.
-
For an attack aimed at you, the baker: While every situation is different, there are times when you need to explain the situation. Your audience is not the shill but anons. Don't get triggered, just use factsand if possible HUMORto deter the shill and diffuse the tension.You'll know you've won when shills stop arguing and just throw epithets ("Shill baker, anons check notables!")
Baking FAQs
draft 1.2 https://pastebin.com/uY58Twkp
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. 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
You can 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.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post if ghosting after posting.
How often do you post notables?
Some ideas:
-
200, 400, 600 (plus a FINAL) or * 250, 500, Last Call after 600 (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.
Max number of breads in Previously Collected Notables?
about 4 lines. To make room, just delete the bottom line(s).
Handoffs and Baker Comms
Indicate baker or note-taker changes
Easy to forget but useful to showing who's responsible for what. insert "baker change" or "note-taker" in the bun.
with baker change in notables on page 2 of dough.
Clear handoffs are very important so it's clear who's baking.
Call and response approach
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
Make SURE you LINK TO DOUGH POST so bakers arriving after @600 will know there's a baker (this avoids dup bakes).
When there is more than one baker per bread
two things to note: first baker's org of notables (top to bottom or bottom to top) and baker change notification.
Either use the same order as first baker or change his to match yours; don't mix them. 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. (When baking, remember to allow at least 30 secs for new thread to appear in index.)
Baking Error Messages
'body too long'?
Happens when there are too many characters per post (4700 or 4800) or too many lines (maybe 200? unclear because it sometimes varies).
Flood detected
Happens if you already posted same exact text (most common); can also happen during DDOS or when too many anons post at once.
Server took too long
Often/usually happens when bakingβin that case, WAIT AT LEAST 30-60 secs because it will eventually post in Catalog despite the message. Can be confusing for first-time bakes 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 selecting 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 about accidental new thread, get back to the bake.).
* Formatting errors in Notables page in dough (Solution: generate new dough and post pastebin link in the bread; if that's too much, post needed dough change for next baker.)
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). See Baker Tips for real-life examples.
* For an attack aimed at you, the baker: While every situation is different, there are times when you need to explain the situation. Your audience is not the shill but anons. Don't get triggered, just use facts - and if possible HUMOR - to deter the shill and diffuse the tension.You know you've won when shills stop arguing and just throw epithets ("Shill baker, anons check notables!")
Baking FAQs
draft 1.2 https://pastebin.com/uY58Twkp
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. 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
You can 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.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post''if 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:
-
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.
-
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 (4700 or 4800) or too many lines (maybe 200? unclear because it sometimes varies).
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!"See Baker Tips for real-life examples.
* 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.
Baking FAQs
draft 1.2 https://pastebin.com/uY58Twkp
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. 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
You can 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.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post''if 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:
-
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.
-
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
Baking FAQs
draft 1.2 https://pastebin.com/uY58Twkp
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. 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
You can 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.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post''if 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:
-
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.
-
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
Baking FAQs
draft 1.2 https://pastebin.com/uY58Twkp
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. 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
You can 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.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post''if 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:
-
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.
-
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
Baking FAQs
draft 1.2 https://pastebin.com/uY58Twkp
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. 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
You can 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.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post''if 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:
-
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.
-
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
Baking FAQs
draft 1.2 https://pastebin.com/uY58Twkp
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. 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
You can 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.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post''if 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:
-
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.
-
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
Baking FAQs
draft 1.2 https://pastebin.com/uY58Twkp
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. 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
You can 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.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post''if 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:
-
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.
-
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
Baking FAQs
draft 1.2 https://pastebin.com/uY58Twkp
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. 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
You can 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.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post''if 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:
-
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.
-
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
Baking FAQs
draft 1.2 https://pastebin.com/uY58Twkp
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. 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
You can 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.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post''if 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:
-
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.
-
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
Baking FAQs
draft 1.2 https://pastebin.com/uY58Twkp
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. 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
You can 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.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post''if 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:
-
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.
-
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
Baking FAQs
draft 1.2 https://pastebin.com/uY58Twkp
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. 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
You can 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.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post''if 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:
-
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.
-
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
Baking FAQs
draft 1.2 https://pastebin.com/uY58Twkp
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. 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
You can 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.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post''if 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:
-
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.
-
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
Baking FAQs
draft 1.2 https://pastebin.com/uY58Twkp
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. 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
You can 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.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post''if 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:
-
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.
-
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
Baking FAQs
draft 1.2 https://pastebin.com/uY58Twkp
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. 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
You can 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.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post''if 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:
-
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.
-
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
Baking FAQs
draft 1.2 https://pastebin.com/uY58Twkp
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. 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
You can 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.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post''if 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:
-
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.
-
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
Baking FAQs
draft 1.2 https://pastebin.com/uY58Twkp
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. 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
You can 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.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post''if 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:
-
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.
-
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
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). You know you've won when shills either shut up or retreat to "Shill baker, anons check notables!" See Baker Tips for real-life examples.
* 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.
Baking FAQs
draft 1.4 https://pastebin.com/uY58Twkp (version 1.2)
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. 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
You can 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.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post''if 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:
-
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.
-
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 & Other Fast Breads
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'.
POTUS rally breads
These can be pretty speedy; bake early so anons have a place to post rally comments.
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. Screencap the evidence. Remember, revenge is a dish best served cold.
Baking FAQs
draft 1.4 https://pastebin.com/uY58Twkp (version 1.2)
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts/pages in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. 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
You can 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.
Q&A
Practice bakers can ask q's by posting in the baking seminar thread or baker's Meta thread in /comms/.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post if ghosting after posting''.
How often do you post notables?
Often enough to give anons multiple chances to have their say about notable selection, 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 or by @600 at the latest (so anons know you're still there).
Max number of breads in Previously Collected Notables?
4 - 5 lines. To make room, just delete the bottom line(s).
Timing Issues
What do I 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. Later, bakers will need to check bread title (update?), check notables page (more room needed?), and transfer notables from text editor to dough.
When to post a final notables 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.
Handoffs & 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:
-
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.
-
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 & Other Fast Breads
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 drops & LINES
Check 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'.
POTUS rally breads
These can be pretty speedy; bake early so anons have a place to post rally comments.
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. Screencap the evidence. Remember, revenge is a dish best served cold.
Baking FAQs
draft 1.4 https://pastebin.com/uY58Twkp (version 1.2)
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts/pages in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. Notables page can be broken into two pages on the fly if notable buns are long (even tho there's no BREAK marker).
Dough problems & change requests
New bakers sometimes inherit a funny-looking dough or are asked by anons to make dough changes. If you're not sure what to do, say so and defer to next baker. Often, bakers in the thread will jump in to help.
Practice Baking
You can 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.
Q&A & getting feedback
Practice bakers can ask q's by posting in the baking seminar thread or baker's Meta thread in /comms/.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post if ghosting after posting''.
How often do you post notables?
Often enough to give anons multiple chances to have their say about notable selection, 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 or by @600 at the latest (so anons know you're still there).
Max number of breads in Previously Collected Notables?
4 - 5 lines. To make room, just delete the bottom line(s).
Timing Issues
What do I 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. Later, bakers will need to check bread title (update?), check notables page (more room needed?), and transfer notables from text editor to dough.
When to post a final notables 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.
Handoffs & 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:
-
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.
-
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 & Other Fast Breads
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 drops & LINES
Check 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'.
POTUS rally breads
These can be pretty speedy; bake early so anons have a place to post rally comments.
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. Screencap the evidence. Remember, revenge is a dish best served cold.
Baking FAQs
draft 1.4 https://pastebin.com/uY58Twkp (version 1.2)
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts/pages in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. Notables page can be broken into two pages on the fly if notable buns are long (even tho there's no BREAK marker).
Dough problems & change requests
New bakers sometimes inherit a funny-looking dough or are asked by anons to make dough changes. If you're not sure what to do, say so and defer to next baker. Often, bakers in the thread will jump in to help.
Practice Baking
You can 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.
Q&A & getting feedback
Practice bakers can ask q's by posting in the baking seminar thread or baker's Meta thread in /comms/.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post if ghosting after posting''.
How often do you post notables?
Often enough to give anons multiple chances to have their say about notable selection, 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 or by @600 at the latest (so anons know you're still there).
Max number of breads in Previously Collected Notables?
4 - 5 lines. To make room, just delete the bottom line(s).
Timing Issues
What do I 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. Later, bakers will need to check bread title (update?), check notables page (more room needed?), and transfer notables from text editor to dough.
When to post a final notables 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.
Handoffs & 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:
-
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.
-
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, then check the Catalog (should post despite the message). Can be confusing for first-time bakers because this lag doesn't happen 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 & Other Fast Breads
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 drops & LINES
Check 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'.
POTUS rally breads
These can be pretty speedy; bake early so anons have a place to post rally comments.
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 bakers
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. Screencap the evidence. Remember, revenge is a dish best served cold.
Baking FAQs
Draft 1.4 https://pastebin.com/GuBCQkB8
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts/pages in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
''post 1 - Q posts, ''post 2 - Notables, ''post 3 - War Room, ''post 4 - QPosts Archives. Notables page can be broken into two pages on the fly if notable buns are long (even tho there's no BREAK marker).
Dough problems & change requests
New bakers sometimes inherit a funny-looking dough or are asked by anons to make dough changes. If you're not sure what to do, say so and defer to next baker. Often, bakers in the thread will jump in to help.
Practice Baking
You can 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.
Q&A & getting feedback
Practice bakers can ask q's by posting in the baking seminar thread or baker's Meta thread in /comms/.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post if ghosting after posting''.
How often do you post notables?
Often enough to give anons multiple chances to have their say about notable selection, 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 or by @600 at the latest (so anons know you're still there).
Max number of breads in Previously Collected Notables?
4 - 5 lines. To make room, just delete the bottom line(s).
Timing Issues
What do I 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. Later, bakers will need to check bread title (update?), check notables page (more room needed?), and transfer notables from text editor to dough.
When to post a final notables 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.
Handoffs & 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:
-
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.
-
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, then check the Catalog (should post despite the message). Can be confusing for first-time bakers because this lag doesn't happen 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 & Other Fast Breads
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 drops & LINES
Check 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'.
POTUS rally breads
These can be pretty speedy; bake early so anons have a place to post rally comments.
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 bakers
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. Screencap the evidence. Remember, revenge is a dish best served cold.
Baking FAQs
Draft 1.4 https://pastebin.com/GuBCQkB8
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts/pages in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. Notables page can be broken into two pages on the fly if notable buns are long (even tho there's no BREAK marker).
Dough problems & change requests
New bakers sometimes inherit a funny-looking dough or are asked by anons to make dough changes. If you're not sure what to do, say so and defer to next baker. Often, bakers in the thread will jump in to help.
Practice Baking
You can 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.
Q&A & getting feedback
Practice bakers can ask q's by posting in the baking seminar thread or baker's Meta thread in /comms/.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post if ghosting after posting''.
How often do you post notables?
Often enough to give anons multiple chances to have their say about notable selection, 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 or by @600 at the latest (so anons know you're still there).
Max number of breads in Previously Collected Notables?
4 - 5 lines. To make room, just delete the bottom line(s).
Timing Issues
What do I 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. Later, bakers will need to check bread title (update?), check notables page (more room needed?), and transfer notables from text editor to dough.
When to post a final notables 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.
Handoffs & 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:
-
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.
-
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, then check the Catalog (should post despite the message). Can be confusing for first-time bakers because this lag doesn't happen 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 & Other Fast Breads
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 drops & LINES
Check 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'.
POTUS rally breads
These can be pretty speedy; bake early so anons have a place to post rally comments.
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 bakers
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. Screencap the evidence. Remember, revenge is a dish best served cold.
SPACER POST
MOAR SPACE
NEXT: REVISED BAKER SEMINAR DOUGH
LIVE Baking Seminar
5/28/2020
We in here
Welcome To LIVE Baking Classes in the Q Research Utility Kitchen
We hold these truths to be self-evident: that all men are created equal; that they are endowed by their Creator with certain unalienable rights; that among these are life, liberty, and the pursuit of happiness.
We are the bakers who provide the breads for those anons who post Qresearch's open-sourced information, reasoned argument, and dank memes. We do battle in the sphere of baking ideas and baking ideas only. We neither need nor condone the use of force in our work here.
VINCIT OMNIA VERITAS
SEMPER FIDELIS
WWG1WGA
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
General Announcements
* Baking Class in /comms/ every Thursday @7pm ET: practice baking, Q&A, all are welcome
* Baking class plan (so any baker can teach) >>11969, https://pastebin.com/gqfunWCR
* How to bake a baking seminar dough >>14289
Past Class links & archives
>>6125 #1 (2/13/20), >>6368 #2 (2/20/20), >>6885 #3 (2/27/20), >>7185 #4 (3/05/20), #5 >>7568 (3/12/20), >>8274 #6 (3/19/20), >>8872 #7 (3/26/20), >>9320 #8 (4/02/20), >>9787 #9 (4/09/20), >>10510 #10 (4/16/20), #11 >>11086 (4/23/20), #12 >>11733 (4/30/20), #13 >>13041 (5/07/20), #14 13590 (5/14/20)
Archives for classes #1 - #12: >>13498
Step-by-Step Baking Instructions
>>14376 STEP 0 - Preparation
>>14383 STEP 1 - Find the Current Dough
>>14384 STEP 2 - Copy the Current Dough
>>14388 STEP 3 - Paste The Dough Into Text Editor
>>14392 STEP 3a - Trim The Notables Section
>>14400 STEP 3b - Make space for your New Notables
>>14414 STEP 4 - Create A New Thread
>>14430 STEP 5 - Enter Thread Info And Post Thread
>>14443 STEP 6 - Enter the Rest of the Dough
>>14452 STEP 7 - Make A New Pastebin & Make The Dough Post
>>14474 STEP 8 - Post Your New Thread Link
Overview & Extras
>>14493 Linking between Boards
>>14513 Timing
>>14523 Baker's Tools Lite
>>11922 Archiving & Teaching Files (screenshot; almost current)
E-BAKE Instructions
NEW! Dough Revision
Page 1 - Baking Seminar Intro & Step-by-Step Baking Instructions
Page 2 - Baking FAQs [derived from old pages 2 & 3, see below]
Page 3 - Baking Resources
Old pages 2 & 3 can be found HERE:
>>14291 Q & A - Baking Seminars #1 - #14
>>14293 Baker Tips, Tricks & Traps''' #1 - #14
Baking FAQs
Draft 1.4 https://pastebin.com/GuBCQkB8
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts/pages in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. Notables page can be broken into two pages on the fly if notable buns are long (even tho there's no BREAK marker).
Dough problems & change requests
New bakers sometimes inherit a funny-looking dough or are asked by anons to make dough changes. If you're not sure what to do, say so and defer to next baker. Often, bakers in the thread will jump in to help.
Practice Baking
You can 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.
Q&A & getting feedback
Practice bakers can ask q's by posting in the baking seminar thread or baker's Meta thread in /comms/.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post if ghosting after posting''.
How often do you post notables?
Often enough to give anons multiple chances to have their say about notable selection, 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 or by @600 at the latest (so anons know you're still there).
Max number of breads in Previously Collected Notables?
4 - 5 lines. To make room, just delete the bottom line(s).
Timing Issues
What do I 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. Later, bakers will need to check bread title (update?), check notables page (more room needed?), and transfer notables from text editor to dough.
When to post a final notables 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.
Handoffs & 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:
-
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.
-
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, then check the Catalog (should post despite the message). Can be confusing for first-time bakers because this lag doesn't happen 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 & Other Fast Breads
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 drops & LINES
Check 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'.
POTUS rally breads
These can be pretty speedy; bake early so anons have a place to post rally comments.
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 bakers
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. Screencap the evidence. Remember, revenge is a dish best served cold.
INTRO TO BAKING
Qresearch is a 24/7 beehive of activity where anons post their diggs, memes and prayers.
For this to happen requires ''bakers''--which is why they have been called "the core of this board."
Bakers perform several key functions:
* Set the tone for each bread via their choice of bread title and /comms/ with posters.
* Post notables for each bread.
* Bake breads (transition the board from one thread to the next).
* Knead the dough (keeping the resource pages clean, tidy, and up-to-date).
When all goes well, baking is a fun & exciting opportunity to serve. When things get wonky and shills attack--bakers carry on anyway.
Shadilay, fellow bakers!
OTHER BAKING RESOURCES
Baker's grab bag
* Baker's Tools App (Version 0.7.2) >>6646, >>6650, >>6652, >>6654, >>6656, >>9584, >>9589, >>9597, >>9601
* Try Atom as a text editor for Macs >>6925, >>6934, >>7055, >>7070
* Meme-making app kek.gg >>8771
* Crazy Bakes: wonky board, lags, baking from Index, "flood detected", dup breads >>9960
* How's your mouse for baking? >>10617
* Font used for baking school slides: >>10642, https://www.dafontfree.net/find.php?q=impact
* Quik Pic bake instructions >>7549
* Original baking video >>7076 (shows how to make room for new notables)
* Overcoming paywalls >>10844
* Pastebin.com problems & alternatives >>11645, >>11609, >>11619, >>11620, >>11627, >>11640
* How to Control-F on androids & IOS devices >>13566, >>13567
* How to do a keyword search when /qresearch/ is down >>13696
Dealing with notables
* Ten Baker Tips for Notables >>8177
* Ways to deal with long notables lists >>13633
* Asking anons to state the main point >>8237
* Anon tips for better notables (bakers can tell anons) >>>/qrb/41937, https://pastebin.com/yq7wQyvn
* Bakers on what they look for in notables >>8351, >>8315, >>8698
* Muh Collector "how to" on notables >>9006, >>9009
* Advanced Google searching protocols https://pastebin.com/raw/JuK0xUDb
* How to read a scientific study >>9036833
Free image/video screenshots, download, production tools
* Image screenshots PrtSc/snipping tool + MS-Paint https://youtu.be/KvXxCE1gxOE
* 8kun video limits (~16mg) >>8760
* Bandicam Screen Recorder >>8759, >>8762 (also: OBS, Kdenlive, Audacity)
* YouTube & Twitter (downloads plus cutting scenes from YT) >>14306
'''* Video downloaders: >>14237, https://www.downloadhelper.net/;
Firefox/Opera: https://technologyto.com/extractor.html
* VLC Player >>8714, >>8715, >>8766
* Windows Movie Maker for Win 10 >>8712
* NVidia cards (can screen-capture vids) >>8785
* Forensically (forensics magnifier) https://29a.ch/photo-forensics/#forensic-magnifier
* ShotCut NLE (open source cross platform video editor) https://shotcut.org/
* MFFmpeg (decodes & plays any format) https://ffmpeg.org/
* Natron (cross-platform video compositor) https://natrongithub.github.io/
* Handbrake (good for transcoding) https://handbrake.fr/
* GIMP & GMIC (image editing) http://gmic.eu/gimp.shtml
* Invidio (copies YT vids, restricted or not, no ads or signup) >>8792
Baker tips IRL
>>8829 Baker's Tips - Read me first
>>6331 #01 - Ghosting a bred
>>6331 #02 - Baker changes
>>6378 #03 - TOR baking
>>6651 #04 - Defeating shills with facts & humor
>>7339 #05 - Announce you're baking (#11 too)
>>6892 #06 - Baking/note-taking protocols
>>7181 #07 - Use RED TEXT and BOLD in handoffs
>>7363 #08 - Try to notice when a cat is baking
>>13038 #09 - Respecting other bakers' notables
>>8174 #10 - Make sure to copypasta the whole page
>>8803 #11 - Announce you're taking responsibility
>>8822 #12 - Embed baker changes to provide more info
>>8824 #13 - Watch out for unknown bakers bearing gifts
>>8825 #14 - Use named pastebins to defeat shill complaints
>>8826 #15 - Responding to shills trying to suck up baker's time
>>8827 #16 - Be aware of muh joos bakers
>>8828 #17 - All bakers screw up
>>10445 #18 - Just do it--bake!
>>9590 #19 - Don't be afraid to bake
>>10789 #20 - Post notes early so changes can be made
>>10791 #21 - No /comms/ creates misunderstandings
>>10792 #22 - Defeat shills with humor
>>14835 #23 - Keep notables [from different bakers] separate
>>14836 #24 - Make sure to ask for Handoff Confirmed
>>14801 #25 - Don't Fuck with the Wrong Baker [ftake a look - funny]
Baker stories & discussions
>>10114 How shills attack bakers--an example ("baker saves notables for his twats")
>>10787 LIVE example of picking up a mid-bread bake
>>10710 Why do you bake? >>10729, >>10731, >>10732, >>10744
>>14837 Forensic baking (Study: who's been messing with the dough??)
>>14114 Editing PB Notables, ok or not? Baker discussion >>14227, >>14248, >>14265
''this dough will change as we collect new resources & refine what's here''
SPACER
LIVE Baking Seminar
5/28/2020
We in here
Welcome To LIVE Baking Classes in the Q Research Utility Kitchen
We hold these truths to be self-evident: that all men are created equal; that they are endowed by their Creator with certain unalienable rights; that among these are life, liberty, and the pursuit of happiness.
We are the bakers who provide the breads for those anons who post Qresearch's open-sourced information, reasoned argument, and dank memes. We do battle in the sphere of baking ideas and baking ideas only. We neither need nor condone the use of force in our work here.
VINCIT OMNIA VERITAS
SEMPER FIDELIS
WWG1WGA
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
General Announcements
* Baking Class in /comms/ every Thursday @7pm ET: practice baking, Q&A, all are welcome
* Baking class plan (so any baker can teach) >>11969, https://pastebin.com/gqfunWCR
* How to bake a baking seminar dough >>14289
* NEW! Dough Revision (see below)
Past Class links & archives
>>6125 #1 (2/13/20), >>6368 #2 (2/20/20), >>6885 #3 (2/27/20), >>7185 #4 (3/05/20), #5 >>7568 (3/12/20), >>8274 #6 (3/19/20), >>8872 #7 (3/26/20), >>9320 #8 (4/02/20), >>9787 #9 (4/09/20), >>10510 #10 (4/16/20), #11 >>11086 (4/23/20), #12 >>11733 (4/30/20), #13 >>13041 (5/07/20), #14 13590 (5/14/20)
Archives for classes #1 - #12: >>13498
Step-by-Step Baking Instructions
>>14376 STEP 0 - Preparation
>>14383 STEP 1 - Find the Current Dough
>>14384 STEP 2 - Copy the Current Dough
>>14388 STEP 3 - Paste The Dough Into Text Editor
>>14392 STEP 3a - Trim The Notables Section
>>14400 STEP 3b - Make space for your New Notables
>>14414 STEP 4 - Create A New Thread
>>14430 STEP 5 - Enter Thread Info And Post Thread
>>14443 STEP 6 - Enter the Rest of the Dough
>>14452 STEP 7 - Make A New Pastebin & Make The Dough Post
>>14474 STEP 8 - Post Your New Thread Link
Overview & Extras
>>14493 Linking between Boards
>>14513 Timing
>>14523 Baker's Tools Lite
>>11922 Archiving & Teaching Files (screenshot; almost current)
E-BAKE Instructions
Dough Revision
Page 1 - Baking Seminar Intro & Step-by-Step Baking Instructions
Page 2 - Baking Resources
Page 3 - Baking FAQs [derived from old pages 2 & 3, see below]
Old pages 2 & 3 can be found HERE:
>>14291 Q & A - Baking Seminars #1 - #14
>>14293 Baker Tips, Tricks & Traps''' #1 - #14
INTRO TO BAKING
Qresearch is a 24/7 beehive of activity where anons post their diggs, memes and prayers.
For this to happen requires ''bakers''--which is why they have been called "the core of this board."
Bakers perform several key functions:
* Set the tone for each bread via their choice of bread title and /comms/ with posters.
* Post notables for each bread.
* Bake breads (transition the board from one thread to the next).
* Knead the dough (keeping the resource pages clean, tidy, and up-to-date).
When all goes well, baking is a fun & exciting opportunity to serve. When things get wonky and shills attack--bakers carry on anyway.
Shadilay, fellow bakers!
OTHER BAKING RESOURCES
Baker's grab bag
* Baker's Tools App (Version 0.7.2) >>6646, >>6650, >>6652, >>6654, >>6656, >>9584, >>9589, >>9597, >>9601
* Try Atom as a text editor for Macs >>6925, >>6934, >>7055, >>7070
* Meme-making app kek.gg >>8771
* Crazy Bakes: wonky board, lags, baking from Index, "flood detected", dup breads >>9960
* How's your mouse for baking? >>10617
* Font used for baking school slides: >>10642, https://www.dafontfree.net/find.php?q=impact
* Quik Pic bake instructions >>7549
* Original baking video >>7076 (shows how to make room for new notables)
* Overcoming paywalls >>10844
* Pastebin.com problems & alternatives >>11645, >>11609, >>11619, >>11620, >>11627, >>11640
* How to Control-F on androids & IOS devices >>13566, >>13567
* How to do a keyword search when /qresearch/ is down >>13696
Dealing with notables
* Ten Baker Tips for Notables >>8177
* Ways to deal with long notables lists >>13633
* Asking anons to state the main point >>8237
* Anon tips for better notables (bakers can tell anons) >>>/qrb/41937, https://pastebin.com/yq7wQyvn
* Bakers on what they look for in notables >>8351, >>8315, >>8698
* Muh Collector "how to" on notables >>9006, >>9009
* Advanced Google searching protocols https://pastebin.com/raw/JuK0xUDb
* How to read a scientific study >>9036833
Free image/video screenshots, download, production tools
* Image screenshots PrtSc/snipping tool + MS-Paint https://youtu.be/KvXxCE1gxOE
* 8kun video limits (~16mg) >>8760
* Bandicam Screen Recorder >>8759, >>8762 (also: OBS, Kdenlive, Audacity)
* YouTube & Twitter (downloads plus cutting scenes from YT) >>14306
* Video downloaders: >>14237, https://www.downloadhelper.net/ ; Firefox/Opera: - https://technologyto.com/extractor.html
* VLC Player >>8714, >>8715, >>8766
* Windows Movie Maker for Win 10 >>8712
* NVidia cards (can screen-capture vids) >>8785
* Forensically (forensics magnifier) https://29a.ch/photo-forensics/#forensic-magnifier
* ShotCut NLE (open source cross platform video editor) https://shotcut.org/
* MFFmpeg (decodes & plays any format) https://ffmpeg.org/
* Natron (cross-platform video compositor) https://natrongithub.github.io/
* Handbrake (good for transcoding) https://handbrake.fr/
* GIMP & GMIC (image editing) http://gmic.eu/gimp.shtml
* Invidio (copies YT vids, restricted or not, no ads or signup) >>8792
Baker tips IRL
>>8829 Baker's Tips - Read me first
>>6331 #01 - Ghosting a bred
>>6331 #02 - Baker changes
>>6378 #03 - TOR baking
>>6651 #04 - Defeating shills with facts & humor
>>7339 #05 - Announce you're baking (#11 too)
>>6892 #06 - Baking/note-taking protocols
>>7181 #07 - Use RED TEXT and BOLD in handoffs
>>7363 #08 - Try to notice when a cat is baking
>>13038 #09 - Respecting other bakers' notables
>>8174 #10 - Make sure to copypasta the whole page
>>8803 #11 - Announce you're taking responsibility
>>8822 #12 - Embed baker changes to provide more info
>>8824 #13 - Watch out for unknown bakers bearing gifts
>>8825 #14 - Use named pastebins to defeat shill complaints
>>8826 #15 - Responding to shills trying to suck up baker's time
>>8827 #16 - Be aware of muh joos bakers
>>8828 #17 - All bakers screw up
>>10445 #18 - Just do it--bake!
>>9590 #19 - Don't be afraid to bake
>>10789 #20 - Post notes early so changes can be made
>>10791 #21 - No /comms/ creates misunderstandings
>>10792 #22 - Defeat shills with humor
>>14835 #23 - Keep notables [from different bakers] separate
>>14836 #24 - Make sure to ask for Handoff Confirmed
>>14801 #25 - Don't Fuck with the Wrong Baker [ftake a look - funny]
Baker stories & discussions
>>10114 How shills attack bakers--an example ("baker saves notables for his twats")
>>10787 LIVE example of picking up a mid-bread bake
>>10710 Why do you bake? >>10729, >>10731, >>10732, >>10744
>>14837 Forensic baking (Study: who's been messing with the dough??)
>>14114 Editing PB Notables, ok or not? Baker discussion >>14227, >>14248, >>14265
Baking FAQs
Draft 1.4 https://pastebin.com/GuBCQkB8
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link.
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts/pages in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. Notables page can be broken into two pages on the fly if notable buns are long (even tho there's no BREAK marker).
Dough problems & change requests
New bakers sometimes inherit a funny-looking dough or are asked by anons to make dough changes. If you're not sure what to do, say so and defer to next baker. Often, bakers in the thread will jump in to help.
Practice Baking
You can 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.
Q&A & getting feedback
Practice bakers can ask q's by posting in the baking seminar thread or baker's Meta thread in /comms/.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post if ghosting after posting''.
How often do you post notables?
Often enough to give anons multiple chances to have their say about notable selection, 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 or by @600 at the latest (so anons know you're still there).
Max number of breads in Previously Collected Notables?
4 - 5 lines. To make room, just delete the bottom line(s).
Timing Issues
What do I 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. Later, bakers will need to check bread title (update?), check notables page (more room needed?), and transfer notables from text editor to dough.
When to post a final notables 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.
Handoffs & 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:
-
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.
-
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, then check the Catalog (should post despite the message). Can be confusing for first-time bakers because this lag doesn't happen 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 & Other Fast Breads
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 drops & LINES
Check 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'.
POTUS rally breads
These can be pretty speedy; bake early so anons have a place to post rally comments.
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 bakers
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. Screencap the evidence. Remember, revenge is a dish best served cold.
baking seminar dough:
https://pastebin.com/vUZnbw7e
>>>/qresearch/9036833
Baking FAQs
Version 1.5
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link. Link to Class #15: 14290
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts/pages in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives.
Notables page can be broken into two pages on the fly if notable buns are long (even tho there's no BREAK marker).
Dough problems & change requests
New bakers sometimes inherit a funny-looking dough or are asked by anons to make dough changes.
If you're not sure what to do, say so and defer to next baker. Often, bakers in the thread will jump in to help.
Practice Baking
You can 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.
Q&A & getting feedback
Practice bakers can ask q's by posting in the baking seminar thread or baker's Meta thread in /comms/.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post if ghosting after posting''.
How often do you post notables?
Often enough to give anons multiple chances to have their say about notable selection, 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 or by @600 at the latest (so anons know you're still there).
Max number of breads in Previously Collected Notables?
4 - 5 lines. To make room, just delete the bottom line(s).
Timing Issues
What do I 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. Later, bakers will need to check bread title (update?), check notables page (more room needed?), and transfer notables from text editor to dough.
When to post a final notables 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.
Handoffs & 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:
-
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.
-
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;
the 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, then check the Catalog (should post despite the message).
Can be confusing for first-time bakers because this lag doesn't happen in /comms/.
SEE ALSO Crazy bakes >>9960
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 & Other Fast Breads
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 drops & LINES
Check 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'.
POTUS rally breads
These can be pretty speedy; bake early so anons have a place to post rally comments.
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.
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 bakers
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.
Screencap the evidence. Remember, revenge is a dish best served cold.
Baking FAQs
Version 1.5
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link. Link to Class #15: 14290
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts/pages in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives.
Notables page can be broken into two pages on the fly if notable buns are long (even tho there's no BREAK marker).
Dough problems & change requests
New bakers sometimes inherit a funny-looking dough or are asked by anons to make dough changes.
If you're not sure what to do, say so and defer to next baker. Often, bakers in the thread will jump in to help.
Practice Baking
You can 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.
Q&A & getting feedback
Practice bakers can ask q's by posting in the baking seminar thread or baker's Meta thread in /comms/.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post if ghosting after posting''.
How often do you post notables?
Often enough to give anons multiple chances to have their say about notable selection, 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 or by @600 at the latest (so anons know you're still there).
Max number of breads in Previously Collected Notables?
4 - 5 lines. To make room, just delete the bottom line(s).
Timing Issues
What do I 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.
Later, bakers will need to check bread title (update?), check notables page (more room needed?), and transfer notables from text editor to dough.
When to post a final notables 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.
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.
Handoffs & 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:
-
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.
-
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;
the 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, then check the Catalog (should post despite the message).
Can be confusing for first-time bakers because this lag doesn't happen in /comms/.
SEE ALSO Crazy bakes >>9960
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 & Other Fast Breads
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 drops & LINES
Check 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'.
POTUS rally breads
These can be pretty speedy; bake early so anons have a place to post rally comments.
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.
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 bakers
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.
Screencap the evidence. Remember, revenge is a dish best served cold.
Baking FAQs
Version 1.5
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link. Link to Class #15: 14290
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts/pages in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives.
Notables page can be broken into two pages on the fly if notable buns are long (even tho there's no BREAK marker).
Dough problems & change requests
New bakers sometimes inherit a funny-looking dough or are asked by anons to make dough changes.
If you're not sure what to do, say so and defer to next baker. Often, bakers in the thread will jump in to help.
Practice Baking
You can 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.
Q&A & getting feedback
Practice bakers can ask q's by posting in the baking seminar thread or baker's Meta thread in /comms/.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post if ghosting after posting''.
How often do you post notables?
Often enough to give anons multiple chances to have their say about notable selection, 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 or by @600 at the latest (so anons know you're still there).
Max number of breads in Previously Collected Notables?
4 - 5 lines. To make room, just delete the bottom line(s).
Timing Issues
What do I 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.
Later, bakers will need to check bread title (update?), check notables page (more room needed?), and transfer notables from text editor to dough.
When to post a final notables 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.
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.
Handoffs & 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:
-
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.
-
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;
the 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, then check the Catalog (should post despite the message).
Can be confusing for first-time bakers because this lag doesn't happen in /comms/.
SEE ALSO Crazy bakes >>9960
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 & Other Fast Breads
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 drops & LINES
Check 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'.
POTUS rally breads
These can be pretty speedy; bake early so anons have a place to post rally comments.
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.
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 bakers
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 powerful and meticulously documented, fact-based counterattack.
Screencap the evidence. Remember, revenge is a dish best served cold.
Baking FAQs
Version 1.5
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link. Link to Class #15: 14290
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts/pages in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives.
Notables page can be broken into two pages on the fly if notable buns are long (even tho there's no BREAK marker).
Dough problems & change requests
New bakers sometimes inherit a funny-looking dough or are asked by anons to make dough changes.
If you're not sure what to do, say so and defer to next baker. Often, bakers in the thread will jump in to help.
Practice Baking
You can 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.
Q&A & getting feedback
Practice bakers can ask q's by posting in the baking seminar thread or baker's Meta thread in /comms/.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post if ghosting after posting''.
How often do you post notables?
Often enough to give anons multiple chances to have their say about notable selection, 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 or by @600 at the latest (so anons know you're still there).
Max number of breads in Previously Collected Notables?
4 - 5 lines. To make room, just delete the bottom line(s).
Timing Issues
What do I 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.
Later, bakers will need to check bread title (update?), check notables page (more room needed?), and transfer notables from text editor to dough.
When to post a final notables 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.
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.
Handoffs & 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:
-
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.
-
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;
the 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, then check the Catalog (should post despite the message).
Can be confusing for first-time bakers because this lag doesn't happen in /comms/.
SEE ALSO Crazy bakes >>9960
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 & Other Fast Breads
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 drops & LINES
Check 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'.
POTUS rally breads
These can be pretty speedy; bake early so anons have a place to post rally comments.
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.
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 bakers
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 powerful and meticulously documented,
fact-based counterattack. Screencap the evidence. Remember, revenge is a dish best served cold.
Step-by-Step Baking Instructions
>>15495 STEP 0 - Preparation
>>15505 STEP 1 - Find the Current Dough
>>15513 STEP 2 - Copy the Current Dough
>>15520 STEP 3 - Paste The Dough Into Text Editor
>>15523 STEP 3a - Trim The Notables Section
>>15530 STEP 3b - Make space for your New Notables
>>15535 STEP 4' - Create A New Thread
>>15542 STEP 5 - Enter Thread Info And Post Thread
>>15560 STEP 6 - Enter the Rest of the Dough
>>15564 STEP 7 - Make A New Pastebin & Make The Dough Post
>>15586 STEP 8 - Post Your New Thread Link
Overview & Extras
>>15626 Linking between Boards
>>15638 Timing
>>14523 Baker's Tools Lite
>>11922 Archiving & Teaching Files (screenshot; almost current)
LIVE Baking Seminar
6/4/2020
We in here
Welcome To LIVE Baking Classes in the Q Research Utility Kitchen
We hold these truths to be self-evident: that all men are created equal; that they are endowed by their Creator with certain unalienable rights; that among these are life, liberty, and the pursuit of happiness.
We are the bakers who provide the breads for those anons who post Qresearch's open-sourced information, reasoned argument, and dank memes. We do battle in the sphere of baking ideas and baking ideas only. We neither need nor condone the use of force in our work here.
VINCIT OMNIA VERITAS
SEMPER FIDELIS
WWG1WGA
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
General Announcements
* Baking Class in /comms/ every Thursday @7pm ET: practice baking, Q&A, all are welcome
* Baking class plan (so any baker can teach) >>11969, https://pastebin.com/gqfunWCR
* How to bake a baking seminar dough >>14289
'''* Too many threads problem - bakers be(a)ware >>15895
Past Class links & archives
>>6125 #1, >>6368 #2, >>6885 #3, >>7185 #4 , >>7568 #5, >>8274 #6, >>8872 #7, >>9320 #8, >>9787 #9, >>10510 #10, >>11086 #11, #12 >>11733, #13 >>13041, #14 >>13590, #15 >>14290, #16 >>14873
Archives for classes #1 - #14: >>14866
Step-by-Step Baking Instructions
>>15495 STEP 0 - Preparation
>>15505 STEP 1 - Find the Current Dough
>>15513 STEP 2 - Copy the Current Dough
>>15520 STEP 3 - Paste The Dough Into Text Editor
>>15523 STEP 3a - Trim The Notables Section
>>15530 STEP 3b - Make space for your New Notables
>>15535 STEP 4 - Create A New Thread
>>15542 STEP 5 - Enter Thread Info And Post Thread
>>15560 STEP 6 - Enter the Rest of the Dough
>>15564 STEP 7 - Make A New Pastebin & Make The Dough Post
>>15586 STEP 8 - Post Your New Thread Link
Overview & Extras
>>15626 Linking between Boards
>>15638 Timing
>>14523 Baker's Tools Lite
E-BAKE Instructions
Dough Revision
Page 1 - Baking Seminar Intro & Step-by-Step Baking Instructions
Page 2 - Baking Resources
Page 3 - Baking FAQs [derived from old pages 2 & 3, see below]
[Note: each page may require more than one post]
Old pages 2 & 3 can be found HERE:
>>14291 Q & A - Baking Seminars #1 - #14
>>14293 Baker Tips, Tricks & Traps''' #1 - #14
INTRO TO BAKING
Qresearch is a 24/7 beehive of activity where anons post their diggs, memes and prayers.
For this to happen requires ''bakers''βwhich is why they have been called "the core of this board."
Bakers perform several key functions:
* Set the tone for each bread via their choice of bread title and /comms/ with posters.
* Post notables for each bread.
* Bake breads (transition the board from one thread to the next).
* Knead the dough (keeping the resource pages clean, tidy, and up-to-date).
When all goes well, baking is a fun & exciting opportunity to serve. When things get wonky and shills attackβbakers carry on anyway.
Shadilay, fellow bakers!
LIVE Baking Seminar
6/4/2020
We in here
Welcome To LIVE Baking Classes in the Q Research Utility Kitchen
We hold these truths to be self-evident: that all men are created equal; that they are endowed by their Creator with certain unalienable rights; that among these are life, liberty, and the pursuit of happiness.
We are the bakers who provide the breads for those anons who post Qresearch's open-sourced information, reasoned argument, and dank memes. We do battle in the sphere of baking ideas and baking ideas only. We neither need nor condone the use of force in our work here.
VINCIT OMNIA VERITAS
SEMPER FIDELIS
WWG1WGA
INTRO TO BAKING
Qresearch is a 24/7 beehive of activity where anons post their diggs, memes and prayers.
For this to happen requires ''bakers''βwhich is why they have been called "the core of this board."
Bakers perform several key functions:
* Set the tone for each bread via their choice of bread title and /comms/ with posters.
* Post notables for each bread.
* Bake breads (transition the board from one thread to the next).
* Knead the dough (keeping the resource pages clean, tidy, and up-to-date).
When all goes well, baking is a fun & exciting opportunity to serve. When things get wonky and shills attackβbakers carry on anyway.
Shadilay, fellow bakers!
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
General Announcements
* Baking Class in /comms/ every Thursday @7pm ET: practice baking, Q&A, all are welcome
* Baking class plan (so any baker can teach) >>11969, https://pastebin.com/gqfunWCR
* How to bake a baking seminar dough >>14289
'''* Too many threads problem - bakers be(a)ware >>15895
Past Class links & archives
>>6125 #1, >>6368 #2, >>6885 #3, >>7185 #4 , >>7568 #5, >>8274 #6, >>8872 #7, >>9320 #8, >>9787 #9, >>10510 #10, >>11086 #11, #12 >>11733, #13 >>13041, #14 >>13590, #15 >>14290, #16 >>14873
Archives for classes #1 - #14: >>14866
Step-by-Step Baking Instructions
>>15495 STEP 0 - Preparation
>>15505 STEP 1 - Find the Current Dough
>>15513 STEP 2 - Copy the Current Dough
>>15520 STEP 3 - Paste The Dough Into Text Editor
>>15523 STEP 3a - Trim The Notables Section
>>15530 STEP 3b - Make space for your New Notables
>>15535 STEP 4 - Create A New Thread
>>15542 STEP 5 - Enter Thread Info And Post Thread
>>15560 STEP 6 - Enter the Rest of the Dough
>>15564 STEP 7 - Make A New Pastebin & Make The Dough Post
>>15586 STEP 8 - Post Your New Thread Link
Overview & Extras
>>15626 Linking between Boards
>>15638 Timing
>>14523 Baker's Tools Lite
E-BAKE Instructions
Dough Revision
Page 1 - Baking Seminar Intro & Step-by-Step Baking Instructions
Page 2 - Baking Resources
Page 3 - Baking FAQs [derived from old pages 2 & 3, see below]
[Note: each page may require more than one post]
Old pages 2 & 3 can be found HERE:
>>14291 Q & A - Baking Seminars #1 - #14
>>14293 Baker Tips, Tricks & Traps''' #1 - #14
LIVE Baking Seminar
6/11/2020
We in here
Welcome To LIVE Baking Classes in the Q Research Utility Kitchen
We hold these truths to be self-evident: that all men are created equal; that they are endowed by their Creator with certain unalienable rights; that among these are life, liberty, and the pursuit of happiness.
We are the bakers who provide the breads for those anons who post Qresearch's open-sourced information, reasoned argument, and dank memes. We do battle in the sphere of baking ideas and baking ideas only. We neither need nor condone the use of force in our work here.
VINCIT OMNIA VERITAS
SEMPER FIDELIS
WWG1WGA
INTRO TO BAKING
Qresearch is a 24/7 beehive of activity where anons post their diggs, memes and prayers.
For this to happen requires ''bakers''βwhich is why they have been called "the core of this board."
Bakers perform several key functions:
* Set the tone for each bread via their choice of bread title and /comms/ with posters.
* Post notables for each bread.
* Bake breads (transition the board from one thread to the next).
* Knead the dough (keeping the resource pages clean, tidy, and up-to-date).
When all goes well, baking is a fun & exciting opportunity to serve. When things get wonky and shills attackβbakers carry on anyway.
Shadilay, fellow bakers!
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
General Announcements
* Baking Class in /comms/ every Thursday @7pm ET: practice baking, Q&A, all are welcome
* Baking class plan (so any baker can teach) >>11969, https://pastebin.com/gqfunWCR
* How to bake a baking seminar dough >>14289
'''* Too many threads problem - bakers be(a)ware >>15895
Past Class links & archives
>>6125 #1, >>6368 #2, >>6885 #3, >>7185 #4 , >>7568 #5, >>8274 #6, >>8872 #7, >>9320 #8, >>9787 #9, >>10510 #10, >>11086 #11, #12 >>11733, #13 >>13041, #14 >>13590, #15 >>14290, #16 >>14873
Archives for classes #1 - #14: >>14866
Step-by-Step Baking Instructions
>>15495 STEP 0 - Preparation
>>15505 STEP 1 - Find the Current Dough
>>15513 STEP 2 - Copy the Current Dough
>>15520 STEP 3 - Paste The Dough Into Text Editor
>>15523 STEP 3a - Trim The Notables Section
>>15530 STEP 3b - Make space for your New Notables
>>15535 STEP 4 - Create A New Thread
>>15542 STEP 5 - Enter Thread Info And Post Thread
>>15560 STEP 6 - Enter the Rest of the Dough
>>15564 STEP 7 - Make A New Pastebin & Make The Dough Post
>>15586 STEP 8 - Post Your New Thread Link
Overview & Extras
>>15626 Linking between Boards
>>15638 Timing
>>14523 Baker's Tools Lite
E-BAKE Instructions
Dough Revision
Page 1 - Baking Seminar Intro & Step-by-Step Baking Instructions
Page 2 - Baking Resources
Page 3 - Baking FAQs [derived from old pages 2 & 3, see below]
[Note: each page may require more than one post]
Old pages 2 & 3 can be found HERE:
>>14291 Q & A - Baking Seminars #1 - #14
>>14293 Baker Tips, Tricks & Traps''' #1 - #14
BAKING RESOURCES
Baker's grab bag
* Baker's Tools app (Version 0.7.2) Baker Tools v0.7.2: >>9584, >>9597, >>9601 https://pastebin.com/L1p6iRzZ
* Baker's Tools Lite (stripped down, good for baking) >>14523, https://pastebin.com/pUVCTeCG
* Try Atom as a text editor for Macs >>6925, >>6934, >>7055, >>7070
* Meme-making app kek.gg >>8771
* Crazy Bakes: wonky board, lags, baking from Index, "flood detected", dup breads >>9960
* How's your mouse for baking? >>10617
* Font used for baking school slides >>10642, https://www.dafontfree.net/find.php?q=impact
* Quik Pic bake instructions >>7549
* Original baking video >>7076 (shows how to make room for new notables)
* Overcoming paywalls >>10844
* Pastebin.com problems & alternatives >>11645, >>11609, >>11619, >>11620, >>11627, >>11640
* How to Control-F on androids & IOS devices >>13566, >>13567
* How to do a keyword search when /qresearch/ is down >>13696
Dealing with notables
* Note-taking roles: baker, note collector, helper anon, posters >>14921
* Ten Baker Tips for Notables >>8177
* Bakers on what they look for in notables >>8351, >>8315, >>8698
* Muh Collector "how to" on notables >>9006, >>9009
* Anon tips for better notables >>>/qrb/41937, https://pastebin.com/yq7wQyvn
* Long notables; Asking anons to state main point >>13633, >>8237
* Asking anons to state the main point
* Advanced Google searching protocols https://pastebin.com/raw/JuK0xUDb
Free image/video screenshots, download, production tools
* Image screenshots PrtSc/snipping tool + MS-Paint https://youtu.be/KvXxCE1gxOE
* 8kun video limits (~16mg) >>8760
* Bandicam Screen Recorder >>8759, >>8762 (also: OBS, Kdenlive, Audacity)
* YouTube & Twitter (downloads plus cutting scenes from YT) >>14306
* Video downloaders: >>14237, https://www.downloadhelper.net/ ; Firefox/Opera: - https://technologyto.com/extractor.html
* VLC Player >>8714, >>8715, >>8766
* Windows Movie Maker for Win 10 >>8712
* NVidia cards (can screen-capture vids) >>8785
* Forensically (forensics magnifier) https://29a.ch/photo-forensics/#forensic-magnifier
* ShotCut NLE (open source cross platform video editor) https://shotcut.org/
* MFFmpeg (decodes & plays any format) https://ffmpeg.org/
* Natron (cross-platform video compositor) https://natrongithub.github.io/
* Handbrake (good for transcoding) https://handbrake.fr/
* GIMP & GMIC (image editing) http://gmic.eu/gimp.shtml
* Invidio (copies YT vids, restricted or not, no ads or signup) >>8792
Baker tips IRL
>>8829 Baker's Tips - Read me first
>>6331 #01 - Ghosting a bred
>>6331 #02 - Baker changes
>>6378 #03 - TOR baking
>>6651 #04 - Defeating shills with facts & humor
>>7339 #05 - Announce you're baking (#11 too)
>>6892 #06 - Baking/note-taking protocols
>>7181 #07 - Use RED TEXT and BOLD in handoffs
>>7363 #08 - Try to notice when a cat is baking
>>13038 #09 - Respecting other bakers' notables
>>8174 #10 - Make sure to copypasta the whole page
>>8803 #11 - Announce you're taking responsibility
>>8822 #12 - Embed baker changes to provide more info
>>8824 #13 - Watch out for unknown bakers bearing gifts
>>8825 #14 - Use named pastebins to defeat shill complaints
>>8826 #15 - Responding to shills trying to suck up baker's time
>>8827 #16 - Be aware of muh joos bakers
>>8828 #17 - All bakers screw up
>>10445 #18 - Just do it--bake!
>>9590 #19 - Don't be afraid to bake
>>10789 #20 - Post notes early so changes can be made
>>10791 #21 - No /comms/ creates misunderstandings
>>10792 #22 - Defeat shills with humor
>>14835 #23 - Keep notables [from different bakers] separate
>>14836 #24 - Make sure to ask for Handoff Confirmed
>>14801 #25 - Don't fuck with the wrong baker [take a look - funny]
>>15894 #26 - Ignore End-of-Bread Antics
Baker stories & discussions
>>10114 How shills attack bakers--an example ("baker saves notables for his twats")
>>10787 LIVE example of picking up a mid-bread bake
>>10710 Why do you bake? >>10729, >>10731, >>10732, >>10744
>>14837 Forensic baking (Study: who's been messing with the dough??)
>>14114 Editing PB notables, ok or not? Baker discussion >>14227, >>14248, >>14265
>>14943 What notables draw your interest and why, baker? >>14947, >>14968 >>14975 >>14983
>>15908 HOW-TO Notables (Class #16) w/baker comments
Baking FAQs
Version 1.5
For step-by-step baking instructions, see page one of current baking seminar dough; baking section of /qresearch/ dough will also have a link. Link to Class #15: 14290
TWO MOST IMPORTANT FAQs:
-
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.
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 4-5 posts/pages in each bread. Each post in one document separated by /////BREAK\\\ markers.
Organization
post 1 - Q posts, post 2 - Notables, post 3 - War Room, post 4 - QPosts Archives. Notables page can be broken into two pages on the fly if notable buns are long (even tho there's no BREAK marker).
Dough problems & change requests
New bakers sometimes inherit a funny-looking dough or are asked by anons to make dough changes. If you're not sure what to do, say so and defer to next baker. Often, bakers in the thread will jump in to help.
Practice Baking
You can 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.
Q&A & getting feedback
Practice bakers can ask q's by posting in the baking seminar thread or baker's Meta thread in /comms/.
Pastebin.com
What is pastebin.com?
An app/site that stores the dough so bakers can transfer it to next baker.
Do I need an account to use pastebin.com?
No, anyone can use it as a GUEST. You can also (optionally) add a pastebin name to identify your acct to anons.
How to make a new pastebin
Copy entire dough from text editor, upload to pastebin.com, select New Paste, paste in dough, select Create New Paste at bottom. See step-by-step instructions for more.
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 post if ghosting after posting''.
How often do you post notables?
Often enough to give anons multiple chances to have their say about notable selection, 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 or by @600 at the latest (so anons know you're still there).
Max number of breads in Previously Collected Notables?
4 - 5 lines. To make room, just delete the bottom line(s).
Timing Issues
What do I 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. Later, bakers will need to check bread title (update?), check notables page (more room needed?), and transfer notables from text editor to dough.
When to post a final notables 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. 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.
Handoffs & 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:
-
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.
-
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; the 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, then check the Catalog (should post despite the message).
Can be confusing for first-time bakers because this lag doesn't happen in /comms/.
SEE ALSO Crazy bakes >>9960
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 & Other Fast Breads
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 drops & LINES
Check 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'.
POTUS rally breads
These can be pretty speedy; bake early so anons have a place to post rally comments.
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.
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 bakers
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 powerful and meticulously documented, fact-based counterattack. Screencap the evidence. Remember, revenge is a dish best served cold.
logo possibility
BAKING RESOURCES
Baker's grab bag
* Baker's Tools app (Version 0.7.2) Baker Tools v0.7.2: >>9584, >>9597, >>9601 https://pastebin.com/L1p6iRzZ
* Baker's Tools Lite (stripped down, good for baking) >>14523, https://pastebin.com/pUVCTeCG
* Try Atom as a text editor for Macs >>6925, >>6934, >>7055, >>7070
* Meme-making app kek.gg >>8771
* Crazy Bakes: wonky board, lags, baking from Index, "flood detected", dup breads >>9960
* How's your mouse for baking? >>10617
* Font used for baking school slides >>10642, https://www.dafontfree.net/find.php?q=impact
* Quik Pic bake instructions >>7549
* Original baking video >>7076 (shows how to make room for new notables)
* Overcoming paywalls >>10844
* Pastebin.com problems & alternatives >>11645, >>11609, >>11619, >>11620, >>11627, >>11640
* How to Control-F on androids & IOS devices >>13566, >>13567
* How to do a keyword search when /qresearch/ is down >>13696
'''* Past bread archive for /qresearch/: https://qanon.news/Archives
Dealing with notables
* Note-taking roles: baker, note collector, helper anon, posters >>14921
* Ten Baker Tips for Notables >>8177
* Bakers on what they look for in notables >>8351, >>8315, >>8698
* Muh Collector "how to" on notables >>9006, >>9009
* Anon tips for better notables >>>/qrb/41937, https://pastebin.com/yq7wQyvn
* Long notables; Asking anons to state main point >>13633, >>8237
* Asking anons to state the main point
* Advanced Google searching protocols https://pastebin.com/raw/JuK0xUDb
Free image/video screenshots, download, production tools
* Image screenshots PrtSc/snipping tool + MS-Paint https://youtu.be/KvXxCE1gxOE
* 8kun video limits (~16mg) >>8760
* Bandicam Screen Recorder >>8759, >>8762 (also: OBS, Kdenlive, Audacity)
* YouTube & Twitter (downloads plus cutting scenes from YT) >>14306
* Video downloaders: >>14237, https://www.downloadhelper.net/ ; Firefox/Opera: - https://technologyto.com/extractor.html
* VLC Player >>8714, >>8715, >>8766
* Windows Movie Maker for Win 10 >>8712
* NVidia cards (can screen-capture vids) >>8785
* Forensically (forensics magnifier) https://29a.ch/photo-forensics/#forensic-magnifier
* ShotCut NLE (open source cross platform video editor) https://shotcut.org/
* MFFmpeg (decodes & plays any format) https://ffmpeg.org/
* Natron (cross-platform video compositor) https://natrongithub.github.io/
* Handbrake (good for transcoding) https://handbrake.fr/
* GIMP & GMIC (image editing) http://gmic.eu/gimp.shtml
* Invidio (copies YT vids, restricted or not, no ads or signup) >>8792
Baker tips IRL
>>8829 Baker's Tips - Read me first
>>6331 #01 - Ghosting a bred
>>6331 #02 - Baker changes
>>6378 #03 - TOR baking
>>6651 #04 - Defeating shills with facts & humor
>>7339 #05 - Announce you're baking (#11 too)
>>6892 #06 - Baking/note-taking protocols
>>7181 #07 - Use RED TEXT and BOLD in handoffs
>>7363 #08 - Try to notice when a cat is baking
>>13038 #09 - Respecting other bakers' notables
>>8174 #10 - Make sure to copypasta the whole page
>>8803 #11 - Announce you're taking responsibility
>>8822 #12 - Embed baker changes to provide more info
>>8824 #13 - Watch out for unknown bakers bearing gifts
>>8825 #14 - Use named pastebins to defeat shill complaints
>>8826 #15 - Responding to shills trying to suck up baker's time
>>8827 #16 - Be aware of muh joos bakers
>>8828 #17 - All bakers screw up
>>10445 #18 - Just do it--bake!
>>9590 #19 - Don't be afraid to bake
>>10789 #20 - Post notes early so changes can be made
>>10791 #21 - No /comms/ creates misunderstandings
>>10792 #22 - Defeat shills with humor
>>14835 #23 - Keep notables [from different bakers] separate
>>14836 #24 - Make sure to ask for Handoff Confirmed
>>14801 #25 - Don't fuck with the wrong baker [take a look - funny]
>>15894 #26 - Ignore End-of-Bread Antics
Baker stories & discussions
>>10114 How shills attack bakers--an example ("baker saves notables for his twats")
>>10787 LIVE example of picking up a mid-bread bake
>>10710 Why do you bake? >>10729, >>10731, >>10732, >>10744
>>14837 Forensic baking (Study: who's been messing with the dough??)
>>14114 Editing PB notables, ok or not? Baker discussion >>14227, >>14248, >>14265
>>14943 What notables draw your interest and why, baker? >>14947, >>14968, >>14975, >>14983
>>15908 HOW-TO notables (Class #16) w/baker comments >>15032
Suggested resources for condensing vids
Avidemux
http://www.avidemux.org/admWiki/doku.php
Download
http://avidemux.sourceforge.net/download.html
https://www.videosmaller.com/
beware the misleading 'start' button, scroll a lil further for the 'upload' button
download link is next to 'completed' by the green check mark
LINKS:
>>>/qresearch/9775692, >>>/qresearch/9775655, >>>/qresearch/9775738, >>>/qresearch/9775730
Step-by-Step Baking Instructions
>>17783 STEP 0 - Preparation
>>17797 STEP 1 - Find the Current Dough
>>17803 STEP 2 - Copy the Current Dough
>>17807 STEP 3 - Paste The Dough Into Text Editor (>>17810 dough in Q-bin)
>>17815 STEP 3a - Trim The Notables Section
>>17822 STEP 3b - Make space for your New Notables
>>17831 STEP 4 - Create A New Thread
>>17831 STEP 5 - Enter Thread Info And Post Thread
>>17845 STEP 6 - Enter the Rest of the Dough
>>17863 STEP 7 - Make A New Pastebin & Make The Dough Post (>>17868, >>17871, >>17875 Q-bin updates)
>>17876 STEP 8 - Post Your New Thread Link
Baking Overview & Extras
>>17777 Overview
>>17884 Linking between Boards
>>17894 Timing
>>14523 Baker's Tools Lite
>>16963 NEW: How to Bake When Q Posts' >>16994, >>17015, >>17032, >>17037
Step-by-Step Baking Instructions
>>17783 STEP 0 - Preparation
>>17797 STEP 1 - Find the Current Dough
>>17803 STEP 2 - Copy the Current Dough
>>17807 STEP 3 - Paste The Dough Into Text Editor ( >>17810 dough in Q-bin)
>>17815 STEP 3a - Trim The Notables Section
>>17822 STEP 3b - Make space for your New Notables
>>17831 STEP 4 - Create A New Thread
>>17837 STEP 5 - Enter Thread Info And Post Thread
>>17845 STEP 6 - Enter the Rest of the Dough
>>17863 STEP 7 - Make A New Pastebin & Make The Dough Post ( >>17868, >>17871, >>17875 Q-bin updates)
>>17876 STEP 8 - Post Your New Thread Link
Baking Overview & Extras
>>17777 Overview
>>17884 Linking between Boards
>>17894 Timing
>>14523 Baker's Tools Lite
>>16963 NEW: How to Bake When Q Posts' >>16994, >>17015, >>17032, >>17037
https://endchan.net/qrbunker/res/5695.html#5739
War Room
>>9820389 Q Research Meme Warfare Operations <- go here for current up to date ops
Get Everyone at ONCE and HIT 'Them' With Everything You Got! THINK PICARD MANUEVER! [POST STORM - THE WAVE]
[1] MEME MEME and MEME some MOAR! Stay Focused on Current HOTTOPICS
[2] Pick 2-3 hashes from the target area htps://www.trendolizer.com Hijack them to get your #hash out.
[3] Post @ 10-11Am | 12-3Pm | 6-9Pm EST
[4] Always Post meme or Cap
[5] Use .@them to respond to all their following.
[6] Remember to be Quirky in your posts.
[7] RT other's tweets
[8] ReTweet LASERFAST. Use https://tweetdeck.com
[9] Information WarFare https://archive.is/E0oJm
#WAKEUPAMERICA #FACTSMATTER #SAVEAMERICA #UNITEDNOTDIVIDED #WWG1WGA #Qanon
Other Dedicated Research Threads
>>6867253 Clockwork Qrange #10
>>9867560 Alien, UFO, Advanced/Hidden Technology, Antigravity, DUMBs, etc. #14
>>>/qrb/13005 Planefag Q+A (Planefagging 101)
>>>/qrb/42185 Boatfagging Q&A
International Q Research Threads
Germany #58 >>9523968
UK #17 >>9566053
Australia #8 >>9062489
Canada #7 >>9725975
New Zealand #4 >>8242350
Nederland #4 >>8826750
France >>8331823
South Africa >>8033191
Nordic >>5290557
Deutsch #2 >>9578272
Q Proofs
Q Proofs Threads Proofs of Q's Validity >>6156082
QProofs.com Website dedicated to Q Proofs
Book of Q Proofs https://mega.nz/#F!afISyCoY!6N1lY_fcYFOz4OQpT82p2w - https://bookofqproofs.wordpress.com/
Q Happenings Calendar
Submit an event here https://teamup.com/ks8x4ixptej432xt2a
Main Calendar URL https://dark-to-light.org/calendar/
Sealed Indictments
Sealed Indictment Master: https://docs.google.com/spreadsheets/d/1kVQwX9l9HJ5F76x05ic_YnU_Z5yiVS96LbzAOP66EzA/edit#gid=1525422677
Sealed Indictment Master Files Backup: https://drive.google.com/open?id=1iBS4WgngH8u8-wAqhehRIWCVBQKD8-5Y
Searchable Indictment Map w/dockets, links & more: https://bad-boys.us/
Resignations
All Resignations Website https://www.resignation.info
All Posts Search Tool https://qresear.ch
Board Admin & Discussion Threads
META (for board admin queries) >>6064510
Letters of Gratitude
>>1215912 (Q posted in #1025)
Q Graphics all in GMT
Q Graphics all in GMT #001-#010 >>>/comms/486, >>>/comms/487, >>>/comms/488, >>>/comms/489, >>>/comms/490
Q Graphics all in GMT #011-#020 >>>/comms/491, >>>/comms/545, >>>/comms/950, >>>/comms/951, >>>/comms/952, >>>/comms/953, >>>/comms/987, >>>/comms/1103
Q Graphics all in GMT #021-#027 >>>/comms/1119, >>>/comms/1156, >>>/comms/1286, >>>/comms/1288, >>>/comms/1303, >>>/comms/1307, >>>/comms/1462
Q Graphics all in GMT #028-#034 >>>/comms/1466, >>>/comms/1489, >>>/comms/2071, >>>/comms/2072, >>>/comms/2073, >>>/comms/2100, >>>/comms/2164
Q Graphics all in GMT #035-#041 >>>/comms/2176, >>>/comms/2228, >>>/comms/2229, >>>/comms/2261, >>>/comms/2268, >>>/comms/2270, >>>/comms/2274
Q Graphics all in GMT #042-#048 >>>/comms/2306, >>>/comms/2312, >>>/comms/2314, >>>/comms/2327, >>>/comms/2450, >>>/comms/2491, >>>/comms/2496
Q Graphics all in GMT #049-#055 >>>/comms/2520, >>>/comms/2528, >>>/comms/2605, >>>/comms/2801, >>>/comms/2831, >>>/comms/2869, >>>/comms/2981
Q Graphics all in GMT #056-#062 >>>/comms/2990, >>>/comms/2996, >>>/comms/3019, >>>/comms/3116, >>>/comms/3187, >>>/comms/3464, >>>/comms/3472
Q Graphics all in GMT #063-#069 >>>/comms/3687, >>>/comms/3688, >>>/comms/3701, >>>/comms/3702, >>>/comms/3858, >>>/comms/3859, >>>/comms/3882
Q Graphics all in GMT #070-#076 >>>/comms/3898, >>>/comms/3920, >>>/comms/3975, >>>/comms/4029, >>>/comms/4197, >>>/comms/4335, >>>/comms/4386
Q Graphics all in GMT #077-#083 >>>/comms/4388, >>>/comms/4423, >>>/comms/4443, >>>/comms/4684, >>>/comms/5035, >>>/comms/5044, >>>/comms/5228
Q Graphics all in GMT #091-#097 >>>/comms/5811, >>>/comms/5890, >>>/comms/5975, >>>/comms/6045, >>>/comms/6083, >>>/comms/6843, >>>/comms/9187
Q Graphics all in GMT #098-#104 >>>/comms/10292, >>>/comms/10459, >>>/comms/11608, >>>/comms/12119, >>>/comms/12621, >>>/comms/12622, >>>/comms/12798
Q Graphics all in GMT #105-#111 >>>/comms/13250, >>>/comms/13486, >>>/comms/13501, >>>/comms/13575, >>>/comms/13928, >>>/comms/14625, >>>/comms/14626
Q Graphics all in GMT #112-#118 >>>/comms/14870, >>>/comms/15179, >>>/comms/15306, >>>/comms/15733, >>>/comms/15801, >>>/comms/16711, >>>/comms/16930
Q Graphics all in GMT #119-#123 >>>/comms/17717, >>>/comms/18151, >>>/comms/18629, >>>/comms/18630, >>9842094
QPosts ArchivesQ Graphics all in GMT #084-#090 >>>/comms/5510, >>>/comms/5577, >>>/comms/5622, >>>/comms/5699, >>>/comms/5700, >>>/comms/5773, >>>/comms/5806
War Room
>>9820389 Q Research Meme Warfare Operations <- go here for current up to date ops
Get Everyone at ONCE and HIT 'Them' With Everything You Got! THINK PICARD MANUEVER! [POST STORM - THE WAVE]
[1] MEME MEME and MEME some MOAR! Stay Focused on Current HOTTOPICS
[2] Pick 2-3 hashes from the target area htps://www.trendolizer.com Hijack them to get your #hash out.
[3] Post @ 10-11Am | 12-3Pm | 6-9Pm EST
[4] Always Post meme or Cap
[5] Use .@them to respond to all their following.
[6] Remember to be Quirky in your posts.
[7] RT other's tweets
[8] ReTweet LASERFAST. Use https://tweetdeck.com
[9] Information WarFare https://archive.is/E0oJm
#WAKEUPAMERICA #FACTSMATTER #SAVEAMERICA #UNITEDNOTDIVIDED #WWG1WGA #Qanon
Other Dedicated Research Threads
>>6867253 Clockwork Qrange #10
>>9867560 Alien, UFO, Advanced/Hidden Technology, Antigravity, DUMBs, etc. #14
>>>/qrb/13005 Planefag Q+A (Planefagging 101)
>>>/qrb/42185 Boatfagging Q&A
International Q Research Threads
Germany #58 >>9523968
UK #17 >>9566053
Australia #8 >>9062489
Canada #7 >>9725975
New Zealand #4 >>8242350
Nederland #4 >>8826750
France >>8331823
South Africa >>8033191
Nordic >>5290557
Deutsch #2 >>9578272
Q Proofs
Q Proofs Threads Proofs of Q's Validity >>6156082
QProofs.com Website dedicated to Q Proofs
Book of Q Proofs https://mega.nz/#F!afISyCoY!6N1lY_fcYFOz4OQpT82p2w - https://bookofqproofs.wordpress.com/
Q Happenings Calendar
Submit an event here https://teamup.com/ks8x4ixptej432xt2a
Main Calendar URL https://dark-to-light.org/calendar/
Sealed Indictments
Sealed Indictment Master: https://docs.google.com/spreadsheets/d/1kVQwX9l9HJ5F76x05ic_YnU_Z5yiVS96LbzAOP66EzA/edit#gid=1525422677
Sealed Indictment Master Files Backup: https://drive.google.com/open?id=1iBS4WgngH8u8-wAqhehRIWCVBQKD8-5Y
Searchable Indictment Map w/dockets, links & more: https://bad-boys.us/
Resignations
All Resignations Website https://www.resignation.info
All Posts Search Tool https://qresear.ch
Board Admin & Discussion Threads
META (for board admin queries) >>6064510
Letters of Gratitude
>>1215912 (Q posted in #1025)
Q Graphics all in GMT
Q Graphics all in GMT #001-#010 >>>/comms/486, >>>/comms/487, >>>/comms/488, >>>/comms/489, >>>/comms/490
Q Graphics all in GMT #011-#020 >>>/comms/491, >>>/comms/545, >>>/comms/950, >>>/comms/951, >>>/comms/952, >>>/comms/953, >>>/comms/987, >>>/comms/1103
Q Graphics all in GMT #021-#027 >>>/comms/1119, >>>/comms/1156, >>>/comms/1286, >>>/comms/1288, >>>/comms/1303, >>>/comms/1307, >>>/comms/1462
Q Graphics all in GMT #028-#034 >>>/comms/1466, >>>/comms/1489, >>>/comms/2071, >>>/comms/2072, >>>/comms/2073, >>>/comms/2100, >>>/comms/2164
Q Graphics all in GMT #035-#041 >>>/comms/2176, >>>/comms/2228, >>>/comms/2229, >>>/comms/2261, >>>/comms/2268, >>>/comms/2270, >>>/comms/2274
Q Graphics all in GMT #042-#048 >>>/comms/2306, >>>/comms/2312, >>>/comms/2314, >>>/comms/2327, >>>/comms/2450, >>>/comms/2491, >>>/comms/2496
Q Graphics all in GMT #049-#055 >>>/comms/2520, >>>/comms/2528, >>>/comms/2605, >>>/comms/2801, >>>/comms/2831, >>>/comms/2869, >>>/comms/2981
Q Graphics all in GMT #056-#062 >>>/comms/2990, >>>/comms/2996, >>>/comms/3019, >>>/comms/3116, >>>/comms/3187, >>>/comms/3464, >>>/comms/3472
Q Graphics all in GMT #063-#069 >>>/comms/3687, >>>/comms/3688, >>>/comms/3701, >>>/comms/3702, >>>/comms/3858, >>>/comms/3859, >>>/comms/3882
Q Graphics all in GMT #070-#076 >>>/comms/3898, >>>/comms/3920, >>>/comms/3975, >>>/comms/4029, >>>/comms/4197, >>>/comms/4335, >>>/comms/4386
Q Graphics all in GMT #077-#083 >>>/comms/4388, >>>/comms/4423, >>>/comms/4443, >>>/comms/4684, >>>/comms/5035, >>>/comms/5044, >>>/comms/5228
Q Graphics all in GMT #084-#090 >>>/comms/5510, >>>/comms/5577, >>>/comms/5622, >>>/comms/5699, >>>/comms/5700, >>>/comms/5773, >>>/comms/5806
Q Graphics all in GMT #091-#097 >>>/comms/5811, >>>/comms/5890, >>>/comms/5975, >>>/comms/6045, >>>/comms/6083, >>>/comms/6843, >>>/comms/9187
Q Graphics all in GMT #098-#104 >>>/comms/10292, >>>/comms/10459, >>>/comms/11608, >>>/comms/12119, >>>/comms/12621, >>>/comms/12622, >>>/comms/12798
Q Graphics all in GMT #105-#111 >>>/comms/13250, >>>/comms/13486, >>>/comms/13501, >>>/comms/13575, >>>/comms/13928, >>>/comms/14625, >>>/comms/14626
Q Graphics all in GMT #112-#118 >>>/comms/14870, >>>/comms/15179, >>>/comms/15306, >>>/comms/15733, >>>/comms/15801, >>>/comms/16711, >>>/comms/16930
Q Graphics all in GMT #119-#123 >>>/comms/17717, >>>/comms/18151, >>>/comms/18629, >>>/comms/18630, >>9842094
War Room
>>9820389 Q Research Meme Warfare Operations <- go here for current up to date ops
Get Everyone at ONCE and HIT 'Them' With Everything You Got! THINK PICARD MANUEVER! [POST STORM - THE WAVE]
[1] MEME MEME and MEME some MOAR! Stay Focused on Current HOTTOPICS
[2] Pick 2-3 hashes from the target area htps://www.trendolizer.com Hijack them to get your #hash out.
[3] Post @ 10-11Am | 12-3Pm | 6-9Pm EST
[4] Always Post meme or Cap
[5] Use .@them to respond to all their following.
[6] Remember to be Quirky in your posts.
[7] RT other's tweets
[8] ReTweet LASERFAST. Use https://tweetdeck.com
[9] Information WarFare https://archive.is/E0oJm
#WAKEUPAMERICA #FACTSMATTER #SAVEAMERICA #UNITEDNOTDIVIDED #WWG1WGA #Qanon
Other Dedicated Research Threads
>>6867253 Clockwork Qrange #10
>>9867560 Alien, UFO, Advanced/Hidden Technology, Antigravity, DUMBs, etc. #14
>>>/qrb/13005 Planefag Q+A (Planefagging 101)
>>>/qrb/42185 Boatfagging Q&A
International Q Research Threads
Germany #58 >>9523968
UK #17 >>9566053
Australia #8 >>9062489
Canada #7 >>9725975
New Zealand #4 >>8242350
Nederland #4 >>8826750
France >>8331823
South Africa >>8033191
Nordic >>5290557
Deutsch #2 >>9578272
Q Proofs
Q Proofs Threads Proofs of Q's Validity >>6156082
QProofs.com Website dedicated to Q Proofs
Book of Q Proofs https://mega.nz/#F!afISyCoY!6N1lY_fcYFOz4OQpT82p2w - https://bookofqproofs.wordpress.com/
Q Happenings Calendar
Submit an event here https://teamup.com/ks8x4ixptej432xt2a
Main Calendar URL https://dark-to-light.org/calendar/
Sealed Indictments
Sealed Indictment Master: https://docs.google.com/spreadsheets/d/1kVQwX9l9HJ5F76x05ic_YnU_Z5yiVS96LbzAOP66EzA/edit#gid=1525422677
Sealed Indictment Master Files Backup: https://drive.google.com/open?id=1iBS4WgngH8u8-wAqhehRIWCVBQKD8-5Y
Searchable Indictment Map w/dockets, links & more: https://bad-boys.us/
Resignations
All Resignations Website https://www.resignation.info
All Posts Search Tool https://qresear.ch
Board Admin & Discussion Threads
META (for board admin queries) >>6064510
Letters of Gratitude
>>1215912 (Q posted in #1025)
Q Graphics all in GMT
All of the following except the last are in order on the same thread on /comms/
Thread link: https://8kun.top/qresearch/res/9891798.html
Q Graphics all in GMT #001- #020 >>>/comms/486 through >>>/comms/1103
Q Graphics all in GMT #021- #041 >>>/comms/1119 through >>>/comms/2274
Q Graphics all in GMT #042- #062 >>>/comms/2306 through >>>/comms/3472
Q Graphics all in GMT #063-#083 >>>/comms/3687 through >>>/comms/5228
Q Graphics all in GMT #091-#111 >>>/comms/5811 through >>>/comms/14626
Q Graphics all in GMT #112-#123 >>>/comms/14870 through >>>/comms/18630
>>9842094
War Room
>>9820389 Q Research Meme Warfare Operations <- go here for current up to date ops
Get Everyone at ONCE and HIT 'Them' With Everything You Got! THINK PICARD MANUEVER! [POST STORM - THE WAVE]
[1] MEME MEME and MEME some MOAR! Stay Focused on Current HOTTOPICS
[2] Pick 2-3 hashes from the target area htps://www.trendolizer.com Hijack them to get your #hash out.
[3] Post @ 10-11Am | 12-3Pm | 6-9Pm EST
[4] Always Post meme or Cap
[5] Use .@them to respond to all their following.
[6] Remember to be Quirky in your posts.
[7] RT other's tweets
[8] ReTweet LASERFAST. Use https://tweetdeck.com
[9] Information WarFare https://archive.is/E0oJm
#WAKEUPAMERICA #FACTSMATTER #SAVEAMERICA #UNITEDNOTDIVIDED #WWG1WGA #Qanon
Other Dedicated Research Threads
>>6867253 Clockwork Qrange #10
>>9867560 Alien, UFO, Advanced/Hidden Technology, Antigravity, DUMBs, etc. #14
>>>/qrb/13005 Planefag Q+A (Planefagging 101)
>>>/qrb/42185 Boatfagging Q&A
International Q Research Threads
Germany #58 >>9523968
UK #17 >>9566053
Australia #8 >>9062489
Canada #7 >>9725975
New Zealand #4 >>8242350
Nederland #4 >>8826750
France >>8331823
South Africa >>8033191
Nordic >>5290557
Deutsch #2 >>9578272
Q Proofs
Q Proofs Threads Proofs of Q's Validity >>6156082
QProofs.com Website dedicated to Q Proofs
Book of Q Proofs https://mega.nz/#F!afISyCoY!6N1lY_fcYFOz4OQpT82p2w - https://bookofqproofs.wordpress.com/
Q Happenings Calendar
Submit an event here https://teamup.com/ks8x4ixptej432xt2a
Main Calendar URL https://dark-to-light.org/calendar/
Sealed Indictments
Sealed Indictment Master: https://docs.google.com/spreadsheets/d/1kVQwX9l9HJ5F76x05ic_YnU_Z5yiVS96LbzAOP66EzA/edit#gid=1525422677
Sealed Indictment Master Files Backup: https://drive.google.com/open?id=1iBS4WgngH8u8-wAqhehRIWCVBQKD8-5Y
Searchable Indictment Map w/dockets, links & more: https://bad-boys.us/
Resignations
All Resignations Website https://www.resignation.info
All Posts Search Tool https://qresear.ch
Board Admin & Discussion Threads
META (for board admin queries) >>6064510
Letters of Gratitude
>>1215912 (Q posted in #1025)
Q Graphics all in GMT
___All of the following except the last are in order on the same thread on /comms/__
Thread link: >>>/comms/1283
Q Graphics all in GMT #001 - #020 >>>/comms/486 through >>>/comms/1103
Q Graphics all in GMT #021 - #041 >>>/comms/1119 through >>>/comms/2274
Q Graphics all in GMT #042 - #062 >>>/comms/2306 through >>>/comms/3472
Q Graphics all in GMT #063 - #083 >>>/comms/3687 through >>>/comms/5228
Q Graphics all in GMT #091 - #111 >>>/comms/5811 through >>>/comms/14626
Q Graphics all in GMT #112 - #123 >>>/comms/14870 through >>>/comms/18630
>>9842094
War Room
>>9820389 Q Research Meme Warfare Operations <- go here for current up to date ops
Get Everyone at ONCE and HIT 'Them' With Everything You Got! THINK PICARD MANUEVER! [POST STORM - THE WAVE]
[1] MEME MEME and MEME some MOAR! Stay Focused on Current HOTTOPICS
[2] Pick 2-3 hashes from the target area htps://www.trendolizer.com Hijack them to get your #hash out.
[3] Post @ 10-11Am | 12-3Pm | 6-9Pm EST
[4] Always Post meme or Cap
[5] Use .@them to respond to all their following.
[6] Remember to be Quirky in your posts.
[7] RT other's tweets
[8] ReTweet LASERFAST. Use https://tweetdeck.com
[9] Information WarFare https://archive.is/E0oJm
#WAKEUPAMERICA #FACTSMATTER #SAVEAMERICA #UNITEDNOTDIVIDED #WWG1WGA #Qanon
Other Dedicated Research Threads
>>6867253 Clockwork Qrange #10
>>9867560 Alien, UFO, Advanced/Hidden Technology, Antigravity, DUMBs, etc. #14
>>>/qrb/13005 Planefag Q+A (Planefagging 101)
>>>/qrb/42185 Boatfagging Q&A
International Q Research Threads
Germany #58 >>9523968
UK #17 >>9566053
Australia #8 >>9062489
Canada #7 >>9725975
New Zealand #4 >>8242350
Nederland #4 >>8826750
France >>8331823
South Africa >>8033191
Nordic >>5290557
Deutsch #2 >>9578272
Q Proofs
Q Proofs Threads Proofs of Q's Validity >>6156082
QProofs.com Website dedicated to Q Proofs
Book of Q Proofs https://mega.nz/#F!afISyCoY!6N1lY_fcYFOz4OQpT82p2w - https://bookofqproofs.wordpress.com/
Q Happenings Calendar
Submit an event here https://teamup.com/ks8x4ixptej432xt2a
Main Calendar URL https://dark-to-light.org/calendar/
Sealed Indictments
Sealed Indictment Master: https://docs.google.com/spreadsheets/d/1kVQwX9l9HJ5F76x05ic_YnU_Z5yiVS96LbzAOP66EzA/edit#gid=1525422677
Sealed Indictment Master Files Backup: https://drive.google.com/open?id=1iBS4WgngH8u8-wAqhehRIWCVBQKD8-5Y
Searchable Indictment Map w/dockets, links & more: https://bad-boys.us/
Resignations
All Resignations Website https://www.resignation.info
All Posts Search Tool https://qresear.ch
Board Admin & Discussion Threads
META (for board admin queries) >>6064510
Letters of Gratitude
>>1215912 (Q posted in #1025)
Q Graphics all in GMT
___All of the following except the last are in order on the same thread on /comms/__
Thread link: >>>/comms/283
Q Graphics all in GMT #001 - #020 >>>/comms/486 through >>>/comms/1103
Q Graphics all in GMT #021 - #041 >>>/comms/1119 through >>>/comms/2274
Q Graphics all in GMT #042 - #062 >>>/comms/2306 through >>>/comms/3472
Q Graphics all in GMT #063 - #083 >>>/comms/3687 through >>>/comms/5228
Q Graphics all in GMT #091 - #111 >>>/comms/5811 through >>>/comms/14626
Q Graphics all in GMT #112 - #123 >>>/comms/14870 through >>>/comms/18630
>>9842094
Most common "tells" for new bakers & how to avoid 'em
Draft 2
Focus mainly on specific acts that can be easily remedied (a) if new baker knows how (e.g., Global Report) or (b) baker realizes why they matter (e.g., tagging dough post).
10 most common "tells" (quik n easy to fix):
1 - using curly quotes from word processing programs to make bold
use text editors not word processors like Word
2 - copying the page breaks into the dough
know what they are and do not copy! ////////////page 1\\\\\\
3 - for Create a Thread, not changing the bread number after the first bake
check and double check bread nos before baking
4 - not tagging the dough post when picking up bake, making dough changes, etc. (see >>19341, >>19374)
always tag the dough!
5 - trying to type in the formating lines in Q posts
don't do it, uses special characters so just copypasta
6 - omitting the colon in the title after the bred number: Q Research General #12695 My First Bread Edition
easy to do but easy to forget - important for aggregators
7 - replying to own posts when generating the dough
''just copy in order, no RT necessary; see >>19339)
8 - trying to replicate lines in Q posts from scratch instead of using copy-pasta
Here's a template: >>19379
9 - making page 2 notables post way too short (to avoid "body too long" message)
use two pages instead of one for notables on p2 of dough
10 - trying to contact BO by posting a message in /qr/ (instead of using Report or Global Report)
use Report/Global Report; in menu to upper left of each post
'Big picture' stuff:
- bakers changing formatting of notables on dough p2 (not realizing aggregator needs)'''
practice bake using exact formatting you see in LIVE bakes
- using "cut-pasta" instead of "copy-pasta" (suddenly, your notes or dough - GONE!)'''
do enough practice baking to get 'muscle memory' to kick in b4 going LIVE
- not saving notables while collecting
losing 'em once will remind new bakers to save frequently
- not reading prior breads before baking to understand what the shit is (see >>19292)
keep up on the news & notables before baking when possible
'''- not using qresear.ch to check for dups
use it; it works (exception: fast breads, heavy news)
'''- forgetting it's about service not ego (hint: don't get triggered!)
let go of small annoyances to maintain 40000 ft view
'''- failing to use good handoff protocol (means uncertainty about who's baking)
learn it, use it, don't slack - it's important
- freaking out when asked to provide a qbin/pastebin for verification
know how it works and why we do it (to batten down the hatches)
- double-spacing notables (happens when baker uses copy-pasta straight from dough instead of pastebin)
learn how to upload/download dough from pastebin/qbin
Most Common "tells" for new bakers
Focus mainly on specific acts that can be easily remedied (a) if new baker knows how (e.g., Global Report) or (b) baker realizes why they matter (e.g., tagging dough post).
10 most common "tells" (quik n easy to fix):
1 - using curly quotes from word processing programs to make bold
use text editors not word processors like Word
2 - copying the page breaks into the dough
know what they are and do not copy! ////////////page 1\\\\\\
3 - for Create a Thread, not changing the bread number after the first bake
check and double check bread nos before baking
4 - not tagging the dough post when picking up bake, making dough changes, etc. (see >>19341, >>19374)
always tag the dough!
5 - trying to type in the formating lines in Q posts
don't do it, uses special characters so just copypasta
6 - omitting the colon in the title after the bred number: Q Research General #12695 My First Bread Edition
easy to do but easy to forget - important for aggregators
7 - replying to own posts when generating the dough
just copy in order, no RT necessary; see >>19339)
8 - trying to replicate lines in Q posts from scratch instead of using copy-pasta
Here's a template: >>19379
9 - making page 2 notables post way too short (to avoid "body too long" message)
use two pages instead of one for notables on p2 of dough
10 - trying to contact BO by posting a message in /qr/ (instead of using Report or Global Report)
use Report/Global Report; in menu to upper left of each post
'Big picture' stuff:
- bakers changing formatting of notables on dough p2 (not realizing aggregator needs)'''
practice bake using exact formatting you see in LIVE bakes
- using "cut-pasta" instead of "copy-pasta" (suddenly, your notes or dough - GONE!)'''
do enough practice baking to get 'muscle memory' to kick in b4 going LIVE
- not saving notables while collecting
losing 'em once will remind new bakers to save frequently
- not reading prior breads before baking to understand what the shit is (see >>19292)
keep up on the news & notables before baking when possible
- not using qresear.ch to check for dups
use it; it works (exception: fast breads, heavy news)
- forgetting it's about service not ego (hint: don't get triggered!)
let go of small annoyances to maintain 40000 ft view
- failing to use good handoff protocol (means uncertainty about who's baking)
learn it, use it, don't get careless - it's important
- freaking out when asked to provide a qbin/pastebin for verification
know how it works and why we do it (to batten down the hatches)
- double-spacing notables (happens when baker uses copy-pasta straight from dough instead of pastebin)'''
learn how to upload/download dough from pastebin/qbin
Most Common "tells" for new bakers
Focus mainly on specific acts that can be easily remedied (a) if new baker knows how (e.g., Global Report) or (b) baker realizes why they matter (e.g., tagging dough post).
10 most common "tells" (quik n easy to fix):
1 - using curly quotes from word processing programs to make bold
use text editors not word processors like Word
2 - copying the page breaks into the dough
know what they are and do not copy! ////////////page 1\\\\\\
3 - for Create a Thread, not changing the bread number after the first bake
check and double check bread nos before baking
4 - not tagging the dough post when picking up bake, making dough changes, etc. (see >>19341, >>19374)
always tag the dough!
5 - trying to type in the formating lines in Q posts
don't do it, uses special characters so just copypasta
6 - omitting the colon in the title after the bred number: Q Research General #12695 My First Bread Edition
easy to do but easy to forget - important for aggregators
7 - replying to own posts when generating the dough
just copy in order, no RT necessary; see >>19339)
8 - trying to replicate lines in Q posts from scratch instead of using copy-pasta
Here's a template: >>19379
9 - making page 2 notables post way too short (to avoid "body too long" message)
use two pages instead of one for notables on p2 of dough
10 - trying to contact BO by posting a message in /qr/ (instead of using Report or Global Report)
use Report/Global Report; in menu to upper left of each post
Ten challenges re gen'l approach & practices:
More subtle and often more challenging initially bc it takes time to develop good habits.
1 - remembering it's about service not ego (hint: don't get triggered!)
let go of small annoyances to maintain 40000 ft view
2 - using good handoff protocol (means uncertainty about who's baking)
learn it, use it, don't get careless - it's important
3 - not freaking out when asked to provide a qbin/pastebin for verification
know how it works and why we do it (to batten down the hatches)
4 - using standards formatting of notables on dough p2 (not realizing aggregator needs)
practice bake using exact formatting you see in LIVE bakes
5 - not reading prior breads before baking to understand what the shit is (see >>19292)
keep up on the news & notables before baking when possible
6 - not using qresear.ch to check for dups
use it; it works (exception: fast breads, heavy news)
7 - using "cut-pasta" instead of "copy-pasta" (suddenly, your notes or dough - GONE!)'''
do enough practice baking to get 'muscle memory' to kick in b4 going LIVE
8 - not saving notables while collecting
losing 'em once will remind new bakers to save frequently
''' 9 - not changing pb notables or notables of another baker in same bread (except for accuracy when needed)
essential for trust; ask other bakers for advice in specific situations
''' 10 - being careful about accuracy with notables (we can't change 'em so sauce really matters)
check for sauce; for quality; for multiple reports w/breaking news
- double-spacing notables (happens when baker uses copy-pasta straight from dough instead of pastebin)'''
learn how to upload/download dough from pastebin/qbin
Most Common "tells" for new bakers
Focus mainly on specific acts that can be easily remedied (a) if new baker knows how (e.g., Global Report) or (b) baker realizes why they matter (e.g., tagging dough post).
10 most common "tells" (quik n easy to fix):
1 - using curly quotes from word processing programs to make bold
use text editors not word processors like Word
2 - copying the page breaks into the dough
know what they are and do not copy! ////////////page 1\\\\\\
3 - for Create a Thread, not changing the bread number after the first bake
check and double check bread nos before baking
4 - not tagging the dough post when picking up bake, making dough changes, etc. (see >>19341, >>19374)
always tag the dough!
5 - trying to type in the formating lines in Q posts
don't do it, uses special characters so just copypasta
6 - omitting the colon in the title after the bred number: Q Research General #12695 My First Bread Edition
easy to do but easy to forget - important for aggregators
7 - replying to own posts when generating the dough
just copy in order, no RT necessary; see >>19339)
8 - trying to replicate lines in Q posts from scratch instead of using copy-pasta
Here's a template: >>19379
9 - making page 2 notables post way too short (to avoid "body too long" message)
use two pages instead of one for notables on p2 of dough
10 - trying to contact BO by posting a message in /qr/ (instead of using Report or Global Report)
use Report/Global Report; in menu to upper left of each post
Eleven challenges re gen'l approach & practices:
More subtle and often more challenging initially bc it takes time to develop good habits.
1 - remembering it's about service not ego (hint: don't get triggered!)
let go of small annoyances to maintain 40000 ft view
2 - using good handoff protocol (means uncertainty about who's baking)
learn it, use it, don't get careless - it's important
3 - not freaking out when asked to provide a qbin/pastebin for verification
know how it works and why we do it (to batten down the hatches)
4 - using standards formatting of notables on dough p2 (not realizing aggregator needs)
practice bake using exact formatting you see in LIVE bakes
5 - not reading prior breads before baking to understand what the shit is (see >>19292)
keep up on the news & notables before baking when possible
6 - not using qresear.ch to check for dups
use it; it works (exception: fast breads, heavy news)
7 - accidental "cut-pasta" instead of "copy-pasta" (suddenly, your notes or dough - GONE!)
do enough practice baking to get 'muscle memory' to kick in b4 going LIVE
8 - not saving notables while collecting
losing 'em once will remind new bakers to save frequently
9 - not changing pb notables or notables of another baker in same bread (except for accuracy when needed)
essential for trust; really try to avoid
10 - being careful about accuracy with notables (we can't change 'em so sauce really matters)
check for sauce; for quality; for multiple reports w/breaking news
11- double-spacing notables (happens when baker uses copy-pasta straight from dough instead of pastebin)
learn how to upload/download dough from pastebin/qbin
Ten common "tells" that out new bakers
Focus mainly on specific acts that can be easily remedied (a) if new baker knows how (e.g., Global Report) or (b) baker realizes why they matter (e.g., tagging dough post).
Qwik 'n easy things to fix:
1 - using curly quotes from word processing programs to make bold
use text editors not word processors like Word
2 - copying the page breaks into the dough
know what they are and do not copy! ////////////page 1\\\\\\
3 - for Create a Thread, not changing the bread number after the first bake
check and double check bread nos before baking
4 - not tagging the dough post when picking up bake, making dough changes, etc. (see >>19341, >>19374)
always tag the dough!
5 - trying to type in the formating lines in Q posts
don't do it, uses special characters so just copypasta
6 - omitting the colon in the title after the bred number: Q Research General #12695 My First Bread Edition
easy to do but easy to forget - important for aggregators
7 - replying to own posts when generating the dough
just copy in order, no RT necessary; see >>19339)
8 - trying to replicate lines in Q posts from scratch instead of using copy-pasta
Here's a template: >>19379
9 - making page 2 notables post way too short (to avoid "body too long" message)
use two pages instead of one for notables on p2 of dough
10 - trying to contact BO by posting a message in /qr/ (instead of using Report or Global Report)
use Report/Global Report; in menu to upper left of each post
Ten challenges re gen'l approach & practices:'
More subtle and often more challenging initially bc it takes time to develop good habits.
1 - remembering it's about service not ego (hint: don't get triggered!)
let go of small annoyances to maintain 40000 ft view
2 - using good handoff protocol (so the board knows who's baking)
learn it, use it, don't get careless - it's important
3 - not freaking out when asked to provide a qbin/pastebin for verification
know how it works and why we do it (to batten down the hatches)
4 - using pretty set formatting for notables on dough page 2 (not realizing aggregator needs)
practice bake using exact formatting you see in LIVE bakes
5 - reading prior breads before baking (see >>19292)
keep up on the news & notables before baking when possible
6 - using qresear.ch to check for dups
use it; it works (exception: fast breads, heavy news)
7 - avoiding "cut-pasta" instead of "copy-pasta" (suddenly, your notes or dough - GONE!)
do enough practice baking to get 'muscle memory' to kick in b4 going LIVE
8 - hands off notables of another baker either pb or in same bread (except for accuracy when needed)
essential for trust; really try to avoid(not true for note collector notables, can be edited)
9 - being careful about accuracy with notables (we can't change 'em so sauce really matters)
check for sauce & sauce quality; look for multiple reports of breaking news
10 - avoid dreaded double-spacing of notables (happens when baker uses copy-pasta straight from dough instead of pastebin)
learn how to upload/download dough from pastebin/qbin
Ten common "tells" that out new bakers
Focus mainly on specific acts that can be easily remedied (a) if new baker knows how (e.g., Global Report) or (b) baker realizes why they matter (e.g., tagging dough post).
Qwik 'n easy things to fix:
1 - using curly quotes from word processing programs to make bold
use text editors not word processors like Word
2 - copying the page breaks into the dough
know what they are and do not copy-pasta when baking! ////////////page 1\\\\\\
3 - for Create a Thread, using wrong bread number
check and double check bread numbers before baking
4 - not tagging the dough post when picking up ghost bake, making dough changes, etc. (see >>19341, >>19374)
always tag the dough if there's more than one baker!
5 - trying to type in the formating lines for each Q post
don't do it, uses special characters so just copypasta
6 - omitting the colon in the title after the bred number: Q Research General #12695 My First Bread Edition
easy to do but easy to forget - important for aggregators
7 - replying to own posts when generating the dough
just copy in order, no RT necessary; see >>19339)
8 - trying to replicate lines in Q posts from scratch instead of using copy-pasta
Here's a template: >>19379
9 - making page 2 notables post way too short (to avoid "body too long" message)
use two pages instead of one for notables on page 2 of dough
10 - trying to contact BO by posting a message in /qr/ (instead of using Report or Global Report)
use Report/Global Report; in menu to upper left of each post
Ten challenges re baking attitude & practices:
More subtle and often more challenging initially bc it takes time to develop good habits.
1 - remembering it's about service not ego (hint: don't get triggered!)
let go of small annoyances to maintain 40000 ft view
2 - using good handoff protocol (so the board knows who's baking)
learn it, use it, don't get careless - it's important
3 - not freaking out when asked to provide a qbin/pastebin for verification
know how it works and why we do it (to batten down the hatches)
4 - using pretty set formatting for notables on dough page 2 (not realizing aggregator needs)
practice bake using exact formatting you see in LIVE bakes
5 - reading prior breads before baking (see >>19292)
keep up on the news & notables before baking when possible
6 - using qresear.ch to check for dups
use it; it works (exception: fast breads, heavy news)
7 - avoiding "cut-pasta" instead of "copy-pasta" (suddenly, your notes or dough - GONE!)
do enough practice baking to get 'muscle memory' to kick in b4 going LIVE
8 - strict "hands off" policy re notables of another baker (except for accuracy when needed)
essential for trust; really try to avoid(not true for note collector notables, can be edited)
9 - being careful about accuracy with notables (we can't change 'em so sauce really matters)
check for sauce & sauce quality; look for multiple reports of breaking news
10 - avoiding dreaded double-spacing of notables (happens when baker uses copy-pasta straight from dough instead of pastebin)
learn how to upload/download dough from pastebin/qbin
https://endchan.net/qrbunker/res/5695.html#5739
LIVE Baking Seminar
7/23/2020
We in here
Welcome To LIVE Baking Classes in the Q Research Utility Kitchen
We hold these truths to be self-evident: that all men are created equal; that they are endowed by their Creator with certain unalienable rights; that among these are life, liberty, and the pursuit of happiness.
We are the bakers who provide the breads for those anons who post Qresearch's open-sourced information, reasoned argument, and dank memes. We do battle in the sphere of baking ideas and baking ideas only. We neither need nor condone the use of force in our work here.
=VINCIT OMNIA VERITAS=
=SEMPER FIDELIS=
=WWG1WGA=
INTRO TO BAKING
Qresearch is a 24/7 beehive of activity where anons post their diggs, memes and prayers.
For this to happen requires ''bakers''βwhich is why they have been called "the core of this board."
Bakers perform several key functions:
* Set the tone for each bread via their choice of bread title and /comms/ with posters.
* Post notables for each bread.
* Bake breads (transition the board from one thread to the next).
* Knead the dough (keeping the resource pages clean, tidy, and up-to-date).
When all goes well, baking is a fun & exciting opportunity to serve. When things get wonky and shills attackβbakers carry on anyway.
Shadilay, fellow bakers!
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
General Announcements
* Baking Class in /comms/ every Thursday @7pm ET: practice baking, Q&A, all are welcome
* Baking class plan (so any baker can teach) >>11969, https://pastebin.com/gqfunWCR
* How to bake a baking seminar dough >>14289
* Too many threads problem - bakers be(a)ware >>15895
* Qbin links qanonbin.com, www2qanonbin.com
* Dough Revision>20538
Past Class links & archives
>>6125 #1, >>6368 #2, >>6885 #3, >>7185 #4 , >>7568 #5, >>8274 #6, >>8872 #7, >>9320 #8, >>9787 #9, >>10510 #10, >>11086 #11, #12 >>11733, #13 >>13041, #14 >>13590, #15 >>14290, #16 >>14873, #17 >>15341, #18 >>15918, #19 >>16885, #20 >>17719, #21 >>18289
Archives: Classes #1 - #20: >>18934
Step-by-Step Baking Instructions
>>17783 STEP 0 - Preparation
>>17797 STEP 1 - Find the Current Dough
>>17803 STEP 2 - Copy the Current Dough
>>17807 STEP 3 - Paste The Dough Into Text Editor ( >>17810 dough in Q-bin)
>>17815 STEP 3a - Trim The Notables Section
>>17822 STEP 3b - Make space for your New Notables
>>17831 STEP 4 - Create A New Thread
>>17837 STEP 5 - Enter Thread Info And Post Thread
>>17845 STEP 6 - Enter the Rest of the Dough
>>17863 STEP 7 - Make A New Pastebin & Make The Dough Post ( >>17868, >>17871, >>17875 Q-bin updates)
>>17876 STEP 8 - Post Your New Thread Link
Baking Overview & Extras
>>17777 Overview
>>17884 Linking between Boards
>>17894 Timing
>>14523 Baker's Tools Lite
>>16963 NEW: How to Bake When Q Posts >>16994, >>17015, >>17032, >>17037
E-BAKE Instructions
Baker verification mini-seminar>>20537
>>19874 Why do bakers verify who they are handing off to?
>>19890 What are some ways that bakers have kept a work history and used it to verify their handoffs so far? What do these verification methods have in common?
>>19914 Example verification using pastebin
>>19934 Example of an incorrect/invalid verification using pastebin
>>19953, >>19990 Is this a valid verification by itself?
>>20026 Verification using qanonbin.com
>>20037 Human or "inexact" methods of verification
>>20047 Bun of verification discussion
Baker verification mini-seminar>>20537
Baker verification mini-seminar >>20537
>>20537 Baker verification mini-seminar==
>>20537Baker verification mini-seminar
Coastal Pac NW: OR & WA states
THIS THREAD is for deep digs on current DS activities in the Pac NW.
Goal: to reveal to NW citizens & others the real agenda behind the "local" politics
and how outside influencers pull the strings.
HINTS
> The more sauce, the better
> Use qresear.ch as a resource - 14mil+ 8kun articles (use F3 to refine searches)
> Don't dox yourself (stay anon or use a dif id's)
> Post digs from QR here too (links there only last a coupla weeks).
TOPICS
* BLM, Antifa, leaders/backers
* Seattle, Portland, Spokane
* govs, mayors, city councils
* draconian Covid-19 policies
* 2020, voting fraud
* ports, I-5 corridor, shipping
* drug-running, trafficking
* school boards, unions, other orgs/companies
* climate change agenda push
* Bill & Melinda Gates Foundation
* UN connections (Agenda 21, 2030)
''DIG ANONS DIG!''
Coastal Pac NW: OR & WA states
THIS THREAD is for deep digs on current DS activities in the Pac NW.
Goal: to reveal to NW citizens & others the real agenda behind the "local" politics
and how outside influencers pull the strings.
HINTS
> The more sauce, the better
> Use qresear.ch as a resource - 14mil+ 8kun articles (use F3 to refine searches)
> Don't dox yourself (stay anon or use a dif id's)
> Post digs from QR here too (links there only last a coupla weeks).
TOPICS
* BLM, Antifa, leaders/backers
* Seattle, Portland, Spokane
* govs, mayors, city councils
* draconian Covid-19 policies
* 2020, voting fraud
* ports, I-5 corridor, shipping
* drug-running, trafficking
* school boards, unions, other orgs/companies
* climate change agenda push
* Bill & Melinda Gates Foundation
* UN connections (Agenda 21, 2030)
''DIG ANONS DIG!''
Coastal Pac NW: OR & WA states
THIS THREAD is for deep digs on current DS activities in the Pac NW.
Goal: to reveal to NW citizens & others the real agenda behind the "local" politics
and how outside influencers pull the strings.
HINTS
> The more sauce, the better
> Use qresear.ch as a resource - 14mil+ 8kun articles (use F3 to refine searches)
> Don't dox yourself (stay anon or use a dif id's)
> Post digs from QR here too (links there only last a coupla weeks).
TOPICS
* BLM, Antifa, leaders/backers
* Seattle, Portland, Spokane
* govs, mayors, city councils
* draconian Covid-19 policies
* 2020, voting fraud
* ports, I-5 corridor, shipping
* drug-running, trafficking
* school boards, unions, other orgs/companies
* climate change agenda push
* Bill & Melinda Gates Foundation
* UN connections (Agenda 21, 2030)
''DIG ANONS DIG!!'
Coastal Pac NW: OR & WA states
THIS THREAD is for deep digs on current DS activities in the Pac NW.
Goal: to reveal to NW citizens & others the real agenda behind the "local" politics
and how outside influencers pull the strings.
HINTS
> The more sauce, the better
> Use qresear.ch as a resource - 14mil+ 8kun articles (use F3 to refine searches)
> Don't dox yourself (stay anon or use a dif id's)
> Post digs from QR here too (links there only last a coupla weeks).
TOPICS
* BLM, Antifa, leaders/backers
* Seattle, Portland, Spokane
* govs, mayors, city councils
* draconian Covid-19 policies
* 2020, voting fraud
* ports, I-5 corridor, shipping
* drug-running, trafficking
* school boards, unions, other orgs/companies
* climate change agenda push
* Bill & Melinda Gates Foundation
* UN connections (Agenda 21, 2030)
''DIG ANONS DIG!''
Coastal Pac NW: OR & WA states
THIS THREAD is for deep digs on current DS activities in the Pac NW.
Goal: to reveal to NW citizens & others the real agenda behind the "local" politics
and how outside influencers pull the strings.
HINTS
> The more sauce, the better
> Use qresear.ch as a resource - 14mil+ 8kun articles
> Don't dox yourself (stay anon or use a dif id's)
> Post digs from QR here too (links there only last a coupla weeks).
TOPICS
* BLM, Antifa, leaders/backers
* Seattle, Portland, Spokane
* govs, mayors, city councils
* draconian Covid-19 policies
* 2020, voting fraud
* ports, I-5 corridor, shipping
* drug-running, trafficking
* school boards, unions, other orgs/companies
* climate change agenda push
* Bill & Melinda Gates Foundation
* UN connections (Agenda 21, 2030)
''DIG ANONS DIG!''
Coastal Pac NW: OR & WA states
THIS THREAD is for deep digs on current DS activities in the Pac NW.
Goal: to reveal to NW citizens & others the real agenda behind the "local" politics.
HINTS
> The more sauce, the better
> Use qresear.ch as a resource - 14mil+ 8kun articles
> Don't dox yourself (stay anon or use a dif id's)
> Post digs from QR here too (links there only last a coupla weeks).
TOPICS
* BLM, Antifa, leaders/backers
* Seattle, Portland, Spokane
* govs, mayors, city councils
* draconian Covid-19 policies
* 2020, voting fraud
* ports, I-5 corridor, shipping
* drug-running, trafficking
* school boards, unions, other orgs/companies
* climate change agenda push
* Bill & Melinda Gates Foundation
* UN connections (Agenda 21, 2030)
''DIG ANONS DIG!''
Coastal Pac NW: OR & WA states
THIS THREAD is for deep digs on current DS activities in the Pac NW.
Goal: to reveal to NW citizens & others the real agenda behind the "local" politics.
HINTS
> The more sauce, the better
> Use qresear.ch as a resource - 14mil+ 8kun articles
> Don't dox yourself (stay anon or use a dif id's)
> Post digs from QR here too (links there only last a coupla weeks).
TOPICS
* BLM, Antifa, leaders/backers
* Seattle, Portland, Spokane
* govs, mayors, city councils
* draconian Covid-19 policies
* 2020, voting fraud
* ports, I-5 corridor, shipping
* drug-running, trafficking
* school boards, unions, other orgs/companies
* climate change agenda push
* Bill & Melinda Gates Foundation
* UN connections (Agenda 21, 2030)
''DIG ANONS DIG!''
Coastal Pacific NW: OR & WA states
''OPPOSE the attempted DS takeover of NW Blue States''
''EXPOSE the groups trying to destroy our liberty''
Information Warfare at its finest!!!
Local gov'ts are supposed to focus on the wants & needs of citizen at the state level and below.
But the DS has been infiltrating local govt's to promote a globalist agenda for decades
promoting globalist governors, mayors, city councils, DA's and other local officials
What's happening right now in cities like Seattle and Portland
reveals the next phase of decades-long plans to implement globalist plans at a local level
[Pincer action: top-down (UN Agenda 21/2020) and bottom-up (fake grassroots orgs)]
TOPICS
-
BLM, Antifa, leaders/backers
-
Seattle, Portland, Spokane
-
govs, mayors, DAs, city councils
-
law & order (police, prisons, etc.)
-
free speech, gun rights
-
K-12 & higher education
-
draconian edicts/policies (CV-19, etc.)
-
2020, voting fraud
-
ports, I-5 corridor, trafficking
-
school boards, unions, other orgs/companies
-
climate change agenda push
-
Bill & Melinda Gates Foundation
-
Int'l connections (UN Agenda 21, 2030), sister cities
''DIG ANONS DIG!''
Coastal Pacific NW: OR & WA states
''OPPOSE the attempted DS takeover of NW Blue States''
''EXPOSE the groups trying to destroy our liberty''
Information Warfare at its finest!!!
Local gov't is supposed to focus on the wants & needs of citizen at the state level and below.
But the DS has been infiltrating local govt's to promote a globalist agenda for decades - promoting globalist governors, mayors, city councils, DA's and other local officials
What's happening right now in cities like Seattle and Portland reveals the next phase of decades-long plans to implement globalist plans at a local level
Pincer action: ''top-down (UN Agenda 21/2020) and bottom-up (fake grassroots orgs)
TOPICS
-
BLM, Antifa, leaders/backers
-
Seattle, Portland, Spokane
-
govs, mayors, DAs, city councils
-
law & order (police, prisons, etc.)
-
free speech, gun rights
-
K-12 & higher education
-
draconian edicts/policies (CV-19, etc.)
-
2020, voting fraud
-
ports, I-5 corridor, trafficking
-
school boards, unions, other orgs/companies
-
climate change agenda push
-
Bill & Melinda Gates Foundation
-
Int'l connections (UN Agenda 21, 2030), sister cities
''DIG ANONS DIG!''
Coastal Pacific NW: OR & WA states
''OPPOSE the attempted DS takeover of NW Blue States''
''EXPOSE the groups trying to destroy our liberty''
Information Warfare at its finest!!!
Local gov't is supposed to focus on the wants & needs of citizen at the state level and below.
But the DS has been infiltrating local govt's to promote a globalist agenda for decades -
pushing globalist governors, mayors, city councils, DA's and other local officials.
What's happening right now in cities like Seattle and Portland
reveals the next phase of decades-long plans to implement globalist plans at a local level.
It's a pincer op: combines top-down strategies (UN Agenda 21/2020)
with bottom-up activities by (fake) grassroots orgs.
TOPICS
-
BLM, Antifa, leaders/backers
-
Seattle, Portland, Spokane
-
govs, mayors, DAs, city councils
-
law & order (police, prisons, etc.)
-
climate change agenda push
-
subverting K-12 & higher education
-
draconian edicts/policies (CV-19, etc.)
-
2020 election, main-in voting fraud
-
ports, I-5 corridor, trafficking
-
Bill & Melinda Gates Foundation
-
Int'l connections (UN Agenda 21, 2030), sister cities
''DIG ANONS DIG!''
Coastal Pacific NW: OR & WA states
''OPPOSE the attempted DS takeover of NW Blue States''
Local gov't is supposed to focus on the wants & needs of citizen at the state level and below.
But the DS has been infiltrating local govt's to promote a globalist agenda for decades -
pushing globalist governors, mayors, city councils, DA's and other local officials.
What's happening right now in cities like Seattle and Portland
reveals the next phase of the plan to implement globalist plans at a local level.
It's a pincer op: combines top-down strategies (UN Agenda 21/2020)
with bottom-up activities by (fake) grassroots orgs entirely controlled by higher-ups.
IT'S TIME TO EXPOSE THE LIE!
TO REVEAL the groups trying to destroy our liberty from the ground-up.
Information Warfare at its finest!!
TOPICS
-
BLM, Antifa, leaders/backers
-
Seattle, Portland, Spokane
-
govs, mayors, DAs, city councils
-
law & order (police, prisons, etc.)
-
climate change agenda push
-
subverting K-12 & higher education
-
draconian edicts/policies (CV-19, etc.)
-
2020 election, main-in voting fraud
-
ports, I-5 corridor, trafficking
-
Bill & Melinda Gates Foundation
-
Int'l connections: UN Agenda 21/2030, Strong Cities Network, Soros' OSF
''DIG ANONS DIG!''
Coastal Pacific NW: OR & WA states
''OPPOSE the attempted DS takeover of NW Blue States''
Local gov't is supposed to focus on the wants & needs of citizen at the state level and below.
But the DS has been infiltrating local govt's to promote a globalist agenda for decades -
pushing globalist governors, mayors, city councils, DA's and other local officials.
What's happening right now in cities like Seattle and Portland
reveals the next phase of the plan to implement globalist plans at a local level.
It's a pincer op: combines top-down strategies (UN Agenda 21/2020) with bottom-up activities by (fake) grassroots orgs entirely controlled by higher-ups.
IT'S TIME TO EXPOSE THE LIE!
TO REVEAL the groups trying to destroy our liberty from the ground-up.
Information Warfare at its finest!!
TOPICS
-
BLM, Antifa, leaders/backers
-
Seattle, Portland, Spokane
-
govs, mayors, DAs, city councils
-
law & order (police, prisons, etc.)
-
climate change agenda push
-
subverting K-12 & higher education
-
draconian edicts/policies (CV-19, etc.)
-
2020 election, main-in voting fraud
-
ports, I-5 corridor, trafficking
-
Bill & Melinda Gates Foundation
-
Int'l connections: UN Agenda 21/2030, Strong Cities Network, Soros' OSF
''DIG ANONS DIG!''
Coastal Pacific NW: OR & WA states
''OPPOSE the attempted DS takeover of NW Blue States''
Local gov't is supposed to focus on the wants & needs of citizen at the state level and below.
But the DS has been infiltrating local govt's to promote a globalist agenda for decades -
pushing globalist governors, mayors, city councils, DA's and other local officials.
What's happening right now in cities like Seattle and Portland
reveals the next phase of the plan to implement globalist plans at a local level.
It's a pincer op: combines top-down strategies (UN Agenda 21/2020) with bottom-up activities by (fake) grassroots orgs entirely controlled by higher-ups.
IT'S TIME TO EXPOSE THE LIE!
TO REVEAL the groups trying to destroy our liberty from the ground-up.
Information Warfare at its finest!!
TOPICS
-
BLM, Antifa, leaders/backers
-
Seattle, Portland, Spokane
-
govs, mayors, DAs, city councils
-
law & order (police, prisons, etc.)
-
climate change agenda push
-
subverting K-12 & higher education
-
draconian edicts/policies (CV-19, etc.)
-
2020 election, main-in voting fraud
-
ports, I-5 corridor, trafficking
-
Bill & Melinda Gates Foundation
-
Int'l connections: UN Agenda 21/2030, Strong Cities Network, Soros' OSF
''DIG ANONS DIG!''
Oregon, Washington, I-5 Corridor: Turn the Tide, ANONS DIG
NW States Aflame!
STOP the burning NOW
NW anons, it's time to take back our cities, counties and states.
Our local gov'ts are supposed to focus on the rights of citizen at the state level and below.
But the DS has been infiltrating local govt's to promote a globalist agenda for decades -
pushing globalist governors, mayors, city councils, DA's and other local officials.
What's happening right now in cities like Seattle and Portland
reveals the next phase of the plan to implement globalist plans at a local level.
It's a pincer op: combines top-down strategies (UN Agenda 21/2020) with bottom-up activities by (fake) grassroots orgs entirely controlled by higher-ups.
TIME TO EXPOSE THE TRUTH!
TO REVEAL the groups & individuals trying to destroy our liberty from the ground-up.
Information Warfare at its finest!!
TOPICS
-
BLM, Antifa, leaders/backers
-
Seattle, Portland, Spokane
-
govs, mayors, DAs, city councils
-
law & order (police, prisons, etc.)
-
climate change agenda push
-
subverting K-12 & higher education
-
draconian edicts/policies (CV-19, etc.)
-
2020 election, main-in voting fraud
-
ports, I-5 corridor, trafficking
-
Bill & Melinda Gates Foundation
-
Int'l connections: UN Agenda 21/2030, Strong Cities Network, Soros' OSF
''DIG ANONS DIG!''
Oregon, Washington, I-5 Corridor: Turn the Tide, ANONS DIG
NW States Aflame!
STOP the burning NOW
NW anons, it's time to take back our cities, counties and states.
Our local gov'ts are supposed to focus on the rights of citizen at the state level and below.
But the DS has been infiltrating local govt's to promote a globalist agenda for decades -
pushing globalist governors, mayors, city councils, DA's and other local officials.
What's happening right now in cities like Seattle and Portland
reveals the next phase of the plan to implement globalist plans at a local level.
It's a pincer op: combines top-down strategies (UN Agenda 21/2020) with bottom-up activities by (fake) grassroots orgs entirely controlled by higher-ups.
TIME TO EXPOSE THE TRUTH!
TO REVEAL the groups & individuals trying to destroy our liberty from the ground-up.
Information Warfare at its finest!!
TOPICS
-
BLM, Antifa, leaders/backers
-
Seattle, Portland, Spokane
-
govs, mayors, DAs, city councils
-
law & order (police, prisons, etc.)
-
climate change agenda push
-
subverting K-12 & higher education
-
draconian edicts/policies (CV-19, etc.)
-
2020 election, main-in voting fraud
-
ports, I-5 corridor, trafficking
-
Bill & Melinda Gates Foundation
-
Int'l connections: UN Agenda 21/2030, Strong Cities Network, Soros' OSF
''DIG ANONS DIG!''
Oregon, Washington, I-5 Corridor: Turn the Tide, ANONS DIG
NW States Aflame!
STOP the burning NOW
NW anons, it's time to take back our cities, counties and states.
Our local gov'ts are supposed to focus on the rights of citizen at the state level and below.
But the DS has been infiltrating local govt's to promote a globalist agenda for decades -
pushing globalist governors, mayors, city councils, DA's and other local officials.
What's happening right now in cities like Seattle and Portland
reveals the next phase of the plan to implement globalist plans at a local level.
It's a pincer op: combines top-down strategies (UN Agenda 21/2020) with bottom-up activities by (fake) grassroots orgs entirely controlled by higher-ups.
TIME TO EXPOSE THE TRUTH! TO REVEAL the groups & individuals trying to destroy our liberty from the ground-up.
Information Warfare at its finest!!
TOPICS
-
BLM, Antifa, leaders/backers
-
Seattle, Portland, Spokane
-
govs, mayors, DAs, city councils
-
law & order (police, prisons, etc.)
-
climate change agenda push
-
subverting K-12 & higher education
-
draconian edicts/policies (CV-19, etc.)
-
2020 election, main-in voting fraud
-
ports, I-5 corridor, trafficking
-
Bill & Melinda Gates Foundation
-
Int'l connections: UN Agenda 21/2030, Strong Cities Network, Soros' OSF
''DIG ANONS DIG!''
Oregon, Washington, I-5 Corridor: Turn the Tide, ANONS DIG
NW States Aflame!
STOP the burning NOW
NW anons, it's time to take back our cities, counties and states.
Our local gov'ts are supposed to focus on the rights of citizen at the state level and below.
But the DS has been infiltrating local govt's to promote a globalist agenda for decades -
pushing globalist governors, mayors, city councils, DA's and other local officials.
What's happening right now in cities like Seattle and Portland
reveals the next phase of the plan to implement globalist plans at a local level.
It's a pincer op: combines top-down strategies (UN Agenda 21/2020) with bottom-up activities by (fake) grassroots orgs entirely controlled by higher-ups.
TIME TO EXPOSE THE TRUTH! TO REVEAL the groups & individuals trying to destroy our liberty from the ground-up.
Information Warfare at its finest!!
TOPICS
-
BLM, Antifa, leaders/backers
-
Seattle, Portland, Spokane
-
govs, mayors, DAs, city councils
-
law & order (police, prisons, etc.)
-
climate change agenda push
-
subverting K-12 & higher education
-
draconian edicts/policies (CV-19, etc.)
-
2020 election, main-in voting fraud
-
ports, I-5 corridor, trafficking
-
Bill & Melinda Gates Foundation
-
Int'l connections: UN Agenda 21/2030, Strong Cities Network, Soros' OSF
''DIG ANONS DIG!''
Oregon, Washington, I-5 Corridor: Turn the Tide, ANONS DIG
NW States Aflame!
STOP the burning NOW
NW anons, it's time to take back our cities, counties and states.
Our local gov'ts are supposed to focus on the rights of citizen at the state level and below.
But the DS has been infiltrating local govt's to promote a globalist agenda for decades -
pushing globalist governors, mayors, city councils, DA's and other local officials.
What's happening right now in cities like Seattle and Portland
reveals the next phase of the plan to implement globalist plans at a local level.
It's a pincer op: combines top-down strategies (UN Agenda 21/2020) with bottom-up activities by (fake) grassroots orgs entirely controlled by higher-ups.
TIME TO EXPOSE THE TRUTH!
TIME to REVEAL the groups & individuals trying to destroy our liberty from the ground-up.
Information Warfare at its finest!!
TOPICS
-
BLM, Antifa, leaders/backers
-
Seattle, Portland, Spokane
-
govs, mayors, DAs, city councils
-
law & order (police, prisons, etc.)
-
climate change agenda push
-
subverting K-12 & higher education
-
draconian edicts/policies (CV-19, etc.)
-
2020 election, main-in voting fraud
-
ports, I-5 corridor, trafficking
-
Bill & Melinda Gates Foundation
-
Int'l connections: UN Agenda 21/2030, Strong Cities Network, Soros' OSF
''DIG ANONS DIG!''
Oregon, Washington, I-5 Corridor: Turn the Tide, ANONS DIG
NW States Aflame!
STOP the burning NOW
NW anons, it's time to take back our cities, counties and states.
Our local gov'ts are supposed to focus on the rights of citizen at the state level and below.
But the DS has been infiltrating local govt's to promote a globalist agenda for decades -
pushing globalist governors, mayors, city councils, DA's and other local officials.
What's happening right now in cities like Seattle and Portland
reveals the next phase of the plan to implement globalist plans at a local level.
It's a pincer op: combines top-down strategies (UN Agenda 21/2020) with bottom-up activities by (fake) grassroots orgs entirely controlled by higher-ups.
TIME TO EXPOSE THE TRUTH!
TIME to REVEAL the groups & individuals trying to destroy our liberty from the ground-up.
Information Warfare at its finest!!
TOPICS
-
BLM, Antifa, leaders/backers
-
Seattle, Portland, Spokane
-
govs, mayors, DAs, city councils
-
law & order (police, prisons, etc.)
-
climate change agenda push
-
subverting K-12 & higher education
-
draconian edicts/policies (CV-19, etc.)
-
2020 election, main-in voting fraud
-
ports, I-5 corridor, trafficking
-
Bill & Melinda Gates Foundation
-
Int'l connections: UN Agenda 21/2030, Strong Cities Network, Soros' OSF
''DIG ANONS DIG!''
ATTN anons from Washington & Oregon
and everyone else too.
NEWWA and OREGON Information Warfare Thread
>>>/comms/xxxxxx
On the attempted revolution
by communist, anarchist & other lawless groups
bent on destroying our freedom
at the regional, state, county & city level
Post NW breaking news here first
''then copy to thread''
so we canDIG DEEPand createMEMES
to out the perps and support the sane people still LEFT
on the NW Left Coast.
ATTN anons from Washington & Oregon
and everyone else too!
NEWWA and OREGON Information Warfare Thread
On the attempted revolution by communist, anarchist & other lawless groups
bent on destroying our freedom at the regional, state, county & city level
Post NW breaking news here first
''then copy to thread''
so we canDIG DEEPand createMEMES
to out the perps and support the sane people still LEFT
on the NW Left Coast.
ATTN anons from Washington & Oregon
and everyone else too!
NEWWA and OREGON Information Warfare Thread
On the attempted revolution by communist, anarchist & other lawless groups
bent on destroying our freedom at the regional, state, county & city level
Post NW breaking news here first
''then copy to thread''
so we canDIG DEEPand createMEMES
to out the perps and support the sane people still LEFT
on the NW Left Coast.
https://8kun.top/comms/res/1903.html#q21177
https://8kun.top/comms/res/1903.html#q21181
ATTN anons from Washington & Oregon
and everyone else too!
NEW THREAD:
WA, OREGON, I-5 CORRIDOR - Turn the Tide Thread
Oregon and Washington are under attack
by groups bent on destroying our freedom at the regional, state, county & city level
Let'sDIG DEEPand createMEMES
to combat this attack.
We know that BLM and ANTIFA are the enemy
But what are the specific groups involved?
-
What are their /comms/?
-
Who are the leaders?
-
Who does the funding and how is the $ passed down/laundered?
-
What's the role of public officials like the mayors of Seattle and Portland?
-
How are those public officials linked to known DS entities?
-
What's the link between local govt's and the UN? (Agenda 21/2030)
STEP BY STEP
1 - Post NW breaking news here first, then copy to thread
2 - Consolidate the info to see what it shows
3 - Develop a flowchart that maps it all out
4 - Get the word out to Defang the Beast
We can work together to TURN THE TIDE
Let the public know what's really going on
Save the coastal Pacific Northwest from the
tyrants
who have invaded our lives.
Help turn the Pacific NorthLeft Coast into the Pacific NorthWest Coast again
ATTN anons from Washington & Oregon
and everyone else too!
NEW THREAD:
WA, OREGON, I-5 CORRIDOR - Turn the Tide Thread
Oregon and Washington are under attack
by groups bent on destroying our freedom at the regional, state, county & city level
Let'sDIG DEEPand createMEMES
to combat this attack.
We know that BLM and ANTIFA are the enemy
But what are the specific groups involved?
-
What are their /comms/?
-
Who are the leaders?
-
Who does the funding and how is the $ passed down/laundered?
-
What's the role of public officials like the mayors of Seattle and Portland?
-
How are those public officials linked to known DS entities?
-
What's the link between local govt's and the UN? (Agenda 21/2030)
STEP BY STEP
1 - Post NW breaking news here first, then copy to thread
2 - Consolidate the info to see what it shows
3 - Develop a flowchart that maps it all out
4 - Get the word out to Defang the Beast
We can work together to TURN THE TIDE
Let the public know what's really going on
Save the coastal Pacific Northwest from the
tyrants
who have invaded our lives.
Help turn the Pacific NorthLeft Coast into the Pacific NorthWest Coast again
ATTN anons from Washington & Oregon
and everyone else too!
NEW THREAD:
WA, OREGON, I-5 CORRIDOR - Turn the Tide Thread
Oregon and Washington are under attack
by groups bent on destroying our freedom at the regional, state, county & city level
Let'sDIG DEEPand createMEMES
to combat this attack.
We know that BLM and ANTIFA are the enemy
But what are the specific groups involved?
-
What are their /comms/?
-
Who are the leaders?
-
Who does the funding and how is the $ passed down/laundered?
-
What's the role of public officials like the mayors of Seattle and Portland?
-
How are those public officials linked to known DS entities?
-
What's the link between local govt's and the UN? (Agenda 21/2030)
STEP BY STEP
1 - Post NW breaking news here first, then copy to thread
2 - Consolidate the info to see what it shows
3 - Develop a flowchart that maps it all out
4 - Get the word out to Defang the Beast
We can work together to TURN THE TIDE
Let the public know what's really going on
Save the coastal Pacific Northwest from the
tyrants
who have invaded our lives.
Help turn the Pacific NorthLeft Coast into the Pacific NorthWest Coast again
ATTN anons from Washington & Oregon
and everyone else too!
NEW THREAD:
=='''WA, OREGON, I-5 CORRIDOR -
Turn the Tide Thread'''==
Oregon and Washington are under attack
by groups bent on destroying our freedom at the regional, state, county & city level
Let'sDIG DEEPand createMEMES
to combat this attack.
We know that BLM and ANTIFA are the enemy
But what are the specific groups involved?
-
What are their /comms/?
-
Who are the leaders?
-
Who does the funding and how is the $ passed down/laundered?
-
What's the role of public officials like the mayors of Seattle and Portland?
-
How are those public officials linked to known DS entities?
-
What's the link between local govt's and the UN? (Agenda 21/2030)
STEP BY STEP
1 - Post NW breaking news here first, then copy to thread
2 - Consolidate the info to see what it shows
3 - Develop a flowchart that maps it all out
4 - Get the word out to Defang the Beast
We can work together to TURN THE TIDE
Let the public know what's really going on
Save the coastal Pacific Northwest from the
tyrants
who have invaded our lives.
Help turn the Pacific NorthLeft Coast into the Pacific NorthWest Coast again
ATTN anons from Washington & Oregon
and everyone else too!
NEW THREAD:
'''WA, OREGON, I-5 CORRIDOR -
Turn the Tide Thread'''
Oregon and Washington are under attack
by groups bent on destroying our freedom at the regional, state, county & city level
Let'sDIG DEEPand createMEMES
to combat this attack.
We know that BLM and ANTIFA are the enemy
But what are the specific groups involved?
-
What are their /comms/?
-
Who are the leaders?
-
Who does the funding and how is the $ passed down/laundered?
-
What's the role of public officials like the mayors of Seattle and Portland?
-
How are those public officials linked to known DS entities?
-
What's the link between local govt's and the UN? (Agenda 21/2030)
STEP BY STEP
1 - Post NW breaking news here first, then copy to thread
2 - Consolidate the info to see what it shows
3 - Develop a flowchart that maps it all out
4 - Get the word out to Defang the Beast
We can work together to TURN THE TIDE
Let the public know what's really going on
Save the coastal Pacific Northwest from the
tyrants
who have invaded our lives.
Help turn the Pacific NorthLeft Coast into the Pacific NorthWest Coast again
BAKING RESOURCES
Baker's grab bag
* Baker's Tools app (Version 0.7.2) Baker Tools v0.7.2: >>9584, >>9597, >>9601 https://pastebin.com/L1p6iRzZ
* Baker's Tools Lite (stripped down, good for baking) >>14523, https://pastebin.com/pUVCTeCG
* Try Atom as a text editor for Macs >>6925, >>6934, >>7055, >>7070
* Meme-making app kek.gg >>8771
* Crazy Bakes: wonky board, lags, baking from Index, "flood detected", dup breads >>9960
* How's your mouse for baking? >>10617
* Font used for baking school slides >>10642, https://www.dafontfree.net/find.php?q=impact
* Quik Pic bake instructions >>7549
* Original baking video >>7076 (shows how to make room for new notables)
* Overcoming paywalls >>10844
* Pastebin.com problems & alternatives >>11645, >>11609, >>11619, >>11620, >>11627, >>11640
* How to Control-F on androids & IOS devices >>13566, >>13567
* How to do a keyword search when /qresearch/ is down >>13696
* Past bread archive for /qresearch/: https://qanon.news/Archives
Dealing with notables
* Note-taking roles: baker, note collector, helper anon, posters >>14921
* Ten Baker Tips for Notables >>8177
* Bakers on what they look for in notables >>8351, >>8315, >>8698
* Muh Collector "how to" on notables >>9006, >>9009
* Anon tips for better notables >>>/qrb/41937, https://pastebin.com/yq7wQyvn
* Long notables; Asking anons to state main point >>13633, >>8237
* Asking anons to state the main point
* Advanced Google searching protocols https://pastebin.com/raw/JuK0xUDb
'''* NEW: 15 kinds of sauce (evidence) that make a notable noteworthy >>9655
Free image/video screenshots, download, production tools
* Image screenshots PrtSc/snipping tool + MS-Paint https://youtu.be/KvXxCE1gxOE
* 8kun video limits (~16mg) >>8760
* Bandicam Screen Recorder >>8759, >>8762 (also: OBS, Kdenlive, Audacity)
* YouTube & Twitter (downloads plus cutting scenes from YT) >>14306
* Video downloaders: >>14237, https://www.downloadhelper.net/ ; Firefox/Opera: - https://technologyto.com/extractor.html
* VLC Player >>8714, >>8715, >>8766
* Windows Movie Maker for Win 10 >>8712
* NVidia cards (can screen-capture vids) >>8785
* Forensically (forensics magnifier) https://29a.ch/photo-forensics/#forensic-magnifier
* ShotCut NLE (open source cross platform video editor) https://shotcut.org/
* MFFmpeg (decodes & plays any format) https://ffmpeg.org/
* Natron (cross-platform video compositor) https://natrongithub.github.io/
* Handbrake (good for transcoding) https://handbrake.fr/
* GIMP & GMIC (image editing) http://gmic.eu/gimp.shtml
* Invidio (copies YT vids, restricted or not, no ads or signup) >>8792
* NEW: Avidemux.org, VideoSmaller.Com (apps for making large files smaller) >>18286
'''* NEW: , >>9655(reduces file size w/good quality)
Baker tips IRL
>>8829 Baker's Tips - Read me first
>>6331 #01 - Ghosting a bred
>>6331 #02 - Baker changes
>>6378 #03 - TOR baking
>>6651 #04 - Defeating shills with facts & humor
>>7339 #05 - Announce you're baking (#11 too)
>>6892 #06 - Baking/note-taking protocols
>>7181 #07 - Use RED TEXT and BOLD in handoffs
>>7363 #08 - Try to notice when a cat is baking
>>13038 #09 - Respecting other bakers' notables
>>8174 #10 - Make sure to copypasta the whole page
>>8803 #11 - Announce you're taking responsibility
>>8822 #12 - Embed baker changes to provide more info
>>8824 #13 - Watch out for unknown bakers bearing gifts
>>8825 #14 - Use named pastebins to defeat shill complaints
>>8826 #15 - Responding to shills trying to suck up baker's time
>>8827 #16 - Be aware of muh joos bakers
>>8828 #17 - All bakers screw up
>>10445 #18 - Just do it--bake!
>>9590 #19 - Don't be afraid to bake
>>10789 #20 - Post notes early so changes can be made
>>10791 #21 - No /comms/ creates misunderstandings
>>10792 #22 - Defeat shills with humor
>>14835 #23 - Keep notables [from different bakers] separate
>>14836 #24 - Make sure to ask for Handoff Confirmed
>>14801 #25 - Don't fuck with the wrong baker [take a look - funny]
>>15894 #26 - Ignore end-of-bread antics
Role of good comms to create a smooth bake
These are the thoughts of ONE BAKER, but reflect the experience of many. They are not rules but rules of thumb. But should be helpful for new bakers. Others bakers, plz chime in.
Generally:
1. Good comms matter. They prevent a lot of confusion (e.g., who is baking, when a handoff is needed, etc.). They also keep the board "happy" and things running smoothly.
2. Lack of attention to comms creates frustration for anons and also gives shills ammo against the kitchen.
3. Taking the time to cultivate good comms makes everything run more smoothly for bakers, note collectors, and anons.
We had a tussle last night over "who's baking" - here's my reconstruction of what happened (correct me if i'm wrong on anything - pretty complicated):
#12992
baker f88 relieves tired baker relief, confirms handoff @500 but relieving baker adds no new notes.
#12993
-
b gets complaints for rejecting a multiply-sauced news item based on a hunch and rudeness (e.g. >>>/qresearch/10151956, >>>/qresearch/10152090)
-
collects 5 notes total including "Shills are weak today" (in response to complaints?)
-
shills take advantage (e.g., >>>/qresearch/10152469). Then no Fresh link (what, no time?)
#12994
-
at dough, anons unhappy; "kitch offer stands"; another baker (bokeh?) confirms it wo/ceremony - does not respect f88 >>>/qresearch/10152516
-
but f88 does not acknowledge. But DOES at collect more notables than previously.
-
posts FRESH here >>>/qresearch/10153267
-
but other baker also bakesβ¦..
#12995 (one of em is labeled #12993 by mistake)
-
dueling doughs which both go to 751. f88's #12995 bread and bokeh baker's #12993 bread (balls of steel ed - 75112995).
-
in #12995, there are posts redirecting to bokeh's bake (e.g., >>>/qresearch/10154517)
(- f88 has no fresh but does bake a bread w/number but no title: #12996)
-
in #12993, baker must leave; another baker attempts to pick up the bake >>>/qresearch/10154250, >>>/qresearch/10154287 but offers no bin; baker rebuttal saying "i've still got the bake" : >>>/qresearch/10154339; other baker then tries to reconcile >>>/qresearch/10154567 but no response - prob coz baking offer looked sneaky)
-
#12995's fresh is here: >>>/qresearch/10154515 (links to #12996 - attack shills suck balls of steel)
#12996
-
dueling doughs again: - f88's and bokeh's.
-
bokeh bred: he hands off to wnb >>>/qresearch/10154870; another baker says he'll grab f88 bread and direct anons to bokeh bread - which he did.
-
#12997 breads merged again.
= = = = =
Summary:
-
f88 did not hijack a bread - received legit handoff in #12992 (I was handoff baker so that's solid)
-
but he royally pissed off anons with his attitude and v short notables list in #12993
-
result was that baker in #12994 "took" the standing offer bc f88 no longer had anons' trust
-
f88 would not give way (his right) but didn't apologize to anons either - so didn't win their support
-
f88 tried to work it out but only after a sneaky handoff offer (to be fair, not 100% sure it was him)
-
seeing this and anon comments, bakers arriving later did not back him
-
when f88 finally handed off, the relief baker went for a merge with other baker's bread.
To f88 if you're around: Purpose of documenting this wasn't to dump on you but to defeat shill narrative that there are now two kitch factions warring for dominance.
Not true - it's was always just you vs anons/other bakers.
Anons and bakers want to give support but it's a two-way street.
Lots of food for thought here.
MINI-COMMS PRESENTATION
>>21400 Role of good comms to create a smooth bake
>>21402 New baker comms
>>21406 Four kind of comms: COMMS w/BO, BAKERS, NOTE COLLECTORS, ANONS
>>21410 BO/BV comms
>>21413 COMMS with OFF-DUTY BAKERS
>>21880 COMMS with NOTE COLLECTORS
>>21422 COMMS with ANONS
>>21436 In a nutshell, good comms are as important to baking as actual baking and collecting notes
Global Announcements
None at this time.
Notables are NOT endorsements
#13036
>>10187311 Former Google Engineer Anthony Levandowski Sentenced to Prison in Trade-Secret Theft Case
>>10187289 MSNBC Producer QUITS: We Block 'Diversity of Thought,' Amplify 'Fringe Voices and Events'
>>10187301 Demsβ demand for βslush fundβ in aid package threatens to derail PPP extension
>>10187284 SHOCK: CBS Experiment Proves Mail-In Ballots Could Be a Disaster
>>10187278 Shock: NBC Admits New Yorkβs Mail-In Ballot System Is a βFiascoβ
>>10187130 Blast aftermath and Possible Connections Bun
>>10187002 COVID-19 'propaganda campaign' by Canadian Armed Forces leads to investigation
>>10186929 Missing Fort Riley warrant officer found dead in Kansas hiking area
>>10186840 At least 100 dead, more than 4,000 injured in Beirut explosion: Lebanese Red Cross official
>>10186823 Navy to Remove Aft Mast on USS Bonhomme Richard This Week in βAbundance of Cautionβ
>>10186814 US Could Bring More Than 4,000 Troops Home From Afghanistan by Election Day: Trump
>>10186800 Chrissy Teigen delivers pizza to photographers. Did she make a deal ? Comms ?
>>10186797 18-Year-Old Accused of Igniting Explosive, Tossing it into Federal Courthouse in Portland, Injuring Marshal
>>10186772 McEnany Scorches Democrats Over Crime Surges In Cities After βDefund The Policeβ Calls: βThere Are Consequencesβ
>>10186762 Cruz Humiliated Hirono, βTask Force on Violent Anti-Government Extremismβ Explained, Democrat Storms Out
>>10186746 UK ANON finds MITT ROMNEY link to CLEAR CHANNEL and BLACK BOX seen in Q LONDON PIC
>>10186640 Mad Dog Mattis Commercial In Washington State Pushing Mask Wearing (video)
>>10187368 #13036
#13035
Baker Change
>>10186563 Army releases footage of new hypersonic missile
>>10186290 Australian MSM pushing fines for Covid-19 conspiracy theorists
>>10186256 Pompeo Extends Condolences to former PM Hariri after Beirut Blast
>>10186089 βA Violent Institutionβ: These Celebrities Are Funding The βDefund The Policeβ Movement
>>10186053 The Circle Of Death: Bankrupt Companies "Unfile" To Receive Government Bailouts, Then Immediately File Again
>>10185947 Netanyahu Warned the United Nations of Iranian Missile Stockpiles in Beirut Back in 2018
>>10185941 POTUS Schedule for Wednesday, August 5, 2020
>>10185928 Morning of August 4th near Wuhan (video)
>>10185873 Your Phone Is Spying On You: Companies Are Generating Secret "Surveillance Scores" Based On That Data
>>10186586 #13035
#13034
>>10185714 Washington State Election Results
>>10185685 Another detailed thread on best science on efficacy of masks
>>10185678, >>10185691 POTUS talking to the board again? "Charles Q. Charles Q Brown Jr, I like that"
>>10185636 Dem Pramila Jayapal advances to Nov election in Washington's 7th congressional district
baker from ghost
>>10185594, >>10185605, >>10185619 PM Hawkins Malipodβ’ and Serco diggs
>>10185576 Peter Meijer wins Repub. Primary for House Seat in Michigan's 3rd congressional district
>>10185541 Cook County Board on Thursday passed a resolution to defund policing & incarceration
>>10185199, >>10185332, >>10185401, >>10185429 Q4630 decode Shelter BIDEN
>>10185492 Short anon video for normie friends: HCQ works
>>10185373 Ex-Google exec sent to prison for stealing robocar secrets
>>10185372 Trump admin to send delegation to Taiwan, the highest level visit in 4 decades
>>10185418, >>10185448 Sally Yates memes
>>10185347 Sperry article: "Sally Yates was the real blackmailer". From May 11,2020
>>10185330 'Obey' transfers for masks
>>10185276 US Darknet Vendor & Costa Rican Pharmacist Charged with Narcotics & Money Laundering
>>10185222 Kodak stock update
>>10185212 Gov. Whitmer orders crackdown on COVID-19 violators
ghost bread, note-taker
>>10185203 NEW: Attkisson v. Rosenstein for government computer intrusions
>>10185125 Antifa get escorted off of private property at gunpoint
>>10185499 Top 5 deadliest ammonium nitrate-related accidents
>>10185360, >>10185722 Past explosions for comparison
>>10185688, >>10185518, >>10185739 On Beruit II
>>10185246, >>10185334, >>10185470, >>10185476, >>10185631, >>10185684 On Beruit I
>>10185785 #13034
Previously Collected Notables
>>10187368 #13036,
>>10185198 #13033, >>10185785 #13034, >>10186586 #13035
>>10182734 #13030, >>10185184 #13031, >>10185186 #13032
>>10180398 #13027, >>10181178 #13028, >>10181941 #13029
Notables Aggregators: https://wearethene.ws & https://qnotables.com
LIVE Baking Seminar
9/3/2020
We in here
Welcome To LIVE Baking Classes in the Q Research Utility Kitchen
We hold these truths to be self-evident: that all men are created equal; that they are endowed by their Creator with certain unalienable rights; that among these are life, liberty, and the pursuit of happiness.
We are the bakers who provide the breads for those anons who post Qresearch's open-sourced information, reasoned argument, and dank memes. We do battle in the sphere of baking ideas and baking ideas only. We neither need nor condone the use of force in our work here.
=VINCIT OMNIA VERITAS=
=SEMPER FIDELIS=
=WWG1WGA=
INTRO TO BAKING
Qresearch is a 24/7 beehive of activity where anons post their diggs, memes and prayers.
For this to happen requires ''bakers''βwhich is why they have been called "the core of this board."
Bakers perform several key functions:
* Set the tone for each bread via their choice of bread title and /comms/ with posters.
* Post notables for each bread.
* Bake breads (transition the board from one thread to the next).
* Knead the dough (keeping the resource pages clean, tidy, and up-to-date).
When all goes well, baking is a fun & exciting opportunity to serve. When things get wonky and shills attackβbakers carry on anyway.
Shadilay, fellow bakers!
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
General Announcements
* Baking Class in /comms/ every Thursday @7pm ET: practice baking, Q&A, all are welcome
* Baking class plan (so any baker can teach) >>11969, https://pastebin.com/gqfunWCR
* How to bake a baking seminar dough >>14289
* Too many threads problem - bakers be(a)ware >>15895
* Q-bin links qanonbin.com (vanwa), www2qanonbin.com (bitmitigate)
* Dough Revision >20538
Past Class links & archives
Links: >>6125 #1, >>6368 #2, >>6885 #3, >>7185 #4 , >>7568 #5, >>8274 #6, >>8872 #7, >>9320 #8, >>9787 #9, >>10510 #10, >>11086 #11, #12 >>11733, #13 >>13041, #14 >>13590, #15 >>14290, #16 >>14873, #17 >>15341, #18 >>15918, #19 >>16885, #20 >>17719, #21 >>18289, #22 >>18935, #23 >>19692, #24 >>20544, #25 >>21322, #26 >>21883, #27 >>22537
Archives: Classes #1 - #20: >>18934, #21 http://archive.vn/wip/NH1Ss, #22 http://archive.vn/olnuG, #23 http://archive.vn/enwhP, #24 https://8kun.top/comms/res/20544.html, #25 http://archive.vn/wip/AWhVb, #26 http://archive.vn/wip/3oSig
Step-by-Step Baking Instructions
>>17783 STEP 0 - Preparation
>>17797 STEP 1 - Find the Current Dough
>>17803 STEP 2 - Copy the Current Dough
>>17807 STEP 3 - Paste The Dough Into Text Editor ( >>17810 dough in Q-bin)
>>17815 STEP 3a - Trim The Notables Section
>>17822 STEP 3b - Make space for your New Notables
>>17831 STEP 4 - Create A New Thread
>>17837 STEP 5 - Enter Thread Info And Post Thread
>>17845 STEP 6 - Enter the Rest of the Dough
>>17863 STEP 7 - Make A New Pastebin & Make The Dough Post ( >>17868, >>17871, >>17875 Q-bin updates)
>>17876 STEP 8 - Post Your New Thread Link
Baking Overview & Extras
>>17777 Overview
>>17884 Linking between Boards
>>17894 Timing
>>14523 Baker's Tools Lite
>>16963 How to Bake When Q Posts >>16994, >>17015, >>17032, >>17037
NEW >>23326 Baking from the Index
E-BAKE Instructions
Baker Verification Mini-seminar, Class #23
>>23070 Why verify, ways to verify, what works & what doesn't
New Baker Checklist
>>23157 Eight things to know before going LIVE
>>23160 How to accept and make a handoff
>>23164 How to verify "who" you are when offering to bake >>23174
>>23175 How to format Notables page
>>23181 What to do if bread "hangs" (which it usually does)
>>23192 What to do if you screw up the bread number
>>23210 How to ghost a bread & pick up a ghost
>>23224 What to do if Q posts
>>23240 What to do if you don't know what to do >>23243
>>23254 Summary of Eight Steps
Updated notables moduleNEW
>>24091 Updated notables module - intro
>>24147 Notables overview/baker's considerations I
>>24165 Notables overview/baker's considerations II
>>24287 Types of possible notables
>>24301 What makes a perfect notable?
>>24314 How to log notables in your dough
>>24319 When to post notables updates in-thread
>>24360 What's a notables bun and how to make one
>>24394 Recap & question time
INFORMATION WARFARE RESOURCES
War Room
>>9967715 Q Research Meme Warfare Operations <- go here for current up to date ops
Get Everyone at ONCE and HIT 'Them' With Everything You Got! THINK PICARD MANUEVER! [POST STORM - THE WAVE]
[1] MEME MEME and MEME some MOAR! Stay Focused on Current HOTTOPICS
[2] Pick 2-3 hashes from the target area htps://www.trendolizer.com Hijack them to get your #hash out.
[3] Post @ 10-11Am | 12-3Pm | 6-9Pm EST
[4] Always Post meme or Cap
[5] Use .@them to respond to all their following.
[6] Remember to be Quirky in your posts.
[7] RT other's tweets
[8] ReTweet LASERFAST. Use https://tweetdeck.com
[9] Information WarFare https://archive.is/E0oJm
#WAKEUPAMERICA #FACTSMATTER #SAVEAMERICA #UNITEDNOTDIVIDED #WWG1WGA #Qanon
Meme Ammo
>>10582798 Memefarmer has resigned and Mega removed the Meme Warehouse. Will other anons pick up the torch?
>>10660694 Meme Overlay Thread - Bypassing Meme Censorship (Digital Camo project)
>>10639500 Social media warrior reports success: black box corner images not being censored
>>10601626, >>10602025, >>10602056, >>10602059, >>10602928 Meme Filter Busters
Tweet Tools
* Deleted Trump Tweets: https://factba.se/topic/deleted-tweets
* POTUS' Tweet Archive: trumptwitterarchive.com
* Twitter Video Downloader: http://twittervideodownloader.com/
Dedicated Research & Feedback Threads
>>10660694 Meme Overlay Thread - Bypassing Meme Censorship <<<< DUPLICATE - REMOVE???
>>6867253 Clockwork Qrange #10
>>1215912 Letters of gratitude (Q posted in #1025)
>>>/qrb/13005 Planefag Q+A (Planefagging 101)
>>>/qrb/42185 Boatfagging Q&A
>>>/comms/12299 Oregon, Washington, I-5 Corridor: Turn the Tide
META (for board admin queries) >>6064510
International Q Research Threads
Australia #9 >>10099681, Brasil/Portugal #1 >>10479225, Canada #7 >>9725975
France #1 >>8331823, Germany #66 >>10534771, Mexico #1 >>9133907
Nederland #5 >>10497699, New Zealand #5 >>10524823, Nordic #1 >>5290557
South Africa #1 >>8033191, UK #21 >>10507852
Sealed Indictments
Sealed Indictment Master: https://docs.google.com/spreadsheets/d/1kVQwX9l9HJ5F76x05ic_YnU_Z5yiVS96LbzAOP66EzA/edit#gid=1525422677
Sealed Indictment Master Files Backup: https://drive.google.com/open?id=1iBS4WgngH8u8-wAqhehRIWCVBQKD8-5Y
Searchable Indictment Map w/dockets, links & more: https://bad-boys.us/
Resignations
All Resignations Website https://www.resignation.info
All Posts Search Tool https://qresear.ch: 15mil+ anon posts from /qr/ & multiple research threads
Other Info War Tools
* Searchable Commercial Aviation Incident List: http://avherald.com
* Searchable Hussein WH visitor list: https://archive.org/details/WHvisitorlogs_2010-16_date
* Qcode Guide to Abbreviations: pastebin.com/UhK5tkgb
* Q Happenings Calendar 2018: https://mega.nz/#F!KPQiBJiY!dK3XRe4RYoXgWq_85u4-yg
* Stock Movement Scraper: http://qest.us (for seeing LARGE movements of $)
* Legal News: www.justice.gov/usao/pressreleases
* Federal Procurement Data System: https://www.fpds.gov/fpdsng_cms/index.php/en/
* Advanced Google Search Operators: https://ahrefs.com/blog/google-advanced-search-operators/
* Federal Judicial Court dataset from 93 Federal Districts - Searchable db: https://bad-boys.us/
* Catalog of US Government Publications: https://catalog.gpo.gov/F?RN=306384688
* Webpage Archiver: http://archive.md/
* Baker Tools v0.7.3: https://pastebin.com/EDmx2iEr
* Check Criminal Cases: https://www.justice.gov/usao/find-your-united-states-attorney
* Get your Q clocks anytime (0 - 59 min past posts): https://q-clock.com
Dedicated Research & Feedback Threads
>>10660694 Meme Overlay Thread - Bypassing Meme Censorship <<<< DUPLICATE - REMOVE???
>>6867253 Clockwork Qrange #10
>>1215912 Letters of gratitude (Q posted in #1025)
>>>/qrb/13005 Planefag Q+A (Planefagging 101)
>>>/qrb/42185 Boatfagging Q&A
>>>/comms/12299 Oregon, Washington, I-5 Corridor: Turn the Tide
>>6064510 META (use for board admin queries)
There is ZERO Evidence of a link between bomb threat post in /qr/ and convo among bakers in /comms/
Background:
-
OSS threatened 3 bakers - DSB, GB and GYB/FRB - in QR #13992.
-
Created a confusing cap consisting of a a mish-mosh of timestamps and comments between DSB and GB to try to "prove" that the two were plotting to post a bomb threat on /qr/. See CAP 3a.
-
Does not say why the bakers were doing this, but the implication is that they are and have always been shills masquerading as bakers, so they could sabotage qresearch. [- How amazing that they should post this bomb threat at precisely the time that OSS is watching their actions - what are the chances of that??]
-
OSS and shills started spamming the idea all over /qr/ that /comms/ bakers are making bomb threats.
-
Also posted it on /comms/, see: >>31036
-
Nobody has refuted this destructive claim, so it continues to circulate. Shills and OSS taking full advantage.
Findings:
-
Upon investigation, it is clear that there is ZERO evidence to support the idea that there's any connection between the bomb threat post and bakers' conversation on /comms/.
-
Timestamps don't match up - see below
-
Convo is not about mail bombs but about why OSS crew is attacking the kitch when it did (on a weekend)- see below
Conclusion:
OSS just juxtaposed a bunch of unrelated stuff OUT OF CONTEXT and then made the outrageous claim it showed bakers planning a mail bomb post
this is a totally SPECIOUS claim based on ZERO evidence
Done SOLELY to discredit traditional baking crew in order to institute a COUP by "No Name" bakers
(No Name bakers had names as recently as last week - "no name" is just a power grab tactic)
Details:
CAP 1 shows OSS's confusing post that tries to use a few random statements by bakers combined with time stamps that don't match up w/convo to "prove" that the two are related. Time stamps here can be confusing because they seem to come from different time zones. But sticking to "minutes past the hour, we can follow the action.
ON /QR/:
0:56 - guy posts on qr with an article on mandatory masks followed by a post with somewhat dank jokey-sounding bomb threat because he's upset about the possibility of mandated masks with very harsh penalties for non-compliance.
1:42 - anon in /qr/ notices a bomb threat in notables and comments in red text (which baker notices and so deletes the notable)
at some point, the bomb threat post is submitted as Global Report and removed from the bread.
__IN /Comms/_:
0:27 >>30617: GB - "just set the bait"
0:38 >>30619: DSB - "Think they'll be gone in the morning?"
0:44 >>30620: BE - "No [then describes DS panic].
0:47 >>20621: GB - "Dey took it. Likely to continue but with sporatic breaks."
0:49 >>30624: BE - "how r you cakes?"
0:49 >>30625: DSB - "be, quite drinking for now eat something, your mind will clear, i swear"
0:54 >>30628: DSB - "during the week they will have a hard way to go and moar anons to put up with"
0:57 >>30633: GB - "perhaps which is why it was set-up for weekend. Just a small little trap, not a big deal. the reasonable I'm going to provide an incomplete summation of what habbened last year shill outed.
1:06 >>30635: DSB - "Appreciate you, hopin it works"
1:06 >>30636: GB - "The moldy shit bred is at a crawl"
1:13 >>30638: DSB - "I'm watchin the catalog naow"
1:34 >>30642: DSB - "...kbee shuttin it down"
1:37 >>30644: GB - "not yet, workin on the faggit posting stale notables, the big push failing"
Bolded stuff appears in OSS post described below.
OSS later posts a CAP claiming that DSB and GB were responsible for the bomb threat post on /qr/ based on two things:
1 - two statements in their convo (the bolded ones)
2 - very loose but out-of-order links to timestamps
When looked at in context, the conversation is about why OSS crew is trying to take over the bake on the weekend (fewer anons, etc) and bakers' efforts to foil that attempt (see "just set the bait" comment) @27 mins. GB's comment is about it "being set up for weekend" is about OSS effort to take over the dough, not planning a bomb threat. The bakers are just tracking the dup breads to see which is ahead.
CAP 1: shows the post from QR and other posts by the same ID. was removed as illegal but stupid OSS reposted it on /comms/, so I'll have to either blot out the bad line or delete the post - will probably do the latter, as i did in this CAP.
CAP 2: QR 13992 bread posts where OSS tries to frame and intimidate bakers, implying he can prove they have been making bomb threats.
There is ZERO Evidence of a link between bomb threat post in /qr/ and convo among bakers in /comms/
Background:
-
OSS threatened 3 bakers - DSB, GB and GYB/FRB - in QR #13992 (https://archive.vn/wip/QMmdr)
-
Created a confusing cap consisting of a a mish-mosh of timestamps and comments between DSB and GB to try to "prove" that the two were plotting to post a bomb threat on /qr/. >>>/qresearch/10937202.
-
Does not say why the bakers were doing this, but the implication is that they are and have always been shills masquerading as bakers, so they could sabotage qresearch. [- How amazing that they should post this bomb threat at precisely the time that OSS is watching their actions - what are the chances of that??]
-
OSS and shills started spamming the idea all over /qr/ that /comms/ bakers are making bomb threats.
-
Also posted it on /comms/, see: >>31036
-
Nobody has refuted this destructive claim, so it continues to circulate. Shills and OSS taking full advantage.
Findings:
-
Upon investigation, it is clear that there is ZERO evidence to support the idea that there's any connection between the bomb threat post and bakers' conversation on /comms/.
-
Timestamps don't match up - see below
-
Convo is not about mail bombs but about why OSS crew is attacking the kitch when it did (on a weekend)- see below
Conclusion:
OSS just juxtaposed a bunch of unrelated stuff OUT OF CONTEXT and then made the outrageous claim it showed bakers planning a mail bomb post
this is a totally SPECIOUS claim based on ZERO evidence
Done SOLELY to discredit traditional baking crew in order to institute a COUP by "No Name" bakers
(No Name bakers had names as recently as last week - "no name" is just a power grab tactic)
Details:
Let's compare the action on /qr/ with the convo on /comms/.
ON /QR/:
0:56 - guy posts on qr with an article on mandatory masks followed by a post with somewhat dank jokey-sounding bomb threat because he's upset about the possibility of mandated masks with very harsh penalties for non-compliance.
1:42 - anon in /qr/ notices a bomb threat in notables and comments in red text (which baker notices and so deletes the notable)
at some point, the bomb threat post is submitted as Global Report and removed from the bread.
__IN /Comms/_:
0:27 >>30617: GB - "just set the bait"
0:38 >>30619: DSB - "Think they'll be gone in the morning?"
0:44 >>30620: BE - "No [then describes DS panic].
0:47 >>20621: GB - "Dey took it. Likely to continue but with sporatic breaks."
0:49 >>30624: BE - "how r you cakes?"
0:49 >>30625: DSB - "be, quite drinking for now eat something, your mind will clear, i swear"
0:54 >>30628: DSB - "during the week they will have a hard way to go and moar anons to put up with"
0:57 >>30633: GB - "perhaps which is why it was set-up for weekend. Just a small little trap, not a big deal. the reasonable I'm going to provide an incomplete summation of what habbened last year shill outed.
1:06 >>30635: DSB - "Appreciate you, hopin it works"
1:06 >>30636: GB - "The moldy shit bred is at a crawl"
1:13 >>30638: DSB - "I'm watchin the catalog naow"
1:34 >>30642: DSB - "...kbee shuttin it down"
1:37 >>30644: GB - "not yet, workin on the faggit posting stale notables, the big push failing"
Bolded stuff appears in OSS post described below.
= = = =
OSS says this shows that DSB and GB were planning a mail bomb threat post based on two things:
1 - two statements in their convo (the bolded ones)
2 - very loose but out-of-order links to timestamps
But the statements in context don't show any such intent. And the timestamps on the threat post in /qr/ don't really match up to the convo.
CAP 1 shows OSS's confusing post that tries to use a few random statements by bakers combined with time stamps that don't match up w/convo to "prove" that the two are related. Time stamps here can be confusing because they seem to come from different time zones. But sticking to "minutes past the hour, we can follow the action.
What we see is that, when looked at in context, the convo is about why OSS crew is trying to take over the bake on the weekend and bakers' efforts to stop them. GB's comment is about it "being set up for weekend" is about OSS effort to take over the dough, not planning a bomb threat. The bakers are just tracking the dup breads to see which is ahead.
CAP 2 shows QR #13992 bread posts where OSS tries to frame and intimidate bakers, implying he can prove they have been making bomb threats.
There is ZERO Evidence of a link between bomb threat post in /qr/ and convo among bakers in /comms/
Background:
-
OSS threatened 3 bakers - DSB, GB and GYB/FRB - in QR #13992 (https://archive.vn/wip/QMmdr)
-
Created a confusing cap consisting of a a mish-mosh of timestamps and comments between DSB and GB to try to "prove" that the two were plotting to post a bomb threat on /qr/. >>>/qresearch/10937202.
-
Does not say why the bakers were doing this, but the implication is that they are and have always been shills masquerading as bakers, so they could sabotage qresearch. [- How amazing that they should post this bomb threat at precisely the time that OSS is watching their actions - what are the chances of that??]
-
OSS and shills started spamming the idea all over /qr/ that /comms/ bakers are making bomb threats.
-
Also posted it on /comms/, see: >>31036
-
Nobody has refuted this destructive claim, so it continues to circulate. Shills and OSS taking full advantage.
Findings:
-
Upon investigation, it is clear that there is ZERO evidence to support the idea that there's any connection between the bomb threat post and bakers' conversation on /comms/.
-
Timestamps don't match up - see below
-
Convo is not about mail bombs but about why OSS crew is attacking the kitch when it did (on a weekend)- see below
Conclusion:
OSS just juxtaposed a bunch of unrelated stuff OUT OF CONTEXT and then made the outrageous claim it showed bakers planning a mail bomb post
this is a totally SPECIOUS claim based on ZERO evidence
Done SOLELY to discredit traditional baking crew in order to institute a COUP by "No Name" bakers
(No Name bakers had names as recently as last week - "no name" is just a power grab tactic)
Details:
Let's compare the action on /qr/ with the convo on /comms/.
ON /QR/:
0:56 - guy posts on qr with an article on mandatory masks followed by a post with somewhat dank jokey-sounding bomb threat because he's upset about the possibility of mandated masks with very harsh penalties for non-compliance.
1:42 - anon in /qr/ notices a bomb threat in notables and comments in red text (which baker notices and so deletes the notable)
at some point, the bomb threat post is submitted as Global Report and removed from the bread.
__IN /Comms/_:
0:27 >>30617: GB - "just set the bait"
0:38 >>30619: DSB - "Think they'll be gone in the morning?"
0:44 >>30620: BE - "No [then describes DS panic].
0:47 >>20621: GB - "Dey took it. Likely to continue but with sporatic breaks."
0:49 >>30624: BE - "how r you cakes?"
0:49 >>30625: DSB - "be, quite drinking for now eat something, your mind will clear, i swear"
0:54 >>30628: DSB - "during the week they will have a hard way to go and moar anons to put up with"
0:57 >>30633: GB - "perhaps which is why it was set-up for weekend. Just a small little trap, not a big deal. the reasonable I'm going to provide an incomplete summation of what habbened last year shill outed.
1:06 >>30635: DSB - "Appreciate you, hopin it works"
1:06 >>30636: GB - "The moldy shit bred is at a crawl"
1:13 >>30638: DSB - "I'm watchin the catalog naow"
1:34 >>30642: DSB - "...kbee shuttin it down"
1:37 >>30644: GB - "not yet, workin on the faggit posting stale notables, the big push failing"
Bolded stuff appears in OSS post described below.
= = = =
OSS says this shows that DSB and GB were planning a mail bomb threat post based on two things:
1 - two statements in their convo (the bolded ones)
2 - very loose but out-of-order links to timestamps
But the statements in context don't show any such intent. And the timestamps on the threat post in /qr/ don't match up to the convo.
CAP 1 shows OSS's confusing post that tries to use a few random statements by bakers combined with time stamps that don't match up w/convo to "prove" that the two are related. Time stamps here can be confusing because they seem to come from different time zones. But sticking to "minutes past the hour, we can follow the action.
What we see is this: when looked at in context, the convo is about why OSS crew is trying to take over the bake on the weekend and bakers' efforts to stop them. GB's comment is about it "being set up for weekend" is about OSS effort to take over the dough, not planning a bomb threat. The bakers are just tracking the dup breads to see which is ahead.
CAP 2 shows QR #13992 bread posts where OSS tries to frame and intimidate bakers, implying he can prove they have been making bomb threats.
>>>/qresearch/10938666, >>>/qresearch/10935072,
>>>/qresearch/10934961, >>>/qresearch/10938775 __Updated Comms Bomb threat graphic showing how they also planted
what a fukking travesty this is! Should be taken down IMMEDIATELY
THERE IS ZERO EVIDENCE OF A CONNECTION between bomb threat post in /qr/ and convo among bakers in /comms/
Background:
-
OSS threatened 3 bakers - DSB, GB and GYB/FRB - in QR #13992 (https://archive.vn/wip/QMmdr)
-
Created a confusing cap consisting of a a mish-mosh of timestamps and comments between DSB and GB to try to "prove" that the two were plotting to post a bomb threat on /qr/. >>>/qresearch/10937202.
-
Does not say why the bakers were doing this, but the implication is that they are and have always been shills masquerading as bakers, so they could sabotage qresearch. [- How amazing that they should post this bomb threat at precisely the time that OSS is watching their actions - what are the chances of that??]
-
OSS and shills started spamming the idea all over /qr/ that /comms/ bakers are making bomb threats.
-
Also posted it on /comms/, see: >>>/comms/31036
-
Nobody has refuted this destructive claim, so it continues to circulate. Shills and OSS taking full advantage.
Findings:
-
Upon investigation, it is clear that there is ZERO evidence to support the idea that there's any connection between the bomb threat post and bakers' conversation on /comms/.
-
Timestamps don't match up - see below
-
Convo is not about mail bombs but about why OSS crew is attacking the kitch when it did (on a weekend)- see below
Conclusion:
OSS just juxtaposed a bunch of unrelated stuff OUT OF CONTEXT and then made the outrageous claim it showed bakers planning a mail bomb post
this is a totally SPECIOUS claim based on ZERO evidence
Done SOLELY to discredit traditional baking crew in order to institute a COUP by "No Name" bakers
(No Name bakers had names as recently as last week - "no name" is just a power grab tactic)
Details:
Let's compare the action on /qr/ with the convo on /comms/.
ON /QR/:
0:56 - guy posts on qr with an article on mandatory masks followed by a post with somewhat dank jokey-sounding bomb threat because he's upset about the possibility of mandated masks with very harsh penalties for non-compliance.
1:42 - anon in /qr/ notices a bomb threat in notables and comments in red text (which baker notices and so deletes the notable)
at some point, the bomb threat post is submitted as Global Report and removed from the bread.
__IN /Comms/_:
0:27 >>>/comms/30617 : GB - "just set the bait"
0:38 >>>/comms/30619 : DSB - "Think they'll be gone in the morning?"
0:44 >>>/comms/30620 : BE - "No [then describes DS panic].
0:47 >>>/comms/30621 : GB - "Dey took it. Likely to continue but with sporatic breaks."
0:49 >>>/comms/30624 : BE - "how r you cakes?"
0:49 >>>/comms/30625 : DSB - "be, quite drinking for now eat something, your mind will clear, i swear"
0:54 >>>/comms/30628 : DSB - "during the week they will have a hard way to go and moar anons to put up with"
0:57 >>>/comms/30633 : GB - "perhaps which is why it was set-up for weekend. Just a small little trap, not a big deal. the reasonable I'm going to provide an incomplete summation of what habbened last year shill outed.
1:06 >>>/comms/30635 : DSB - "Appreciate you, hopin it works"
1:06 >>>/comms/30636 : GB - "The moldy shit bred is at a crawl"
1:13 >>>/comms/30638 : DSB - "I'm watchin the catalog naow"
1:34 >>>/comms/30642 : DSB - "β¦kbee shuttin it down"
1:37 >>>/comms/30644 : GB - "not yet, workin on the faggit posting stale notables, the big push failing"
Bolded stuff appears in OSS post described below.
= = = =
OSS says this shows that DSB and GB were planning a mail bomb threat post based on two things:
1 - two statements in their convo (the bolded ones)
2 - very loose but out-of-order links to timestamps
But the statements in context don't show any such intent. And the timestamps on the threat post in /qr/ don't match up to the convo.
CAP 1 shows OSS's confusing post that tries to use a few random statements by bakers combined with time stamps that don't match up w/convo to "prove" that the two are related. Time stamps here can be confusing because they seem to come from different time zones. But sticking to "minutes past the hour, we can follow the action.
What we see is this: when looked at in context, the convo is about why OSS crew is trying to take over the bake on the weekend and bakers' efforts to stop them. GB's comment is about it "being set up for weekend" is about OSS effort to take over the dough, not planning a bomb threat. The bakers are just tracking the dup breads to see which is ahead.
CAP 2 shows QR #13992 bread posts where OSS tries to frame and intimidate bakers, implying he can prove they have been making bomb threats.
CAP 3 shows one of the posts made by OSS on comms /bakers meta/ thread when the conversations took place - meant to threaten and mock the bakers there. see >>>/comms/31036 for all three posts.
BAKING RESOURCES
Baker's grab bag
* Baker's Tools app (Version 0.7.2) Baker Tools v0.7.2: >>9584, >>9597, >>9601 https://pastebin.com/L1p6iRzZ
* Baker's Tools Lite (stripped down, good for baking) >>14523, https://pastebin.com/pUVCTeCG
* NEW Updated Baker's Tools Lite (q.js) >>21036, https://github.com/learnedtocode/qjs
* Try Atom as a text editor for Macs >>6925, >>6934, >>7055, >>7070
* Meme-making app kek.gg >>8771
* Crazy Bakes: wonky board, lags, baking from Index, "flood detected", dup breads >>9960
* How's your mouse for baking? >>10617
* Font used for baking school slides >>10642, https://www.dafontfree.net/find.php?q=impact
* Quik Pic bake instructions >>7549
* Original baking video >>7076 (shows how to make room for new notables)
* Overcoming paywalls >>10844
* Pastebin.com problems & alternatives >>11645, >>11609, >>11619, >>11620, >>11627, >>11640
* How to Control-F on androids & IOS devices >>13566, >>13567
* How to do a keyword search when /qresearch/ is down >>13696
* Past bread archive for /qresearch/: https://qanon.news/Archives
Dealing with notables
* Note-taking roles: baker, note collector, helper anon, posters >>14921
* Ten Baker Tips for Notables >>8177
* Bakers on what they look for in notables >>8351, >>8315, >>8698
* Muh Collector "how to" on notables >>9006, >>9009
* Anon tips for better notables >>>/qrb/41937, https://pastebin.com/yq7wQyvn
* Long notables; Asking anons to state main point >>13633, >>8237
* Asking anons to state the main point
* Advanced Google searching protocols https://pastebin.com/raw/JuK0xUDb
-
5 kinds of sauce (evidence) that make a notable noteworthy >>9655
Free image/video screenshots, download, production tools
* Image screenshots PrtSc/snipping tool + MS-Paint https://youtu.be/KvXxCE1gxOE
* 8kun video limits (~16mg) >>8760
* Bandicam Screen Recorder >>8759, >>8762 (also: OBS, Kdenlive, Audacity)
* YouTube & Twitter (downloads plus cutting scenes from YT) >>14306
* Video downloaders: >>14237, https://www.downloadhelper.net/ ; Firefox/Opera: - https://technologyto.com/extractor.html
* VLC Player >>8714, >>8715, >>8766
* Windows Movie Maker for Win 10 >>8712
* NVidia cards (can screen-capture vids) >>8785
* Forensically (forensics magnifier) https://29a.ch/photo-forensics/#forensic-magnifier
* ShotCut NLE (open source cross platform video editor) https://shotcut.org/
* MFFmpeg (decodes & plays any format) https://ffmpeg.org/
* Natron (cross-platform video compositor) https://natrongithub.github.io/
* Handbrake (good for transcoding) https://handbrake.fr/
* GIMP & GMIC (image editing) http://gmic.eu/gimp.shtml
~~* Invidio (copies YT vids, restricted or not, no ads or signup) >>8792~~
DO NOT USE! apparently malware now
* Avidemux.org, VideoSmaller.Com (apps for making large files smaller) >>18286
* Free Convert ((reduces file size w/good quality) https://www.freeconvert.com/video-compressor/download
-
NEW: FFmpeg (record, convert and stream audio/video): https://ffmpeg.org/
Baker tips IRL
>>8829 Baker's Tips - Read me first
>>6331 #01 - Ghosting a bred
>>6331 #02 - Baker changes
>>6378 #03 - TOR baking
>>6651 #04 - Defeating shills with facts & humor
>>7339 #05 - Announce you're baking (#11 too)
>>6892 #06 - Baking/note-taking protocols
>>7181 #07 - Use RED TEXT and BOLD in handoffs
>>7363 #08 - Try to notice when a cat is baking
>>13038 #09 - Respecting other bakers' notables
>>8174 #10 - Make sure to copypasta the whole page
>>8803 #11 - Announce you're taking responsibility
>>8822 #12 - Embed baker changes to provide more info
>>8824 #13 - Watch out for unknown bakers bearing gifts
>>8825 #14 - Use named pastebins to defeat shill complaints
>>8826 #15 - Responding to shills trying to suck up baker's time
>>8827 #16 - Be aware of muh joos bakers
>>8828 #17 - All bakers screw up
>>10445 #18 - Just do it--bake!
>>9590 #19 - Don't be afraid to bake
>>10789 #20 - Post notes early so changes can be made
>>10791 #21 - No /comms/ creates misunderstandings
>>10792 #22 - Defeat shills with humor
>>14835 #23 - Keep notables [from different bakers] separate
>>14836 #24 - Make sure to ask for Handoff Confirmed
>>14801 #25 - Don't fuck with the wrong baker [take a look - funny]
>>15894 #26 - Ignore end-of-bread antics
BAKING PROCESS: 3 PARTS
I. ''THE DOUGH''
Here baker finds the old dough and copy it to a text editor.
II. ''THE THREAD''
Next we prep the next thread (bread) and so we can create it at end of current bread.
'III. ''DOUGH POST & FRESH BREAD''
Finally, we post the new paste and put a link from old to new bread.
BAKING PROCESS: 3 PARTS
I. ''THE DOUGH''
Here baker finds the old dough and copy it to a text editor.
II. ''THE THREAD''
Next baker preps the next thread (bread) and so we can create it at end of current bread.
III. ''DOUGH POST & FRESH BREAD''
Finally, baker posts the new paste and put a link from old to new bread.
How to find m3thods, redpill 78, and we know, praying medic, x22
M3thods
https://twitter.com/M2Madness/with_replies
RP78
https://twitter.com/M2Madness/status/1317909950686003200
https://cms.megaphone.fm/channel/redpillnews?selected=REP4109872238
And We Know
https://twitter.com/andweknow/status/1317320970898726912
Praying Medic
prayingmedic.com
x22report
x22report.com
We Shall Build a SHIP OF WAR
We shall build a ship of war
For Patriot Anons standing strong
Come join us friends, come to the fore
Into the fray, we carry on.
Never flagging, always there
Never sagging, strong in prayer
Meming, digging, daily baking
Q, our mentor, n'er forsaking.
Freedom's flag shall ever wave
As long as there are patriots brave
Singing songs of liberty
We shall prevail! We shall be FREE!
Our prow of WAR shall piece the waves!
Its proud white sails like banners flying
We won't be the craven slaves
Of those who specialize in lying
Come Patriots, now join with us
Come join with fellows round the world
Come light the flame of liberty
We shall see freedom's flag UNFURLED!
In every country, every town
Throught the globe, we'll pass that flame
Til all the world is blazing LIGHT
And we are free to e'er proclaim:
WE ARE NOW FREE!
WE ARE ALL ONE
THE WAR IS OVER
BATTLE'S DONE.
Patriots will share a beer
We'll all rejoice, in great good cheer.
But then return to steady vigil
So our fate shall stand in His will.
Never done, we keep the watch
Atop the crow's nest, e'er surveilling
Eyes wide open, sleeping nought
So freedom's flame is e'er prevailing.
Ten Tips for Notables
11-5-2020
GENERALLY
1. Maintain a separate Notepad++ file for notables (don't insert directly in the pastebin file).
Enables you to note missing sauce, put in "iffy" notes at the end (waiting for a nom), etc.
2. Post about four times during the bread, (early, middle, last call, final).
Don't stick anything iffy in at the last moment, make sure anons can vet it first.
3. Make notables easy to find with RED TEXT and BOLD.
Especially important if you may have to ghostβnext baker needs heavy formatting to locate important info like notes.
4. Link notes to dough post if you have to ghost.
Same reason as above.
DECIDING WHAT TO NOTABLE
5. Look for anon noms, they are usually notable.
"Usually" because shills nom too. So do trolls. If not sure, ask for a 2nd nom or say what's missing.''
6. For noms wo/a description (usually anon diagrams, etc.), ask for one.
It's anons' responsibility to summarize a main point.'
7. Look for newsy articles
If necessary, edit the title to be more neutral (not insulting) or shorter if wordy (or add important details if missing).
8. Look for special reports: planefags, boatfags, Resignations in the News, etc.
Anons seldom nom these, except for RA's stuff if they don't see it in Notes.
9. If there is too much news & bred is fastβ¦
β¦focus mainly on nommed posts, breaking news (if verified), news re Q concerns (CP, etc.).
10. Check for two things: dates and whether it's been notabled (in qresear.ch).
Easy during slow breads, hard during fast ones. Dates take priority. But if you forget, anons or shills will always let you know.
>>15034 pb
>>15035 pb
>claim that bakers want to take control of/qr/
Key thing is what it means to 'take over' or 'take control.'
There is nothing wrong with control. Critical thing is what kind of control and the motive behind it. There is nothing wrong with seeking to create protocols that promote smooth running, appropriate notables, and the prompt collecting of Q drops. There is nothing wrong with coordinating bakes so that there is 24/7 coverage. And there is nothing wrong with trying to protect the dough to ensure continuity.
There IS something wrong in exercising control for personal gain, personal 'glory' or in the service of those who oppose the goals listed at the top of each bread. Shills are always trying to exploit that understanding for their own purposes. Biggest reason shill baker was able to succeed this time was that he got the support of /qr/ BO - and therefore a certain form of legitimacy (at least at the outset).
It's amazing that bakers were able to do as well as they did up to that point, given such a hostile mgmt. Nothing made bakers give up - not captchas, not FJ takeover, not deplatforming, not FJ inaction after replatforming. Bakers worked around all these problems. But the combo of a psychopathic shill baker teaming up the FJ - that was one obstacle too many.
As i see it, FJ is the problem. As long as FJ controls /qr/, only bakers who suck up will have his support. Those who don't will be called names and blamed for any bad thing that happens. Not just bakers but all anons. So what to do? Work elsewhere.
The key thing now: to have a place to stand, from which to fight on. A place we can dig/meme/pray - and get the word out.
MNR is that place. Also serves as a reminder to visting anons what /qr/ used to be. So they do not forget - and (hopefully) more forcefully demand something better.
My stance: to necessarily support /qr/for long as Q continues to post there. But only as a digger, in order to get the word out. Not as a baker. Not so long as there is no serious challenge to the grossly false and disgusting accusations made against bakers whose only sin was trying to keep the place open 24/7.
Grateful thanks to all those who support MNR.
Shadilay fellow patriots. WWG1WGA.
>>15034 pb
>>15035 pb
>claim that bakers want to take control of/qr/
Key thing is what it means to 'take over' or 'take control.'
There is nothing wrong with control. Critical thing is what kind of control and the motive behind it. There is nothing wrong with seeking to create protocols that promote smooth running, appropriate notables, and the prompt collecting of Q drops. There is nothing wrong with coordinating bakes so that there is 24/7 coverage. And there is nothing wrong with trying to protect the dough to ensure continuity.
There IS something wrong in exercising control for personal gain, personal 'glory' or in the service of those who oppose the goals listed at the top of each bread. Shills are always trying to exploit that understanding for their own purposes. Biggest reason shill baker was able to succeed this time was that he got the support of /qr/ BO - and therefore a certain form of legitimacy (at least at the outset).
It's amazing that bakers were able to do as well as they did up to that point, given such a hostile mgmt. Nothing made bakers give up - not captchas, not FJ takeover, not deplatforming, not FJ inaction after replatforming. Bakers worked around all these problems. But the combo of a psychopathic shill baker teaming up the FJ - that was one obstacle too many.
As i see it, FJ is the problem. As long as FJ controls /qr/, only bakers who suck up will have his support. Those who don't will be called names and blamed for any bad thing that happens. Not just bakers but all anons. So what to do? Work elsewhere.
The key thing now: to have a place to stand, from which to fight on. A place we can dig/meme/pray - and get the word out. MNR is that place. Also serves as a reminder to visting anons what /qr/ used to be. So they do not forget - and (hopefully) more forcefully demand something better.
My stance: to necessarily support /qr/for long as Q continues to post there. But only as a digger, in order to get the word out. Not as a baker. Not so long as there is no serious challenge to the grossly false and disgusting accusations made against bakers whose only sin was trying to keep the place open 24/7.
Grateful thanks to all those who support MNR.
Shadilay fellow patriots. WWG1WGA.
>>52059
How to navigate to a thread where you can post
In the first version of this thread, a perceptive anon pointed out that many newfags get confused about where to post.
Please: Do NOT post in the Catalog by selecting Create a Thread.
Instead, go to an existing thread first - usually the General thread (see second CAP here for an example: >>51805.)
Here's the whole process.
Getting from a browser to the General thread:
-
Go to the catalog for the board you are accessing - in this case, /midnightriders/, by entering "8kun.top/midnightriders/catalog.html"
-
Select the open General thread (see >>51805, second CAP).
-
Once in the thread, enter text in the New Reply box at the top and select New Reply - post will appear on screen.
The video CAP will take you thru these steps. VIDEO CAP 1
I dragged in an image to post using drop 'n drag in the field labeled "Select/drop/paste files here". You can view that field at the top of Quickstart CAP here: >>51801
Bringing over posts from other boards
An anon gives tips on handling off-board posts (those imported from a different board like /qresearch/). CAP 1
Include something like "originally >>>/qresearch/12502496" to give credit to OP (original poster).
Advantages:
-
Giving credit where credit is due.
-
Allows anons to respond directly to the poster.
-
Allows access to anon responses to the OP.
(see >>52067 for how to link to off-board posts)
OPTIONS MENU
Lets each user decide on their preferences in how 8 kun renders posts and other stuff.
General Menu'CAP 1
Recommend turning these options ON initially:
-
Auto update thread
-
Auto clear fields
-
Scroll to new posts
-
Color IDs (see )
-
Hide poster disclaimer
-
Drag and drop file selection
You don't have to save anything - changes saved when you exit the menu.
VIDEO CAP 2
Theme MenuCAP 3
Here you can select the color theme for the current board or the entire site.
HINT: some work better than others.
You do have to save for changes to go into effect.
VIDEO CAP 4
There's more, but that's a good start.
You can explore the options and see the effects.