La chat richiede un account Telegram. Per chi volesse può anche usare la versione web, che non richiede alcuna installazione: http://web.telegram.orgLINK invito: Compra / vendita Bitcoin e annunci offerte/richieste varieREGOLE:- Attualmente il BOT butta fuori dal gruppo se l'utente scrive due messaggi di seguito nell'arco di 20 secondi. L'obiettivo è bloccare il più possibile le discussioni sulla chat. - Si possono fare annunci per offerte e richieste su tutto (che sia legale), basta che sia previsto in qualche modo l'uso di Bitcoin - Vietato qualsiasi tipo di discussione, è tollerato fare una o due domande ogni tanto purchè queste siano in topic e utili allo scopo della chat. Per discutere pubblicamente di qualcosa correlato alla chat di compravendita è possibile usare la chat offtopic https://telegram.me/bitcoinofftopicitalia- Vietate immagini che non siano strettamente legate all'acquisto/vendita di un qualche prodotto/servizio (quindi ovviamente, vietati meme vari), vietati sticker e video. - Le discussioni di compravendita con i clienti vanno fatte in privato - La promozione va bene, l'eccessivo spam no. Non ha senso proporre qualcosa alle stesse persone per più di 1/2 volte. E' possibile ripostare un annuncio al massimo ogni 48 ore. - Alla prima violazione delle regole si riceverà un warn, alla seconda si riceverà un ban di tempo variabile. - Vietata la compravendita con Paypal, a causa di truffe e chargeback. NOVITA'L'uso di Bitrated.com è fortemente consigliato: https://bitcointalk.org/index.php?topic=1055575.0Dare fiducia ad uno sconosciuto nella chat ti farà probabilmente perdere i soldi Se non usi l'escrow lo fai a tuo rischio e pericolo, non ti lamentare con i moderatori se i tuoi soldi spariscono. Quindi:- Lamentele causate dal suo NON uso (tipo truffe) saranno probabilmente ignorate. - Lamentele in privato per eventuali ban saranno ignorati. - Lamentele su altri gruppi per eventuali BAN potrebbe facilmente portare a ban da TUTTI i gruppi Altre chat:https://bitcointalk.org/index.php?topic=792300.0 |
|
|
|
Aggiunto un pezzo alla guida  |
|
|
|
E' solo questione di tempo Attendete che questa tecnologia arrivi a completamento https://webtorrent.ioVedrete i film in streaming p2p direttamente su thepiratebay. |
|
|
|
|
I'll wait for your 100%-sure-solution to catch fake accounts, but before developing it, you should give back the money to your unlucky customers.
|
|
|
|
I've a discussion with all the "probably" legitimate sellers about this problem. They say that there are "other" sellers that are using fake accounts, but I usually say to them that I'll give them the benefit of the doubt. Again, I've even wrote this in the hope to lower the problem. https://bitcointalk.org/index.php?topic=1120461.0This discussion is going in circle  |
|
|
|
|
In the market section I've made a rule where it isn't possible to bump the thread more that one time in 24 hours.
The only allowed way to have more "bumps", is by the "thanks" from their customers.
So, sellers are directly asking to their customers to write thanks.
Then yes, they are "bumps", but they are legitimate.
They are not (legitimate) if they comes from fake/clone of customers (made from the same sellers)
But this put back the problem on what I wrote, it isn't easy to find them.
You were really easy to catch.
I thought that you where FX_trader from your first message on the italian section, but I wasn't sure.
That I found your messages on the other english sections, and you were making the same things.
|
|
|
|
The problem of italians is that: - Many doesn't know english (than this make it hard for them using exchanges) - They are used to use cash, and so they aren't comfortable on using bank transfers. - Many of them prefer to use cash to maintain a good anonymity This create a situation where there are a lot of REAL newbies that come to buy Bitcoin from the sellers available in our market section. Then, this make it really hard to find who is a clone/fake and who is not. If the forum would be able to give us (Staff) a least if an user is using the IP of someone else, I'll be happily using it. But now there isn't, and I try to maintain the benefit of the doubt on our section. I even tried to make a threat agaist "possible" sellers that are making fake account: https://bitcointalk.org/index.php?topic=1120461.0Se scopro un feedback fasullo vi beccate un trust negativo da me
Siete quindi fottuti come venditori, pensateci bene It's something like: If I'll find a fake feedback I'll give you a negative trust Then you know, you will be fucked, think hard about it. Now about FX_trader. He owes money to an italian user, and then I found that there is another user that wants back his money (And maybe, even others): https://bitcointalk.org/index.php?topic=1175224.msg12442622#msg12442622https://bitcointalk.org/index.php?topic=1198054.msg12580337#msg12580337I think that FX_trader isn't so crafty, it was really easy to catch him |
|
|
|
|
Mi sa che potrei anche valutare di vietare i prestiti se si continua cosi.
Qua si chiude.
|
|
|
|
Aggiunto |
|
|
|
C'è un bug su quella versione che non lo fa partire su alcune versioni di Windows. Come fix temporaneo modificate questo file: Messenger/TorMessenger/Data/Browser/profile.default/prefs.jsAggiungendo queste due righe: user_pref("gfx.direct2d.disabled", true);
user_pref("layers.acceleration.disabled", true); |
|
|
|
No no, aggiungo tutti, l'utente sceglie liberamente Per di più appunto, state scrivendo i feedback in questa discussione! |
|
|
|
|
Hai intenzione di svilupparne una anche per Android?
|
|
|
|
Tor Messenger: Chat over Tor, Easily https://blog.torproject.org/blog/tor-messenger-beta-chat-over-tor-easilyWhat is it?
Tor Messenger is a cross-platform chat program that aims to be secure by default and sends all of its traffic over Tor. It supports a wide variety of transport networks, including Jabber (XMPP), IRC, Google Talk, Facebook Chat, Twitter, Yahoo, and others; enables Off-the-Record (OTR) Messaging automatically; and has an easy-to-use graphical user interface localized into multiple languages.
What it isn't...
Tor Messenger builds on the networks you are familiar with, so that you can continue communicating in a way your contacts are willing and able to do. This has traditionally been in a client-server model, meaning that your metadata (specifically the relationships between contacts) can be logged by the server. However, your route to the server will be hidden because you are communicating over Tor.
We are also excited about systems like Pond and Ricochet, which try to solve this problem, and would encourage you to look at their designs and use them too.
Why Instantbird?
We considered a number of messaging clients: Pidgin, Adam Langley's xmpp-client, and Instantbird. Instantbird was the pragmatic choice -- its transport protocols are written in a memory-safe language (JavaScript); it has a graphical user interface and already supports many natural languages; and it's a XUL application, which means we can leverage both the code (Tor Launcher) and in-house expertise that the Tor Project has developed working on Tor Browser with Firefox. It also has an active and vibrant software developer community that has been very responsive and understanding of our needs. The main feature it lacked was OTR support, which we have implemented and hope to upstream to the main Instantbird repository for the benefit of all Instantbird (and Thunderbird) users.
Current Status
Today we are releasing a beta version with which we hope to gain both usability and security related feedback. There have been three previous alpha releases to the mailing lists that have already helped smooth out some of the rougher edges.
Downloads
Linux (32-bit)
Linux (64-bit)
Windows
OS X
sha256sums.txt
sha256sums.txt.asc
The sha256sums.txt file containing hashes of the bundles is signed with the key 0x6887935AB297B391 (fingerprint: 3A0B 3D84 3708 9613 6B84 5E82 6887 935A B297 B391).
Instructions
On Linux, extract the bundle(s) and then run: ./start-tor-messenger.desktop
On OS X, copy the Tor Messenger application from the disk image to your local disk before running it.
On all platforms, Tor Messenger sets the profile folder for Firefox/Instantbird to the installation directory.
Note that as a policy, unencrypted one-to-one conversations are not allowed and your messages will not be transmitted if the person you are talking with does not have an OTR-enabled client. You can disable this option in the preferences to allow unencrypted communication but doing so is not recommended.
Source Code
We are doing automated builds of Tor Messenger for all platforms.
The Linux builds are reproducible: anyone who builds Tor Messenger for Linux should have byte-for-byte identical binaries compared with other builds from a given source. You can build it yourself and let us know if you encounter any problems or cannot match our build. The Windows and OS X builds are not completely reproducible yet but we are working on it.
What's to Come
Our current focus is security, robustness and user experience. We will be fixing bugs and releasing updates as appropriate, and in the future, we plan on pairing releases with Mozilla's Extended Support Release (ESR) cycle. We have some ideas on where to take Tor Messenger but we would like to hear what you have to say. Some possibilities include:
Reproducible builds for Windows and OS X
Sandboxing
Automatic updates
Improved Tor suport
OTR over Twitter DMs
Produce (and distribute) internationalized builds
Secure multi-party communication (np1sec)
Encrypted file-transfers
Usability study
How To Help
Give it a try and provide feedback, requests, and file bugs (choose the "Tor Messenger" component). If you are a developer, help us close all our tickets or help us review our design doc. As always, we are idling on IRC in #tor-dev (OFTC) (nicks: arlolra; boklm; sukhe) and subscribed to the tor-talk/dev mailing lists.
Please note that this release is for users who would like to help us with testing the product but at the same time who also understand the risks involved in using beta software.
Thanks and we hope you enjoy Tor Messenger! |
|
|
|
|
Nuova release
# Release 2.5.2 (bugfixes)
* fix bug #1513 (client tries to broadcast transaction while not connected)
* fix synchronization bug (#1520)
* fix command line bug (#1494)
* fixes for exchange rate plugin
|
|
|
|
|
Show Posts
