So it has been quite a while since I have published the BabyPingViewer app on the app store. The reception was great, yet there is one recurring question that people raise: Since BabyPing has modified their way to create a password for the admin user, now depending on the specific model of the camera, there is no more a standard password that you can use. Which is great, but which leaves you with the issue to detect the password if you want to use another app than the one that comes with the camera. Here’s a short description how you can get to the password. Read more…
Ok, this has annoyed many people out there, including me: Apple found it clever to remove the pinch gesture on the icon view of the Finder window. For what ever reason, but it was annoying me enough to find a solution. Read more…
I’ve recently upgraded to MacOS 10.10, a.k.a. Yosemite. Here’s a measurement of my wired throughput to my server. Before, I got a maximum of about 75 MB/sec on large files. This is a nice improvement…
When connecting with Lync on Yosemite, and your primary system language is not English (how could that potentially be…), Lync up to 14.0.9 will cycle the login process. Microsoft has acknowledge the problem and provided for a fix.
Same procedure as last year, Ms Sophie? I’ve had another round of checking Apple’s Thermal Paste, this time on two MacBook Air’s I’ve bought about a year ago. And, just like before, same problem. Read more…
Three Nighthawk X6‘s arrived. Bricked one hacking it misconfiguring DD-WRT; serial cable debricks it. Here’s some throughput that brings it to precisely half my wired network connection (measured OTA from my 2013 Macbook Air to my server which is wired using Gigabit LAN / Cat7 to the routers, measured to 943 Mbit/s):
mnott-laptop:~ mnott$ iperf -c monster -P 10 -w 1000k
------------------------------------------------------------
Client connecting to 192.168.1.10, TCP port 5001
TCP window size: 257 KByte (WARNING: requested 1000 KByte)
------------------------------------------------------------
[ 13] local 192.168.1.151 port 53571 connected with 192.168.1.10 port 5001
[ 4] local 192.168.1.151 port 53562 connected with 192.168.1.10 port 5001
[ 5] local 192.168.1.151 port 53563 connected with 192.168.1.10 port 5001
[ 6] local 192.168.1.151 port 53564 connected with 192.168.1.10 port 5001
[ 7] local 192.168.1.151 port 53565 connected with 192.168.1.10 port 5001
[ 9] local 192.168.1.151 port 53567 connected with 192.168.1.10 port 5001
[ 8] local 192.168.1.151 port 53566 connected with 192.168.1.10 port 5001
[ 12] local 192.168.1.151 port 53570 connected with 192.168.1.10 port 5001
[ 10] local 192.168.1.151 port 53568 connected with 192.168.1.10 port 5001
[ 11] local 192.168.1.151 port 53569 connected with 192.168.1.10 port 5001
[ ID] Interval Transfer Bandwidth
[ 13] 0.0-10.0 sec 61.0 MBytes 51.1 Mbits/sec
[ 5] 0.0-10.0 sec 61.0 MBytes 51.0 Mbits/sec
[ 9] 0.0-10.0 sec 61.0 MBytes 51.0 Mbits/sec
[ 8] 0.0-10.0 sec 61.0 MBytes 51.1 Mbits/sec
[ 12] 0.0-10.0 sec 60.8 MBytes 50.9 Mbits/sec
[ 10] 0.0-10.0 sec 60.6 MBytes 50.8 Mbits/sec
[ 11] 0.0-10.0 sec 60.6 MBytes 50.8 Mbits/sec
[ 4] 0.0-10.0 sec 47.9 MBytes 40.0 Mbits/sec
[ 6] 0.0-10.0 sec 61.0 MBytes 51.0 Mbits/sec
[ 7] 0.0-10.0 sec 47.9 MBytes 40.0 Mbits/sec
[SUM] 0.0-10.0 sec 583 MBytes 487 Mbits/sec
I’ve been doing some investigation on speed reading, here’s there result.
Have shown this to my little daughter. She really likes string theory, so I’ve got that going for me, which is nice…
Yesterday’s post regarding the adoption of Perl and RegEx in early childhood has raised some questions as per to which degree we should expose our kids to potentially questionable content.
