Updated screenshots on http://www.goxsh.info. There is a "bug" in the output of one of the commands of goxsh 0.25 you can find among the new screenshots. Found it? Twitter a tweet like Among all correct reported found-the-bug-tweets a Mt. Gox redeemable code worth 0.5 BTC will be raffled off. Deadline is September 1, 2011, 00:01 UTC. Good luck :-)

It is affected. Orders remain "pending"/"in queue" due to a long queue or because processing is stuck. I would call this beeing affected :-)

goxsh 0.25 released: https://github.com/Optonic/goxsh/tree/0.25

Excerpt from Changelog

• 0.25
  
  • Added deposit-command to print a BTC-address to deposit BTC and added the ability to withdraw to Dwolla, Liberty Reserve and Paxum with the withdraw-command. Changed output of several commands in particular the output of the orders-command which now fits into a standard terminal with a width of 80 characters.

goxsh 0.24 released: https://github.com/Optonic/goxsh/tree/0.24

Excerpt from Changelog

• 0.24
  
  • Beautified output of depth-, bids- and asks-command.

goxsh 0.23 released: https://github.com/Optonic/goxsh/tree/0.23

Excerpt from Changelog

• 0.23
  
  • Added bids- and asks-command additionally to the depth-command and improved code a little (mostly additional exception-handling).

The profit command calculates from which rate a buy/sell is profitable when bought/sold at a specified rate considering the current commission fee of Mt. Gox. E.g. if you sold 1 BTC at $10.00 you will start making profit (ending up with more BTC) when rebuying at < $9.94008. If you bought 1 BTC at $10.00 you will start making profit (ending up with more $ in your account) when selling at > $10.06028. If you rebuy > $9.94008 or sell < $10.06028 fees will be greater than what you actually gain in the actual trade and you end up with a loss.

This is a known bug with the last release of ahihi. Doesn't affect the withdraw–it just fails to print the new balance after the withdrawal. Fixed since 0.20.

goxsh 0.22 released: https://github.com/Optonic/goxsh/tree/0.22

Excerpt from Changelog

• 0.22
  
  • Merged changes made by bitplane (NiceText), cleaned up goxsh.cfg (removed values set to default) and goxsh.cfg.example (removed tabs and replaced them with whitespaces for a better readability), added cumulation to the depth-command (for now works for last-trade-depth only).

Sure, every involvement is very much appreciated!

goxsh 0.21 released. See New goxsh fork#msg446216.

goxsh 0.21 released: https://github.com/Optonic/goxsh/tree/0.21

Excerpt from Changelog

• 0.21
  
  • Modified (extended) depth-command and added configurable color support for it. Minor update in README.md.

Paranoia is a good thing for sure when it comes to money/worth-related things BUT why don't revert to something which works quite well in real life/with fiat money: contracts/agreements/treaties (whatever you'd like to call them). At least when it comes to a larger transfer of money/btc this could come in handy. This even works within the digital world. Set up a contract both parties agree on and let both contractual partners sign this contract with a class II certificate issued by an approved CA. In Germany there are even offically accredited CAs (accredited by the "Bundesnetzagentur" (lit.: Federal Network Agency)) (accredited CAs). One of the accredited CAs is the "Bundesdruckerei" (lit. Federal print office). Its subsidiary D-TRUST offers class II certificates for personal use for 83,19 Euros (link) which are valid for two years. Tractis will help to find a CA near you :-)

Is this of such an importance (besides ego ;-)?

I don't think this is the appropriate answer to a technical question which has nothing to do with the previous MyBitcoin-Threads.

To actually answer the question: to my knowledge a once made transaction cannot be reversed even it's not yet redeemed.

Have you checked your client has already fetched the latest block in the blockchain (down in the right corner, next to connections, it shows "xxx blocks")? Match this with http://blockexplorer.com/q/getblockcount. If your client displays a number < getblockcount your client is probably still downloading the blockchain. If this number is < getblockcount and not increasing, check if your client is connected right.

All I see is an empty estate. Maybe he just built his home and now needed some money to pay the bills?

Let's see how Google reacts :-)

Have you tried? Would be interested if everything went well, because yesterday at IRC I tried to help someone to run goxsh within a Windows environment, which failed at all. Lack of readline support was the first hurdle. Not to mention GMP :-( Within cygwin everything is fine, but to have someone install cygwin just to run a python-script is a little bit too much trouble imo.

The last days I noticed some outages, which seem to heap up every day :-( Any idea of what the reason for the outages might be? MtGox Live-ticker doesn't seem affected of this–nevertheless, I prefer watching the charts on bitconity.org!

You have to work on your translation, Tenobis, because this doesn't sound like propper German:


And wouldn't it be better to put those info on the page itself instead of asking for a mail first?

Take a look at Newbie restrictions. You will find something like this there: