|
One of the only reasons why I'm trading with ~10 BTC over there, rather than 100+
I'd really like this to get fixed/improved, as I'd love to learn more about trading shares and bonds (just trying things out atm).
How was the security done on GLBSE 1.0 that you needed psychical access to your computer?
And why wasn't this implemented in version 2.0?
|
|
|
|
why doesn't he just declare bankruptcy I read through that whole thread, and seems like that is what bankruptcy is for, he is suffering physically because of a bad business move.
What's the bad business move he made? How can someone possibly lend 4000 BTC and lose not part of it, but all? =/ **disclosure: I am completely clueless on what happened** |
|
|
|
|
Bump! This needs to be implemented! How can we gain widespread adoption if this forum doesn't even support bitcoin URLs?
|
|
|
|
I see. Is it possible to get more than 8 connections on the initial download of the chain? The number of connections finally went past 8 when the download was very close to being finished. Maybe that had something to do with it?
There's no point in that: downloading the chain will not go faster with more connections - one good one suffices. In fact, incoming connections have a much larger chance of wanting to request your block chain, slowing your sync down further. I know it will only use 1 connection at a time for downloading, but with more connections there's a bigger chance you get connected to a fast peer, right? |
|
|
|
Same problem here. Getting stuck on 8 connections sometimes. uPnP doesn't seem to be working as well as it used to.
The reason is IRC being deprecated and defaulting to off. This will indeed mean less very fast incoming connections, but better connectivity for longing-living listening nodes (as others don't rely on recently IRC-advertized nodes, but on the addresses propagated through the network). I see. Is it possible to get more than 8 connections on the initial download of the chain? The number of connections finally went past 8 when the download was very close to being finished. Maybe that had something to do with it? |
|
|
|
Just upgraded, and it seems to be stuck at 8 connections even though port 8333 is open. Version 0.5.3.1 under same settings worked fine. Any ideas?
False alarm - after 5 minutes or so it started going up.
Same problem here. Getting stuck on 8 connections sometimes. uPnP doesn't seem to be working as well as it used to. |
|
|
|
|
The old LadyBytes address is still getting coins send to it =/ Has InstaWallet done something that new donations to that address are going to LadyBytes?
|
|
|
|
|
The site seems to be down?
|
|
|
|
|
I agree with the OP. Speculation forum was fun! Please give back our old speculation forum!
|
|
|
|
|
How are you going to get USD/EURO/etc funds? By selling BTC? How are you going to protect yourself against exchange rate swings in that case?
|
|
|
|
|
This is just ridiculous...
|
|
|
|
Heh. The Harddisk is still choking once it's past ~80-85%.  And there's still several gigabytes of free RAM that isn't being used. Perhaps the caching settings still need some tweaking? |
|
|
|
i certainly doubt it. i'm willing to bet many early adopters have long since already sold most of their coins or lost them. the pessimism was extreme back in November.
Not me! I doubled my holdings through trading  And I will keep them and keep adding to them for the long term =) |
|
|
|
As I've said before in another thread, the initial synchronisation process consists of three steps: - Downloading the data: limited by your and your peer's network speed
- Maintaining the database: mostly limited by disk latency
- Verifying the chain: limited by CPU speed
Before 0.6.0, maintaining the database almost always outweighed the other two. With 0.6.0rc5 the caching settings have been tweaked, resulting in a remarkable speedup for the database. This means that now the downloading time may indeed become significant, and it may be worth looking at improving the download process, for example downloading from several peers at once. Increasing the number of outgoing connections will not help you get the chain faster: even when you use 0.6.0rc5, the chain is still downloaded from a single peer, and frequently still not the slowest step. In fact, increasing this number is a bad idea for the network, as peers with open incoming ports are not too abundant. Thank you very much for tweaking the caching settings! Tremendous improvement in synchronize speed! I too believe downloading from multiple peers at once is going to be the next logical step in speeding the initial download up. Do you happen to know how hard this would be to implement? It's not as necessary as improving the caching was, but it would most definitely help and would be very welcome |
|
|
|
Since I was most interested in seeing the speedups on downloading the chain, I deleted the chain and ran 0.6 RC5. Now I'm not sure if this is normal, but I'm only getting 8 active connections. Prior to this, I was always getting 30-60 connections depending on the time of the day. uPnP Test 1.16 tool is showing that uPnP is working on my network, and uPnP is in fact enabled in the Bitcoin client. Is this because I'm still in the initial download phase? Or did this release perhaps break uPnP support? Could someone test this out as well, please? Thanks By the way, wonderful job on the database speedups! No more HDD grinding, and the download is already much faster. Could be even faster if I had more active connections though. It would improve my chances of finding a fast peer. |
|
|
|
|
What are we voting on? It says I should check the forums, but I'm not finding anything specific. Help?
|
|
|
|
whats the new red/green bar on the right indicate?
All the trades that have been made in the last X minutes, where X is the number set at "Sales range". Green trades have been buys, red ones have been sells. Trades at the bottom are the most recent trades. thanks. where can i see the Sales Range? Hover your mouse over the tiny little + in the top-left corner. |
|
|
|
whats the new red/green bar on the right indicate?
All the trades that have been made in the last X minutes, where X is the number set at "Sales range". Green trades have been buys, red ones have been sells. Trades at the bottom are the most recent trades. |
|
|
|
I will definitely focus more on non-Elliott Wave charting for the foreseeable future with my day to day emails since what has happened these last few days makes little to no sense from an Elliott Wave standpoint and therefore I cannot just keep following slight error after error down the rabbits hole.
Do you have any idea why this could be the case? It didn’t make any sense to me either. But then again, so did the rise from the 4.5, then the 4.75 low not make sense to me at all at the time. Like it wasn’t supposed to happen, and yet it did, both times up and down. I enjoyed this email btw. Probably, because as I've already said, Elliott Wave Theorem is about mass psychology. There's just not enough people trading on the shorter time scales to call it mass psychology. It would most likely be a lot more accurate if the market was a lot bigger, but for now, I think it's indeed much better to focus on non-Elliot Wave analysis for the shorter term pictures. Also, I think the effectiveness of short-term analysis in general is too inaccurate for the Bitcoin market right now. As of now, I'll focus on mid and long-term pictures. I would have done very well if I did. Now, not so much  You live and learn, I guess  |
|
|
|
Notme was just trolling...
But this guy is not right 100% of the time even thought he pretends he is. I just wonder how much over 50% it is.
+1 His public updates have been particularly wrong recently though. In the past, they were better. Still, I doubt he's intentionally screwing the public. Yeah agreed, he's not intentionally screwing the public. The private and public updates always painted the same picture. There's just been some unlucky situations (for the people following the public updates) where the picture changed really fast after a public update, and he corrected that in a new private mail. The public updates rang true when he gave them, and he's not forced to update those if/when the picture changes. |
|
|
|
|
Show Posts
