Silk Road forums

There was a user named typtap who went on an epic 3 day trip for New Years with 2000 ug LSD and some other stuff. He wrote a detailed follow up post. You would have appreciated it, but I can't find it. It looks like he deleted all of his posts.

Ya, i think we learned that lesson with Lim.

It's funny, because Lim popped in my head as I wrote that.

It's ok Aussie. I probably would get all the girls if I didn't like boys.

The average confirmation time has actually gone down:

https://blockchain.info/charts/avg-confirmation-time

And we haven't had any big hacks in a long time, so I think overall the service providers are safer and more mature.

Will there be more issues? Certainly. With a hard limit of 1 megabyte per block, bitcoin can't handle as many transactions as Visa. Some things will have to change before it becomes a global currency.

Off topic, but are ssbd and scout both guys? I get the vibe from them that they are girls.

Makes sense anyway. I read about bars in England that were employing female bouncers because they are better are diffusing situations without resorting to violence.

Yes, that means you need to update your browser bundle.

They recently switched from Firefox 10 to Firefox 17. Because there are so many differences, you can't extract the browser bundle over top of the old one. You have to extract it into a new folder. That may be why  you can't connect.

Ok, the first thing you should know is that Bitmessage connects to a set of IP addresses which act like Tor's directory authorities. That's where it gets info about other nodes. The problem is that there are only 300-400 nodes in the network, and we don't want our real IP addresses on that short list, especially since we're talking about using Bitmessage openly on this forum. Bitmessage will connect to these IP addresses immediately the first time you start it, before you can change proxy settings in the GUI, so we need to configure it to run over Tor before the first time we run it.

1. Install git and torsocks the normal way for your distro. The packages should be in your repos if you're using a Debian or Fedora based distro. Otherwise, torsocks source can be downloaded here: https://code.google.com/p/torsocks/

2. torsocks is preconfigured to use Socks port 9050 with the Tor daemon. If you want to use TBB's Tor instead, open /etc/torsocks.conf and change

    server_port = 9050

to 9150.

3. Clone the Bitmessage repo with git over Tor.

    torsocks git clone https://github.com/Bitmessage/PyBitmessage.git

4. Now we preconfigure it to run over Tor. Create this folder:  ~/.PyBitmessage

Put this in a file called keys.dat (in that folder)

[bitmessagesettings]
settingsversion = 3
port = 8444
timeformat = %%a, %%d %%b %%Y  %%I:%%M %%p
blackwhitelist = black
startonlogon = False
minimizetotray = False
showtraynotifications = True
startintray = False
socksproxytype = SOCKS5
sockshostname = localhost
socksport = 9050                   # change this to 9150 for TBB's Tor
socksauthentication = False
socksusername =
sockspassword =
keysencrypted = false
messagesencrypted = false

Yes, I know it's retarded that the configuration options are in the same file where the bitmessage keys are stored instead of a separate config file.

And yes, I know it says messagesencrypted = false at the end. SS and I were looking into it, and that option seems to be unused. It may be there for some future feature.

5. Finally, start Bitmessage from the terminal with logging. Go to the folder where you cloned it and run:

    python bitmessagemain.py | tee -a messages.log

You will see a red circle in the status bar. It will change to yellow when you establish your first connection (may take 3-5 minutes). It won't turn green, because we're running it over Tor and can't accept connections.

Leave Bitmessage running for a few hours, create some keys, send messages, play around with it to see what kind of error messages you get. I'll make a separate post on the kind of stuff I'm looking for.

You can send a message to me at this address:  BM-onsou9SN9ufFztCs8Cq6srFogEw5FdXAX

Which will be easier I think now that FINCEN has weighed in on it. Even bitcoin-otc could get shutdown if they start regulating moneypaks and such.

Yep. That's good and bad.

It's bad if you want anonymous bitcoins for illegal purchases, but it's good if you are a legal business that wants to integrate bitcoins as a payment option, because the rules for doing so are clearly defined now.

Haven't tried 1.0.4 but I'll test it out and get back to you later today.