Bitcoin may use multiple outputs from different addresses to fund the transaction. It will always be impossible to predict what the user is doing, for example, they could be using CoinJoin and the actual sender could be any of the inputs.

Also remember that services like SatoshiDice causes huge network strain and is preferred to use a deposit address and have the user specify an address to withdraw. It solves both network strain and your issue.

In addition, never assume that a certain output is the change address. The user could be doing anything (like sending the rest to someone else).

EDIT: Downvoting both mine and David Schwartz's answer doesn't help anything. It is just not possible to anticipate every use-case. In the words of the Satoshi client developers; "Sometimes a documentation limit is a feature, not a bug". The important point there is that if you have to ask then maybe giving you the answer will cause more harm than good. The only ways to do this are:

1. Try to guess the change address. If there are two outputs you could use the one that isn't yours. If the sender has an exact output then you might not even get a second output. If there are >2 outputs you might use the last one but that makes a ton of assumptions and any wallet that even cares about privacy will randomise the outputs.
2. Try to guess the sending address. If there is one sending address you could use that, in the case of more than one, it's anyone's guess (maybe use the top one?).

Noone can answer the question any more than that. Even my answer is just made up, it is not allocated for using the protocol and is just a guess based on how some wallet software works.

I can't recommend against this enough though. It is extremely dangerous. SatoshiDice is not recommended by anyone who knows anything about how Bitcoin works, it is simply popular because it was one of the first, if not the first Bitcoin betting site.

Each transaction can have multiple inputs and thus can have multiple senders.

Here's how you get the sender(s):

bitcoin-cli getrawtransaction 8386a8d2870c0df79f652ef4d981b21649ebf40601948c1c0709de0f02de8c8c 1

(the 1 flag indicates that you want the raw tx to be decoded)

Note: make sure that you have already indexed the blockchain or else this might not work. To index, restart bitcoind with txindex=1 as a config variable.

From that, you get a fairly big response, which contains the following:

"vin" : [{
    "txid" : "5203d1db5eeef77de7c404ec14487892e3dd12b4a562537243533a169d45753c",
    "vout" : 1,
    "scriptSig" : {
        "asm" : "304402200ee65c9f757eb6c240efe5a7e4427e04174a32da14b1eef459d36d61d031f6e702202d6b5383f86f155d92a494e80a1242af7e160faf16d597ea457b6e3bf08bb1ca01 02be7759e73363488269f0257158177f3295af42d1f3a6b2fdf8fb4380b1d16ae9",
        "hex" : "47304402200ee65c9f757eb6c240efe5a7e4427e04174a32da14b1eef459d36d61d031f6e702202d6b5383f86f155d92a494e80a1242af7e160faf16d597ea457b6e3bf08bb1ca012102be7759e73363488269f0257158177f3295af42d1f3a6b2fdf8fb4380b1d16ae9"
    },
    "sequence" : 4294967295
}]

This means there's a single input, so there is in fact one sender.

Now, there are two ways to get the sender.

Method A (should always work but is slower):

1. grab the txid and the vout
2. do bitcoin-cli getrawtransaction <txid> 1
3. find the output of this new tx where the value n is equal to the vout of our original tx
4. go to the scriptPubKey section and check the hex or addresses field - that's the sender (in hex pubkey script or address form)

We now have:

"scriptPubKey" : {
    "asm" : "OP_DUP OP_HASH160 17492e77be2c666af78993020b90235cd1d3738d OP_EQUALVERIFY OP_CHECKSIG",
    "hex" : "76a91417492e77be2c666af78993020b90235cd1d3738d88ac",
    "reqSigs" : 1,
    "type" : "pubkeyhash",
    "addresses" : [
        "1388D9sHH4HXdGLxkSipxe2noZuekHZmaF"
    ]
}

and the sender is 1388D9sHH4HXdGLxkSipxe2noZuekHZmaF

Method B (faster but only works for certain types of transactions):

1. check the 'asm' field inside the 'scriptSig' field
2. if the field has two components separated by a space, and the second component is a valid public key, then we have a standard pay-to-pubkey(-hash) transaction, so convert the pubkey to an address
3. fallback to method A

We see that there is in fact a valid pubkey in the original tx scriptSig:

02be7759e73363488269f0257158177f3295af42d1f3a6b2fdf8fb4380b1d16ae9

We use Coinkit to extract the address:

$ sudo pip install coinkit
$ python
>>> from coinkit import BitcoinPublicKey
>>> pub = BitcoinPublicKey('02be7759e73363488269f0257158177f3295af42d1f3a6b2fdf8fb4380b1d16ae9')
>>> pub.address()
'1388D9sHH4HXdGLxkSipxe2noZuekHZmaF'

And we have the same answer!

P.S. you can inspect the Coinkit library I used above on github