It was the Bitcointalk forum that inspired us to create Bitcointalksearch.org - Bitcointalk is an excellent site that should be the default page for anybody dealing in cryptocurrency, since it is a virtual gold-mine of data. However, our experience and user feedback led us create our site; Bitcointalk's search is slow, and difficult to get the results you need, because you need to log in first to find anything useful - furthermore, there are rate limiters for their search functionality.
The aim of our project is to create a faster website that yields more results and faster without having to create an account and eliminate the need to log in - your personal data, therefore, will never be in jeopardy since we are not asking for any of your data and you don't need to provide them to use our site with all of its capabilities.
We created this website with the sole purpose of users being able to search quickly and efficiently in the field of cryptocurrency so they will have access to the latest and most accurate information and thereby assisting the crypto-community at large.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
- From goatpig on October 7th 2016:
Situation is back to normal. I am now confident my accounts were not compromised. Regardless, I have recycled the passwords on my accounts and upgraded security practices where possible.
If anything, this episode has reinforced my motivation to add Gitian support to Armory.
This is also a good opportunity to remind community of a few points:
1) When it comes to important announcements, do not trust my forum posts or comments on Github unless they are signed with my offline key (745D 707F BA53 968B DF63 AA8D 8C52 1176 4922 589A).
Day to day troubleshooting and bug discussion do not fall under that scope obviously. Annoucements of this nature do. Releases are also always signed.
2) I will never ask for your private keys or information revealing your identity. The most I ask for are log files, testnet watching-only wallets and blkXXXXX.dat raw blockchain data files.
3) When providing log files, feel free to edit potentially privacy leaking information, however do not simply post a snipet of your choosing unless you are familiar with the method of Armory error logging.
If you have to crop the log file, always prioritize the latest entries.
4) Ultimately the security of the project relies on code reviewers and community testing. Do not hesitate to take part in our testing phases and ask me about change sets. Our IRC channel is a good place to get in touch with me on these topics (no general trouble shooting there please)
5) The trully security oriented users should always at least resort to building the offline signer themselves. Building Armory on Linux is fairly easy, particularly on Debian like distros.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJX9AD7AAoJEIxSEXZJIlia7D8QAMblBFSxTcPRxk/5tN/klMfF
TF41oB4g+EbBU3VbRYiS0+PR0Td58Bk3V+56DQw2ASiTE/JSMrgPzzQnu+1EsTc1
0ZPsYmoCGIKQTccCNkg553TyC717CXN8HsVvNM+TBtGGFvq6Ml2MjQf2xdaCezbd
w2i6szS6AXka+/H/JGhRSi+0SMvRgsks+M6DF+kVwsdBkttRao8I2qPSX/g3LhEA
Nmx1eu5Q2hA9itMrB7HtxITABvOcxb/TdcsKuMa3Ohb/Fi5zVwsBKEKW3NG9IiFg
J/2kSaF4/sOUu6HJc+VYTMpXj25aJ8MMGxhDjqcRdXAwOtyvjL0bzE8thecEt/up
XhJdo94nAf1ycdOky5cm3lLLNpeXuCuiK4E614DXjA2L4IsSu6bq5fzbQxs7b8Iy
pUbdrdqlow6Cj0PHzXXROxVXFqZjHlaIEQSvFesUEu/2XKVOL1m9krGPml8RWH9w
fSaunXvqHIAVoZqgtbqOjckH8LI7ku9u17VqoO12m2HrpZucWTP3v60Kzg0kyDNn
FTtLe1Ze8fTV+JE68P0kca3BwDJA30JjO77aBOQ5r8h2/e+nFdSGM682L7srR2Th
EjVNLD37atvvzmlHEzTJ+zaKC8HESCj82gpEjD5hPXpIzsBYSerl6s0QuKSVyhJg
eYknJwOM/1OmgHriNyBs
=a9RC
-----END PGP SIGNATURE-----