If you are right, a website could automate the cycle as follows: 1) Every user belongs to at most two (or k) classes. 2) Each class can have a finite number o

If you are right, a website could automate the cycle as follows: 1) Every user belongs to at most two (or k) classes. 2) Each class can have a finite number of users n. 3) When a class fills up, a new one is opened. 4) There are always two (or k) open classes at a time, and new users join both of those two (or k) classes. 5) The classes are staggered so they don't close at the same time; e.g. if k=2, n=10000, the first 5000 people to join belong to class 1 and class 2, the next 5000 belong to class 2 and class 3, the next 5000 to class 3 and class 4, and so on. 6) Users can only post to classes they are in, and can only comment on posts in classes they are in (or maybe newer ones too). 7) By default, users only see posts to classes they are in (or maybe their classes + older ones). They can opt in to see more if they want. The idea might work better if it is combined with some more onerous mechanism to join classes late - a fee, a requirement for an endorsement from a member or someone. Charging a fee for access to the more '1337' earlier classes might be a good way to monetise the site; the fees could either be flat, or could escalate (exponentially?) with the age of the class and / or the number of people who pay to join it late (possibly with a discount applied as active members leave). Classes might get too small due to attrition - coalescing older classes when they get too small might be a solution to this - it might also make sense to increase class sizes (exponentially?) as the site gets more popular.