Anonymous ID: 10df9a March 24, 2019, 11:08 p.m. No.5877487   🗄️.is đź”—kun   >>7518 >>7555

>>5877395

I put out an "ad" for bakers during graveyard and someone was honest enough to say he was basically terrified of baking. Baking instructions emphasize the "how to" parts and most common problems. Might help to talk about uncommon problems, too. I can envision a video series of say 10 problems involving things like baking late, leaving off the bun, responding to requests to add or correct stuff in notables, etc.

 

BTW, what are the pages above the dough called (just the "paste")?

Anonymous ID: 10df9a March 24, 2019, 11:10 p.m. No.5877501   🗄️.is đź”—kun

>>5877404

>and say that you are in the report too.

 

Say I am in the report too? Not sure what you mean. I'm sending the reports from my ID, would say something like, "Baker departing the kitchen, ghost handoff"

Anonymous ID: 10df9a March 24, 2019, 11:22 p.m. No.5877579   🗄️.is đź”—kun

>>5877488

Not sure what you're asking. But when I dig on something Q has discussed, it's often on my own–at least at first. I do the digg, come back with something, and announce the results in bold or red text:

Alabama senatorial election results not from Russian bots: Q #2635

If I find something juicy, I would usually say somewhere: '''Call for a DIGG"' and list the people, companies or website to digg on.

 

Less often, I run across a digg in progress and decide to chime in, e.g, the dig on who was funding the Central American caravans. Anons had listed some places to dig, and I started there.

 

When posting, it's helpful to say. eg, "Caravan funding DIGG, con't." or "Alabama election DIGG, con't." That's so bakers know it's probably notable (notable so that what you've found is visible to other diggers).

 

Hope that helps.

Anonymous ID: 10df9a March 24, 2019, 11:40 p.m. No.5877695   🗄️.is đź”—kun   >>7780

>>5877555

Good stuff. You're articulating why they're scared. The part about being here for Q–that's the key. Q was here at 2:30 am the third night I was baking. And that's what I remembered: record Q posts, bake early and make sure the new thread is up in time. Went fine.

 

Last night had problems due to a combo of waiting for info from anons and baking too late then rushing to catch up, leading to a cascade of problems. Complicated by the thread handing, lagging, etc.

 

The results can be seen in the notables list in #7498. Took over an hour to fix due to losing some of the data and having to reconstruct (and also my inexperience). But it was pristine in the end.

 

Maybe one thing potential bakers should know is that any mistakes can be fixed. The only one that can't is dropping the thread when Q posts. And we can prevent that just by making it our first priority. You don't even need to do notables, just get that thread generated in time.

Anonymous ID: 10df9a March 25, 2019, 12:16 a.m. No.5877954   🗄️.is đź”—kun   >>8020

>>5877780

After reading the baking instructions–with MULTIPLE warnings about bread numbers–I have so far been able to avoid that problem. Probably shouldn't say that, tho, you know what happens….

 

Re screenshots: Great that you had the guts to continue baking. I hear people are more scared of being humiliated than dying in battle. I had that experience; it's survivable. Humiliation is humbling. But then you realize, the real idiots are the ones who humiliate people. Cowards, just trying to be part of the crowd (= mob).

 

Yours is a great story, once you get past the first couple of weeks. You can even try to one-up other "baker screw-up stories" in the long run. I think mine gets at least an honorable mention. (Maybe we need a thread for that, would be hilarious, and also let anons realize it happens to everyone, no big deal.)