My "steemgigs" Witness Is Now On The Recent V19.6 & Other Updates.
My "steemgigs" witness have been upgraded to the more recent version 19.6 from the version 19.5 that it was. This is a relation to a patch released by steem to fix a bug. This was a quick process and didn't require a replay.
In the long run, i will be shifting to version 19.11, the patch that allows unlimited edits of posts, when more of the top 20 witnesses have decided to shift and the version attains a stability and this is likely to be soon. As this switch is very likely to require a replay and a period during which the witness will be disabled (temporarily) for maintenance, i am will have to look for a timely time to carry this out. I will likely do an update post regarding the temporary disabling to inform "everyone" who supports my witness and potential supporters.
I also wanted to use this post to speak of a full public RPC 256 GB RAM node that once was active on on steemd.steemgigs.org It is no longer active though may still be listed on different portals across steem as a valid node but it is inactive.
RAM requirements grew rapidly during the times when it was active; thus, i had to consider disabling it being that it was becoming evident at the time, that it was going to start requiring 512 GB RAM and maintaining that at the time, would have been too high for me per month as it would cost more than 1,000 dollars to set it up and close to 1000 dollars to maintain it per month. Besides it was a scarce server for being very large and there weren't many options of data centers to use let alone cheap options. Also, at the time i was having many expenses in relation to the development of steemgigs.org etc
Thus, i had decided to have more focus and divert expenses towards the development of https://steemgigs.org after running the steemd.steemgigs.org 256 GB RAM public node for many months. More recently though, steem has made endeavors to reducing server requirements for witnesses and nodes by the application of Appbase; thus, in due time especially, when some of my steem-based interfaces are in stable motion, i will love to go back to contributing a full RPC node to support the steem ecosystem as i very much love steem and heartily seek its growth.
https://steemgigs.org has been pretty inactive too. Its use has drastically reduced in relation to slowed development. In recent times, development on steemgigs.org has been slow due to many factors. It is not a very easy site to build overall and even with a development budget, development has stalled as there are many other factors that come into play apart from a budget. For as much as possible, i want to build interfaces that are practically free, so even with regards to a team, we need to share "a mindset" in this regard.
I very much want "everyone" in the paradigm. I want all the interfaces that i am involved with in relation to steem to represent bigger things than a website. I want these spaces to form a home; "a haven"; away from the rest of the internet. Thus, there has been need to experiment and grow in experience overall, to return to the development and completion of steemgigs.org
While it appears easily like a freelance marketplace, steemgigs.org was a ecosystem for "SteemGiggers" (Dream-builders).
Considering also that we want to apply the use of the teardrops SMT among all our interface, we have to take things slow, to build models that will give our token spanless value beyond just a spendable currency. The teardrops token is "an emblem"; "an emblem of human" and we want each one to love possessing it.
Though it still holds of a database, activity in its development has slowed down as it needs intense focus and experience and this experience i am now accruing over the course of developing ulogs.org
"Experience" especially with regards to dealing with developers, relationships etc
This has birth an entire enterprise in Macrohard, that has scaled methods drastically using a "micro-programming-tasks" paradigm, to create a more balanced ecosystem, allowing "everyone" to contribute to development without stalled relationships and thus, without stalled projects.
The development of ulogs.org has ever since formed a very viable case-study and has helped me accrue very necessary "experience" that will help me drastically, when returning to the development of steemgigs.org
ETA to take all my steem-based interfaces to stable and use-able state is still this year as each of these interfaces have to be ready before the Smart Media Protocol is implemented by Steemit INC.
I look forward to choosing a team over the course of time. Well, i have been on steemit for up to two years and now have a community on the SteemGigs discord approaching 6,000 members and i have come to identify brothers and sweeties and a "great team" is attainable.
In my case, "talent" is not everything, "brother" more is. There are tons of talents worldwide, it is no standout. Other virtues even un(dis)talentedness is of more pertinence to me, among the things i seek out in brothers/sweeties.
Once ulogs.org enters a certain state of stability, it will be announced for full-blown use, then we will return to Project SteemGigs to develop it using the "micro-programming-tasks" paradigm. This way, we very actually involving "everyone", removing all barriers-to-entry. While we accomplish "true celebrity-hood for everyone once and for all" using https://ulogs.org, we will seek to accomplish "a world of dream-builders (SteemGiggers) using steemgigs.org
All interfaces are tied as a "true celebrity" will form a great SteemGigger (dream-builder), creating beautiful disruptions; "SurpassingGoogle".
#ulog is a global movement
- Please like this page on Facebook
- Please subscribe to this YouTube channel: UloggersTV
- Kindly join the communities on Discord & Telegram
Kindly vote for the "steemgigs" witness.
If you want to support an extra witness and you support mine "steemgigs", it will be really helpful.
If you want me to make witness voting decisions on your behalf, simply visit https://steemit.com/~witnesses and type in "surpassinggoogle" in the second box for proxy.