Regarding the hivetips proposal, if you followed it closely enough (which few do, so I can see why you might have missed it), their actual plan at this point is to use a far smaller amount. However, they'd

Yes, it's known, there was a miscommunication with the implementer of the code, he's fixed it and testing it on his local system now. Likely will be fixed on Monday I suppose.

All the above sounds good, and I'm glad to hear it. But one thing that mildly confused me, however, was that the comment you're replying to was addressing @thecryptodrive, not you. In particular where

It's a known issue and the code in question was entirely rewritten, but the new code hasn't been fully vetted yet, as I recall, so not yet merged in:

The importance to Hive of user-creatable decentralized tokens is well-understood by all Hive devs (core and apps devs both), I think. From my own team's perspective, this is now one of the highest priorities,

Unfortunately I don't have a lot of time to address the past, and it would take some time to talk about all the things you've mentioned in a comment this long, but your last paragraph really strikes to

I suppose it's reasonably well-understood that Hive-engine tokens are currently centralized tokens, unfortunately, although I believe they are working to change that. In the meantime, while I can't speak

Ok, well here's a more accurate summary, I'll try to keep it as short as possible: I explained to her that one of the basic tenets of the chain was anti-censorshipment, so individual Hive users don't censor

As it happens, I just didn't read any of this msg chain except for your comment about me, hence I didn't make any such comment. I don't really follow Blurt news much, I just don't have time for it. But

Maybe you accidentally replied to wrong comment? I'm not sure what you're referring to.

Wow, you read my entire response, and your summary was "She cain't take no trollinng"? Every time I try to give you some credit for having a brain, you actually write words that make me think

It's quite important for two reasons: *we've successfully completed increasing the scalability of Hive by about 12x which means it is far more decentralizable we can begin to work on new and important

At this point, I think we could increase traffic to 12x our current traffic (which would far exceed anything Steemit ever did), and the cost for the servers wouldn't go up (unless some network traffic

From what I recall (and I'm usually pretty good at recalling such things), within the first few years, Steemit was spending $75K per month on supporting their nodes (i.e. around $900K/year).

@leprechaun There's already code that stops printing of HBD when the ratio of issued HBD to Hive market cap goes too high. And there's also code that starts to lower the value of HBD if amount of HBD issue

Yes, that error typically indicates some form of excessive loading on the server when you see it (the other possibility can be to ask a question with a difficult answer, but we've speeded up the code to

yes

I think api.hive.blog has almost always had the strongest overall performance (because it was internally supporting several hiveminds and hiveds), but it also had the most traffic, so performance perceived

I've discussed this some already in our roadmap post, but I'll reiterate here briefly: the microservice app itself is quite simple, the idea is to have hived directly deliver blockchain data to a stripped

I have some old files with previous data at various times in the past, of course, but the reporting format became more sophisticated with time as I learned more about the nature of the data, so it will