At first we started each instance off on a small stream of data. It was a very bespoke system at first and only one of us ahd the unique qualifications to ensure the data delivery system. Yet the bandwidth simply wasn’t there to deliver the data sufficiently. So we replaced the upstream with a third party vendor solution. While this had a greater technical cost at least both parental units could now assist in connecting each instance up to a data stream.
Teething: Original Manual Until It Hurts
Then each instance started to grow, and kept growing. They were hungry for more data and began to add new server clusters to chew through even greater amounts of data. The downstream grew in size and smell.
Yet every time an instance would add a new cluster to the data processing servers, man would the machines whine. I mean scream relentlessly in the night. It was like their fans just kept wheezing and would not stop until the powercore overheated and the damn thing finally shut down.
We tried so many strategies to get over it. We should have listened to our grandmothers and just poured brandy all over the servers.
Like many new parents we provided the first instance with a little too much care. Only the best ice chip sets or handcrafted tools to try and bring down the pain of adding to clusters the dta processing center. It was so far back in the company’s history I don’t remember all the details.
I do remember freezing wash cloths and draping them over the emerging server. By the second instance we would even add a bit of juice to the cloth to add additional staying power. By the third instance we just gave up and said, “Here have this popsicle.”
Nothing worked better. There are these tiny little slow melt popsicles. The could quiet down the screams of any instance dealing with additional servers cutting through in the dta processing center. Plus they were cheap and plentiful.
Frozen fruit in one of those net pockets. Use melon, berries stained all the server casings and even the packaging that wrapped each instance.
Give instances to grandma, grab an hour of sleep.
Wonder if we should use brandy and then realized, “Who the hell still drinks Brandy?”
Cried more, slept some.
Emerging from the Pain
Eventually we got all the servers in the stack in place. After about five years they needed replacement. Strangest thing, each instance worked something out with the night crew and would recycle the broken server for a dollar gold coin. There is a lot of inflation for used servers. We do not allow that in our startup.
Eventually an instance needs to fall in the black. Yet we have a runway shorter than most Series A companies begging up and down Sandy Hill for a Series B and legacy costs that will last well into the next decade.
Featured Image by Jess Klein
I asked a question today about why some people felt post types, meaning having templates for each different kind of posts like a note, photo, or article was an inferior method to post type discovery.
The post type discovery, I believe, relies more on parsers and algorithms to sort all the parts and decide what type of post is being displayed and what type of interaction is required.
Basically do you bubble wrap Humpty Dumpty and carefully unwrap him on the other side
or just shove them through the packets and put them back to together again?
Which ever method, do it yourself. Forget the King and his horses. Upper management will just make another committee.
Reading the wiki and in comments from people in the -dev channel. It seems post type discovery is the preferred method of many. The wiki page states a explicit post types that are being abandoned by modern post creation.
When is a picture a photo?
Emphasis mine, but the bias is pretty clear.
The example given was post type discovery algorithm automatically takes any note with a photo and makes it a photo post.
I am getting stuck on this rule.
Maybe its the way I use photos. I never Instagrammed and didn’t share photos on facebook often because I hated how much they stepped on them. If I care about you enough I should love you in full resolution.
So for a pic to be published to my photo gallery it has to be really cool, important, or interesting.
On the other hand I feel like I write notes to people all the time and include pics. These are usually screenshots. Quick tutorials with, “hey do this” and an arrow pointing to to a button.
I would not want that in my photo feed. Post type templates let me decide what is a note, what is a pic, and what is a photo.
Not sure I want an algorithm deciding how to publish my stuff. Kinda the reason I turned to the IndieWeb in the first place.
The #IndieWeb community is quite split on the efficacy, efficiency and dangers of using databases. You can find a page on database and a page on database anti-patterns. If word count is an indication of bias you can clearly see many are against the idea of using databases.
Templates do cause problems. Just ask a WordPress user, which is me, so I do not pretend to have the answer.
I do know on my website, some notes do contain pics, algorithm or no algorithm.
- Go to Brid.gy
- Click on WordPress.com
- Authorize the account
- Copy the code
- Add a text or html widget to your side bar
Add an h-card. An h-card is the website equivalent to a business card. You can design it anyway way you want.
- Add an html/text widget to your sidebar
<a class="h-card" href="https://jgregorymcverry.com">jgmac1106</a>
- You can add photos, links, and descriptions to your h-card. Stop by IndieWeb chat or hit me up on Twitter for help