[–] 1 point 8 months ago*

Here are some of the ones I use most frequently that are somewhat unique:

# Grep Bash files
function rgb() { rg "$1" ~/.bash_aliases ; }
function rgj() { journalctl -b0 --grep="$1" --no-pager; }
function rgj4() { journalctl --since "4 hours ago" --grep="$1" --no-pager; }
function rgj1d() { journalctl --since "1 day ago" --grep="$1" --no-pager; }
function rgrc() { rg "$1" ~/.bashrc ; }
function rgt() { rg "$1" ~/.taskrc ; }
function rp() { rg "$1" ~/.bash_profile ; }

# Sharing aliases across devices
alias dba='diff -s ~/.bash_aliases  ~/Sync/.bash_aliases.bak|cat' # Diff between loaded vs saved
alias ba2s='cp ~/.bash_aliases ~/Sync/.bash_aliases.bak'  # Replace saved w/ loaded
alias s2ba='cp ~/Sync/.bash_aliases.bak ~/.bash_aliases' # Replace loaded w/ saved
# I have the same for bashrc and taskrc and bash_profile as well for the most part altho they are used more sparingly
  • source
  • [–] 7 points 1 year ago* (1 child)

    IMO, your suggestion assumes that today's government and tomorrow's government will have the same ideals and viewpoints on pornography, and not for 1-2 administrations, but indefinitely. Being able to reverse engineer someone via metadata is possible as is, and likely will become even more finetuned as we AI evolves.

    As an American, there are plenty of examples under the current administration where data shared in confidence by undocumented immigrants are now being used to target them for deportation.

    It's kind of like sharing data with a company indefinitely because of their current ToS, which is just a snapshot in time. Today's "helpful" approach towards data collection becomes a key part of surveillance in tomorrow's world.

  • source
  • parent
  • context