Great sound.

Too good NOT to share.

My brothers and sisters in Christ I want you to know that I care about your souls enough to share these truths with you:

• You don’t need JavaScript to make a web page.
• You don’t need JavaScript to write styles.
• You don’t need JavaScript to make an animation.
• You don’t need JavaScript just to show content.

Great sound and mixing. Powerful rendition.

Mood.

The reporting methodology employed should yield valuable insights, spanning both technical details and high-level strategic considerations.

Dude(ettes),

This community has dropped off fast in the now trending list on the sidebar. That is awesome. When I first started supporting Beehaw, it was a matter of minutes before the site crashed due to processing and load. Gone are the days of 3,4 or 10 posts in Beehaw Support about content issues, server instability and server errors. Here are the days of no support requested. We have improved the uptime and responsiveness of Beehaw for all users, in a short time. Extenstive work and efforts have been placed into not only keeping Beehaw running; but improving Beehaw.

Those efforts and support have paid off I think. I say this as a primary systems admin of Beeehaw:

Thank you

To all monetary supports and lurkers, your contributions are immensely appreciated. We hope you continue to find value in our presence on the internet and in the Fediverse.

For example, things you do often but not often enough to make a muscle memory? On Linux systems with Bash, I just use bash aliases. If I do it more than once, It gets an alias or a script; cause I won't remember next time. Example of my current desktop aliases :

alias fuck='sudo $(history -p \!\!)'
alias hstat='curl -o /dev/null --silent --head --write-out '\''%{http_code}\n'\'''
alias ls='ls -la --color=auto'
alias pwgen='< /dev/urandom tr -dc "_A-Z-a-z-0-9\#\+=\$" | head -c${1:-15};echo;'
alias rsync='rsync -ah --info=progress2'

And in my bashrc I have the following settings and functions which come in handy when heads down in the terminal:

# append to the history file, don't overwrite it
shopt -s histappend

# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
HISTSIZE=1000
HISTFILESIZE=2000
HISTTIMEFORMAT="%Y-%m-%d %T "

####
function stopwatch() {
    local BEGIN=$(date +%s)
    echo Starting Stopwatch...

    while true; do
        local NOW=$(date +%s)
        local DIFF=$(($NOW - $BEGIN))
        local MINS=$(($DIFF / 60))
        local SECS=$(($DIFF % 60))
        local HOURS=$(($DIFF / 3600))
        local DAYS=$(($DIFF / 86400))

        printf "\r%3d Days, %02d:%02d:%02d" $DAYS $HOURS $MINS $SECS
        sleep 0.5
    done
}

function md() {
  pandoc "$1" | lynx -stdin;
}

function weather() {
  ( IFS=+; curl wttr.in/$(curl -s http://ipwho.is/ | jq .postal););
}

So what do you do to remember or recall your most used commands?

Deploy Golang applications to a Raspberry PI