Has the anoncoin.net website been moved, and if so, to where?

It was my own fault for not reading the solution further down the page.

I  have been trying to build anoncoin-qtc on my ubuntu 16.04.5 32-bit computer.
I followed the instructions on the web page to the letter, but they don't work properly.

https://anoncoin.net/How_to_build_Anoncoin_from_source/

anoncoin-cli and anoncoind both build correctly, but anoncoin-qtc fails to build.
During the compiling, I get this error:

checking for QT... no
configure: WARNING: Qt dependencies not found; anoncoin-qt frontend will not be built
checking whether to build Anoncoin Core GUI... no (Qt5)

I don't know what I did wrong. What Qt dependencies do I need to install that are not on the instruction page?

I don't understand the transfer command. How do I send B1TES to another address?

help gives me:

transfer             transfer <mixin_count> <addr_1> <amount_1> [<addr_2> <amount_2> ... <addr_N> <amount_N>] [payment_id] - Transfer <amount_1>,... <amount_N> to <address_1>,... <address_N>, respectively. <mixin_count> is the number of transactions yours is indistinguishable from (from 0 to maximum available)

I have no idea what these parameters mean.

I have mined a few B1TES, and also a few testnet B1TES.
Where can I send them, to test whether sending works correctly?

I was unable to build the testnet wallet. It ended with this error:

/home/user/Documents/Software/testnet-b1t/src/simplewallet/simplewallet.cpp: In member function ‘bool cryptonote::simple_wallet::show_notarizations(const std::vector<std::__cxx11::basic_string<char> >&)’:
/home/user/Documents/Software/testnet-b1t/src/simplewallet/simplewallet.cpp:893:9: error: ‘get_transaction_hash’ is not a member of ‘crypto::hash’
         crypto::hash::get_transaction_hash(pd.m_tx_hash);
         ^
src/CMakeFiles/simplewallet.dir/build.make:86: recipe for target 'src/CMakeFiles/simplewallet.dir/simplewallet/simplewallet.cpp.o' failed
make[3]: *** [src/CMakeFiles/simplewallet.dir/simplewallet/simplewallet.cpp.o] Error 1
make[3]: Leaving directory '/home/user/Documents/Software/testnet-b1t/build/release'
CMakeFiles/Makefile2:565: recipe for target 'src/CMakeFiles/simplewallet.dir/all' failed
make[2]: *** [src/CMakeFiles/simplewallet.dir/all] Error 2
make[2]: Leaving directory '/home/user/Documents/Software/testnet-b1t/build/release'
Makefile:138: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/user/Documents/Software/testnet-b1t/build/release'
Makefile:20: recipe for target 'build-release' failed
make: *** [build-release] Error 2

I have mined 1033 B1TE, but the big guns are beginning to take over, so I'm giving up on this coin for now.

No, my CPU is an old Pentium 4 3.2GHz.

I've now got 274 B1TE.

I'm using an Nvidia GT 610 which gets around 27 H/s!

Would anyone like some BBQCoins?
I have some to give away.

I have updated to version 2.7.3, but it still won't work to import my private keys.

I have updated my Electrum wallet from 2.6.4 to 2.7.2, and it has deleted my wallet.
I created a new one from my seed and have added 5 private keys from my old original Bitcoin wallet, which I have been using for years, using the instructions here:

http://docs.electrum.org/en/latest/faq.html#can-i-import-private-keys-from-other-bitcoin-clients

The process has arrived at a box marked Install Wizard which says Please wait...

Nothing has happened for several hours. How long am I supposed to wait?

Bitmessage is legitimate and safe software, but the OP here is just a troll, and the bitmessage address he gave is not his, but that of [chan] general, and he is encouraging users to spam the channel with their Bitcoin addresses.
No one who posts their Bitcoin address to [chan] general will be sent any Bitcoins. Be told!

I've pretty much stopped using Bitcoin faucets in the last few months due to their low payouts, but I still visit bithits.info every day.
I guess it's just a strange habit that I've gotten into. I keep telling myself that once I've received a payout then I'll stop.
You're probably right, I should have given up ages ago. Maybe after I get paid!

I've been patiently clicking 3 bit hits per day for over a year but I haven't been able to identify any payouts.
In fact, when I check my balance on the page, it doesn't seem to be increasing at all, and sometimes even goes down, and never reaches the payout threshold!

Thank you very much. You have been very helpful to me, and I appreciate what you have done.

PM sent.

That wasn't my intention, as my balance on the 2 imported addresses is 5.15215 mBTC, and after modifying my client as you described, the fee asked for to send it was 1.56 MBTC. I intended to send 3.59215 mBTC, and I don't know where the 5.83952 mBTC came from.

I will take your advice, and attempt sending smaller amounts. I'm not very keen on trying to send with no fee at all, as there is always the risk that the transaction won't get relayed and get stuck in limbo.

@zetaray. Maybe your solution to wait is the best after all, because as micro transactions become more common in the future, fees will inevitably need to be reduced in line with this. At the moment, the Bitcoin system doesn't seem to handle bitdust very well.

As an aside, my Electrum 1.9.8 doesn't seem very stable, and quite often when I start it up it seems to need to re-download all 25MB of the blockchain headers again, then spend over half an hour resynchronizing, with the hard drive thrashing away furiously and using 1GB of RAM before the GUI will display any output!

I've uploaded my saved transaction file to:
http://0bin.net/paste/wsJSxJggZsHdzIf0#S0pW++aLllF3fPy4E1PAOkWp5ZdeRhkrE2NHRe9Lqek=

I'm trusting you on this that this information can't be used to steal my coins!

My saved transaction file is 254.0 kB (254,003 bytes) in size. When I tried to post it here I received the message:
 
The following error or errors occurred while posting this message:
The message exceeds the maximum allowed length (64000 characters).

Just out of interest, my default_wallet file in my .electrum folder is 59.2 MB (59,235,431 bytes).