Great idea! Sorta like the DNSBL systems for ignoring email spam.
Simple text box in your profile where you can list user names, and then when the ignore function is working, it operates on the union of your ignore list and the ignore lists of the people you've listed.
A more advanced version of this feature could add named ignore lists. I could then organize my lists into categories, and people could select only the ones they want. For example, rather than ignore everyone that I've ignored, someone could use kjj.scammer to ignore only people on my scammer sublist.
It is nice option. But can another person see your scammer sublist or will that should be implemented too? Sorry, I am not good at this. ~~MZ~~ I think the user should decide himself for each sublist whether he wants it to be public or not |
|
|
|
|
I know that could be dangerous for newbies but it's much more practical than using Greasemonkey, moreover for phones/tablets.
It's nearly nothing to implement but is a great feature.
If you really think rogue scripts are really an issue the setting could be put in an hidden place, only js files from github/pastebin/etc could be used, js files must be pre-approved, etc.
|
|
|
|
|
If admins don't respond, I'd advise you to use them until one of them tell you to stop
They look pretty random after all...
|
|
|
|
Hello scammer...  |
|
|
|
On en parle depuis hier mais j'ai toujours du mal à y croire. Idem... |
|
|
|
|
Done!
0.2.96 released with bookmarks enabled.
You can bookmark threads or posts, the button is next to the "Quote in BT++ chat" button.
And again, the bookmarks are at the bottom of the pages. If you don't find it practical (and I know you won't), please tell me where I should put them.
|
|
|
|
Oh I'm sorry, the characters I put were only examples The command is python privkey.py 64-character-private-key without any bracket, period or anything. For example: python privkey.py 0123456789abcdefaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa The private key is the hexsec entry of dumpwallet. The hexsec entry only exists when you provide the passphrase (which is not the case in you previous post). |
|
|
|
GUI gives me this other error:
Constant Numerica Incorrect: 4e4.
Line: 1 Character: 38
parser error: <4e4: String> [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId: BadNumericConstant
I'm not familiar with these errors, would you mind sending me a screenshot? Check there's no visible private key beforehand. Now seems like a good time to bug you (jackjack I mean, not tevayo) to consider this pull request. With PyCrypto installed, I don't think Pywallet will create a usable wallet.dat file without this patch... Github can't automatically merge it, so I'll apply the patch as soon as I have my dev computer with me (within 2-3 days) I rebased the pull request, it should be OK to merge now (it was just a conflict in the version number which I shouldn't have touched to begin with...) Thanks Done Thanks again for your interest and for sending pull requests |
|
|
|
|
The tool I sent you transforms hexadecimal privkey to base58. Then you can import with the command line in the GUI client.
By the way, did you try using the recovered wallet (from pywallet --recover) directly as wallet.dat?
|
|
|
|
I did it, I'll push the update really soon. I didn't find a nice place so I'll put the list at the bottom of the page for now. I'm thinking about doing a list of bookmarked threads
In "Show new replies to your posts" and "Watchlist" you can't see the threads if you already read all the posts
In this new list you would see them all
That is good! Can you make an option to un-watch a thread? Because, I already clicked unwatch but the thread is still showing in new replies. Anything you can do? ~~MZ~~ Unwatch can only be done server-side. |
|
|
|
hello, I have a problem with a wallet deleted by mistake.
I recovered with recuva but after copying it to a flash drive formatted and after applying the pywallet says " 0 wallets recovered , 0 recovered private keys" so I assume that this wallet is totally corrupt.
Now I installed windows7 on a new hard disk (installed python27, pywallet, setuptools 4.1b1, bsbbd 3-6.0.1, pycrypto2.6, Twisted 14.0.0, python ecdsa) and the old record is not system disk. Now I'm trying this:
... <clip> ...
Now seems like a good time to bug you (jackjack I mean, not tevayo) to consider this pull request. With PyCrypto installed, I don't think Pywallet will create a usable wallet.dat file without this patch... Github can't automatically merge it, so I'll apply the patch as soon as I have my dev computer with me (within 2-3 days) |
|
|
|
Stuffing your altcoin's transaction data into the Bitcoin blockchain doesn't make it not-an-altcoin. The main sections are for the Bitcoin currency and things that you can directly do with bitcoins. If I can take my bitcoins, deposit them into your site, and then do something interesting without explicitly converting to a different currency, then your site can go in the main sections. For example, a casino could use a Counterparty currency as "chips", and this would be OK for the main sections as long as the casino could automatically convert deposited BTC into these chips. Similarly, if someone was selling Overstock shares for BTC, then this trade would be OK for the main Marketplace regardless of the technology used to handle the Overstock shares. (But don't try any nonsense like saying that every unit of an altcoin is a share in a company...) Noob question for sure.
If a coin or protocol isn't Bitcoin, then by definition isn't it an "Alternative Currency" ?
Is Mastercoin or Counter Party, Bitcoin?
Mastercoin is a normal scamcoin (more scammy than usual, in fact). Apparently it's common to transact in BTC using Counterparty, but Counterparty also has its own currency. I suspect that Counterparty has no really useful technology, but all I can find about their technology via Google is marketing fluff (bad sign), so I can't be sure. They both use the Bitcoin block chain for timestamping instead of doing their own mining. I think that this is often a good idea, but it doesn't mean that they're not altcoins (or that they're actually useful). By the way, if you're already using the Bitcoin block chain, then why are you even creating a currency? Just use BTC. From what little I've read about Counterparty, it looks to me like their XCP was included just to enable pump-and-dump. (The BitDNS proposal that I co-authored in 2010 was probably the first to propose using the blockchain like this, but it just used BTC.) Regardless of whether or not something is a scam, people building things on top of the blockchain is a reality. I can understand the 'don't bloat the blockchain' thinking, but by not engaging the bitcoin 2.0 crowd there are no productive discussions about how both can coexist- be it on the blockchain or on some sort of side chain, merge mining, etc, etc, etc..... 1) Why would that be bitcoin 2.0? 2) AFAIK a potential bitcoin 2.0 is for sure NOT bitcoin. 3) It's like your old idea of making testnetcoins a valuable altcoin: non-sense |
|
|
|
Oh it's for an altcoin! The problem must be this.
Please create a dummy address in your client then export the coresponding private key through the console and post it here.
I highly advise you to delete the address afterwards.
Thanks to this I'll be able to know which leading byte your altcoin uses to export private keys.
PS: without quotation marks
As you indicated me I made a dumpprivkey created and removed for the occasion wallet and this is what it returns me: WnPrHA434nWat8CL131TTsZ3w2GYXm15ConQfcMjpNg2zwiG2kJB I have taken other privatekeys and let you know that all start with W It does not look anything like the PrivateKey to recover remanded me, 52 characters instead of 64 characters. Let me know if you can do something about it. greetings Great! I changed pywallet a bit to make a script for you I just added those lines (do a diff before running it if you want): if len(sys.argv[1])==64:
print EncodeBase58Check(chr(201)+(sys.argv[1]).decode('hex')+'\x01')
else:
print 'bad private key length (%d)'%len(sys.argv[1])
exit() The result is here: http://pastebin.com/raw.php?i=VYJkFfMcJust save it to privkey.py then python privkey.py 2a5b4c4e1d5f...(64 hexadecimal characters) |
|
|
|
|
Oh it's for an altcoin! The problem must be this.
Please create a dummy address in your client then export the coresponding private key through the console and post it here.
I highly advise you to delete the address afterwards.
Thanks to this I'll be able to know which leading byte your altcoin uses to export private keys.
PS: without quotation marks
|
|
|
|
|
Happy birthday
May you be touch by his noodly appendage
|
|
|
|
|
If it bothers admins (and this is not the case), the only solution is punishing such behavior
It's just common sense: when you're new somewhere you search for habits before asking about them
Moreover when the rules are on the top of the page on which you send your thread!
"Search then post". Not the other way around!
|
|
|
|
if it were me, i'd make it a requirement that the newbies read for most common FAQ questions before being able to register an account.
IMO, they should be asked to read the FAQs and then be required to get through a short and simple multiple choice quiz on activity, forum rank, posting limit, etc. before they can actually make their very first post.  +1 The problem is that you'd see a website containing all the answers popping up really soon |
|
|
|
L'avantage de Bitcurex était de pouvoir rapidement envoyer ou retirer des fonds sans tracasserie administrative particulière. Suffisait de renseigner son numéro de compte (IBAN) et de respecter le plafond (2500€ je crois). Cet avantage valait bien le taux d'échange exorbitant appliqué (0.40%).
Maintenant, Bitcurex ressemble plus à un échange classique et se noie dans la masse.
Je serais prêt à payer jusqu'à 5% pour qu'on me foute la paix administrativement et qu'on garde ma privacy. (qui est limité car ils connaissent quand meme mon iban) +1 Carrément intéressé Je sens qu'il ne restera que localbitcoin |
|
|
|
Open notepad Write 50 random characters Ctrl-A Ctrl-X Bitcointalk.org -> change password Ctrl-V "Save" "Logout"  |
|
|
|
|
I rarely look at my github account and when I do it's in a hurry.
Thanks a lot for bringing that to my attention. I'll apply it by Monday.
|
|
|
|
|
Show Posts
