{"push_id":1051694631,"size":2,"distinct_size":1,"ref":"refs/heads/broadcast-exactly-52chars","head":"a2edda376ba1945c25d111c849e88c57caad397f","before":"b6234ee8231935535053b8d5589ebf7b55ea11b8","commits":[{"sha":"617e8a7ae8b9107668f99f0ab06ae2b301272ed3","author":{"email":"c24783ba96a35464632a624d9f829136edc0175e@rubensayshi.com","name":"Ruben de Vries"},"message":"add a way to have vectors for code paths before protocol changes.","distinct":false,"url":"https://api.github.com/repos/rubensayshi/counterparty-lib/commits/617e8a7ae8b9107668f99f0ab06ae2b301272ed3"},{"sha":"a2edda376ba1945c25d111c849e88c57caad397f","author":{"email":"c24783ba96a35464632a624d9f829136edc0175e@rubensayshi.com","name":"Ruben de Vries"},"message":"PROTOCOL CHANGE: no longer differentiate between short and long broadcast text messages.\nthe old way had an issue when the string was exactly the switch point (52), because it turned into a 53 long string (+1 from length byte) and that resulted in length byte becoming part of the result.\n\nalso properly take into account utf-8 chars for length.","distinct":true,"url":"https://api.github.com/repos/rubensayshi/counterparty-lib/commits/a2edda376ba1945c25d111c849e88c57caad397f"}]}