>Wow this board is a fucking mess.
NO. It's you.
TYB.
Have a look if you would, bakers. Thought this might help new bakers deal with wonky baking situations. But maybe could check for accuracy? Or make suggestions. -gyb
= = = = = = = = = =
CRAZY BAKES
Most often due to variable lags from DDOS or technical problems. Could also happen on baker's end due to poor signal, emergencies, etc. Shills also create duplicate bakes sometimes.
Generally
If you anticipate problems, TRY TO LET THE BOARD KNOW IN ADVANCE ("system wonky, any other baker available?"). If no reply, wing it!
* If in the middle of a bake, POST A MESSAGE:
"Baker emergency, cannot bake" (like when the kids set fire to the microwave)
"Baker having problems, someone plz take over"
"Bake will be late, anons plz wait."
Scenario 1: Was the thread REALLY created? (normal)
You get the "100% posting" message for a long time, followed by "Server took too long." Never says "Posted."
''What to do''
* Wait 30-40 seconds; then open Catalog or Index in a new tab; see whether new thread is there.
* If board's really laggy, wait longer.
* If there's no new thread after more than 2-3 minutes, go to Scenario 2.
Scenario 2: Was the thread REALLY created? (during times when board is really wonky)
You get the "Server too long" message within seconds after posting. Means no new thread created.
''What to do''
* Click "Create a thread" again. Might take several attempts (record for me is 8x). You are looking for the "100% posting" message to persist.
This might create a duplicate bake but is necessary when board is really wonky - see below.
IF you get "Flood Detected," see below.
Scenario 3: BAKING FROM THE INDEX when Catalog is Down
Not really hard, just follow these steps.
1. FINDING THE NEW THREAD BOX
* Open the Index: 8kun.top/qresearch/index.html
New Thread box is at the top.
2. PREPPING THE BAKE
* Fill in fields the same way as always (Q Research General #0000: E-bake Edition, etc.)
* Click on New Thread - which will probably hang ( displaying "posting 100%" message)
3. TO FIND THE THREAD
* Scroll DOWN thru about half a dozen pinned threads to find the first Research General thread.
The next thread down is usually the new thread.
* Not there yet? Refresh the screen and look again.
Scenario 4: "FLOOD DETECTED" message
Two possible situations: (a) system is confused by your multiple thread creation attempts OR (b) system is trying to create a thread and rejects new attempts with identical text.
A. System confused.
* Try a coupla more times (click New Thread). No change? Go to B.
B. System refusing to make two threads that are exact duplicates.
* Add a blank space at the end of some random line & try again.
* Keep checking to see if there's a new thread. Take your time, especially when board is very laggy.
Scenario 5: DUPLICATE BREADS
Happens when board is very laggy. Or when shills bake dup breads.
What to do
1. Copy OP link from good bread.
2. Go to moldy bread and insert a Fresh Bread link for good bread.
3. In moldy loaf, use "Report" to ask BO/BVs lock the bread. It's found by clicking the little triangle on the upper left of any post.
(Do NOT use Global Report, that's only for CP and other serious violations).
Try "Dup bread, plz lock".
4. In the good bread, apologize for the dup. The purpose is both as a courtesy to anons but also to deprive shills of the chance to claim COMP'D BAKER.
Always remember: Any mistakes can be fixed.
Whatever the outcome, you stepped up. Each time, it gets easier
>>Wow this board is a fucking mess.
NO. It's you.
>>It’s better now, Fuck you anyway cunt.
Then why did you post that at the top of bread?
tx for feedback. if i recall, you were the one trying to bake the other night and didn't know about index? tyvm for that - and for letting the board know about the problems so others could help. everything worked out in the end.
your post is why i created this guide. hope it helps anyone trying to bake w/index for the first time.
yes, two identical thread attempts will elicit 'flood detected'. That's why adding a space helps. but you may still get a dup; seems to depend on whether the system actually processes the thread or not. Just happened to me in the last 2 days bc i could not tell whether the thread was processing or not.
tx, you're right about ddos–reworded to include it. Seems like 'flood detected' can come up anytime the server is somehow jammed with too many responses. Worse when board is already wonky (due to DDOS jamming), and then something else becomes the last straw: like Q posting. (Many times in Nov.)
But i think–but am not certain–that the 'straw' can happen with multiple thread attempts. I made 8 attempts the other night to create a thread; at some point, started getting 'flood detected' messages. When thread still wouldn't show in index, added a blank space, knowing i might get an extra thread or two. Just one extra–not too bad.
>It means your previous attempt to post or create a new thread worked
That's what i'm not sure of at the moment.
Did it really work? Yes–has been true in the past. But not sure whether it is true right now. What if it's processing but never manages to post?
I think i have seen that recently with regular posts–where the "posted" message appears, text disappears, but then the post text never appears on the board. It doesn't happen often but i'm pretty sure it does happen (but if other anons have had that problem, plz let me know–could use verification).
With variable lag time for Creating a Thread, how long should a baker wait to see whether there's a new thread? 40 secs in normal. but can be longer no. Wait 2-3 minutes? Longer? In Nov., it took up 10-15 MINUTES for threads to post. Interesting problem.
>So sick of the condescending DivisionShillBakers
what makes you think it's bakers who are acting like hall monitors?
Anons, look at the other posts of this baker critic:
015503
not fukken notable
dankly kekking here….
Many anons are concerned about Boris Johnson. I posted an update early this am; many anons are praying; diggers are trying to find out what therapy he is receiving since UK doesn't seem eager to use the new "cocktail."
But notabling Fredrick Brennan for what he wrote here? What complete sentimental drivel!
Hotwheels will have survivor's guilt is BJ passes? Sounds like it's mainly coz "i could be next."
Pathetic.
>normal hang
kekking
Now we got 3 kinds of baking lags:
-
"normal" (30-40 sec)
-
moderate (2-4 minutes)
-
oh-my-gawd-what-the-hell-is-going-on-now?" (10-15 mins).
Haven't seen the last kind since Nov/early Dec.
Just more spice for the stew!!
Good tip on pre-loading separate bread pages, baker. Saves time during wonky bakes. Stolen!
might have been another meme baker, kek. the moar the merrier.
>ShillBakers, Shill operatives. They are everywhere. Night Shift is fully comped. Day Shift at least has dedicated diggers….
Listen anon, i'm a night baker. Have been for more than a year. Know exactly what goes on there. Night Shift is not "fully comp'd" although there's plenty of shill activity–just as on days. Plenty of good diggz, memes and prayers too. All shifts are in better shape than a year ago bc anons are more experienced, the board is more cohesive, and core baker crew has been in place for a long time now. Baking classes are not only helping support new bakers but also giving any interested anon the chance to talk with bakers about board issues.
>Night shift
>Should call yourselves CompedClownCrewShift.
Nah…. think we'll stick with Night Shift. Thanks anyway.
tyvm, meme-baker.
i mean the moar bakers (of any stripe), the merrier. maybe a few other memists could give you a hand, they are welcome at baking class thurs 7 pm in /comms/.
Wow, you seem to be darkly hinting that Q thanking bakers is some kind of a nefarious plot. Bit of a stretch, I would say.
>if i get into trouble
seems like memefags get into trouble mainly on social media sites, kek. not likely to get into trouble here except with shills.
Unless of course you start a memefags union. Could combine with diggers union, pray-ers union and bakers union to kick out shills union. just an idea….