J !OlcPsstCIA ID: e5bb64 June 25, 2018, 3:57 a.m. No.1430   🗄️.is 🔗kun   >>1432

>>379

Notepadqq, ironically named (available on Linux, as Mac is Unix, in theory should be available).

 

Be wary, doesn't autosave or reopen files consistently.

 

>>448

It's being debated in meta that bakers 'show some ID' on qresearch, but as tripcodes are prohibited there, I've proposed a 'secret field' only the admin can see, there's disagreements.

 

For anti-bread corruption, I've suggested CRC hash of previous bread in current bread, coupled with perhaps some dedicated 'bread verifiers' (taste testers?) whose sole job is to scan through the current bread to make sure it isn't being tampered with.

 

Ideally what we need is a system that prevents previous bread information from being tampered within the current, some sort of 'Copy-On-Write' type deal.

 

I think link verification/notables tampering is going to be the biggest cause for concern.

J !OlcPsstCIA ID: e5bb64 June 26, 2018, 9:52 a.m. No.1436   🗄️.is 🔗kun   >>1736

>>1432

Useful insights, thank you. I'm made an alternate proposal in baker chat, as I realise I'm off-topic here.

 

When I meant hidden field, I meant in the sense of information a user could control or input (for example, off-site hash). I suppose that could fall under 'reporting a post'. Anyway, I digress, apologies for derailing your thread, I shall slink away.