Kyluke McDougall

Cornelius Weidmann

Ever wanted a smart helper right in your terminal? Termai makes that possible.
Built with Rust, it brings AI capabilities directly to your command line,
turning your terminal into an interactive and intelligent workspace.

Termai is a tool that integrates OpenAI's models into your terminal. It's
designed for single requests, offering quick answers, code snippets,
explanations, and more, all without leaving your command-line environment.

: Work within your familiar terminal setup.
- 

: Get instant responses without breaking your flow.
- 

: Include directories as context for more relevant
answers.
- 

: Pipe outputs from other commands directly into Termai.

: Need a function or snippet? Ask Termai right away.
- 

: Generate README files based on your project's code.
- 

: Pipe `git diff` into Termai for concise commit
suggestions.
- 

: Provide data and receive instant insights.

termai "Create a README for this project" .

termai "Explain this code to me" src/main.rs

git diff | termai "Create a short git commit message"

I dislike submitting content AI's that include certain phrases or names (company names, clients, my personal name etc). It's possible to set redactions as well.

Anything added to this list will be replaced before sending to OpenAI with '<REDACTED>'. 
You can also view the list of redacted phrases/words by running

Discover how Termai can enhance your terminal experience. Give it a try and see
the difference!

Bringing AI to Your Terminal: Meet Termai

Sometimes all we need is just a little bit of fresh paint. And when it comes to websites and apps this is equally true. Sometimes a small dash of fresh "paint" can make an old and never-changing UI feel fresh and modern.

The kyco website itself has undergone several iterations, however, the most recent one must have been the easiest to implement with the most drastic impact. The change already took place last year May (2023) and I feel it still looks fresh and modern, especially when compared against the old design.

Can you notice a difference? Which one do you prefer?

All it took was adding two new fonts, adding more whitespace here and there and slightly adjusting the font sizes.

When giants like WhatsApp or Google change their UI the whole world gets to see it and it is very apparent that - even when nothing functionality-wise changes - a small splash of fresh paint can make a big difference!

The difference a small splash of fresh paint can make

Google Analytics allows you to export your data in several formats including PDF, Google Sheets, Excel and CSV through its user interface. While there are plenty of guides out there that cover these methods, they all seem to assume that you love spending hours on end laboriously exporting your data manually. We can skip these time-consuming approaches and use a smarter, more streamlined, automated approach.

Instead of relying on the manual process in Google's user interface, we will use code to directly access and format the data we need. Our goal is to create a tool which will end up looking something like the below.

The tool provides a basic "pagepath" / "pageviews" chart and table, which can be effortlessly exported to both CSV and JSON.

 you need to setup a "report request". For this you will require a 

 linked to your Google Analytics account and a 

, which are essential for authentication with the Universal Analytics API. Below is the foundation of our automated approach:

You can also enhance your report by adding more metrics and dimensions. For instance:

. If you have specific questions about the report request then the 

Google Analytics Viewer simplifies the process of retrieving and displaying data and gives you a good basis to start your own "code to data export" mission. For a detailed walkthrough on setting it up locally refer to the 

Configure the metrics and dimensions which are relevant to you.

Manage initial data transformations and adjust the frequency of API calls. The code already accounts for API request limits and uses the library 

 to ensure all data can be fetched without hitting thresholds.

Adjust how the data is finally transformed and exported. The main methods you'll want to adjust are:

used to manipulate data for display in the chart and table

used to define the structure of the CSV file export

And that's already it! I hope this tool helps you get your data exported.

How to backup Universal Analytics data?

Have you ever written code which you then had the joy of revisiting a few months or even years later and found yourself asking, "What the fruit cake is going on here?"

Me too... Here's a list of how to make code simple and easy, not complex and hard.

Hope that helps. Good luck on your coding adventures fellow traveller.

Simple made easy

The following is a short story I read many years ago while I was at university studying to become an engineer. It is a story which I think about quite often, even to this day.

I think it resonates with me because I've always had a deep yearning to be content with what I have, and also, because I would love to live on an island... who wouldn't want to stroll along the beach every day of their life? The sound of the waves with the palm trees in the background and nothing more than the sunshine inviting you to enjoy the beauty of life.

A boat is docked in a tiny Mexican fishing village.

A tourist complimented the local fishermen on the quality of their fish and asked how long it took to catch them.

"Not very long." they answered in unison.

"Why didn’t you stay out longer and catch more?"

The fishermen explained that their small catches were sufficient to meet their needs and those of their families.

"But what do you do with the rest of your time?"

"We sleep late, fish a little, play with our children, and take siestas with our wives. In the evenings, we go into the village to see our friends, have a few drinks, play the guitar, and sing a few songs. We have a full life."

The tourist interrupted, "I have a MBA from Harvard and I can help you! You should start by fishing longer every day. You can then sell the extra fish you catch. With the extra revenue, you can buy a bigger boat."

"With the extra money the larger boat will bring, you can buy a second one and a third one and so on until you have an entire fleet of trawlers. Instead of selling your fish to a middle man, you can then negotiate directly with the processing plants and maybe even open your own plant. You can then leave this little village and move to Mexico City, Los Angeles, or even New York City! From there you can direct your huge new enterprise."

"Twenty, perhaps twenty-five years." replied the tourist.

"Afterwards? Well my friend, that’s when it gets really interesting," answered the tourist, laughing. "When your business gets really big, you can start buying and selling stocks and make millions!"

"Millions? Really? And after that?" asked the fishermen.

"After that you’ll be able to retire, live in a tiny village near the coast, sleep late, play with your children, catch a few fish, take a siesta with your wife and spend your evenings drinking and enjoying time with your friends."

"With all due respect sir, but that’s exactly what we are doing now. So what’s the point wasting twenty-five years?" asked the fishermen.

A story about fishermen

In the realm of public spaces, the concept of a 'commons' bears versatile significance. Essentially, a commons is an open, publicly available space, inviting everyone without any discrimination. This age-old idea of a common ground, a place for civic discourse, collaboration and co-creation, remains as relevant today as it ever was. But what happens when private entities step into this traditionally public domain? Can a private entity create a true 'commons'? If so, what does it look like, and is it really a commons?


Before we engage with these questions, let's look at a few instances where private entities have created a space marketed as 'commons.' A case in point is the Apple App Store, an ostensibly open space marketed as being available to any developer, despite being restrictive and curated. Google Play Store provides similar services, with slightly fewer restrictions, but toeing the same line with respect to government restrictions. Twitter, now rebranded as X, has strived to be the “town square” of the internet, upholding the ethos of a commons where anyone can engage in global discussion and voice their opinions. Yet, even they have drawn flak for censoring tweets and users, under the guise of protecting narratives or advancing ideologies.


So, given these instances, can a private company genuinely create a commons? Can a space crafted by a private entity, intended for public consumption, still bear the same level of unrestricted access and equitable engagement that defines a true commons? The answer is somewhat layered. Yes, private entities can form what can be called 'commons,' provided they manage to nurture an atmosphere of inclusivity and public ownership while maintaining a transparent and restricted influence.


Historically, examples from Ford Motors to Penguin Random House seek to suggest that the definition of commons can be as fluid as the entity creating it. Henry Ford’s Model T car democratised access to a public commons of roadways, while private publishers have created a knowledge commons accessible to the masses. In the advent of open-source software, companies like Red Hat have given the world a model of collaborative creation and shared ownership.

Modern sharing economy models, as seen in Uber, Lyft, and Airbnb, serve as an illustration of a 'sharing commons.’ Herein, resources like vehicles and homes, instead of being individually owned, become part of a shared ecosystem, marking a transformative step towards communal consumption.


However, these examples also drive home a crucial point. The true spirit of a commons—untrammelled access, absolute freedom for public discourse and collaboration—should not be sidelined. This balance between upholding the ethos of a commons while acknowledging the limited role of a private entity is the key to achieving a truly open commons.

As we advance further into this interconnected age, the conversation around private entities and the formation of a commons will only escalate. As such, striking a delicate balance between preserving the integrity of a commons and acknowledging the evolving role of private entities in contributing to it remains crucial. A commons, whether physical or digital, whether initiated by a public or private entity, should fundamentally serve as a foundation where humanity can thrive.

While it is indeed possible for private entities to birth a 'commons', ensuring the universality, inclusivity and equity of such spaces poses an ongoing challenge. But, if addressed correctly, these can serve as spaces that truly epitomise a 'commons' where ideas are freely exchanged, and community creation is prioritised. This lies at the heart of what a ‘commons’ originally strives to be, regardless of its origin or who sparked its creation.

Private Entities and the Creation of Commons

In the rapidly evolving realm of software architecture, it is all too easy to become overwhelmed by the complexities and intricacies of numerous features, tools, and frameworks. As a developer, prioritising software minimalism – the practice of implementing only what is necessary while maintaining simplicity and efficiency in your code – can significantly bolster your productivity and ensure long-term scalability & maintainability. In this article, we delve into the essential aspects of software minimalism.


At the core of software minimalism lies the guiding principle: "

implement only what you're going to need.

" By adhering to this fundamental tenet, you can ensure that your code remains pristine, manageable, and efficient, even as your project expands in complexity.


Essential Components of Minimalism in Software Development:

Consolidate and Streamline your Infrastructure

When working with various services and internet accounts, strive for simplicity by consolidating and streamlining your digital interactions. By opting for a focused ecosystem, you can ultimately save time, resources, and administrative effort, even if it entails a minor premium.

Emphasise Simplicity: Avoid over-complicating implementations

Concentrate on addressing the most pressing and immediate requirements, rather than attempting to predict every possible scenario. Trying to accommodate numerous use cases simultaneously can lead to intricate, difficult-to-maintain code and potentially trap you in seemingly insurmountable software challenges.

Complex implementations can wreak havoc down the line, resulting in protracted feature development times, more arduous bug resolutions, and escalating iteration costs.


Practical Strategies for Embracing Software Minimalism:

Prioritise the essentials: Focus on the features critical at the present moment while thoughtfully designing an architecture that accommodates future developments or modifications.

Remove redundancies: Swiftly eliminate components that do not serve an immediate purpose, preventing unnecessary clutter and confusion.

Engage in regular refactoring: Consistently refine your code to ensure it remains clean, efficient, and well-organised, even as new features are introduced or requirements evolve.

The Potential of Minimalist Software Development

Software minimalism is a sound approach to software development that emphasises simplicity, productivity, and enduring maintainability. By concentrating on the essentials, eliminating excess, and diligently refining your code, you can master the art of minimalist programming, crafting efficient and adaptable software capable of being maintained long into the future.

Software Architectural Minimalism: Simplicity and Efficiency in Development

When it comes to writing a feature, and when it comes to getting that feature out the door, and usually when that feature should have been out the door yesterday, managers very often tend to "solve the problem" by 

"More" or "more senior" is not a guarantee for anything

Features are not "problems" that get solved by simply throwing "more resources" at them

Features are not "things" that get resolved in a randomly allocated set of time which was determined by someone who has never touched the code (cough cough, e.g. managers or even worse finance departments)

Features are intricate and complicated - you could even argue they are an art form, and this needs to be understood!

These so-called "resources" that mangers work with are actually human (who would've thought?) They can hear, they can see, they can touch, they can smell, they can taste - and, they can even "break", "malfunction" or "simply not work". If a manager assumes: "I have one developer here, and I can add another one here and then perhaps a third, then I will have exactly 300% output - or perhaps even 350% depending on the so-called seniority. Brilliant!" Then that assumption is wholly flawed!

"Resources", aka developers, aka humans, have very different approaches to solving problems, writing features and creating art. Some might love building nice-looking features, some might prefer practicality over aesthetic, some might prefer speed over function, some might not even care about the feature, some might want to paint the inside of the box even though no one will ever see the inside of the box, etc. etc. You get the point.

Knowing the people that you have working on writing features will help you understand how to resolve problems without necessarily throwing more people at the problem - as your general approach!

And usually, the more people that are involved in writing a feature the more difficult it will be for them to complete it.

Would you rather have 10 people write an essay, or three, or rather one?

If you have one person writing an essay (regardless of the length or complexity of it) you'll most likely end up with an essay that has great coherency. If you have three, you might still have the same coherency but the writing styles might differ or it might seem like different people wrote the essay. If you have 10 people writing the essay, heck, you might end up with a poorly executed ChatGPT essay which you've explicitly told to be unreadable and incomprehensible.

Perhaps you have a person that's really good at writing the entire essay. And maybe that person is also really fast and can always tackle an essay on their own. But maybe you have an essay that needs to be a 1,000,000 words long and it needs to be done yesterday. In such a case, 

People have different strengths and quirks - and things take time. There is no magic "reduce the amount of time it takes to complete" button - we would have all pressed it a long time ago!

One person might be really good at writing introductions (starting the feature), another might be really good at writing the body, yet another might be really good at fleshing out sentences and filling them with emotions and capturing a reader's attention, yet another might be a better grammar police than any online grammar tool.

If one person is slow, another might be quicker, but therefore sloppier. One person might not be able to express sentiment in coherent sentences, let alone write a word, and is being asked to write a really short and simple introduction. All of these things matter! The people might not even like working with each other. Some might not have the right tools, some might need "bringing up to speed" (lol - should've been done yesterday), some might need to jump off other things they're in the middle of. It's really a bit of a jungle and simply "adding 10 more people in the last minute" will 

It takes great skill to find and encourage people to work together on something as seemingly simple as a feature.

Given that each person has their own strengths and that each person approaches problems differently one has to make room for interactions that take place outside of the "writing the feature" part - and those take time and need that time. No amount of "it needed to be done yesterday" can speed this process up.

 purposefully allow for extra time to overcome the initial complexity which you are disruptively adding into the mix before expecting even a single line of hoped-for "quicker code" to be implemented.

There is always a trade-off where adding more people will simply result in a communication and complexity overload which, sure, by your calculations would just be a matter of "add more", but in the end will result in something more along the lines of "should've added better".

What managers need to know about writing features

Rust is not trivial and neither is testing your code. How you approach your testing can depend on your perspective.

If you're coming from the OOP mindset, you probably want to mock all objects and almost see that as a given. Some people with a functional programming background are already going wtf, this is a code smell. However, in both cases, at some point you'll find yourself trying to test code that interacts with another system.

If you need to define functions in rust that need to return different values (maybe something akin to a mock?) when writing tests, the 

 annotations can be really useful. Let's use an integration test as an example.

 package as an example for this. It has an interesting feature that allows you to open up a database in memory. This is different to other setups where you would usually provide a database connection string as an environment variable or a config. This also allows us to create and destroy the database purely for testing purposes.


Let's say you're trying to code that does a database read/write. During automated testing you want to create the database in memory, but in production, it would need to open a connection to the production database.


Rust allows us to annotate functions, imports, structs etc with 

. Depending on the context of the compile and runtime of the application, rust will decide which one of these annotations is currently contextual and will execute the code beneath.

Here we define two connection methods. One for the tests and one for, well, not test.

cargo build #( with or without --release )

Splitting by context like this can be used in other areas of your code as well. Maybe there are specific things that should only be executed in test scenarios.


Rust Testing Context

Make it your passion to hunt down your goal like you would a wild beast.

Wake up with a sense of going out to hunt and come back home to sleep saying, "It was a good day hunting!"

Never focus on what you or others can't do. Focus on what you can do. And don't quit!


Are you hunting?

Here are some bits and pieces pulled out of an excellent article posted on hackernoon.com

"These are the true origins of Bitcoin and everyone knows it. Bitcoin is a solution to the problem of the State having absolute control over the form and supply of money and the regulation of banks. That is why it is so powerful; it solves two difficult problems at once, and offers an unimaginable number of secondary uses that are tangential to the money use of Bitcoin."

"There is no place in the Bitcoin world for the Federal Reserve; Bitcoin was designed to destroy it. This is the real reason these institutions are testing new networks." (aka Ripple)

"there is no Blockchain without Bitcoin:"

"you will never again see people complaining that a bank where they had an account has shut off their access to their own money. All the artificial rules and restrictions of the central bank licenced banking system evaporate in Bitcoin."

"Bitcoin is not a simple transition to a new medium. It is a paradigm shift. Every assumption about what money is, how it is stored, who should control its production, how it is transmitted and managed is turned on its head in Bitcoin. This is not a simple matter of moving from Oracle to MySQL; this is the equivalent of computing without computers. Its something that is very hard to accept for people inured to the idea that the State should be the sole provider of money; "

"the idea that anyone should rely on a State issuer of an alt-coin for money is absurd."

"You do not need to “put an asset on the network”. All you need Bitcoin for is a means of accounting for something. Once again, this idea of “putting assets on the network” is an example of computer illiterates trying to find a use case for something designed to do a job that they do not believe needs to be done. None of these people believed that there was a need for Bitcoin before Bitcoin existed; they were all happy with the Federal Reserve and its fiat currency, inflating money supply and all the ills that were borne of it. They had no interest in cryptography, privacy and especially financial privacy, which they believed was inherently criminal and they still do."

"This is the explicit purpose of Bitcoin; to eradicate the central banks and put the money function out of reach of regulators permanently. People are asking the wrong questions about Bitcoin. One of these wrong questions is “What role should we (the state) play in the emerging digital asset economy?” The answer is you have no role to play. You are now nothing more than peers on the network at best. You will only be tolerated if you provide a useful service."

A tl;dr of "Why Central Banks Will Fail at Digital Currency"

Proof of concept for website tracking/analytics using only CSS and without JavaScript.

Webpage tracking only using CSS (and no JS)

"The only way that is known to me currently is, to disable CSS for a webpage completely (you can do this with a plugin like uMatrix). The problem that almost every modern webpage looks very ugly without CSS and is sometimes even unusable completely. So, disable CSS is not a real option, except when you are very worried about your privacy (for example, when you are using Tor browser, you should maybe disable CSS).

A better solution would be, that browsers does not load the external content (referenced in CSS), when it is needed, but when the site is loaded. Then it would be impossible to detect single actions. This modification to content loading could be implemented by the browsers itself, or maybe by a plugin (similar to NoScript or uMatrix)

The problem is that this solution maybe has a performance impact, because the browser has to load a lot of content on initial site loading (and maybe the browser will not use the content at all)."

Tracking via CSS

The SEC released a statement yesterday, concluding that DAO (Distributed Autonomous Organisations) tokens would be seen and dealt with as securities and as such, would be subject to federal securities laws. Regardless of whether these tokens were purchased using the US Dollar or 

While the report claims that the SEC will not bring up any charges against companies at this time, it does highlight the fact, that this is to be seen as a strong warning to the market, that they are definitely aware of what is going on and is busy studying the effects of distributed ledgers.

The SEC is concerned that investors and market participants are protected under federal law with regards to ICOs (Initial Coin Offerings) used to fund new ventures.

SEC rule ICOs as securities

A service which queries the API's of various Bitcoin exchanges around the world.

Busy working on a Bitcoin Price ticker which runs as a service and grabs the current exchange rates from various exchanges.

. I'm open to / looking for contributors who are interested in reviewing the code, adding support for exchanges etc etc.

I'll be adding exchanges as time goes on myself and improving the code. The idea is mainly to provide an option to self-host (or something like that) your own exchange rate data.

I have this running on my netbook as a background service in Linux. Which means that while I'm working, it keeps a SQLite database up to date with exchange rates etc, which can then be queries locally.

Bitcoin currency ticker project

Over the last 2 to 3 years Bitcoin has been facing the same question that any other network faces at some point, "How do we scale this?"

Bitcoin is a peer to peer payments network, comparable only to cash or gold. While it differs in many ways from cash or gold, they remain the closest comparison. The heart of the network is made up of the Blockchain. An immutable, transparent, distributed and open to innovation ledger, that keeps a record of all transactions, that have occurred on the network. This ledger is kept up to date using a consensus mechanism called proof of work; which validates all new transactions made on the network, as well as inadvertently confirming every existing transaction over and over again.

The people who partake in this consensus mechanism are called miners. Miners dedicate hardware which they have purchased, as well as electricity, to validate transactions made on the Bitcoin network. They group transactions into chunks (from the mempool, where new transactions are submitted to) and validate whether or not they are legitimate transactions. This is done based on an algorithm agreed upon by the entire world. Once they have validated the transactions, they solve a puzzle to prove that they did the work (proof of work) and submit these chunks to the Blockchain.

These chunks are called blocks. Each block, is currently 1MiB in size. The average transaction can range between 226 bytes and 1kb in size. Which usually translates to around 1500 -> 2500 transactions being mined in each block. Each block takes about 10 minutes to "find" (to validate transactions and to solve the puzzle). This is what is called Bitcoin's heartbeat. It beats every 10 minutes at a rate of 7 transactions per second (compared to VISA which handles on average around 2,000 transactions per second).

The 1MiB limit was imposed by Bitcoin's creator Satoshi Nakamoto, about 1.5 years after it's launch, from 32MiB to 1MiB. Based on interpretations of his comments relating to it, this change in code was to keep bandwidth and network requirements low enough, to be practical for anyone to keep a copy of the Blockchain on their computer. The idea was to increase the block size at a later stage. However, he never commented on when or how this size increase would roll out. The idea was that by the time this question needed to be answered, we would've advanced far enough, in accordance with Moore's law, that a block size increase would essentially keep the cost of running a node to about the same as it was back then.

We've come to this point. Blocks are constantly reaching their 1MiB limit and have been for more than a year, we have a serious back log of transactions in the mempool every couple of days (think on average 60k transactions waiting to get confirmed) and have split the community into two camps. Each with their own idea on how to scale the Bitcoin network.

On the one hand we have a Bitcoin improvement protocol called Segregated Witness or SegWit (segwit). Segwit's purpose isn't directly related to a block size increase but its improvements allow for a theoretical 0.7MiB increase in block size. To understand how this works, we need to look at how Bitcoin transactions work.

On a very simplistic basis, a Bitcoin transaction consists of inputs and outputs. Inputs contain transactions that you reference to prove how you got the Bitcoins that you are about to spend and outputs contain the destinations and amounts, where you would like to send these Bitcoin. The inputs are then signed by your private key which proves ownership of those Bitcoin and the the entire transaction (signed input and outputs combined) is submitted to the Blockchain. Each transaction in a block contains its own set of signatures and this contributes to the size of a transaction.

Segwit allows a miner to take the transaction signatures and split them from the transactions portion of the block. One of the problems that segwit is trying to fix is a more complex one called transaction malleability. Essentially, in some edge cases, transaction ID's can be changed during the mining process. Which means if you were monitoring a specific transaction ID to see if it has been confirmed or not, you'd never know. Once it is mined, the ID is "accidentally" changed. Causing a lot of confusion. Segwit solves this problem by splitting signatures from the transactions which prevents this change in ID from being possible. Which also provides the 0.7MiB block size increase.

Fixing transaction malleability (which enable things like the lightening network)

Increases the block size from 1MiB to ~1.7MiB

Provides security gains for hardware wallets

Linear scaling of sighash operations (prevents maliciously designed transactions from clogging up the network)

Efficiency gains when not verifying signatures

For a more in-depth look at each of these points above, visit 

On the other side of the coin, we have the so called "Big Blockers". Who firmly believe that in order to scale Bitcoin as a network, we must increase the block size. This would mean that more transactions can be mined at once. For instance, if the current "heartbeat" of Bitcoin produces 7 transactions per second with a 1MiB block size, increasing the block size to 2MiB would directly increase the transactions per second processed to 14. The debate between the "Big Blockers" is still open as to how big this increase should be, some want 2MiB, others 8MiB. Out of this dilemma, Bitcoin Unlimited was born. Bitcoin Unlimited tries to solve the block size issue by allowing users to define their own consensus on what block sizes to accept.

Problems with this solution include the increased cost of keeping a Bitcoin Node running. Meaning the number of Nodes would drop and the risk of centralisation increases. Other problems, related more specifically to Bitcoin Unlimited, stem from the ability for users to dictate their own accepted block sizes. Causing the network to be in constant flux over what is the true Blockchain and what is discarded as a side-chain. This can cause confusion as transactions which may have been mined on a side chain, will all of a sudden lose confirmations and end up in the mempool again (ending up in the mempool is the best case scenario, worst case, the transaction just disappears and the sender has their money back); due to the side chain being discarded.

Bitcoin works on a consensus protocol. Every decision made in Bitcoin needs the buy in from the entire network. If a new feature is to be implemented, which changed the way Bitcoin functions, a voting mechanism is kicked into play. Anybody accepting this new feature, and would like to include it into their implementation of Bitcoin, casts their vote by "signaling" their support for this feature.

This is done by installing and running the version of Bitcoin which implements it. If more than 75% of the network is in agreement and votes toward a new feature, it becomes part of the Bitcoin consensus and the network moves in that direction as a whole. The other 25% have the choice to either take it or leave it. In a situation where the change is a so called "Soft Fork", the 25% will not be excluded from the network but will not reap the benefits of the new feature. If the implementation is rolled out as a "Hard Fork", the 25% are "forced" to switch otherwise they will end up on a side-chain. A version of Bitcoin which is not accepted by the new direction of the Blockchain and therefore has no buying power.

Everyone on the new main Blockchain will not see any transactions on the side-chain and vice-versa. They cut themselves off.

If we take a look at the current state of the Bitcoin Mining network, we see the following stats (these are sourced from 

SegWit: 25.7% have signaled their support

Bitcoin Unlimited: 19.9% have signaled their support

8MiB Block Size Increase: 6.2% have signaled their support

It seems that after 2, going on to 3, years of this debate, we have not found a scaling solution that is accepted by everyone. Unfortunately, politics has had an influence in the decision making of many and each side has valid points. Regardless in which camp you sit, a scaling solution needs to be implemented. Sooner rather than later. We may only have a year or so left before the first contentious hard forks become a reality.

How do we scale Bitcoin

Changing the default vim theme is quite simple yet so many don't bother to spend two minutes to improve their quality of life dramatically.

 or any other scheme you like. Make sure that the 

 file ends up in the following directory (you'll need to be root):

Then add the colour scheme as default for all users:

Add the following to the very bottom of the file:

Save and exit. Next time you open any file with vim the colour scheme should be applied.

Giving vim a colour scheme

What is it that you want to achieve? What drives you? Where are you heading?

Recently I was asked what my 2 and 5 year goals are professionally and personally. I was stumped! I had no idea. Why do I even need to answer such questions? I'm content, I'm happy. I have nothing to complain about. At this stage in my life everything is pretty peachy.

I'm employed, I love what I do and the people closest to me are awesome. I couldn't think of anything that I desperately want to achieve. I have no plans. I have no great, life-changing ambitions.

Ok, well if I have to answer then I will need some time to think about it. So I thought about it... for weeks. And what I came up with is, well... it's not much.

Professionally, I want to encourage other people to reach their full potential. I want to help them unlock their talents. I want them to achieve the things that they set out as their goals. I want to help them fight their uphill struggles in life. I want to provide the tools or financial support they need. I want to be the person they can come to when they have no-one to talk to. I want to be there. I simply want to be there next to them. I want to say the right word at the right time. I want to make them believe in themselves when all odds are against them. I want to make them power through the wall they have their back up against.

Personally, I want to be a good friend, brother, son and someday a loving husband. I'm emotionally cold. I don't like that about myself. And to convey my feelings is a real struggle. You know, like a cold bucket of ice? That's me. You have an awesome idea? I'll most probably think it's a crappy idea (pour that bucket of ice all over you...). Not because I don't think it's an awesome idea, because I'm ice cold. But that can change. And it has to change, that's my ambition, that's my drive. "Eliminate the negatives and strengthen the positives."

These aren't even 2 or 5 year plans and goals. These are things I yearn for. These are things that will define me. These are the things that will define others that interact with me. These are things that are more important than "earning a higher salary" or being a "successful individual". What even is that? Who came up with that? Why do we measure ourselves by the material gains we make? That is pathetic! Why do we even measure each other by what school or college we went to? Are we for real?!

I want to live in a world where goals and ambitions are to help others first and then focus on ourselves. I strive to create such a future. Imagine a world where you try to help someone and that person asks you "Hey, how can I help you?". Wouldn't that be awesome? A world where we help each other, a world where we strive to bring each other forward.

So what is it you want to achieve? What drives you? Where are you heading?

Finding purpose

grep is a wonderful tool that I think those new to Linux should really come to grips with.

Essentially, it allows you to search for strings. Simple as that. However, I recently discovered that grep can also be used to search for strings in files in folders, i.e. if you've got a folder full of text files and you're looking for one containing a specific string use grep! syntax:

Here's an example of me trying to find files still containing the string "dev.journeyatrest.com" that I use in my development environment:

Or you can omit the directory and it will search in the currently active directory. 

 just means recursive; so it will search through sub-directories as well. You can limit your results to display only file names using 

You can take this further and pipe the result to 

 can then use the results from a "grep -rl" to replace the string you're searching for with another string, e.g.: