Similarly, hard-coded limits to contact lists, e-mail address books, etc. It'd never work, but I'm curious what the effects would be.
Similarly, hard-coded limits to contact lists, e-mail address books, etc. It'd never work, but I'm curious what the effects would be.
http://service.path.com/customer/portal/articles/257552-why-...
You can do this on your own if you so care - I use Twitter in pretty close to this way (I follow 158 accounts as of today, and ~10 of them are service status accounts). Anything over that I might also be interested goes on a List and I check them whenever I'm bored (and I also cap lists at ~150 or so accounts, but none of them are even close to that).
I'm of the opinion that software shouldn't build limitations, it should only be a tool for how users want to use it. (It could be a better tool by instead telling users "Hey, you're following a lot of users, things are probably pretty noisy for you huh? Maybe you want to use a list for {these similar accounts} or something?")
Better yet, come up with a platform that naturally incentivizes users to engage in more sophisticated interactions with a smaller number of people instead of shallow interactions with large numbers of people.
Also, Path [1] was social network app that had these kinds of limits back in the day.
> ...which might explain why there wasn't as much benefit from it as one might have hoped.
I think you've got this the wrong way around. The users probably didn't like being constrained to an arbitrary number. My main point was that any service that tries to impose such limits is going to feel pressure to raise/abolish them.
That makes it quite different, as what you think are your closest friends won’t be forced to choose between you and somebody else in their size-limited friend list.
Because of that, I doubt it would be very similar.