Anonymous ID: 1dd1e9 March 12, 2019, 3:24 p.m. No.5646510   🗄️.is 🔗kun   >>6538 >>6587

'''re-post of

>>5389728 Baker Protocol: Do NOT Add Non-Tripcode posts from Q'''

 

Baker

Global Notable

Retrieved the original posts on non-Q trip codes that turned into green text in Globals. Bolded the key sections. Could maybe be streamlined further.

 

——————–

>>5389728

If a UID tripfags to Q on my bread i will only add the tripfagged Q to the Q part of the bread

 

anons screencap the other posts from that ID

 

secondly, if any of those IDs posts are notable i will just do a plain old notable and treat the poster like a plain old anon, giving zero nods to that ID being Q

 

obviously Q needs to tripfag at least once in the bread for this protocol

 

>>5392971

 

>>5392811

The 'official' standing on non-Q posts posted by the same hash of Q is following:

 

Q confirmed ID 43c548 (>>5386040) posted without tripcode multiple times but the post in question is >>5386106 where Q states

 

>>>5386088

 

>Do not add this

 

>Private comms will be important in the future.

 

Going forward:

 

Non-Q tripcoded posts will not be capped and recorded as Q, even if you can prove it is Q(No increase in index of QPosts for samethread non-Q). They can easily override this if a mistake is made by indicating as Q that a mistake was made. I plan on honoring my interpretation of their wishes in this matter.

 

I hope this addressed the situation, this is our plan going forward.

Anonymous ID: 1dd1e9 March 12, 2019, 3:28 p.m. No.5646587   🗄️.is 🔗kun   >>6698

>>5646510

Just noticed the update, was working from >>5646538

 

There is an update above in Global notables:

>>5644463 Baker Protocol: Do NOT Add Non-Tripcode posts from Q

 

I was working from last bread. Don't know whether anything here adds something to the new version, but it's here if you want it.