https://en.wikipedia.org/wiki/5_Whys Now for a catch-22.. Why is there no such thing as a stupid question?
https://en.wikipedia.org/wiki/5_Whys Now for a catch-22.. Why is there no such thing as a stupid question?
https://github.com/Dokument/PyBitmessage-Daemon https://bitmessage.org/wiki/Compiling_instructions#Download_and_run_PyBitmessage
sudo apt-get install python openssl git python-qt4 … Download the source code from github: git clone https://github.com/Bitmessage/PyBitmessage $HOME/PyBitmessage Run PyBitmessage: ~/PyBitmessage/src/bitmessagemain.py If you receive a warning that you need to use python 2.7.5 or greater, and have followed the above instructions to upgrade it, your system may be attemping to run PyBitmessage with python 3. Run: python2 ~/PyBitmessage/src/bitmessagemain.py
You can leave python-qt4 out. After your first run of bitmessagemain.py, it will return this:
|
|
PyBitmessage requires PyQt unless you want to run it as a daemon and interact with it using the API. You can download PyQt from http://www.riverbankcomputing.com/software/pyqt/download or by searching Google for ‘PyQt Download’. If you want to run in daemon mode, see https://bitmessage.org/wiki/Daemon
Error message: No module named PyQt4
Then follow these instructions: https://bitmessage.org/wiki/Daemon Result: An interesting POC Vanity address generator (singlethreaded, written in Python, don’t expect much): https://bitmessage.org/forum/index.php?topic=1727.0
http://www.dowdandassociates.com/blog/content/howto-repair-windows-7-install-after-replacing-motherboard/ Successfully replaced an AMD 760G motherboard with a nForce 630a chipset motherboard without having to reinstall Win 7 Ultimate x64 after following these directions. A menu offering to launch the startup repair tools will appear after Windows fails to boot, or can be accessed through the F8 screen before Windows boots.
|
|
A note: you can compile torsocks in a VM like virtualbox and edit /usr/local/etc/torsocks.conf to point to the tor daemon running on the host. In VBox’s NAT networking mode the host can be accessed through the gateway IP.
https://github.com/tannn/TriviaTime/pull/147 Apparently mIRC doesn’t respond to ping messages over a certain length. This is the first part of the problem. According to http://www.irchelp.org/irchelp/rfc/ctcpspec.html
The querying client can then subtract the recieved timestamp from the current time to obtain the delay between clients over the IRC network.
The client sending the ping will do Current Time - Timestamp that it sent out (which is echoed by the target of the ping) , so it can send the ping payload in any format it finds convenient. All we have to do is:
The replying client sends back an identical message inside a notice: 01PING timestamp01
So add this to the top of your Remote script….
|
|
Perfect. A better ping script that will display ping replies in miliseconds: http://www.mircscripts.org/showdoc.php?type=code&id=1102
Update your browser to view this website correctly. Update my browser now