I created an opinionated price feed widget - and got blocked by Google

Please see my previous "building on HIVE" post How I use AI to "Build Things on HIVE" to get caught up to date.

While working on this story, I stumbled through all sorts of exemplary complications that one faces when "building on HIVE" - so today we get a grab bag of lessons learned and being learned.

"It all fits together" (in your head)

So our site today happens to be a grab-bag of experimental ideas all its own - at once a Colombian operating entity (S.A.S.), a hive-engine token, an experimental "front-end and onboarding platform", and loosely linked to other experimental work with standalone tools (https://tools.crypto-dreamr.com) and TTRPG gaming (https://thecrazygm.com), which I am sure will feature more as this series goes on.

It turns out our https://ecobankdevelopment.com site is already public, I guess I didn't know this - but probably after our experimental attempt with DHF funding on a platform of "yourFrontend / yourBackend" - and a few years of actually being "HIVE travelling salesmanonboarders" - we began exploring deeper and more sophisticated onboarding "optional solutions" directly inside our work with Ecological Restoration.

Easily found with TAO image search tool

This Repository is Public

https://github.com/TheCrazyGM/ecobank

I insist this post started by talking about an opinionated price feed widget! It turns out that the original widget mock-up isn't even public repository (but that's the subject of the next post now... such is life), but our fascinating rabbit hole here will only let us stop to contemplate the "opinionated" decision-making framework - in a world of "open data" - opinions are valuable!

I have an opinion

If I learned anything from our experimental DHF shenanigans, its that everyone has an opinion. You don't have to like it, you might not agree with it, you probably don't have time to rebutt "all of it" (pick your battles), but now I'm on that DHF drip with @acidyo and I am set out to prove one of my opinions - "making posts about what you (we) do is important, especially in "development", and not doing so - considering HIVE's nature - is a sociological crime".

Yes posting is hard - and its a separate skill set you might say than "development".

And beyond that - development is non-linear. It turns out - Google has an opinion too!

Claude, I have a problem - and I need your help

So the first thing you can do when "things happen" is talk to your agent. Talk to your agent and make a plan - this is the way. The modern way:

1. Please explain this, what is the scope?
2. Let's make a plan to address this - what are the options?
3. What are the tradeoffs - pros and cons?

And soon enough you will be "proceeding step by step":

https://github.com/TheCrazyGM/ecobank/pull/18

You can review the Pull Request yourself - check the commit lists - read the comments. Github isn't an alien planet - but it can feel that way at first.

Group onboarding

While I have explained Who is this for? and tried to break down the Group Onboarding Strategy in the past - I'm not convinced anyone actually noticed. But now that I'm getting the DHF bucks, prepare for more explanations and efforts to break down this strategy and techniques more fully.

"We need these things for our business", maybe others will too. And we are happy to help - including recieving feedback, issues and PRs. The last grab-bag item today is about "collaborators" - this is Open Source after all!

Email to our corporate github: SRBDE

We got this question from a "fan", and it was some great feedback using their tools and cross-referencing their own work - a fantastic thing to find in the inbox and read through - very motivating.

And I did email back! "I serve the HIVE" so-to-speak, and we love to see it and want it to be known:

1. use issues, or tightly-scoped PRs
2. comments welcome
3. we are happy to review real efforts

We continue to improve our (cross) linking and outreach - working hard to show you how the sausage is made.

Freedom and Friendship