|
What's happened to dwolla and bitinstant?
|
|
|
|
|
If this Pump-dump-DDoS-Buy cycle is going to keep repeating, things are going to get tiresome VERY quickly.
|
|
|
|
|
For me:
1. Not selling a bunch at $260 when I was seriously considering it.
2. Not logging in to account in time to cancel the buy @220 when I saw the price plummet to 222.
Damnit!
|
|
|
|
|
And who still uses TH DIP chips?
|
|
|
|
|
It does annoy me when anyone refers to DDoS as 'hacking'.
|
|
|
|
It's all a massive pain in the arse.  |
|
|
|
Crashing to, say, $70, would be nice  |
|
|
|
Yay! Dunno what video Bitcoinity just played.... but I was there to see it!  |
|
|
|
0.02 to go |
|
|
|
|
I think you should make the option to connect to a non-local bitcoind a little easier and have a big warning not to use servers which you don't have control over. If the user still needs to manually set up network shares, and map drives etc. to allow access to the data files, then you won't be able to 'accidentally' connect to a non-trusted server... you'll REALLY have to put effort in to it. As with anything in the bitcoin world, let people do whatever they want and caveat emptor.
|
|
|
|
I wish some the design patterns that emerged in the 90s would just die already.
The case of a single user on a single computer should be treated as a rare exception, not the default use case.
Unix-like operating systems had solved this problem by assuming that all computers were part of a LAN and were used by more than one person. Windows destroyed this paradigm and the industry has never recovered.
Right. |
|
|
|
|
It's ridiculous to have 3 sets of the same 7Gb data connected to other peers through a single IP address... my home ADSL line.
It is not ridiculous for me to have another full copy at work, that being on an entirely different IP.
Electrum isn't quite what I'm looking for either, as that connects to public servers. I do want to run 'A' Full node. A cursory look doesn't show me how to create my own private electrum server, though I'm sure it's possible.
Maybe when Armory handles the full node itself, it could also act as a server to other Armory clients.
|
|
|
|
Bitcoin wasn't designed with a client-server model in mind and it's causing problems. A single home or business network shouldn't need to store N*M copies of the blockchain and require N*M external connections to the P2P network where N is the number of users and M is the number of devices each user owns.
Yeah, that seriously needs looking at. At 7GB (or so) sitting on my machine, it's pretty ridiculous to have to repeat the exact same open-for-everyone-to-see information for each user. |
|
|
|
|
I don't REALLY need it... but what if I want a copy on my machine, girlfriends machine, kitchen machine, someone else's machine etc.?
Have to install a full client on each? That's a whole lot of redundant data!
Sharing the data directory is entirely possible, but then where do I specify where Armory should look for these?
|
|
|
|
|
I want to connect to a bitcoin server I have running on my home network, rather than a local copy... can we specify an IP/hostname:port somewhere to connect to?
|
|
|
|
|
This whole double spend at a POS thing... not exactly the easiest thing to do, surely?
I mean, your standing there at the cashier paying for your coffee and at the exact same instant, you spend the money elsewhere. How whould you even do that?
|
|
|
|
|
Show Posts
