I build a tool that schedules social posts. This week I added four new places to publish: WordPress, dev.to, Hashnode and Lemmy. Then I had each adapter reviewed by someone who did not write it. The most useful findings were all the same kind of bug: the code said "published" when it had only proven "the server answered". Here are four ways that happens. 1. A 200 is not the post My first version of the read-back check fetched the public page and treated HTTP 200 as "live". Tha...