If the userID is long enough (it is) and all the communication is https (it almost is), then you dont need anything else.
It's not the most secure, but it's actually a pretty elegant solution. The userIDs are never used anywhere else, just as a cookie session ID essentially. They should have had them expire though. Your public key solution is definitely more secure and would accomplish hthat.
There's no visible usernames in the app. I'm not sure what good taking over someone's account would do you.
1. Hack someone in your office
2. Hack someone in your home (one of your kids for example)
3. Hack someone in a coffee shop
Generally, when someone thinks they're anonymous and they aren't, bad things are going to happen.
By "hack", you mean "discover the userIDs of users launching the app in your {office/home/coffee shop}." But this does not equate to a deanonymization of ANY past posts necessarily. userIDs are generated on app install, so anyone hoping to be anonymous needs only connect via a VPN to avoid a MITM on that particular connection, post the anonymous secret, and re-install the app. Then any further use of the app will not leak that they posted the secret, and in fact the information has been destroyed.
And I'm sure that's exactly what most users will do.
Did you not read the part in the article about de-anonymizing user ids?
Re:Yik Yak Hack
by DonHopkins on Tuesday December 09, 2014 @04:31PM
(#8725917)
Delete something they posted about you.
By the sounds of the Wikipedia article the developers were novices, however, which might be why they didn't think of doing this.