Stumbled over a site which lists a bunch of referral sites: http://bitly.com/bundles/opticbit/3From a quick scroll through the list, there seem to be around 40 Bitcoin related links which contain what looks like a refid. I didn't check if any of those are already posted here though. But I guess it will be a good start for you.
|
|
|
Should I send to 1BitskyZbfR4irjyXDaGAM2wYKQknwX36Y?
Yeah, that's ok. Thanks
|
|
|
From your FAQ: These surveys are powered by CPALead. CPALead? Really? The same CPALead which was sued by Facebook for scamming users? The same CPALead which is the first entry in every browser's blocklist? New to Bitcoin and need to get some free Bitcoins? Or just want some more Bitcoins for free?
This is a brand new site allowing you to get Bitcoins for free by completing surveys, trial offers and purchasing certain products. You can also get Bitcoins my referring your friends and family to the site!
Free? Sounds like you have to work for it, so it's not free. Ok, maybe the 0.1BTC signup bonus is. But you still need to work to make 0.9BTC more to request a payout.
|
|
|
Bounty received. Nice guy to work with and he paid promptly too.
|
|
|
Splitting the private key to front and back would increase security but would increase the rate of printing errors (imagine a single sided printer and multiple bills per page...multiple pages in a print job...you're just begging for mistake).
No. You are splitting the code, but you print both parts at the same time, onto the same film. Or in case of "split" notes, on two different films. You do not print onto the backside. That's why the medium is transparent, so there is no need to do anything on the backside. You are still thinking of paper. That said, in case of the private key in text form, you can use a monospaced font and print every second letter in area 2 (or film 2). So even if you somehow mess up the OR code, you still can type in the privkey.
|
|
|
I haven't read the whole thread, so maybe someone else already suggested this: don't be limited to paper only in the designs. Banknotes could also be printed on transparency film.
That way, QR-codes and privkeys can be broken up into grids of small squares and printed twice onto the banknote. One field contains half the squares, the second field the rest. You then need to fold the node so that the two layers create the complete code again. That way, a quick glance at the QR-code or the privkey isn't useful anymore.
Or print on two completely separate sheets. Store one in your safe, the other one somewhere else. You need both of them to redeem the coins then. Or it can be used as some sort of escrow: hand over sheet 1 and after the deal is done sheet 2 too. When the public code is on both, anybody can change the balance, but only when you have both sheets you can redeem it.
Using such plastic would also allow the user to cover the important codes with a paint that is soluble in water. Black paint covering black toner. You have to wipe it off to scan the redeem code for example.
|
|
|
I have some AES-256 encrypted zip files that I need to open in Linux. Can someone tell me what the best encryption tool in Linux is?
From what I read, 7-zip and RAR have a command-line version for Linux. So, that would work, but a GUI is easier and faster to use.
I am not interested in GPG because I don't want to mess with keys. I simply want to encrypt and decrypt using AES-256 in Linux with a single password, using a GUI instead of command-line. In other words, a WinRAR-type program that runs in Linux.
Maybe PeaZip: http://peazip.sourceforge.net/peazip-linux.html- 7Z files' AES256 encryption - ZIP WinZip's AE encryption based on AES256 (and ZipCrypto for legacy compatibility); can decrypt PKZip's AES encryption - FreeARC's ARC: AES256, Blowfish, Twofish256 and Serpent256; this format also supports recovery records to protect data against corruption - PEA: AES256 EAX authenticated encryption
|
|
|
Hmm, I don't get any tasks. Did 1 task yesterday, think it was just some kind of test and earned 0 points. And now there's only 1 task available worth of 2 points and when click it, it says that it's finished. Does my location affect to those available tasks? And how many tasks there should be / day? I'm pretty new, so might be that I do something wrong?
For many tasks, the location is relevant. My tasklist looks pretty much like yours it seems. I haven't done any task for months now because CrowdFlower (who is running the backend) seems to be incapable. Their support board is filled with complains about accuracy problems, missing points and bugs (Simple bugs haven't been fixed since weeks. Or listing finished tasks as available). What's even worse is that the payment constantly goes down while the amount of time you'd need to invest increases.
|
|
|
Site is currently broken: Server Error in '/' Application. Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
<!-- Web.Config Configuration File -->
<configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration>
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
<!-- Web.Config Configuration File -->
<configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>
|
|
|
If you're on cPanel, you can setup one domain to use the shared IP as the SSL. It's a little tricky, but it's possible.
cpanel? I hope you are not serious. It's one of the worst ways to ruin a perfectly fine Linux installation. If it's the only SSL, you won't need another IP. HTTPS runs on 443, so set up a vhost to listen on that port only. Add another vhost for that domain on port 80 and use mod_rewrite to redirect all requests to https.
|
|
|
Ok so I noticed in apache2.conf there was Include sites-enabled AND Include /var/www I commented out /var/www and restarted apache and the error is gone. HOWEVER! The page still wont display at all: http://phr0stbyt3.com/index.phpMaybe you should post the errors from the error.log instead of letting everybody look at a blank page to guess what the error might be
|
|
|
There have been numerous reports about this problem lately, mainly since Satoshidice caused a spike in transactions. In my opinion, this is a real roadblock for new users, who usually don't want to invest the time it takes for the initial download. Defenders of the status quo will mention web-based wallets (which I don't trust), or other clients (where only Electrum seems to be the only choice (if you don't want Java)).
The main client needs to be optimized in that area (I/O and pruning). Currently, it's faster (for me) to download a snapshot and only verify the last missing blocks than letting the client take care of updating 3+ days; and I'm on a slow connection.
|
|
|
No need for pywallet anymore, the following command should do it: bitcoind -dumpprivkey [your_address] (while bitcoin-qt is running)
True. Pywallet dumps a lot more interesting information though.
|
|
|
So, the address bitcoin-qt sent my change to isn't on the "recieve coins" list. Is this normal?
The addresses are marked as "reserve" and those aren't displayed; unless you use coincontrol. Also, why does it send the change to a difference address for every damn transaction I make?
To support privacy up to some point. If you send out 1btc from an address holding 2btc, the other 1btc will go to another address (your reserve address), but from the blockexplorer you don't know which one is yours and which one is the real recipient. Or if both belong to other persons. Having said that (and being a coincontrol user), I think it would be nice to let the user decide if the change should go back to the source address. And I haven't found a way to export my private keys that works.
pywallet --dumpwallet
|
|
|
Did you PM him? He'll automatically receive a notification in his email.
Did you PM him? He'll automatically receive a notification in his email if he did not change "Notify by email every time you receive a personal message" to "Never". Fixed.
|
|
|
Very funny personal attack. Locking accounts at random because they did not have time to log in = genius policy.
You worked hard to get this tag, along with 22.5btc, so you've got to live with it. Also the locks won't happen randomly, but after a defined time and with a redirect to an explanation. Use escrow and you are safe ... but some just want / beg to get scammed !
So how does an escrow protect you from someone who just keeps the money lent to him? Like in this case: https://bitcointalk.org/index.php?topic=86248.msg982776#msg982776
|
|
|
Does not mean that you should lock the account mate.
That is not nice for people that don't even have any idea why the account is locked nor can find out why.
-1 for this policy.
Well, with that tag below your username, I'm not really surprised that you don't like my suggestion. Of course you can let people know why the account is locked. Just redirect them to a page explaining why and what to do about it when they try to log in. An email verification or a signed message isn't really that much work if you can't be bothered to log in at least once every month or two. With such a policy, threads like this one would not exist: https://bitcointalk.org/index.php?topic=86248.msg982776#msg982776The lender would still have his 55btc.
|
|
|
It looks like quite a few members here got scammed by people who managed to get access to abandoned accounts, most likely because they used the same password on multiple sites. Especially if the accounts belong to users with more than 100-200 postings, others trust them more than newbie accounts, what makes the scam easier to pull off.
There should be a "max days between logins" limit, after which an account gets locked and need to be manually enabled again by a mod. Either by sending a new password to the registration mail (which could be hacked too however), or by having the member sign a message with the btc address in the sig (if available; perhaps make providing a btc address mandatory), or by giving hints about who they sent PM's to.
If someone doesn't log in at least once every 30-60 days, he hasn't much interest in Bitcoin at all.
|
|
|
- A large country that won't be easily intimidated. - A country without strong ties to the US. - A country that runs its own registrar. For-profit registrars can be easily intimidated.
bitcointalk.cn? bitcointalk.ir? bitcointalk.cu? bitcointalk.ru?
|
|
|
|