can be as painful and tedious as the process of birth. Well, I exaggerate a little, but I don't think that is so great an exaggeration.

So, it turns out there is a nice, kinda high-tech latinic related TLD

.ae

Yes, UAE. That bit kinda bugs me, but, hey, I don't think it really matters, because if the DIV design goes forward, down the track, this will mean that calibr.ae is not the actual site that delivers any content, only the app. The replicators will serve up the pages, and they will be anywhere and everywhere.

Update

It took me a little while to make it obey me, but now calibr.ae is pointing in the right direction. Tomorrow I am putting gitlab and jekyll on it, and in the meantime, it's syncing steem blockchain so I can export it and start writing code to slice up the export.

By the way, I updated the image, the lil' hummingbird on the top right there is the 256x256 pixel version of the logo. I will work on the text soon. I did all that cutting manually, using the Gimp. I need to refine it a little more, especially over it's head, and at the edges of its wings, which need to sorta be a bit more blurry, but I am pretty pleased with how it looks so far.

So, to explain the name. Many words are linked - Libre, Liber, Calibre, Collaborate. That pretty much sums up all the parts. Free, literature/media, measure, and collaboration. I have always liked the latin words that end this way. You can pronounce it there ways, -i, -ay and -ai. I don't really care how you pronounce it. It just mainly was the TLD that dictated this. I couldn't find .ia, and .io is so saturated with crypto names these days, like even steem.io.

@xeroc was greedily exclaiming that he wants to build shit for this fork, asap. He said the name was important. So, I started this process of decision.

Another steem-dweller who came and chatted at the discord helped me get into this process, and we started actually by discussing computer language grammars, he's a fan of OCAML. I explained to him how I really like Go, but mainly because of the short notation for return tuples. It made me remember how Haskell has these, and how much I liked them in Vala as well.

In my opinion, Go's 'goroutines' are a waste of space, and I will never use them. I will prefer memory-isolated processes, and functions that don't share variables. Functional Go, if you like. It's my personal Idiom. Event driven, but concurrency is handled through OS process management and memory isolation.

So, I go off topic quite a bit. As you can see in the floaty image above, I have a nice CC image from wikipedia, of a hummingbird. Kolibri is the Bulgarian word (and several other languages) for hummingbird. So, this will be the logo.

Nothing springs to mind about conceptual associations with hummingbirds, except maybe that they pollinate and they love flowers and nectar, and they are extremely fast.

So, maybe the image is acutely appropriate, considering that I may decide that I am going to pull SporeDB into the mix, and these fast reliable broadcast and epidemic protocols.

The Migration Process

The fork will first just be a straight, simple transplant, with the 'genesis' blocks compiled from the Steem account registrations, and account balances, at the day announced, which will be a week in advance, here, on Steem, maybe even 2 weeks, to be sure to be sure. And on other places like bitcointalk, and wherever anyone who gets involved wants to announce it.

The extracted accounts, the usernames and balances, will be altered in only one respect: all the SP mined before the steemit.com site went live, will be subtracted from the relevant accounts, and added to the initial rewards pool. Yes, @berniesanders, @dan, @nextgencrypto, and all the rest, you will lose your advantage. The loss may not be enormous, but to compound that, I doubt you are gonna come play where you are no longer Gods.

Outside of this initial migration process, it is intended that on one side, the database backend of the RPC nodes will be split up to put the forum posts in a separate store to the rest of the transactions.

Beyond that, I am going to work on upgrading the validation mechanism, data propagation mechanism, on devising a data pruning scheme, monetising the service of RPC endpoints, and adding Code Repository to the rewards scheme, as well as Q&A, Wikipedia type data, as well as, of course, adding a special type of user registration that is corporate and can have internal voting systems for ownership transfer and control of group membership. And all the rest. Exchange, classified advertising...

This is basically going to be DIV, except, step-wise. I think it will work out much better if we bring the people with us. So we start with a fork. I will be digging through the code and making sure that I can implement a chain, and we will be then looking for people to run the network. The consensus rules will be frozen as they are now, with Steem, until the system is up and running and all the accounts are migrated, and the developer group will also have to be formed, of course.

Changes beyond this will be more frequent, and less in number per change (preferably one change at a time) under the Calibrae system.

I am still even considering if the premined accounts should even be permitted at all. I am inclined to say no. They kept mining quite a ways after, and many started witnessing as well. I am going to just analyse the new account creation frequency, and the steemit.com site launch, and balance it so that everyone can migrate, but the early people, who not just had direct advantage, but also may have circle jerked themselves in the early days, do not get any advantage.

I don't think they will want to come anyway. No skin off my nose, and I don't think that is gonna be a dealbreaker for the at least several thousand users that will migrate at the drop of a hat.