Why only have the link to bitcoin core at the top, and not classic, unlimited and XT as well?
Because those are altcoins, and this forum is called Bitcoin Talk. I'm not sure if you are serious but just so that newbies have better information, if I can use software to spend and receive bitcoins then the software, at a high level, is Bitcoin. Classic, unlimited, and XT are Bitcoin forks and become "Bitcoin" if enough people believe them to be. They fork not only the codebase but would also fork the Bitcoin blockchain. Even if one of the forks dies, including the old fork we are all currently using, the bitcoins you held before the fork would continue to function as bitcoins albiet with some changes due to the different code of the new fork. So far in Bitcoin history this has already happened twice and it continues to be the case that the current newest fork is the one we all call "Bitcoin". The only difference is that those two prior forks were non-contentious and the old forks died out quickly. On the other hand, if someone forks the Bitcoin codebase and starts it over with a new blockchain then I cannot spend and receive bitcoins using it. It is thus an altcoin. So let us please maintain some credibility among ourselves and just admit that the reason that Classic, XT, and others aren't allowed is because the administrator of this forum, theymos, believes that Bitcoin should not be forked at the current time at least in such a way as the authors of Classic and XT have proposed and he has chosen to have the forum reflect that belief. |
|
|
|
I have begun mentally planning to add a new address format to Bitmessage which has the public key encoded right in the bitmessage address. This comes at the behest of gmaxwell. It's a good idea. It would allow a Bitmessage user who receives messages to remain completely passive, and thus anonymous, even against a global attacker who can listen and even modify traffic on any or all individual Internet connections. But This would require that the same EC key be used for both signing and encryption where ECIES is used for encryption. Is there currently sufficient reason to believe that this should be avoided? Or is there specific reason to believe that it is safe? If there is only a small risk of it being insecure then it might be outweighed by the benefit of completely passive client operation. -Atheros |
|
|
|
|
I own bitcoinstats.org but I no longer need it. I used it for a while to display transaction confirmation times and some other things. I would like it to go to use for some sort of public good. Is anyone working on anything that could use it, hopefully as a not-for-profit service? I'll give it to you on the condition that what you build has at least some sort of use to the bitcoin community (like the display of Bitcoin-related statistics perhaps) and is at least partially free.
-Atheros
|
|
|
|
|
Do people these days still keep a computer on in their house? Assuming yes..
IPv6 should make it easier for mobile and home devices to connect. Then devices could pair by requiring that the user take a picture of a qr code on the computer screen using the phone. That's all it takes to authenticate the computer and the phone to each other when they connect forever after. Perfect forward secrecy could even easily be used for this connection. We can use all this to guarantee security but unfortunately not anonymity because a local passive attacker would be able to see when the user gets a message: it would be immediately* relayed to the phone.
*One might argue that you could introduce a randomized delay. But it would still be discernible after a number of trials and the number of trials wouldn't need to be very large. The only solution I'm aware of is to send data of definite size to the phone every x minutes thus an attacker wouldn't know what is real data and what is just filler. But I don't like this solution.
|
|
|
|
attachments sound like a good solution, thank you
is there any time frame for that?
There is not.  |
|
|
|
it is an useful feature to have the html displayed formatted, allows things like image sending, which might be a necessary feature for this to spread
but unfortunately as soon as you unselect the message you were looking at the display changes to unformatted and needs to be changed for seeing it formatted again, which is a barrier to general users
so is there a way to have it format html by default that is acessible to people not compiling their own clients?
ideally at some point this would be accessible through a checkbox in the settings, but for the time being is there a config to edit or something like that?
also, what would be nice for a future release is a image to base64 converter built into the client, that could vastly broaden the userbase for bitmessage
HTML content is purposely not displayed by default unless the user is white-listed, is in your address book, or you are subscribed to them. It would be better for us to support attachments before we bother building in a base64 encoding mechanism. It would be more data-efficient also. |
|
|
|
|
Please try renaming the PyBitmessage folder (which holds the messages.dat and other files) to something different. Do start by terminating the running Bitmessage process(es).
|
|
|
|
Running from XP.
Process does start but there is no any window or icon.
Version latest (0.4.1)
WTF?
You are the first person to report such a problem. If you want to provide the debug.log in the PyBitmessage folder, it might be of use. |
|
|
|
|
Yes, it is still active. I'm reviewing pull requests right now. The last binary release was in October because that is the last time we added "must have" features. In the source code is much more recent development.
|
|
|
|
|
So this solves the mystery of Satoshi's miner being 4 times faster, and we can tell he had only one computer mining. Which, as far as I understand it, makes the current question: Why was Satoshi's miner skipping byte values 10 through 18 and then resetting after 58?
|
|
|
|
Question about streams, there's only 1 now. When are more added?
When people feel that current system resource usage is getting too high. There is no clear defined line as I'm not even sure what the bottleneck will be (bandwidth? Disk IO? CPU? Memory?). |
|
|
|
|
^_^
At this point I find myself reading research papers about messaging networks and anonymity on my way to work. So it is indeed a turn around. Though that doesn't mean that there aren't interesting tools and programs I don't know about and I would always like to learn more.
|
|
|
|
Which source are you using? What OS? Any other info that you think might be helpful.
Edit: I just tried it out here and didn't see anything like that ... seems to be saying some source/header files not found?
I'm on Xubuntu 13.04. I am using the most recent Namecoin code (in the namecoin-qt branch) as of now. Here is the latest entry from 'git log': Merge: c540853 a9c69f2 Author: khalahan < khal@dot-bit.org> Date: Mon Jul 1 12:11:55 2013 +0200 Merge branch 'namecoin-qt-snailbrain' into namecoin-qt Thank you. |
|
|
|
|
BM-GteJMPqvHRUdUHHa1u7dtYnfDaH5ogeY
|
|
|
|
I followed the directions here: http://dot-bit.org/BuildNamecoinQTFromSourceOn this step: qmake "USE_UPNP=-" I get these errors: Project MESSAGE: Building without UPNP support
Project MESSAGE: Building without IPv6 support
sh: 1: /usr/lib/x86_64-linux-gnu/qt5/bin/lrelease: not found
WARNING: Failure to find: auxpow.cpp
WARNING: Failure to find: headers.h
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_bg.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_ca_ES.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_cs.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_da.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_de.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_el_GR.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_en.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_es.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_es_CL.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_et.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_eu_ES.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_fa.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_fa_IR.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_fi.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_fr.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_fr_CA.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_he.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_hr.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_hu.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_it.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_lt.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_nb.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_nl.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_pl.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_pt_BR.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_pt_PT.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_ro_RO.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_ru.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_sk.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_sr.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_sv.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_tr.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_uk.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_zh_CN.qm'
RCC: Error in '../src/qt/bitcoin.qrc': Cannot find file 'locale/bitcoin_zh_TW.qm'
I also tried using QT Creator and the namecoin-qt.pro file but that gave me an error about auxpow.cpp. I'd like to use Namecoin for something but if I can't get it to work then my users certainly won't be able to. |
|
|
|
Is this dead? The charts don't work any longer...
Yes, the blockchain has grown too large for ABE (a block explorer) to catch up which I depended on. I've removed links to the project where I can find them on the Wiki and I suppose I should point the domain to a better stats website. |
|
|
|
It also holds other people's public keys, the network object inventory, your subscriptions, and your whitelist and blacklist. So it is reasonably logical that it would also hold your address book. I think this is flawed: the green stuff is user settings and the red comes from the network. Those should be separated. I agree that that is the most logical way to separate them. But that isn't what people are asking for. |
|
|
|
Another question - backing up the address book. How do I do that. Couldn't find an obvious address book file.
The address book is, uh... in messages.dat. Don't ask me why. As for upgrading with git, you can "pull" or you can "fetch" and "merge." Oh, that's a GREAT place to put the address book.  It also holds other people's public keys, the network object inventory, your subscriptions, and your whitelist and blacklist. So it is reasonably logical that it would also hold your address book. And possibly a way to access and import addresses directly from the address book in the "Send" dialogue? This way I don't have to switch tabs and copy+paste manually.
Right click on one or more addresses in your address book and "Send message to this address". OperationalError: database is locked
A quick google search suggests that you should restart your computer because some process besides Bitmessage might have a lock on the database. |
|
|
|
Bug report:
On my Windows 7 machine, when Bitmessage is closed (through f.ex the tray icon), it will not re-open. Attempting to open it results in 2 Bitmessage.exe process instances, but no tray icon and no window.
Portable mode is on.
This is only sometimes reproducible. Deleting all .dat files resolves the problem, but wipes the "portable mode" setting.
If you go to Help > About, are you running v0.3.211 ? If not you might consider upgrading. |
|
|
|
I have reverted the EXE on the website back to the prior version (0.3.1) because some Windows 7 (and Windows server) users have reported having an issue sending messages with the current version.
I have fixed the issue. The binary on the website is current and working. how about UPnP port mapping or some other method? I don't have to mess with my router to get Bitcoin or uTorrent to work.
UPnP would be nice and it is on the feature request list. I will work on some other things like OSX support and attachments first. |
|
|
|
|
Show Posts
