We just increased the maximum number of pinned chats from 4 to 10, so you can show 6 more people how much you love what they have to say.
@signalapp why is there a limit of pinned chats in the first place? So many apps do that. why not let the user decide how many pins are too many? The reasonable number of pinned chats from a UX perspective depends heavily on screen size, scale / zoom, font size and other things.
@torgeros @signalapp I wonder if it's just a client-side limitation or a server one. Because, since it's E2EE, is it fine the server knowing the length of the list of pinned chats? But, even if it doesn't know, how would it store it? 
@qgustavor @torgeros @signalapp Since Signal uses Sealed Sender, this can not be server side. So it is purely client side and a design decision. (But I don't know why there would be a limit)

@chefx @torgeros @signalapp Sealed sender for storing or syncing pinned chats? Really?

If we ignore "they added the limit just for UX reasons" and try answering it as being a technical limitation, it just does not make sense:

It doesn't matter the data is encrypted, because encrypted data is barely larger than non-encrypted data. It does matter how pins are stored, but, even so, isn't like it takes a lot of space: just an integer to keep track of the order, it isn't that much. So arguing it may to avoid users wasting storage in their clients or wasting server bandwidth is non-sense.

Thus, the only argument that remains is exactly what you said, just a design decision. In the best case: just because UX. In the worst: they can make increasing this number a paid feature like WhatsApp. 😐

@qgustavor @torgeros @signalapp No sorry that is not what I meant.
I wanted to say that since the sender of a message is not known on the server, the server cannot handle messages from pinned contacts differently. And Signal is not supposed to know who you contact, so nothing will be stored on their servers.
Pinned chats is local device only.
@chefx @qgustavor @signalapp probably it is int[] pinnedUsers = new int[4] somewhere and now they changed it to 10 because refactoring it was not requested by mgmt. Next upgrade 255 pinned chats mark my words.