https://bitcointalksearch.org/topic/m.2744224
Da seguire poi anche questo:
http://blog.frog.li/
https://github.com/FrogMessenger
Topic: Bitmessage - Alternativa decentralizzata all'email - page 4. (Read 43175 times)
Altra fork con grosso potenziale in arrivo
https://bitcointalksearch.org/topic/m.2744224
Da seguire poi anche questo:
http://blog.frog.li/
https://github.com/FrogMessenger
https://bitcointalksearch.org/topic/m.2744224
Da seguire poi anche questo:
http://blog.frog.li/
https://github.com/FrogMessenger
http://bitmsg.me
Questo servizio permette di usare il network di Bitmessage senza installare niente, direttamente da browser.
Attualmente il PoW viene eseguito serverside, ma è probabile che venga presto portato su javascript.
Naturalmente c'è un calo di sicurezza facendo uso di un servizio simile
https://bitcointalksearch.org/topic/announce-bitmsgme-now-featuring-ssl-deterministic-address-support-247951
https://pay.reddit.com/r/bitmessage/comments/1hec3f/bitmsgme_a_new_way_to_send_bitmessages_from_a_web/
https://bitmessage.org/forum/index.php/topic,2557.0.html
Ecco anche il changelog della v0.3.4
Questo servizio permette di usare il network di Bitmessage senza installare niente, direttamente da browser.
Attualmente il PoW viene eseguito serverside, ma è probabile che venga presto portato su javascript.
Naturalmente c'è un calo di sicurezza facendo uso di un servizio simile
https://bitcointalksearch.org/topic/announce-bitmsgme-now-featuring-ssl-deterministic-address-support-247951
https://pay.reddit.com/r/bitmessage/comments/1hec3f/bitmsgme_a_new_way_to_send_bitmessages_from_a_web/
https://bitmessage.org/forum/index.php/topic,2557.0.html
Ecco anche il changelog della v0.3.4
Code:
0.3.4
Linux: Store config files in $XDG_CONFIG_HOME
Added a new global variable user option: doTimingAttackMitigation
Moved a variety of classes and functions out of bitmessagemain.py and to their own modules
New API command: getSentMessageByAckData
Modified the getAllSentMessages and getSentMessageById commands to return ackData
API commands to get messages now return actual encoding type
Bugfix: Unicode chars in localtime prevented the gui from starting
Added 'Save message as...' option in Inbox
Added OS X Build scripts
Added option to subscribe to an address in your address book
Added getInboxMessageById API command
Updated icons to have sRGB profile to prevent warnings
Added French translation
Switched addr, msg, broadcast, and getpubkey message types to 8 byte time. Last remaining type is pubkey.
Added tooltips to show the full subject of messages
Added Maximum Acceptable Difficulty fields in the settings
Send out pubkey immediately after generating deterministic addresses rather than waiting for a request
Linux: Store config files in $XDG_CONFIG_HOME
Added a new global variable user option: doTimingAttackMitigation
Moved a variety of classes and functions out of bitmessagemain.py and to their own modules
New API command: getSentMessageByAckData
Modified the getAllSentMessages and getSentMessageById commands to return ackData
API commands to get messages now return actual encoding type
Bugfix: Unicode chars in localtime prevented the gui from starting
Added 'Save message as...' option in Inbox
Added OS X Build scripts
Added option to subscribe to an address in your address book
Added getInboxMessageById API command
Updated icons to have sRGB profile to prevent warnings
Added French translation
Switched addr, msg, broadcast, and getpubkey message types to 8 byte time. Last remaining type is pubkey.
Added tooltips to show the full subject of messages
Added Maximum Acceptable Difficulty fields in the settings
Send out pubkey immediately after generating deterministic addresses rather than waiting for a request
E' un alternativa all'email, ma non ha niente a che fare con le infrastrutture che gesticono/muovono l'email.
ma posso inviare email ad un provider tipo gmail ?
E' uscita la 0.3.4, anche se non è ancora presente il changelog.
Si sono aggiunti tanti altri sviluppatori, ed è probabile che fra non molto avremo un light client android, che si connetterà a server remoti (magari quello installato a casa o altrove...) per eseguire il PoW, e poter poi inviare il messaggio al network
Al che si avrà un sistema di messaggistica, completamente decentralizzato, sicuro e a portata di mano ovunque!
Si sono aggiunti tanti altri sviluppatori, ed è probabile che fra non molto avremo un light client android, che si connetterà a server remoti (magari quello installato a casa o altrove...) per eseguire il PoW, e poter poi inviare il messaggio al network
Al che si avrà un sistema di messaggistica, completamente decentralizzato, sicuro e a portata di mano ovunque!
0.3.3
Remove inbox item from GUI when using API command trashMessage
Add missing trailing semicolons to pybitmessage.desktop
Ensure $(DESTDIR)/usr/bin exists
Update Makefile to correct sandbox violations when built via Portage (Gentoo)
Fix message authentication bug
Remove inbox item from GUI when using API command trashMessage
Add missing trailing semicolons to pybitmessage.desktop
Ensure $(DESTDIR)/usr/bin exists
Update Makefile to correct sandbox violations when built via Portage (Gentoo)
Fix message authentication bug
Nuovo 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
Nuova versione
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
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
Quote
Bitmessage v0.3.0 is available. It is an important release with a new change relevant to everyone.
The most significant change is the move from version 2 to version 3 addresses.
With version 3 addresses, users may set the minimum-Proof-of-Work-difficulty that they require of others in order to receive a message. The network-minimum difficulty is 1 but you may, for example, demand that people who send you messages accomplish a proof of work with a difficulty of 1.5.
Before making new addresses, see the 'Demanded difficulty' tab in the settings menu.
The next new feature is encrypted broadcasts. Broadcasts sent from v3 addresses will now all be encrypted. Broadcasts sent from v2 addresses will remain in clear-text until 2013-05-28 at 10:00 UTC at which time all upgraded clients will automatically switch to using encrypted broadcasts for all addresses.
Note that broadcasts are only encrypted with the address of the person sending them.
Anyone who has the address may read the broadcast. Some people may try to decrypt all broadcasts with all addresses ever seen on the network; this is expected.
The purpose of this feature is to encrypt the data sufficiently well such that unencrypted data will not flow through your Internet connection that you are not actually interested in.
Going forward, all new addresses will be v3 addresses thus it would be wise to upgrade soon so that you may receive messages from new Bitmessage users. v2 and v3 addresses will remain mutually-compatible indefinitely.
The next new feature is Daemon mode which allows Bitmessage to run without a graphical user interface. https://bitmessage.org/wiki/Daemon
You may report issues to the Github issue tracker or by replying to this bitmessage. https://github.com/Bitmessage/PyBitmessage/issues
Users who downloaded the source code with git may use 'git pull origin master' to upgrade.
All the best, Atheros
https://bitmessage.org/
https://github.com/Bitmessage/PyBitmessage
Nuova versione.The most significant change is the move from version 2 to version 3 addresses.
With version 3 addresses, users may set the minimum-Proof-of-Work-difficulty that they require of others in order to receive a message. The network-minimum difficulty is 1 but you may, for example, demand that people who send you messages accomplish a proof of work with a difficulty of 1.5.
Before making new addresses, see the 'Demanded difficulty' tab in the settings menu.
The next new feature is encrypted broadcasts. Broadcasts sent from v3 addresses will now all be encrypted. Broadcasts sent from v2 addresses will remain in clear-text until 2013-05-28 at 10:00 UTC at which time all upgraded clients will automatically switch to using encrypted broadcasts for all addresses.
Note that broadcasts are only encrypted with the address of the person sending them.
Anyone who has the address may read the broadcast. Some people may try to decrypt all broadcasts with all addresses ever seen on the network; this is expected.
The purpose of this feature is to encrypt the data sufficiently well such that unencrypted data will not flow through your Internet connection that you are not actually interested in.
Going forward, all new addresses will be v3 addresses thus it would be wise to upgrade soon so that you may receive messages from new Bitmessage users. v2 and v3 addresses will remain mutually-compatible indefinitely.
The next new feature is Daemon mode which allows Bitmessage to run without a graphical user interface. https://bitmessage.org/wiki/Daemon
You may report issues to the Github issue tracker or by replying to this bitmessage. https://github.com/Bitmessage/PyBitmessage/issues
Users who downloaded the source code with git may use 'git pull origin master' to upgrade.
All the best, Atheros
https://bitmessage.org/
https://github.com/Bitmessage/PyBitmessage
- Broadcast criptati
- Modalità demone (prevedo l'arrivo dei primi keylogger che lo sfruttino
)- POF per ricevere impostabile
Pare funzionare ora. Vediamo se ricevo una rispota da un certo marrano...
E anche da un certo zio...
E anche da un certo zio...
Nuova versione
0.2.8
- Fixed Ubuntu & OS X issue: Bitmessage wouldn't receive any objects from peers after restart.
- Inventory flush to disk when exiting program now vastly faster.
- Fixed address generation bug (kept Bitmessage from restarting).
- Improve deserialization of messages before processing.
- Change to help Macs find OpenSSL the way Unix systems find it.
- Do not share or accept IPs which are in the private IP ranges.
- Added time-fuzzing to the embedded time in pubkey and getpubkey messages.
- Added a knownNodes lock to prevent an exception from sometimes occurring when saving the data-structure to disk.
- Show unread messages in bold and do not display new messages automatically; let user click it.
- Support selecting multiple items in the inbox, sent box, and address book.
- Use delete key to trash Inbox or Sent messages.
- Display richtext(HTML) messages from senders in address book or subscriptions (although not pseudo-mailing-lists; use new right-click option).
- Trim spaces from the beginning and end of addresses when adding to address book, subscriptions, and blacklist.
- Improved the display of the time for foreign language users.
0.2.8
- Fixed Ubuntu & OS X issue: Bitmessage wouldn't receive any objects from peers after restart.
- Inventory flush to disk when exiting program now vastly faster.
- Fixed address generation bug (kept Bitmessage from restarting).
- Improve deserialization of messages before processing.
- Change to help Macs find OpenSSL the way Unix systems find it.
- Do not share or accept IPs which are in the private IP ranges.
- Added time-fuzzing to the embedded time in pubkey and getpubkey messages.
- Added a knownNodes lock to prevent an exception from sometimes occurring when saving the data-structure to disk.
- Show unread messages in bold and do not display new messages automatically; let user click it.
- Support selecting multiple items in the inbox, sent box, and address book.
- Use delete key to trash Inbox or Sent messages.
- Display richtext(HTML) messages from senders in address book or subscriptions (although not pseudo-mailing-lists; use new right-click option).
- Trim spaces from the beginning and end of addresses when adding to address book, subscriptions, and blacklist.
- Improved the display of the time for foreign language users.
download for MAC and Linux? nisba?
Io sto provando con questa guida sperando funzioni per MAC OS X https://bitmessage.org/forum/index.php/topic,1451.0.html
EDIT: a me da strani errori..
EDIT2: In qualche modo sono riuscito (spero di aver fatto tutto giusto)
BM-oq7rHGTQJSY6ffJUU1SJrkk4JHCtDUW34
@(A)social Ti ho scritto, qualche giorno fa anche io.
Nemmeno una risposta. Maleducato !
Nemmeno una risposta. Maleducato !
Ho risposto, e mi risultava messaggio ricevuto, tsè. Se vuoi ti mando lo screenshot.
Nel dubbio avevo mandato anche un PM qui.
In ogni caso non funziona, pare non basti reinstallare PyBitmessage da capo, bisogna cancellare completamente la cartella .PyBitmessage. Anche lasciare uno solo dei file creati durante la prima sessione (keys.dat o messages.dat) pare bloccarne il funzionamento.
Boh, Chi ci capisce qualcosa? Possibile non capiti al developer?
@(A)social Ti ho scritto, qualche giorno fa anche io.
Nemmeno una risposta. Maleducato !
Nemmeno una risposta. Maleducato !
Me ne sono accorto ora, secondo me è un bug che che non è avvenuto subito.
Saranno 4/5 giorni che l'ho installato (Linux) e ho notato subito questa cosa, già i primi messaggi non me li aveva inviati "completamente", uno pure a te.
Me ne sono accorto ora, secondo me è un bug che che non è avvenuto subito.
Fa questo problema anche a me, con la precedente versione andava tutto bene ...
Ora lo dici?
Quindi non rimane che aspettare o installare la versione precedente... se si trova.
Fa questo problema anche a me, con la precedente versione andava tutto bene ...
Va bè, per ora penso di dover rinunciarci, peccato.
Funziona solo al primo avvio (ho anche inviato/ricevuto un paio di messaggi) ma al secondo non c'è più attività, nonostante abbia 8 connessioni. Se lo reinstallo da zero, cancellando anche tutto il contenuto di .PyBitmessage funziona per quella sessione e poi basta. Sob!
Funziona solo al primo avvio (ho anche inviato/ricevuto un paio di messaggi) ma al secondo non c'è più attività, nonostante abbia 8 connessioni. Se lo reinstallo da zero, cancellando anche tutto il contenuto di .PyBitmessage funziona per quella sessione e poi basta. Sob!
Il progetto è nato da poco e attualmente c'è praticamente solo un dev
Jump to: