tcely

#!/usr/bin/env python3

import datetime
import os

# import wmi
# https://github.com/tjguk/wmi
# https://github.com/tcely/wmi

class LastBoot:

tcely

Messaging

SimpleX

Join the "Lobby" group with the link above to initiate contact.

• GitHub

Threema

tcely

#!/usr/bin/env python3

import hashlib
import io
import os
import pathlib
import sys

def sum_file(hasher, file_path):

tcely

Using GitHub & GPG together

Fetching GPG keys

Any GitHub user account can contain GPG keys used for signed commits. To verify these signatures, your local gpg.program needs the public key.

To fetch them, just use a URL such as this: https://github.com/<ACCOUNT>.gpg

tcely

url_decode() {
    local arg ;
    if [ $# -gt 0 ]; then
        for arg; do
            printf -- '%s\n' "${arg}" ;
        done | url_decode ;
    else
        check_printf ;
        printf -- '%b\n' "$(sed -E -e 's/\+/ /g' -e 's/%([0-9a-fA-F]{2})/\\x\1/g')" ;
    fi ;

tcely

# Add this to the ~/.ssh/config file
#

Match Exec "ssh-rsa-needed.sh '%n' '%C' '%l' '%h' '%p' '%r'"
    PubkeyAcceptedKeyTypes +ssh-rsa

tcely

if [ "${BASH_VERSION-}" ]; then

# Local variables the functions depend upon
_bash_history_prefix=~/.local/history/bash

# {{{ Begining of the temporary functions block
_bash_history_get_today() {
    date '+%Y/0%m/%d'
}

tcely

My thread about which social media accounts I have:

https://fosstodon.org/@tcely/109317571417810234

This is the thread I wrote with helpful tips about moving away from Twitter and getting started on Mastodon:

https://fosstodon.org/@tcely/109501305674813494

See you on Mastodon!

tcely

#!/usr/bin/env sh

secho() {
    _arg="${1}";
    _fmt='%s';
    _sentinel='--';

    case "${_arg}" in
        (-e|-en|-ne) _fmt='%b'; shift ;;
        (-n|-En|-nE) shift ;;

tcely

1. Shell (ash from busybox) variables are always quoted and use curly braces.

   "Optimize for the inexperience newcomers rather than the experience gurus." As explained in this post there are a few quirks when dealing with shell variables that do not use the curly braces. For example: $pkgver

   Instead of expecting new contributors to already know about all of the pitfalls involved with using that syntactic sugar, it is better to just always use the braces. Shell variables are quoted when assigned and used, when accessed they are quoted and surrounded by curly braces. For example: pkgname='bind' or pkgdesc="${pkgname} tools" and "${pkgname}"

The characters that do and do not extend the name of the variable are not a concern when the intention of what the variable name should be is made clear by using this explicit syntax. Users don't need to remember which of _, -, or . will change the variable name and lead to an empty value be