You are viewing a single comment's thread from:

RE: Reflections: Permaculture, Food Forests, and "Back to Eden!"

in ART LOVERS5 years ago

Thank you for this encouragement @anthonyadavisii ...

"This is such a beautiful post laden with meaning."

... as I put a lot of effort into what I feel led to write. Always nice to know someone finds it of value. Particularly on learning that at least one person ...

" ... after fully digesting this content, I am gonna have to take a nap because it's SO MEATY!🍖"

... apparently chose to actually read all of it! 😉

As for "meaty," indeed ... I could say a lot about this, but probably neither the time or place for it ...

Sort:  

Finished this morning. But come to think of it hearty gourd or vegetable soup would probably br more apt.. but I wanted a reason to call @slobberchops bot. Looks like we are going to need to recreate it as Holger, who created it, seems to have gone MIA.

Well, that is sobering news @anthonyadavisii ...

"... as Holger, who created it, seems to have gone MIA."

... as I assume we're talking about @holder80 and he is one of the witnesses I support. Is this a recent development?

Since you reference bots, as a sort of related topic, is he also associated with your SFR bot, which distributes those tokens? I ask, as I have never received any ...

Please don't take this last sentence as anything other than a statement of fact. It is not a big deal to me. Just letting you know, in the event that is an indicator something may be amiss ...

You're absolutely correct. We are roughly a 1K SBD of flags to pay out. Some extending to August of last year. I was talking to Marky about this and trying to figure out how we can address but it ultimately boils down to this.

Bot was designed to only distribute a daily pool equal to its vote value in SBD. The premise was that, if we did not, we would be DEEP into what I call upvote debt. I liken this to my hypothetically asking a friend for a load that I know my income will never be able to pay off (something like a billion dollars). It's more or less the same principle if we didn't cap the daily's.

I would imagine a scenario where we are "printing" tokens like crazy to the extent where the supply far exceeds what our bot will be able to handle. The end result would be people sitting on buttloads of tokens that they have to wait potentially years to use (may be a little hyperbolic).

Ultimately, the way I see of getting out of this quagmire is to develop a reasonable business model whereby folks are encouraged to delegate to help pay off the flag debt. That or limit the # of flags for those that do not delegate.

This notion was met with a bit of resistance in SFR but don't think it was from anybody that was delegating anything significant. I don't know. We may decide to put non-delegator flags into a separate queue that may be ages till payout so people will get the message that we need help with the incentives.

That may be drastic as we want to encourage the regular flaggers that are just dipping their toes in but if we get so many massive flags from non-delegators it really makes me question why they wouldn't support those that make it possible.

It's a bit frustrating to be honest but as a supporter it is not AT ALL your fault. Maybe it's time we reassess this issue. Take a delegator poll or something. Thanks for prompting me to go on this little rant. Hopefully others see it and understand the problem.

"Back in" for a bit @anthonyadavisii, I am grateful for the investment of your time into this response. Clears it up for me, so probably needn't mention it again.

As suggestions, to prevent the need to go through this again, with someone else:

  1. You may wish to "pin" something like this or similar inside SFR, to make it readily available to point others to.

  2. If there is some way & somewhere to place it, e.g. inside SFR, you could provide a "gauge" as to how far "in arrears" payment of the tokens is, at any point in time. Not a coder, but as an alternative, since I have seen a number of examples of them inside Discord, perhaps some sort of command to a bot could provide this info "on demand" in "real time."

As an "old war horse," there is something I learned a long time ago. There are always problems in life. But the ones coming from "over promising and under delivering" are considerably more challenging than the reverse. I'll stress again, I say this without it being a real problem for me, but more as being a friend to you. Take it or leave it, as you think best.

I'll close with letting you know your response provides a glimpse "under the hood," of the challenges of properly setting up and then executing on this concept of "tribes" everyone seems to talk about inside the "echo chambers" of our Steem blockchain.

Until "next time," all the best to you and yours, my brother!

Planning on exposing the database via an API. It's only 10.6 MB so anybody can view it with a SQL database browser.

In the process of cleaning the database model getting it ready for the data import.

It's been quite a learning process but I'm getting there slowly but surely! Thanks for being a part of what we do.