internally, bbycll relies on a post lookup table with post hashes as keys, this is really fast but i knew i'd inevitably run into this issue (just not so soon) so now i have to either:
1) pick the newer post over the other
2) break from specification and not lowercase hashes
3) secretly associate canonical urls or additional entropy with post hashes in the backend without a sizeable performance impact somehow
Poster do festival para o dia 13   
Sunset
Estante com 3 livros de receitas: "Start Here" da Sohla El-Waylly, "Korean American" do Eric Kim e "Dessert Person" da Claire Saffitz
Cartaz para o dia 12  
Uma pilha de revistas e autocolantes SHIFTER
Privacy-concerned duck in a creek