Evenin' all
I have some stuff to post about verification, how to do it, how to read and confirm it, how not to do it
Seen new and experienced bakers alike have trouble with this so I think it'd be good to go over it
Why do bakers verify who they are handing off to?
To try to make sure we're not handing off to a shill (or an unprepared noob during fast bakes).
There might be other reasons but that is the main one that I'm aware of and that makes sense to me. Bakers like to know they're handing off to someone who will take good care of the dough.
When 8bit was BO of qresearch and it snowed uphill both ways to school and back, he and his BVs used to help bakers out a bit by looking at the post history for a user's IP address.
Identifying users across threads like this is something that only BO/BVs can do, but it makes it easy to tell whether someone is a shill or not. If someone is on a VPN that switches IP addresses every so often, then this method won't work anyway.
This was also a lot of work for BO/BVs and it's really something the kitchen should be able to handle by itself.
Next up: some ways that bakers have kept a work history and verified it so far
So far I am just rehashing stuff you probably already know, feel free to chime in at any time
Those look good. I'll have one of each, except the first one.
Verification usually also means keeping a work history and proving that you are the person associated with that work history.
What are some ways that bakers have kept a work history and used it to verify their handoffs so far?
-
pastebin.com
-
a private board that only a single baker has access to, combined with an 8kun tripcode
-
qanonbin.com
One verification method that I haven't seen used, but would work just fine, is something like a dedicated verification thread here on /comms/ and using that + a tripcode to confirm their posts.
What do these verification methods have in common?
Some secret piece of info that only I have (usually a password) and proof that I just used that password to confirm my identity somewhere.
-
pastebin.com: I have a user account there, and no one else has access to the password associated with that account. Some of my past bakes are linked to this account: https://pastebin.com/u/newsbaker
-
8kun private board: I don't have one of these, but kekbees does. The secret info used here is the password that generates kekbees' unique tripcode, and the password he uses to get access to the admin interface as BO and make sure that only he can post on the >>>/doughlist/ board.
-
qanonbin.com: I have a password there, which is used to generate my tripcode. Some of my past bakes are linked to this tripcode: https://www2.qanonbin.com/trip/k9VsKvRBTand
-
verification using any 8kun board that allows tripcodes: the secret info I use for verification is the password that generates my unique tripcode.
We'll look at examples of each of these verification methods in a bit.
Example verification using pastebin
This is from last night, bread #12764 post >>>/qresearch/9974233
This is a correct and valid verification using pastebin.
There was some confusion about this because of the content of the pastebin - it contains links to wnb's dough buns.
But the content of the bin doesn't matter. Let's take a closer look at why:
In >>19890 I said the two elements of a successful verification are some secret piece of info that only one person has (usually a password that's used to log in to a known account or generate a known tripcode for that person) and proof that the account holder just used that account to confirm their identity.
-
Secret piece of info that only one person has - Pastebin user cfranklin88 obviously did make this pastebin at some point. You can also click on their username to go to https://pastebin.com/u/cfranklin88 and see their paste history.
-
Proof that the account holder just used that account to confirm their identity - for this, we compare the timestamps between the handoff post on 8kun and the pastebin. There is a difference of just a bit less than 1 minute between these timestamps.
This baker copy/pasted the dough post from the current bread into his verification bin, that's why you can see the post number, quoted posts, timestamp, etc, and also the original bins for that bread's dough.
This does not matter - the content of the paste could literally be empty and it is still a valid verification, because we have (1) proof that a known person used a known account and (2) proof that the account was used at the same time of the handoff offer + verification.
Hopefully this makes sense. Summary: the right thing to do when evaluating a verification is to completely ignore the content of the pastebin itself, and look at the username, the past history of that username, and the timestamp of the pastebin in relationship to the post offering a handoff.
Probably contains Monsanto. No offense but fuck Monsanto.
>BO and BVs can see our post history, as each post we make through the same IP address is turned into a unique 'hash' - a numbers n letters sequence that they can see, along with our past posts.
>It isn't 100% failsafe, as anons can be using the same VPN and therefore the same IP addy of that connection.
Good info, thanks for the clarification here.
>ip hopping is guud then because the shill bakers that track us can't lock in
Personally I have seen no evidence that anyone is tracking me based on my activity on 8kun. "normal" 8kun users do not have the ability to do this, and even BO/BV level users do not have the ability to trace an IP hash back to a real IP address. but I think diagnosing and working around common tech issues would also be a good thing to discuss.
>this thread >>5101 might work?
Yep, something like that. I suspect it might work out better over the long term to have one thread per baker - like what kb does but all on the same board. But we have other methods also, and none of this is intended to force anyone to do anything.
Yeah, actually would be good to talk about "inexact" or "human" methods of verification after covering the "exact" or "technical" ways.
Example of an incorrect/invalid verification using pastebin
-—-
Hey baker I can take this one.
https://www2.qanonbin.com/paste/9Ccobresa
Handoff confirmed?
-—-
Can anyone spot the problem with this?
Right, not just a baker's dough, but anyone can pull up an old verification bin from the list.
Right, the timestamp is the key here. When we're checking a handoff with verification, the main thing we should be looking for is a fresh paste.
The content of the verification paste can literally be empty, that doesn't matter, as explained in >>19914
Now let's look at the second verification method using a private board, and the details of how and why it works.
You may already understand all of this but I think it's a good idea to cover it precisely and try to lay out the details clearly.
Is this a valid verification by itself?
If so - why?
If not - what's missing in order to make this a complete verification?
——————
Handoff confirmed?
Past bake history: >>>/doughlist/91
Tripcode validated here: >>>/doughlist/19
——————
>Only thing I'd like to add is that the content can make it easy for a baker to quickly scan over and say yes, that's what I just posted a minute ago.
Right. I haven't really said anything about how to offer a good verification yet, but that's pretty much the only thing I had to say.
I usually put "verify [current bread number]" in the bin content or title to keep it simple and make it super clear that it's a bin just for verifying a handoff.
It's a nice thing to do for other bakers, but not everyone understands this so don't get distracted by the paste content. Look at the user, the user's history, and the timestamps instead!
>one issue it brings up:
>infrequent bakers getting miffed about being asked about previous bakes
>get offended coz oldfag bakers ("i been here since the beginning")
>not used to this approach
>related thing to consider: how shills exploit any system we create (for anything really) to "prove" there's a bakers union
Agree with all of this.
I think it should be up to individual bakers to decide whether we are going to try to verify handoffs - when the board is flowing nicely we probably don't need to be as anal about that. When shills are out en masse then that's the time to pay more attention.
My goal here is to lay out the details of how and why this should work in order to make verification foolproof for those who choose to use it!
>Is this a valid verification by itself?
No, it isn't - this is usually what kekbees posts to offer a handoff, but anyone could copy/paste this text just like I did!
When you see >>>/doughlist/ links it's probably kekbees but you're still missing actual definitive proof that it's him. You're waiting for him to use his secret piece of info to authenticate his handoff post.
He should be posting a cap of his handoff post on his private board under the >>>/doughlist/19 thread, like the attached image.
Once you see that, you know it's really kekbees offering the handoff because this meets both of our criteria above:
-
It's definitely kekbees - he used his tripcode to post it, and he's got the >>>/doughlist/ board configured so that only he can post on it. I checked a while ago.
-
It's fresh - he capped his own post which he just made.
The caps also give kekbees and all the rest of us a way to look at his baking history. Pretty clever use of available tools, and this is a 100% foolproof verification method without using any external sites.
>Another example of an incorrect/invalid verification using pastebin
>https://pastebin.com/u/NIghtBaker
Right, I've seen this before too.
That's why if we're going to verify then we need to be able to generate proofs in real time.
I think all of us here "get" this intuitively.
Moving on…
Verification using qanonbin.com
This is pretty easy, just make a new paste:
https://www2.qanonbin.com/paste/lNxWKza8t
-
This paste uses newsbaker's tripcode, and you can see a count of how many pastes were made under that tripcode right away.
-
The timestamp matches up closely with this post apart from the time it took me to finish writing it
The only other thing I'd like to mention is that when you use any site to verify your identity, you are implicitly trusting that site's administrators to operate the site correctly without changing data around.
Using pastebin for verification: we already know they delete shit whenever they feel like it.
Using 8kun for verification: good choice if you don't mind the couple of extra steps to host a dough, you're just placing your trust in Ron which you already need to do in order to use the site.
Using qanonbin for verification: this means you are trusting me not to edit or delete anything. As a Free and Sovereign Citizen under God and the Constitution of the United States, I am telling you that I will continue to run qanonbin well, some will know that is not a thing to be said lightly but as always you each have to use your own judgment and discernment.
>sometimes it's just a funny message to baker, if it's a friend
Human or "inexact" methods of verification
muh autism may be showing a bit here but I can't think of a better way to explain it.
Many bakers have a set of images they like to post. Many regular bakers can recognize each other through existing relationships whether on or off-board - if that works for you then great!
Personally I put caps of your own bakes with ( You )s into this same category because they are easily faked.
My recommendation would be don't treat this as 100% evidence - if you want to know for sure who you're handing off to, then offer and check verification using a known account and a recent timestamp using that account.
Happy to help, it bugs me to see things not going well and sometimes we are in a position to do something about those things.
Always open to suggestions for the site. One thing I've thought about adding later is a way to compare any 2 pastes.
Bun of verification discussion
Summary:
When confirming a handoff to someone who has offered verification, look for a known user account and a confirmed recent use of that account that relates back to the handoff post.
There are many possible ways to do verification 100% correctly but all of them share these elements in common.
When offering verification, make a new bin for this purpose!
It's a good idea to be very clear about what you're doing ("verify handoff for bread 12345") and not include other bin links, but the content is not the important part of verification!)
I would post a pic of Forrest Gump saying "that's all I have to say about that", but unfortunately it seems like tom hanks is a satanic fuck so we'll skip that part!
Hopefully this was a nice mix of stuff you already knew, and stuff you knew but hadn't thought about in detail and precisely.
Any questions?
keks in REEEEEEEE
>once things have moved on, can relax verification if desired
>Now I hope for back to organic. I don't like what I've seen lately.
somewhat related, we have a few new-ish bakers who look promising but have their Ego set way too high. can that be taught? I am one of those "better with computers than people" so probably not the right person for that, kek!
until that situation passes I will probably also look for and ask for verification. how people respond to that question is telling in itself.
Thanks to all of you for following along and helping also!
>I been making a new pastebin like that each time I verify for baker.
Yep many of us have been doing it for a while, but I hadn't seen anyone spell out that specific topic clearly yet, including how to know when and why it works, and when and why it doesn't work.
>none of this is difficult
none of the things that bakers do while baking are really difficult individually but it is still about 100 different things to do at once. that volume of stuff is complicated no matter what you're doing, and regardless of what our frendly banned torfaggit says that is an accomplishment!
>I don't agree with that either and it makes me sad that new bakers are getting treated as they are lately.
I agree with this too. "in-group bias" or preference for people we already know is a real thing. combined with disagreement over the details of things like handoffs and verification I think that explains most of it.
>Fuck, I don't know why you've stuck it out given how you've been harassed and attacked. (if this is you).
that's doc, check the ID. he did warn us! kek
>baker's union
Bakers are not a union, but we are unified.
Ideals to do our best to live up to.
>I see him as the teletubby that needs the helmet
kek
>not realizing that it was TOR shill's post
>AND SO, he reverted the dough thinking he was doing right.
mistake - recoverable
<not responding to any questions about what happened
this is when I'm going to start making noise
as anon, hopefully politely
to me, this also means he won't learn from his mistakes
bit of both
I try not to see questions or suggestions as attacks until it's blindly obvious that someone's being a fuckwit, and when people ask me shit about my bakes, I respond
even if they are being a fuckwit I'll try to see if there is anything legitimate in there that I can pay attention to
I pretty much expect the same behavior of others
I try to ask questions and give suggestions in a non-combative manner
don't always succeed at either side of that dilemma
I'll try to relax more
>But will as a rule be persistent if there is a dough mistake or if there is something unclear (like what is mean by 'bad' dough) that needs to be clarified, so anons/bakers know what kind of dough problem he's referencing. Any anon has the right to seek clarification about that.
still have to agree with this. I didn't see much that was really attacking in any of the recent discussions in the main stream
but each of us sees things that others miss, if you see specific posts that bakers would see as an attack, please do point it out
>No one told him otherwise, just assumed he was a shill.
I noticed this too
especially if you expect verification,communicate clearly
>That's my dough post, not a verification, can you post a fresh bin from your own account?
<kek handoff denied
big difference
>Hell, it's so bad around here ;ately I've been refused 3 hadnoffs WHILE SHOWING MY PASTE. From my team mates.
saw that too
all started because you pasted a link to the dough or some other bin instead of a fresh verification
my guess was copy/paste error
baker on duty assumed you were a shill instead of …..communicate clearly
repeating bc I wish I had said this earlier
>That's my dough post, not a verification, can you post a fresh bin from your own account?
<kek handoff denied
communicating clearly gives honest mistakes a chance to be corrected, and shows everyone that you won't be fucked with if it really is a shill
Hello fren.
qbin does not have an edit option, because once a paste is made, it shouldn't be changed.
You might try clicking "clone" on an existing dough instead, and only saving that new paste when the new bread is ready.
Most bakers also edit the dough in Notepad++ or another editor program on their computer.
not the same format, but all the post data (minus images) should be available here:
https://wearethene.ws/qresearch/res/9965726.html
etc.
also on qanon.news but clownflare is asking me to fill out a captcha before seeing that site, and they can fuck off
>The 8kun captcha popped up mid practice bake
normal
>and my pages aren't loading like before
how so? what's different or what's not working?
>Will this happen in a real bake, often?
probably, all kinds of shit happens during bakes
I am trying to post in the qresearch thread right now but was getting "Flood detected. Post discarded", even though my first post definitely did not go through
added a space to my post and then it went through. looks like the 8kun flood detector thing thought the post had succeeded even though it hadn't. that happens during bakes too, and you can usually fix it by adding a space somewhere in the post
>Can you please check my practice bakes for improvement?
I'll take a look at the doughs, but you can post links to the threads where you made your practice bakes, that's better and easier than a screenshot
>Anonbin is GREAT TO USE. LOVE IT!!
glad to hear it o7
>Have I used anonbin correctly?
you are going by XIclaveli on there? if so, looks right to me
if you want to confirm that's your account 100% then make a fresh paste and link to it here, some bakers will ask for that during handoff
>Who would you recommend to help take my training wheels off, when I feel ready?
pretty much any of us can help with that and we'll be happy to
better to do it during late night when things are slow
like now - there's no baker on deck but I just offered to take notes for a bit: >>>/qresearch/9996072
I've seen a few bakers out there that I wouldn't recommend because they get a bit snippy and think everyone is a shill instead of responding to questions… I'll leave that up to your judgment though, if you get a weird vibe from someone then they're probably not the right person
>When are you ready?
no better time than now! bread is slow, but I can't make it through the full bread. you can do it though!
>How is your day going? :D
good! long day, just about over for me. how about you?
links to same board have 2 >and no board name:
off-board links have 3 >>>:
I'm baking currently, will take a closer look at this later. you're welcome to follow along with notable collection and Q posts updates and all the rest. link: >>>/qresearch/9996420
>when I go to do something it takes ages and before it was instant.
sounds like an issue with your internet setup. 8kun is buggy but not in that particular way, and everything is working fine for me right now.
kek, I was wondering about the name, you can put whatever you like in the username field on anonbin
you should be using a strong, unique password to generate your tripcode there, if you are then you can just keep the same password with your new username
>i copied you and made a dough
that works
a couple of things:
-
three >>quote marks in your first notables bun, this will make all those posts show in green with non-working links
-
notables got cut off
see pic
I also spot checked a few of your practice bakes, they look excellent, only thing I saw was that in >>20234 the bread title is #12779 but the first notable bin is also #12779. the title should always be one more than the first notables bin, so I guess that title should be #12780. the other 2 I spot checked were literally perfect, didn't see any issues at all. great work.
I think collecting good notes is one of the hardest parts of baking, and there's not really a good way to practice that other than doing it live
I just ghosted the main bread if you wanna try it, cant think any more and need to sleep
if you do collect some notes, just tag (quote) the dough post and the post where I ghosted
>do you think Q has finished?
probably
>your bin is a guest
shouldn't be? I bake as newsbaker with the tripcode !!!k9VsKvRBTand on anonbin and !!IcCEmB4cYM on comms
>If you see me again can you please ask me.
yep
I'm usually on evenings/nightshift, sometimes during the day also
a bit earlier than when we started today should be perfect, I should be around tomorrow and sunday
>Ill keep the silly name, till baking my first bread in the next few days maybe?
totally up to you
goodnight fren
o7
>Second, to see whether there seemed to be some general problem for bakers a group.
fwiw, I definitely see the general problem. existing bakers are reluctant to accept new bakers, and are often harder on new bakers than on people we already know.
I think this is mostly due to "in-group bias" which is well documented.
I did not see any problem with your specific statements in this situation though.
I still think it is also a problem when bakers are unable to see anon feedback due to their own ego, thinking everyone that could possibly have anything negative to say about them is a shill. when anyone gets to that point they are effectively having a conversation with their own ego instead of being able to pay attention to what others are saying, and it is very difficult to reach through that.
>And tried to shrug it off as a first time baker. (cap related) If a first time baker, how come so many 'bakes' in pastebin?
because he practiced extensively before baking live, you dumbfuck
you would know that if you had read this same thread you posted in here, literally the last 10 posts before yours
>How do I fix broken links in past breads, the Q posts specifically.
8kun has archived these older posts and they can no longer be linked to directly.
adding the full URL to each post might work but that sounds very time-consuming and annoying for little gain.
>So there is a way, laborious way to do it, mmm.
I havent seen any bakers do this but I think it would work in theory.