With the pace of technology, even those phones will soon be replaced by 4GB phones :-) Its just like there is no point in us designing for 16KB computers (the first ones I worked on).

I'm not involved in marketing for Hive very much, I just provide technical info to people that want to market Hive. I made a decision early on not to get involved in the marketing of Hive and stay on the

Yes, the idea is that the customizable web sites will be built from the web components we've already released. First issue that has come up is potentially allowing them to server-side render for SEO

Docker for Windows is actually super simple to install :-)

We've been working on our smart contract system since Hive began :-) I posted about a few of my ideas for it back then: Update: actually reading post in the above link, it didn't actually talk about smart

The new stack is fully self-documenting for all the new REST calls (not so much for the legacy JSON calls, but these are going away). And the interactive docs are "forced" to keep up, because

Actually, HBD is listed on some exchanges, just not many. Many people actually run bots trading HBD on those exchanges, because it is possible to profit from the "stable coin" value and temporary

I guess most obvious thing would be the description of themselves from their json metadata + some account statistics. But seems like a good question to ask potential users. Anyone want to suggest what

I think the "hive account" should be the next implemented, I guess a lot of people would like that one.

"your vote is enough" -> That's just my point: my vote is not enough. I'm voting for all 3 of those proposals, but they aren't funded (one was for a while, the other two have never received

It's a bug in condenser (the software that runs on hive.blog and some other sites). A fix for it has been merged, but not yet deployed. Here's the MR by @quochuy to fix it:

Proposals #322 #337 and #346 disagree with your statement :-)

You also kept your cool well during the time Bartek and I were having epic text battles about the wax API :-)

We have several ideas for how to roll out the technology to public nodes, but it's too early to comment much until we've completed more performance tests on exactly which method we'll use to support api

Here's output from ours this year so far in kWh: jan 749 feb 863 march 1420 april 1360 may 713 System config: Panels capable to generate up to 12.5kWh, 70% on the east side, 30% on west side. The inverter

I'm not much for burning, but willing to throw a vote for the experiment.

Looking over a long period, the volume doesn't look too different from previous periods of time. As to why we see spikes, could be any number of reasons. I do feel that's been a lot of positive developments

Regarding metamask flask, I was told: I think it's because we are still not official and for that third party audit is required which is scheduled soon

I think around 10 is enough for now. With the new stack, any single one of them can easily handle all of the current traffic load of Hive, so adding lots at the moment is just overkill in terms of resource

It's also worth pointing out it's not a complete summary either :-) For example, it doesn't even mention the new health checker component or workerbee at all as far as I can see. It seems like a good summary