/doughlist/ Information
Over the course of the /CBTS/ to /QR/ timeline there have been several instances where the "proof of ability" of any given anon would be called into question for various reasons while baking, whether it be outright fuckery or just inexperience in the kitchen during high traffic times. Because of the recurrence of this, a few attempts were made in the /qr/ General threads to ID the anons who baked regularly, for better or worse.
The problem is, all group based methods of "keeping obvious malcontents from baking" suffer the same shortcoming: Who chooses who is a goodbaker, and who is a shitbaker? Whether it be so-called "baker unions", support and resource groups, participation protocol, etc etc, the problem of "who's the gatekeeper now?" will always come up.
From April 2020 until The Great Kitchen Fire of October 2020, a group of bakers had begun to institute a protocol of handing off by confirming identities with pastebin user account names. Since I wasn't interested in being a baker with a pastebin account, I refused to get one. This made baking in the /qr/ stream hit or miss if you "didn't have id". What to do?
I had gotten a board on 8kun to mess around with, so I made a baking log. It started out as an experiment in finding a reliable and relatively pain free way to bake on /qresearch/ under those circumstances, without having to use any external user account providers or having to cobble a chain of authorship out of a collection of disposable one-shot proofs. It also allowed the casual reader (or baker in a rush) to see what the past work history of that given baker was, at a glance.
What is a "chain of authorship"? A chain of authorship allows an individual to be able to prove their own capacity to be what they state over time, whether they are anonymous or not. The idea is to completely lock a board so only (you) have authorized access to it. This does a few important things:
-
NO comms outside of the 8kun platform, at all. Period. Zero off-site service accounts or providers needed.
-
NO contentious publishing authorities. The only authorization required comes directly from the 8kun platform owner, in order to get your board.
-
It allows you to use a secure tripcode to prove a chain of authorship rather than wasting raw evidence in a single-use scenario every time you want to bake.
-
It secures the validation transaction using a challenge-response method, making the issue of whether tripcodes are being moderated on /qr/ itself or not, irrelevant.
-
It allows you to keep a current record of bakes available, and secure that résumé from being ripped off, because publicly claiming ownership of it requires your tripcode and board access.
-
It allows you to have a secured public place to authoritatively regenerate a new tripcode if your tripcode is guessed or otherwise compromised.
-
Conversely, If someone does manage to compromise your board, you still control your chain of authorship with your tripcode, allowing recovery/replacement of the board itself through the 8kun admins.
Things needed to complete this guide:
-
A board.
-
A tripcode of your choosing.
-
A screen capping tool of your choice. As long as it facilitates quickly capping a single post easily, it will work.
-
Evidence of at least one good /qr/ bake, with a (you) and a timestamp. You'll want to keep your résumé fresh from time to time, but one bake is enough to get you going in this walk-through.
-
A screencap from the /qr/ stream of a post you would like to claim as a "hand off post", with a (you) and a timestamp.
If you do not yet have a board, you need one to finish this walk-through.
-
Go create a board.
-
Send a courteous email to the 8kun admin @isitwetyet explaining that you'd like a board; 8kun staff is reviewing all board creation requests to make sure humans are doing it.
-
Come back and do this guide once your new board is approved.
If you already have one, keep reading.