There could dns seeding
There is but it is disabled when you use a SOCKS proxy (like Tor).
Also, I believe that the latest release will fix your "GUI doesn't display" problem.
Topic: [ANNOUNCE] Bitmessage - P2P Messaging system based partially on Bitcoin - page 17. (Read 89873 times)
June 03, 2013, 12:41:25 PM
There is but it is disabled when you use a SOCKS proxy (like Tor).
Also, I believe that the latest release will fix your "GUI doesn't display" problem.
June 03, 2013, 12:37:15 PM
New update 
0.3.2
Bugfix: Remove remaining references to the old myapp.trayIcon
Refactored message status-related code. API function getStatus now returns one of these strings: notfound, msgqueued, broadcastqueued, broadcastsent, doingpubkeypow, awaitingpubkey, doingmsgpow, msgsent, or ackreceived
Moved proof of work to low-priority multi-threaded child processes
Added menu option to delete all trashed messages
Added inv flooding attack mitigation
On Linux, when selecting Show Bitmessage, do not maximize automatically
Store tray icons in bitmessage_icons_rc.py
0.3.2
Bugfix: Remove remaining references to the old myapp.trayIcon
Refactored message status-related code. API function getStatus now returns one of these strings: notfound, msgqueued, broadcastqueued, broadcastsent, doingpubkeypow, awaitingpubkey, doingmsgpow, msgsent, or ackreceived
Moved proof of work to low-priority multi-threaded child processes
Added menu option to delete all trashed messages
Added inv flooding attack mitigation
On Linux, when selecting Show Bitmessage, do not maximize automatically
Store tray icons in bitmessage_icons_rc.py
June 02, 2013, 01:24:06 PM
There could dns seeding
June 02, 2013, 07:36:11 AM
Bitmessage doesn't seem to be playing very well with Tor. It's giving all sorts of warnings.
Works without any problems..
TOR just warns you that a 3rd party program is using the connection may leak DNS information.
BUT Bitmessage doesnt request any DNS infos..( correct if I am wrong though).
So you are completely safe..BUT it still be nice to get rid of this messages..
Also my nix warns me all the time of an unknown email client using un-encrypted connections...
gotta live with that
June 02, 2013, 07:34:14 AM
Aetheros ... just wondering if there is a use case [for] a reputation scoring system [with] Bitmessage addresses?
Only about a thousand possible use cases. I've long thought that an actual working distributed web of trust would be as revolutionary as the Internet: imagine having a complete stranger walk up to you on the street outside your home and say, "Hey man, Can I borrow your keys like right now?" and you hold your phones up next to each other, a light turns green, you check to make sure he matches the picture on your phone, and you hand him the keys.
For Bitmessage alone it means getting rid of the PoW for identities who are sufficiently trusted, eliminating spam entirely, and obviously integration with other systems which depend on feedback and trust of identities.
As far as implementation of the distributed web of trust, I'm not sure how it would work but there does appear to be a lot of research on the topic. We could use someone who can recommend some set of papers to read first since there is so much.
http://privwiki.dreamhosters.com/wiki/Distributed_Web_of_Trust_Proposal_2
yes excellent !!
DO IT !
June 01, 2013, 06:34:46 PM
Bitmessage doesn't seem to be playing very well with Tor. It's giving all sorts of warnings.
May 29, 2013, 04:27:45 AM
Aetheros ... just wondering if there is a use case [for] a reputation scoring system [with] Bitmessage addresses?
Only about a thousand possible use cases. I've long thought that an actual working distributed web of trust would be as revolutionary as the Internet: imagine having a complete stranger walk up to you on the street outside your home and say, "Hey man, Can I borrow your keys like right now?" and you hold your phones up next to each other, a light turns green, you check to make sure he matches the picture on your phone, and you hand him the keys.
For Bitmessage alone it means getting rid of the PoW for identities who are sufficiently trusted, eliminating spam entirely, and obviously integration with other systems which depend on feedback and trust of identities.
As far as implementation of the distributed web of trust, I'm not sure how it would work but there does appear to be a lot of research on the topic. We could use someone who can recommend some set of papers to read first since there is so much.
http://privwiki.dreamhosters.com/wiki/Distributed_Web_of_Trust_Proposal_2
May 27, 2013, 12:07:40 AM
Confirmed, 3.0 good, 3.1 no GUI, no crash though.
May 27, 2013, 12:01:01 AM
:/
let me quickly retry .3, can i get a link? sanity check.
let me quickly retry .3, can i get a link? sanity check.
https://bitmessage.org/download/windows/Archive/
May 26, 2013, 11:58:39 PM
:/
let me quickly retry .3, can i get a link? sanity check.
let me quickly retry .3, can i get a link? sanity check.
May 26, 2013, 11:57:44 PM
It works on 7 x64. But not on 2012 x64. In the task manager it seems to be active, it has 2 processes. The GUI doesn't display. I tried deleting the knownnodes and message but still no gui.
Time for me to add logging functionality.
May 26, 2013, 11:52:56 PM
It works on 7 x64. But not on 2012 x64. In the task manager it seems to be active, it has 2 processes. The GUI doesn't display. I tried deleting the knownnodes and message but still no gui.
May 26, 2013, 11:50:55 PM
0.3.1 doesn't seem to be starting up.
What does it do?
May 26, 2013, 09:53:42 PM
0.3.1 doesn't seem to be starting up.
May 26, 2013, 11:20:53 AM
Bitmessage suddenly wont load after working for weeks. Any ideas?
Are you running the Windows EXE or the source code?
The EXE
May 25, 2013, 11:54:52 PM
Couple of pages ago (#102), I was asking for help with Debian Testing compilation, as Testing is provided with python2.7, but there is no PyQt4.QtCore for python2.7, only for python3.0, which is not supported by Bitmessage.
But on Ubuntu it's working fine, thanks I just compiled binary and installed it without problems.
I will have to look again on my Debian laptop
But on Ubuntu it's working fine, thanks
I just compiled binary and installed it without problems.I will have to look again on my Debian laptop
Unfortunately Debian, Fedoria, (and thus others like Mint Linux) cannot run it as easily because their copies of OpenSSL doesn't include Elliptic Curve cryptographic functions for patent reasons.
Any chance of switching from OpenSSL to GnuTLS? It would solve that problem, which is rather large considering how many of your users are likely on a linux machine.
May 25, 2013, 11:19:40 PM
I've looked for a btc donation address but haven't yet found.
May 25, 2013, 09:27:37 PM
Quote from: dokument
I made a short video describing the core features and functions of Bitmessage. I would like to know if anyone sees incorrect information so that I can fix it before I share the link more broadly.
https://www.youtube.com/watch?v=t_dTotavJZ8
Thanks,
.dok
https://www.youtube.com/watch?v=t_dTotavJZ8
Thanks,
.dok
May 25, 2013, 07:02:44 PM
Atheros, what's your donation address for Bitmessage?
May 25, 2013, 06:19:35 PM
0.3.1
Added new API commands: getDeterministicAddress, addSubscription, deleteSubscription
TCP Connection timeout for non-fully-established connections now 20 seconds
Don't update the time we last communicated with a node unless the connection is fully established. This will allow us to forget about active but non-Bitmessage nodes which have made it into our knownNodes file.
Prevent incoming connection flooding from crashing singleListener thread. Client will now only accept one connection per remote node IP
Bugfix: Worker thread crashed when doing a POW to send out a v2 pubkey (bug introduced in 0.3.0)
Wrap all sock.shutdown functions in error handlers
Put all 'commit' commands within SQLLocks
Bugfix: If address book label is blank, Bitmessage wouldn't show message (bug introduced in 0.3.0)
Messaging menu item selects the oldest unread message
Standardize on 'Quit' rather than 'Exit'
[OSX] Try to seek homebrew installation of OpenSSL
Prevent multiple instances of the application from running
Show 'Connected' or 'Connection Lost' indicators
Use only 9 half-open connections on Windows but 32 for everyone else
Added appIndicator (a more functional tray icon) and Ubuntu Messaging Menu integration
Changed Debian install directory and run script name based on Github issue #135
Added new API commands: getDeterministicAddress, addSubscription, deleteSubscription
TCP Connection timeout for non-fully-established connections now 20 seconds
Don't update the time we last communicated with a node unless the connection is fully established. This will allow us to forget about active but non-Bitmessage nodes which have made it into our knownNodes file.
Prevent incoming connection flooding from crashing singleListener thread. Client will now only accept one connection per remote node IP
Bugfix: Worker thread crashed when doing a POW to send out a v2 pubkey (bug introduced in 0.3.0)
Wrap all sock.shutdown functions in error handlers
Put all 'commit' commands within SQLLocks
Bugfix: If address book label is blank, Bitmessage wouldn't show message (bug introduced in 0.3.0)
Messaging menu item selects the oldest unread message
Standardize on 'Quit' rather than 'Exit'
[OSX] Try to seek homebrew installation of OpenSSL
Prevent multiple instances of the application from running
Show 'Connected' or 'Connection Lost' indicators
Use only 9 half-open connections on Windows but 32 for everyone else
Added appIndicator (a more functional tray icon) and Ubuntu Messaging Menu integration
Changed Debian install directory and run script name based on Github issue #135
Jump to: