Blurt Exists
This is great, and I'm thrilled about it. We are developing an incredible community, and there are now more third-party interfaces (front ends, block explorers, even maybe wallets) than interfaces built and operated by Blurt / Blurt Foundation / SocialGraph.
We are also having some very real issues.
I've just spoken with @megadrive and I'd summarize and prioritize those issues like this:
1
Resource Credits / Rate Limiting
Currently blurt uses steem's system of resource credits to limit requests to the chain. Well, we think that Blurt does. Users are making seemingly unrestricted writes to blurt at machine speed, more or less. Some of them were so kind as to report this to us.
You know who you are, thank you.
I have not yet done the needed review to figure out what is happening here. I'll do it and post again today.
Solutions
Short term: ensure that resource credits are properly enabled on Blurt and that the API plugin is enabled. Today/tomorrow.
Medium term: Per-byte transaction fees
Long term: Migrate to cosmos-sdk
#2
Payouts
Users aren't getting as much blurt as they should from the reward pool.
Solutions
Hard fork or wait. This situation will correct itself as the chain continues to operate, but we are likely to do a hard fork to correct it in a more timely manner.
#3
Account Authorizations
We chose not to import account authorizations. Some users are unable to access accounts that were only used through authorizations.
Solutions
Might not be real solvable, but it's on our mind. Let's see.
Thanks for getting the chain up and running now we can work out the bugs
It's a real head scratcher, that's for sure... I know it is fixable long term what is making the nerves stretch is the short.
I don't see the harm in a slow warm-up and since it's 65% of supply and plenty of users have liquid tokens and wallets are not yet fully functional. With the spam problem forum rewards being small isn't a bad thing if it gives us time to eliminate this problem or substantially mitigate it.