BCH/HIVE/HBD pairs are there now (although it looks like BCH -> HBD is missing, so I'll add that one shortly).

We've got 35 programmers/devops people at BlockTrades (well, technically they work at other associated companies I'm involved with, since BlockTrades doesn't directly employ anyone), and 14 are currently

I suspect we've actually got one of the largest development teams in crypto.

Randomization on a blockchain is more work than it sounds, especially to get it right. The proposed change is actually easier.

Those are high on my list too.

The wake up call, I think, is recognizing how others who completely disagree with you feel the same way about you and your beliefs. I disagree with this. Sure, both sides in major disagreements often actively

There's two communities for that: "Hive improvements" for change suggestions "HiveDevs" for ongoing work Maybe we could give these particular communities automatic visibility on the

I hope (and believe) we're far faster, considering we've got 12 programmers working on hived and hivemind, and they generally had an average of around 4 programmers or less working on those code bases,

I'm not sure why there wasn't a notification about his cc, maybe there were so many it blew some kind of limit. I'll check into it when I get a chance.

Hi, I'm sorry about that, but I asked someone involved in the exclusion analysis to check into this, and it looks like your account was proxied to zzhang at the time of the hardfork, and that account was

The rating system I'm planning has little or no relation to steem-ua's purpose (or to Hive's current reputation system either). It certainly requires human interaction, but I see no way to solve the problems

The brief image outage was a problem with the cloud service provider that hosts the image server. We do have a plan to add redundancy there, but all our devops people have been buried in work associated

All 2nd layer transactions are stored on the 1st layer. The first layer does the required step of "ordering" the transactions in a decentralized system. Without this ordering step, different

Any automatic market maker would need to be defined in the context of the token system it makes markets for. For HMTs, this would would mean some extra functionality that would need to be built into the

As I mentioned at the end of my post, this is just a list of changes that the BlockTrades team plans on implementing. I believe @howo has done some work on the RC delegation feature, which we'll review

I don't see any immediate reason why this should lead to more spam (assuming you're talking about the 2 hour window change). If you're talking about going back to straight linear vs quasi-linear, I think

It's a comment pretty much intended for Hive programmers, I think. I understood it all, but I can see it would be confusing for anyone else.

Ratings are planned to be a mix of public and private information. Software timelines are always difficult to set. But the things planned for HF25 are easily achievable in 6 months I think. The other features

Yes, this is ultimately what I'm most excited about too. If I ever have a magnum opus, this will likely be it.