A Meta Post: The State Of Linux Tips

There was one site before this one and we’ll just ignore that in favor of the current site that contains various Linux tips, tweaks, and tutorials. This is an article about the state of this site, linux-tips.us, and is a measure of progress. This is an article about where we started, where we are now, and where we’ll be in the future. Something like that… I should also disclose that this post was authored under the influence of rum.

I think it’s important to first mention what the goal is. It’s not a lofty nor noble goal. I set out to get some of my Linux notes online. My plan has been to write an article for every other day. So far, so good. I’ve even had some help along the way, for which I am forever grateful.

(Don’t worry, we’ll cover some ways you personally can help elsewhere!)

When I think of about a summary of how the site is doing, it’s just “Holy crap!” I didn’t expect the site to do as well as it has. I really didn’t. For example, the site already has an Alexa ranking. Many sites never achieve that level of use. I get a ton of traffic (to me) from search engines, so the site is legitimately answering questions and helping people solve their Linux problems. To me, that’s pretty sweet!

Some Linux Tips metrics:

  • About 400 of my hours have been invested.
  • We chew through 4 to 5 GB of bandwidth per month.
  • We average about 120, and growing, unique visitors a day.
  • 93 articles have been published.
  • That’s about 75,000 words.
  • Which would take almost 5 hours to read.
  • Some 207 tags exist.
  • Only 44 people have commented so far.
  • The longest article is about should you use Linux.
  • The highest ranking article is Screenfetch vs Neofetch.

If you recall, one of the reasons from moving from the old site was that Google hated the .gq domain name (it’s a ‘free’ or paid domain) and those domains are so full of crap content that no reputable email provider would let the email notifications though its filters.

On this site, Google straight up loves us, as do email providers. The ads are doing better than I expected, but not great. Then again, I have no frame of reference, so maybe the ads are doing great. Speaking of which, maybe you could opt to show ads on this site. They’re just Google ads. They’re mostly harmless.

Beyond that, in the past few months Google has shown this site in the results (not very high) like 40,000 times. Only 600 have clicked through, but that’s actually a pretty respectable click-through-rate. 

Bing, of course, is the exact opposite. They mostly refuse to index the site, regardless of what changes I make. I have no idea what I’m missing. To make it even more confusing, Bing kinda liked the previous site.

Linux Tips’ Future:

We’ve come a long ways since the first article six months ago. People keep participating, signing up for the newsletter, registering for the site, and writing articles.

When I started this, I said I’d keep it up for a year. At this point, I can say that’s pretty likely. In fact, if I were to speculate, I’d be inclined to say I’ll keep going even after the year is over.

As far as my notes go, we’ve just barely scratched the surface. Beyond that, there’s always new stuff to learn and share. So, it seems pretty likely that I’ll keep going. After the year is up, I may change the publication schedule a bit. 

I won’t make any commitments until I get there, but I’m enjoying the project and having fun with the hobby. The every other day publishing thing is a bit much, but it hasn’t made me burn out yet. I think a part of that is the lovely feedback that I get.

You can help:

How can  you help? Above every article are some links where you can easily share the articles on your favorite social media platform. It’s nice and easy. You can do that without investing much effort, just share with your friends and groups who are also tech-minded.

There is the donations thing, but I don’t really need donations. The site’s going to stay online regardless. Still, it’s there if you want. If you do donate, I’d consider it more a motivator than a source of income. Who knows, maybe I’ll save all the donations and we can decide on something fun to do with them?

You too can participate. Go ahead, register. It won’t hurt. Leave a comment now and again. A small number of you are coming in from Linux.org, but you can still comment here. You can even write an article. It’s not that hard. If I can do it, you can figure it out. Heck, you don’t even have to register to write an article. I’ll even do the proofreading, formatting, and scheduling.

Most of those ways mentioned above are things that motivate me, things that make me more inclined to keep going. If nothing else, I’ll certainly finish the year – but it’d be nice to be motivated the whole way. It’d be nice to keep going and stay motivated even after the year has ended. For whatever reason, the interactions and climbing metrics make me enjoy it more.

As I mentioned above, you can still do that whole whitelisting this site in your ad blocking extension. 😉

Closure:

Yup. It has really been a full fix months already. It has probably been a full year if you count the previous site. I’ve invested a ton of hours into this hobby. It is pretty fun, as well. I encourage you to hop in and get involved. If you don’t want to do so here, start your own site with Linux tips. The more the merrier. 

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your own site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

Screenfetch vs. Neofetch, You Decide!

Should you use screenFetch or Neofetch? That’s up to you to decide. This article will share some info about both of them. This should be a pretty short article.

I also confess that there’s not much of a “vs.” here. The screenFetch app hasn’t been updated in a long time and Neofetch is the clear winner for most folks. But, well, it seems like people have forgotten that screenfetch exists and that it existed well before neofetch was conceived. That’s why I’ve picked ‘History’ as one of the categories.

See, the thing is, screenfetch (I’m tired of capitalizing the F, and the N, just to be right!) still exists and still works just fine. In some cases, you might get the wrong information from it, especially with newer distros, so why use it? Well, you use it because it shouldn’t be forgotten – and ’cause it still works most of the time.

So, you decide… Screenfetch or neofetch? Or maybe both?

Screenfetch:

The screenfetch application was was created to gather system information so that it could be presented in a screenshot format. In fact, their GitHub page clearly states the purpose as:

Fetches system/theme information in terminal for Linux desktop screenshots.

Though it’s old, it’ll almost certainly be available in your default repositories. Just because it’s old doesn’t mean it isn’t still useful! (Perhaps I’m having some sort of crisis, ’cause I too am old and part of the purpose of this site is to be useful!)

Assuming you’re using a distro with apt, it’s a mere install command away:

Then, well, you use it. You could just run it with ‘screenfetch’, but you can also actually use the -s switch and create a screenshot of your full screen, making it easy to take and share a picture of your desktop to show others in forums and social media sites.

This is an edited down screenshot, ’cause the rest of my desktop isn’t all that interesting right now.

screenfetch
See? Screenfetch in action. I like the ASCII art better, actually. That’s a matter of taste.

As you can see, that was with the -s switch. It happily generates a screenshot of the entire screen, but I edited it down to just the terminal. There’s nothing interesting on my screen right now. Just a bunch of open windows, largely with text in them.

Screenfetch still works, and I like the ASCII art better. I suppose I could probably customize neofetch to make it do the same thing, but I’m way too lazy for that. Either way, it works – and it works just fine. It still does the task it was designed to do, even without any recent updates.

Neofetch:

Neofetch is newer and probably better in every single way. (Though I do have some issues with it on some systems, as it won’t create its own screenshot! That’s a ‘me’ thing, I suspect.) It’s also familiar to many people, and indeed has been mentioned on this site multiple times.

It gets regular updates and has a ton of options. It’s also able to be highly customized. In pretty much every single way, it’s the superior solution. It’s described by the authors like so:

The overall purpose of Neofetch is to be used in screen-shots of your system. Neofetch shows the information other people want to see. There are other tools available for proper system statistic/diagnostics.

It’s a much newer application. Screenfetch last had a release in 2019, while neofetch had a release just last August (at the time of writing). It should be noted that there have been some commits at the screenfetch repository, but they’ve not yet been released. The project isn’t dead. It just isn’t as active as neofetch.

Again, it’s easy to install. It’s in the default repositories for most any distro out there, at least the major ones. There are some distros that include it by default, including Lubuntu! Again, assuming you’re using a distro with the apt package manager, it’s installed just like screenfetch:

And, like screenfetch, you can just run it as ‘neofetch’. However, check the man page for it and you’ll see there are a ton of other options. It’s seriously highly configurable. It looks like this:

neofetch in action
This looks a lot like screenfetch, doesn’t it? The art is different. The output is also different!

For whatever reason, on that system the neofetch doesn’t seem to want to take a screenshot. I’m probably missing scrot or something like that. I’m too lazy to figure it out, but it’ll likely work just fine on your system. It’s a great way to gather a bunch of presentable information about your system, with the end goal being to show it to other people.

So, is neofetch the one for you? Is it really any better?

Screenfetch or Neofetch:

Sure, there hasn’t been a screenfetch release in a long time – but there’s sure to be one eventually. There’s activity in the repository at GitHub. That’s usually an indicator that there’s still more to come. I wouldn’t count it out and it’s pretty much feature complete.

Neofetch? Well, it’s much newer and has more consistent releases lately. It’s also highly configurable. You’ll be able to customize it all you want. You’re encouraged to edit ~/.config/neofetch/config all you want, making neofetch your own. It’s also a mature application, with a large install base and likely also feature complete.

Either one works. They do spit out different information. If you examine both screenshots above, you’ll see the data output is different. Not gonna lie, I ain’t gotta clue why they’re different. The areas where they’re different are trivial and I’ve made no effort to find out which is correct. 

What? It’s a blog. I have finite time for these things, you know! 😊

You can decide between screenfetch or neofetch – or you can use both. They’re both very similar and neither should be used for anything all that serious. They spit out some system information in a form that’s convenient for screenshots so that you can show off your system to your forum friends.

Closure:

Here’s another article in the books. It’s not really about a ‘vs’ anything, but the title seemed appropriate. It’s a good time to expose some of the newer Linux users to the venerable screenfetch tool, as choice is always a good thing.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your own site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

Subscribe To Our Newsletter
Get notified when new articles are published! It's free and I won't send you any spam.
Linux Tips
Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.