>>33260345Man, this is the lamest gotcha I've seen in months. Work better on your material, of course I'll be more inclined to respond if my thread is mentioned.
There are general similarities in everyone's votes, and I don't think there are "blocs" in the way that there's a whip who sets a "group's" vote. That being said, countries in similar situations tend to vote similarly, which is another not-at-all surprising discovery.>>33260357You delayed the vote too early, the current situation generated discussion. Well, I was only basing the point about going to the threads based off my own experiences - I was essentially approved by the thread to represent it. Then again, /nasfaqg/ isn't a regular split.
Regarding blobbing, I believe it's not bad short-term, but can generate a lot of awkward placements over the long term. Consider, for example, /nasfaqg/. I think placing it next to /#/ would make sense in-lore, and let's assume that a potential /#/ rep will think so too, for the sake of the example. However, before they appear, EN3 debuts, and seeking the hot-spot of activity that is the Holosea/Niji area, some settle for the ex-Neutralcontinent. Now, if /#/ rep comes in, they are left in an awkward situation if they'd want to border /nasfaqg/ or maybe /hfz/, or other neutral threads.
It'll generate a non-zoned world,
which was the right idea from the start, I fucking hate zoning bros but the dispersion of threads will be more or less random as they gravitate towards centers of activity. Yes, blobbing won't be a problem when 1, 2, or 3 new threads join in, but 6 months down the line we might find ourselves silently cursing not thinking about it sooner.
>>33260773Isn't lore already collaborative? Aren't Reps solely just designated voters so we get the good ol' one thread = one vote?
>33261197Hi. Last time I voted differently from /morig/ was on the 2nd of September, 2022, aka. last time a vote was held. Thank you for coming to my talk.
