RE: Learning From Others Experiences & Mistakes or Do We Do It The Hard & Costly Way?
Those are good points that you are making. Splitting up Steemit in regions might end up to be a good idea, although I think the time is not right for it at the moment. For every change the platform implements, there will always be a certain number of people in favor and a certain percentage against it. Reaching concensus acros the entire chain is a very hard thing to do, just ask the Bitcoin community :)
If I could add my 2 cents here I would prioritize the necessary changes as follows:
1. Direct messaging within the Steemit platform, including group chat functionality. The community now must always resort to other areas like Steemit.chat, Discord, Telegram, or other channels, which leads the attention away from the central Steemit hub activity
2. Curation tab I think, next to the ' home' , 'new', 'hot', 'trending' and promoted' tag we should see a 'curation' tab where users can follow the activities of the different curating groups - maybe set some minimal quality standards to become an official curating group - also maybe make it is easier to delegate SP to one or more of those groups directly within the platform - because really, I think it's great curation that will really be key to becoming the ultimate quality content platform
3. Re-thinking the ways that Steempower can be acquired Right now, Steem Power can be bought, if an organisation with a lot of funds comes barging in to our community, they would immediately have massive voting and curation power. And that could pose a potential risk in the coming future, especially as Steemit is gaining traction and therefore will automatically attract more attention in the world
Great, no... RUDDY FANTASTIC THOUGHTS (ideas).
Will have to sleep those over and re read them a few more times to have them sink in and be able to grasp all the potential they offer.
However I would state that doing the multilingual/national organization of Steemit is something that is better done earlier than later. The lingual translations are inevitable and the opportunity to use that to reorganize the micromanagement would by far help manage the entire project.
It took facebook years to get it done, no matter how much they resisted it, they had to do it (the multilingual thing) and then they had to reorganize the inner micromanagement based on the languages used.
Lesson is there to be learned from!
So too did Wordpress have to give in to multilingual options on their platform, I can keep going on with the list but you get my point.
However because there is $ involved here, there is also the management and micromanagement factor, this is no "tea and biscuit get together"!
Thus the argument to get this done ASAP stands.
We want STEEM and SBD to be up there in value and usage all over the world and that then entails managing the implementations of this country by country because of local legislature/laws. Once again another argument for the above reorg.
Inevitable and all the others have had to do it, so the sooner we get this done the better, that is just my opinion based on these arguments.
Don't lose sleep over my ramblings. I don't even have the programming knowledge to back up those ideas. And I concur with your views on the importance of regionalizing things. It IS very important. But my reaction and the points I mention are simply there to give you some ideas to weigh the urgency. For developing features of Steemit, priorities must always be chosen, so which aspect first and how, depends on the urgency and the calculated feasibility and effort required. For regionalizing things, we'd need local teams in every continent, don't you think?
Translations first, once that is done the micromanagement becomes a logical process.
The logistics (human resources) are then known up front and are based on languages and countries.
The damage control becomes effective and the scammers out there are at a disadvantage.
So the answer is YES, not just continent but by language and country.
PS. The crew at Wordpress had groups of users make translating teams who did a mighty fine job of taking care of business.
Same approach could be taken here too. I don't see why not.