Sometimes it's useful to think about the limitation of the data model. Every developer can remember both cases when the model was too limited and when it was too over-engineered, the former case is hard to fix because the data is already used in many places, the latter because, well, the data is already used in many places.
One limitation of current dabdab data model is that the handle (can3p in my case) is tightly coupled to the user account. It may seem natural, but doing it this way automatically makes impossible to have shared handles (just imagine having a corporate space on dabdab) or makes it very complicated to transfer the handle between the accounts. Also, it implies that one user account can have only one handle, which may be true for some time, but it's super hard to fix at the later stages.
I've been designing dabdab in a way to solve/avoid many limitations of existing systems and that's one more worth solving