Tuesday, August 9, 2016

Best fonts for eBooks

The Best Fonts for Ebook Readers, According to Book and Typeface Designers


Friday, August 5, 2016

LastPass JS Exploit

Yet another event that vindicates my paranoia and persistence in sticking with offline KeePass

LastPass Happily Forfeits Passwords to Simple Javascript http://feedproxy.google.com/~r/hackaday/LgoM/~3/MaAlZfRKEm0/

Thursday, July 14, 2016

Advice for night owls in dealing with the normal work grind

There is actually really good advice in this!

Six Ways Night Owls Can Thrive in a Nine-to-Five Work World http://lifehacker.com/six-ways-night-owls-can-thrive-in-a-nine-to-five-work-w-1783537377

Sunday, June 26, 2016

Explore investment opportunities

SeedInvest: Explore investment opportunities

 (public equity crowdfounding)

Found via Wikipedia - looks interesting

Tuesday, June 21, 2016

OnePlus 2 - Rooting and Multi-Window Mode

OnePlus 2 Rooting:
OnePlus 2 - Enabling Multi-Window Mode / True Multi-tasking:
  • After using the OnePlus 2 for more than 5 minutes, I quickly realized just how big my new phone was. Coming from the Moto G, this phone feels enormous, and to be realistic, it is pretty big, even when compared to competitors. Thus, it felt really wasteful to have this huge screen and be only using it for one simple app at a time. I wanted to see if I could multitask, and specifically with multi-window mode.
  • If you are rooted, this is actually incredibly easy.
  • Guide: http://forum.xda-developers.com/android/general/guide-enable-multi-window-mode-android-t3121483
    • My steps were even simpler; I simply installed the ROM Toolbox app (free), which let me edit my build.prop file in seconds to change the user type from "user" to "userdebug", then I rebooted, went into develop options, and turned on "multi-window".

  • So far, most apps work fine with it, and it is great for using Gmail on one side and some other thing on another.

Monday, June 20, 2016

June 2016 - Smartphone Research and Comparison

These are my quick notes / comparison table for shopping for a new Android smartphone. I was only looking at phones with 3GB of RAM or more, since my irritation with my current phone was how the small amount of RAM (1GB, it is a Moto G 1st gen) caused pretty much every app to crash or behave erroneously when being pulled from the background.

Major Pros
Major Cons
Astounding price to spec ratio, plus 4165mAh battery
Company has horrible rep, dev support, BAD signal support
Price is sort of a red flag and is in line with consensus to avoid - IGNORE
AMOLED (pretty), nice design
Not much, just stiff competition, no LTE band 12, NOT AVAILABLE ANYWHERE
Good budget phone, but not much else.
AMOLED (pretty),  good specs
Mixed reviews, no LTE band 12
Considering, but steep jump from $200 range to $300+ -- tied with Nexus 6
Trustworthy, pure android, Moto
Rumors of heating issues, not out for a bit, pricey, NO COMPASS?!
Probably worth jumping off the Moto ship, considering the high price and mixed initial reviews - seems like Nexus 6 would actually be better
AMOLED (pretty), STOCK, great reviews
Dated (2014), no fingerprint
Seems like Moto X Pure is much better bang for buck
Big battery (4100 mAh)
No LTE band 12, Dated
No compelling reason to get instead of competitors - IGNORE

No LTE band 12
Nothing impressive - IGNORE
Full LTE support (including band 12), Removable battery,
No fingerprint

Full LTE support (including band 12), water protection
No fingerprint, IPS instead of AMOLED
$300 (don't be misled, DON’T BUY ON AMAZON)
Full LTE support, 64GB OF MEMORY, 4GB OF RAM!!!!!!
It's not moto. That's it. The only con. Type-C USB is a little annoying, but it is the future anyways.
Full LTE, AMOLED, Fast charge, NFC, 6GB OF RAM!
If you want the newest and greatest, this is the BEST bang for your buck. If you like to upgrade frequently, OnePlus 2 might be a better buy until this drops in price.

I ended up going with the OnePlus 2, despite the OnePlus 3 just being released, since I didn't want to pay over $300 for a smartphone that I am probably going to upgrade out of anyways in a year or two. So far, I have been extremely satisfied with my OnePlus 2! I'll have another post in a bit about what I did to make the phone even better right out of the box.

Honestly, I don't get the hate towards the OnePlus brand of phones. I had never heard of them before, because they are rarely mentioned online (if you bring up the brand on most common forums, you get hushed really quickly). From my perspective, it seems like everyone should love them: they are really close to stock android, easy to root, the spec/feature to price ratio is INCREDIBLE, they are good looking, and they (so far) have been OK with rolling out updates (my OnePlus 2 immediately upgraded to Marshmallow after I turned it on).

Monday, May 30, 2016

Kolor Panotour - VR Mistakes - 5.30.2016

After enabling VR for a tour that I recently made in Kolor Panotour I noticed that several hotspots were missing in the tour when using the VR mode, but were there when using the normal viewing mode. I quickly stumbled upon this thread on the official Krpano forum that made me think maybe my hotspots were not being set as "distorted". I was quickly to able to verify that this wasn't the case, by examining the special VR XML file that PanoTour creates in the output folder - the distorted="true" flag was indeed correctly set on hotspots.

However, in inspecting the VR XML file, I found that not only were the missing hotspots not present in the VR XML, neither were the entire panoramas that they were linking to! I was thoroughly perplexed and spent quite a while screwing around with various settings to no avail. Finally, I found my answer and facepalmed myself I may now have a blister; I missed the fact that PanoTour only supports FULL 360x180 scenes for VR - as per this extremely relevant note from a page on their site about VR mode:

  • Only full 360°x180° scenes are kept.
    • If there are no 360x180° scenes, then the tour will be empty (blank screen).
    • Any spots pointing to non 360x180° scenes will be removed.

From < http://www.kolor.com/wiki-en/action/view/Panotour_-_Notions_-_VR_Mode >

Whew! Easy fix! On scenes were the source file is not a full 360x180, just tell the program that it is (simply change the "Horizontal" to "360" and "Vertical" to "180" when you have a scene selected > Settings (sidebar) > Projection > Input Field of View"). After I did this to all my scenes, all the missing hotspots reappeared in VR mode as well as the full scenes they are linked to.

The only way this really affects output is now you can't have cropped panoramas where, if for whatever reason you wanted to exclude the very bottom and top of your source file from showing (perhaps because it isn't there to start with), you can't. If it simply isn't there, the program simply fills in the space with black (I'm sure you have seen this before in virtual tours before, where instead of gracefully masking out a tripod, the editor has simply left a big gaping black hole.