aclindsa

I recently started an open-source tax solver, partly because I'm not a huge fan of Intuit: https://github.com/habutax/habutax

It isn't perfect since its a young project, but I've attempted to simplify and modularize the process of creating/maintaining forms to allow for that part to be crowd-sourced as much as possible (and I'd love your help!).

As someone who attempts to import all my own banking transactions into open-source personal financial software, I certainly don't like the situation, but banks often give someone looking to download their own financial transaction data no other choice. This is basically what Intuit/Quicken do for 'Quicken Web Connect', too...

Additionally, though I think the advent of new APIs which will allow you to authenticate directly with your bank (FDX) are a great improvement for overall security, I think they're going to be a step backwards for free access to your own personal financial information. Because banks are limiting access to FDX to large players like Plaid/Quicken, I fear you will be forced to pay a third-party to get your own personal financial data in the future!

I have a simple pair of functions which I use to go up a level based on typing the portion of the path I want to go up until:

  # When called as `argu string`, prints the closest ancestor directory which
  # contains "string". If none is found, or "string" is empty, the current
  # working directory is printed. This function is useful if you need to specify
  # a file as an argument, but the relative path to it involves moving several
  # directories up from the current directory. For example, instead of doing:
  #  $ pwd
  #  /this/is/a/very/long/directory/path/for/demonstration/purposes/
  #  $ ls ../../../../another/directory/something.log
  # You could do:
  #  $ ls `argu dir`/another/directory/something.log
  argu() {
    if [[ "$1" == "" ]]; then
        echo "`pwd`/"
        return
    fi
    echo "`pwd | sed "s/^\(.*"$1"[^/]*\)\/.*$/\1/g"`/"
  }

  # When called as `cdu string`, changes directories into the closest ancestor
  # directory of the current directory which contains "string". If none is found,
  # or "string" is empty, no changes are made to the current directory.
  cdu() {
    cd `argu $1`
  }

I also put the following in ~/.zsh/completion/_cdu so I can get tab-completion of the portions of the path:

  #compdef cdu
  _cdu_parents=$(pwd | tr '/' ' ')
  _arguments "1:parents:($_cdu_parents)"

Or bash (in ~/.bash/completion/cdu):

  # bash completion for cdu

  _cdu()
  {
    local cur prev split=false
    COMPREPLY=()
    _get_comp_words_by_ref -n : cur prev
    _dirs=$( pwd | tr '/' ' ' )
    COMPREPLY=( $( compgen -W "$_dirs" -- "$cur" ) )
  }

  complete -F _cdu cdu

  # Local variables:
  # mode: shell-script
  # sh-basic-offset: 4
  # sh-indent-comment: t
  # indent-tabs-mode: nil
  # End:
  # ex: ts=4 sw=4 et filetype=sh

> So e.g. smaller ARM CPUs don’t use micro-ops at all. But that also means they cannot do things such as OoO.

Perhaps I'm picking nits, but the second sentence is not true. The dependency/resource-tracking and scheduling required for OoO execution do not depend upon using micro-ops.

Yeah, I know I can do it through the website - I'm specifically interested in being able to do it through a terminal-based program. Partially because it suits my workflow better, and partially because I enjoy being able to have logs of my conversations that I control.

I've grown accustomed to being able to text people from my computer with weechat/bitlbee/libpurple. Is anyone aware of any ways to continue doing this type of thing when the google voice/hangouts integration stops working?

I specifically like being able to access my messages in a terminal/ncurses-style gui, and being able to log them locally.

Do you have a source for that?

> It was designed to satisfy the needs of the Tarsnap online backup service for high-performance key-value storage, although it is not yet being used for that purpose

Does the fact that you're still maintaining Kivaloo this many years later imply it's now being used by Tarsnap?

No - there doesn't have to be. As long as there are no barriers or other instructions which restrict memory ordering relative to particular instructions in the dynamic instruction stream, it doesn't matter what the actual interleaving is between different cores as long as there is a given execution order which is valid for the observable side effects.

> If you're a postfix person, you can use + or -, with recipient_delimiter.

Even better: postfix and dovecot (as of v2.3) now both allow specifying multiple recipient delimiters. So if you run your own mail server you can specify as many recipient delimiters and switch between them if websites are being picky.