lenish

My concern with the IPFS claims of permanence, like "Where you can know for sure your pictures will be available forever" is that, AFAICT, files are only uploaded to the network once another party requests them.

An example:

  $ipfs init
  $echo 'agdkjagka' > test
  $ipfs add test
  added QmTtmsSSTH5fMQ9fn9NRXWtcZXnBBazxR8fidXcE5KB76h test
  $rm -R ~/.ipfs
  $ipfs init
  $ipfs cat QmTtmsSSTH5fMQ9fn9NRXWtcZXnBBazxR8fidXcE5KB76h
  Error: merkledag: not found

In English, `ipfs add` does not upload anything to the network. The only way a hash becomes distributed on the network is for another party to request that hash. Even then, I believe that the data only exists on that party's system. That is, if both you and the requester leave the network, the data is gone.

>Oh and it is missing functions keys which means I could never use this....

There are 5 rows of keys on each hand, just like a standard QWERTY keyboard with a function key row, you just have to place them along the bottom row instead of the top. The problem, I guess, is that there's only 10 keys along the bottom row, but you could place F11 and F12 on one of the many extra keys. Keep in mind they're programmable, and you can have different layers and modifiers that just exist in the keyboard itself.

This is only true in bash if HISTCONTROL contains ignorespace or ignoreboth (ignoreboth implies ignorespace and ignoredups), so you should check that before relying on this functionality.

The IRC gateway also does not. It typically wasn't an issue for me when I was using it as most of my coworkers at the time did not frequently edit messages.

For people who don't care for 'apps' that are just websites inside browsers, Slack supports XMPP and IRC gateways. I've only used the IRC gateway, and there are some janky bits, but it got the job done. https://slack.zendesk.com/hc/en-us/articles/201727913-Connec...