Known issues

Please submit HTML user interface related bug reports here.

• User creation may take some time on slow computers due to the “proof-of-work” required. This is normal and it shouldn’t take more than 5 minutes in worst case. Then, after user is created, the browser is redirected to the profile configuration screen. At this point, however, the last phase of user registration may take much more time to complete because the transaction must be accepted into the block chain of the entire network. On average, a new block is generated every 10 minutes but the exact time cannot be predicted, so it might take anything from like one minute to half an hour. Before this new block is produced, other peers will refuse to accept the profile “save” action or any new posts. Please be patient.
• Usually users are redirected to the Network status page whenever twisterd experiences connectivity problems. However, if one insists on creating a new username with network down, this may result in an incomplete username creation, that is, the key pair is created in local wallet but not sent to other peers. Currently there is no UI option to fix this. The solution is to use the following command to force transaction propagation:

./twisterd sendnewusertransaction my_user_name

• Backup your private key. Backup your private key. Backup your private key. You can do this either by copying the 52-character secret or the twisterwallet.dat file.
• Support for encrypted wallets still exists in code base, but this feature has never been tested.
• Private messages are saved to the file named user_data. Because the messages you send are only encrypted with the recipient’s key, you won’t see these messages in other computers sharing the same account. Unless, of course, this file is copied to the other computer.
• If file user_data is lost, both sent and received private messages will disappear from the interface. It is possible to force twisterd to reprocess the received messages from all followed users and populate this file again with plain-text (decrypted) messages with the command:

./twisterd rescandirectmsgs my_user_name

• Network status page is your friend, use it to try to debug connectivity problems. twister needs both registration (blockchain) and DHT networks to have reachable nodes and will try to populate IP address from one to the other. The bootstrap is provided by three DNS servers. Alternatively, known peers (other computers running twister) may also be used for bootstrapping purposes.
• In case Network status page still reports “Connections: 0″ after a while try manually re-adding DNS seeds “seed.twister.net.co”, “seed2.twister.net.co” or “seed3.twister.net.co”.
• Besides block synchronization which may be checked at Network page, torrent download of posts may prevent your timeline from displaying correctly. You may check posts download status at the Following page.
• While best efforts have been made trying to fix torrent bugs caused by twister’s modifications (basically we have a “growing torrent” file now) it seems that some corner case might still be problematic, preventing proper synchronization. Symptom: you compare two computers running twister and they report different number of pieces for a given user in the “Following” page. Then you make sure you have good network connectivity but your posts still don’t propagate. Ok, please be patient because sooner or later we will fix this! Restarting the deamon may help (or you may also try to debug this if you are a programmer).
• A bug has been seen (and hopefully fixed) which caused ~/.twister/debug.log to grow ridiculously large (like 20GB). If you miss your free space you may want to check this file size. During initialization twisterd should shrink debug.log whenever it gets larger than 10MB.
• Followers numbers are unreliable/not working. Actually there is no easy of figuring out who follow you except by checking all users. It should be possible, however, to find how many users are connected to your swarm (a sort of “online followers”). I tried using certain internal variable of libtorrent expecting to obtain this information but unfortunately I was wrong. This is still an open issue.
• Sometimes the block chain database may get corrupt, preventing twisterd from starting. You should first try the -reindex flag to see if it recovers. If it still refused to start, the solution is to completely erase the block database. So, unless you feel attached to it by some reason, erase the directories ~/.twister/blocks and ~/.twister/chainstate and let twisterd download it all over again from other peers.