Ok, you’ve been hearing about Scuttlebutt and decided that “Yes, I do want to join an amazing social network with lots of good people that no company can control and also happens to also work offline. Here’s a quick overview with the basics you need to know. First off Scuttlebutt is a protocol on which many different kinds of apps can be built. As for the social network, there are many clients, just like there are many Twitter clients.
I’ve been thinking a lot about Scuttlebutt lately (see my Why Scuttlebutt post), and Srol just wrote a great post about how Mastodon makes the internet feel like home again. There’s a lot of good reasons for people to use tools like them for socializing online, and I don’t want these services to just wither as their users wander off. I want there to be options that aren’t controlled by large companies, but at the same time services that require servers (like Mastodon) need someone to pay for those servers.
I fell in love with the scuttleverse because of the people who are inhabiting it. Regardless of UX/UI, I continually come back because here I found people discussing practical ways of building their own airships, and what life is like doing guerilla gardening in Berlin or living in a self-reliant shack on top of a lava flow. There’s a distinct social anarchist bent to the discussion, and folks are not only discussing alternate societies at length, but also have the skills to realize them.
v2.0 Offically Scuttlebutt doesn’t support posting from the same identity on multiple computers (as of Dec 2017). Unofficially, it’s easy but requires a little bit of care. In practice this means never run the Scuttlebutt client on two computers at the same time. The gotcha is that if you post from both computers before the changes of one have had a chance to replicate to the second via scuttlebutt one or both of your feeds will get screwed up and you won’t see some of your own posts ever again.
Many would not guess it, but I am a minimalist at heart. I don’t like looking around and seeing all the crap I’ve accumulated. So this year, I’m going to do something about it. This year, I’m working towards only owning 100(ish) things, and I’d like to encourage you to too. The 100 is easy. The “ish” requires some explaining, but I feel it is the key to making this workable.
Changelogs are an invaluable, and often neglected part of any software project. So, how do you do that? A good changelog helps you users to understand: Why they should care about your latest version If any of your changes affect the problems or frustrations they’ve been having. If there are any changes that might affect how they use your app / library. Why your efforts are worth their continued support.
Let’s start by taking it as a given that a Changelog file is something very valuable that every product should come with. Even if your “product” is a library for other developers. With that in mind, the question rises of “How can I make it really easy to generate one”. Many developers have had exactly that thought. There are many free and some paid solutions that will “Autogenerate your changelog from your git commits/tickets”.
At its core, being a manager is about power. I feel that many managers fail to understand what that power is for. A manager is a lot like being the King or Queen of a tiny, tiny kingdom. The sovereign of a country can impose their will upon their people, but that’s not their job. A sovereign’s job is to keep their people safe, happy, and prosperous. The more prosperous the people become, the more power they gain.
“Follow Friday” has been a longstanding tradition on Twitter. It’s a great idea. People you follow, make curated recommendations of good content. Well, the world needs balance, and I’m instituting Weeding Wednesday. Weeding Wednesday is a day for reducing internet noise. This Weeding Wednesday watch your Twitter feed from a different perspective. Don’t look for the great posts. Look for the “meh” posts, then unfollow anyone with a low cool to meh ratio.
Where to start creating a Terminal Emulator from scratch Before I get started I need to link you to this great answer on the Unix & Linux Stack Exchange which explains the differences between a Terminal (tty), a Console, and a Shell. That knowledge will be key to writing a terminal emulator. VT100 (and beyond) Setting the stage with a little background. Most terminal emulators claim to be VT100 emulators.