Remove your GPS location EXIF geotags from IOS videos before sharing them

Suppose you want to sell an item online, and post photos and videos of the item online. And to protect yourself you plan to meet a potential buyer at a public place such as a Big Box Store parking lot. That’s more or less pointless if you link your ad to your photos and videos but they were taken at home, if they are geotagged, since you’ve now shared your home address with anyone on the internet. And geotagging is on by default for many people.

For Mac users, with photos, it is relatively simple to remove the geotag data right within Preview. (Open the photo, under Tools show Inspector, click on the ‘i’ icon, click on GPS, then click ‘remove location information’.)

However, for videos, the Mac offers no such shortcut to remove the location information on a video you took… a lamentable oversight IMO.

The free FFMPEG command line app will do the trick, and is easy to install.

Assuming you have Homebrew installed (Google it, if not):

brew install ffmpeg

Once installed, run it for each video with the options
-map 0 -map_metadata -1 -c copy

I copy the videos into a desktop folder such as ‘nogps’ then run ffmpeg for each video in that folder:

cd ~/Desktop/nogps

ffmpeg -i -map 0 -map_metadata -1 -c copy

ffmpeg -i -map 0 -map_metadata -1 -c copy

IMO fatal flaws – OrchestraOne practice management for therapists

  • OrchestraOne touts a flat $20/month cost but (literally) hides huge extra costs on their pricing page that makes it 10x – 20x more expensive even for modest practices. Their “3% for payment processing and $5 per insurance claim submission” is not unreasonable, but it IS (literally) hidden on their Pricing page in a way that I consider outright misleading. see for yourself I assumed it was an oversight, but a month later they still hide that pricing on their pricing page.

  • No self-pay under client control. Hard to believe, but they don’t support clients managing their own credit card info.

    • In order for a client to make a copayment via credit card, the client must give you their card info to store, then you have to initiate the charge. Better systems provide a way (such as base don Stripe Checkout) that lets the client click a link, enter their payment info for that one transaction, and optionally store the info at Stripe for next time.)
  • Literally zero support for any kind of group sessions, much less the full ability to book arbitrary client for a Tuesday night drop-in support groups.

  • No data export feature. They say it is coming, but a database-centric product without data export on Day One is a red flag.

  • Feature-poor. It’s a young product, with IMO far too many shortcomings to be viable for a real practice. Their feature requests page includes such basics as:

    • no support for patient intake/history forms in client portal
    • no ability to sign notes
    • no ability for patient to opt out of SMS reminders
    • no ability for clients to upload docs to their portal (prior lab results for example)
    • no client search by phone or email

IMO fatal flaws – Theranest practice management for therapists

When evaluating practice management software for therapists, Theranest gets thumbs down for the following reason:

  • Holds your data hostage. If you decide to use Theranest a while, they seem to want to make it as painful as possible to take your marbles (data) if you close your account.
    • Will not export client notes as text. (A printout or PDF is useless when it comes time to import data into a new system. And you know that Theranest knows that.)
    • Will not export client session history as text, not even just dates of past or future sessions.
    • Will not export client payments as text.
  • Literally impossible to schedule support group meetings where the attendees change from meeting to meeting.

Whether or not support group scheduling is important to your practice, as a matter of principle and practicality you should, in my opinion. reject ANY application that doe snot offer complete data portability.

Why IMO using FreshSales CRM could be hazardous to your business

I really wanted to like FreshSales, or at least be able to tolerate it until they made improvements over time. I think very highly of their helpdesk FreshDesk, and a year ago they got some heavy-hitter funding. Yet their FreshSales product management appears to be asleep at the wheel.

Setting aside all the CRM nice-to-have bells and whistles (like deal funnel management) the CRM sine qua non certainly includes:

  1. Let sales people send/receive business emails.

  2. Let sales people make/receive business phone calls.

As of mid-May 2017 FreshSales is IMO literally hazardous to your business on both counts for the following reasons:

1. Using it in the USA for business email seems to me like a huge CAN-SPAM fine just waiting to happen. How anyone could offer a bulk-email campaign capability without built-in support for opt-out links is puzzling. (Google “can-spam fines” sometime.)

  • There is no opt-out URL capability eg, no built-in support for inserting a URL into outgoing email that allows the recipient to opt-out of future emails from your FreshSales account.

  • IMO simply adding text like “reply to unsubscribe” is not the answer because if you miss such an unsubscribe request for any reason, for example if your spam blocker ate the unsubscribe request, or that email goes to your salesperson who doesn’t handle it correctly, it is my (layperson) understanding you have violated CAN-SPAM.

  • It gets much worse. When you edit a lead you have the ability to (manually) set a “don’t disturb” flag. And their API docs sound like that will prevent that person from being emailed: do_not_disturb (boolean) The lead have enabled do not disturb or unsubscribed to your mails”. However, if a sales person starts to compose an email to that lead, that field is not even displayed by default, and so if the sales person proceeds and hits send… yep, the email gets sent anyway. Ditto bulk emails, unless you manually add a filter on the “do not disturb” setting. (FreshSales support confirmed this.)

2. Inbound phone call voicemail greetings are Text-to-Speech, worse than some cheap answering machine. Which creates a terrible impression for callers.

  • FreshDesk uses Twilio to offer integrated voice functionality. That should be a good thing, Twilio is awesome, powerful, and flexible.

  • Twilio makes it trivially simple to use a greeting that is a recording instead of text-to-speech, you simply point the voicemail handler to an audio file that can be anywhere on the internet.

  • So even if FreshSales engineers somehow got stuck on how to let people record or upload a greeting, there is quite literally no excuse for not allowing you to upload your own greeting to your own website or S3 and point FreshSales to your URL. (Having used Twilio in-depth myself, I can tell you it’s likely a 5 minute change to their code.)

  • To add insult to injury, their FreshDesk product includes both a simple IVR setup capability and recorded greetings, so leaving those capabilities out of FreshSales as of mid-May 2017 is just plain bizarre.

  • A serious flaw with both FreshDesk and FreshSales is they silently discard your messages that are not at least 5-7 seconds. So if a customer calls and says “I’m really upset call me back asap” you will NOT get that message. Nor will you get the message that says “Whitepaper looks great, please call Tim back!” An incredibly stupid design decision by someone who fails to understand that getting 100 1-second hangup messages is preferable to throwing away 1 message from a pissed-off customer or a terse prospect.

I have no doubt they will get a viable version at some point, but our own assessment was to steer clear until phone calls and emails are handled with at least nominal competency.

“We’re not UPS.”

“We’re not UPS.” Truer words have never been spoken by a US Post Office Employee.

That is what she replied, verbatim, when I trekked to the office to pickup a package and said “I’m confused why your carrier said they could not deliver this package Friday due to ‘no access’ to my porch when I got a UPS package the same day, and a Fedex package the day before, and my porch has no ice, the entire sidewalk leading up to my front door has no ice, wanna see a picture I just took of the front of my house?”

They tried once, Friday. Didn’t leave a notice I had a package. Didn’t include a notice in my daily mail today or yesterday. So, had I not looked up the tracking number then called TODAY, they would have returned my Pu-ehr tea. To Yunnan, China. Where it was shipped from.

The tea, which I sip as I write this, is utterly remarkable. Thanks to son Nate for turning me onto it

A Dlink Camera iPhone/iPad workaround for error 0.70 …

On the whole I cannot recommend Dlink cameras, they are just too flaky.

After upgrading to Mac OSX Sierra there does not seem to be a way to view the live video when accessing the camera directly on the local network. The camera webpage guides you to a plugin that is obsolete, and the Dlink support website refers you to yet another plugin which also does not work. And Sierra has been out for months.

Another case in point is the in ability to use the latest iPhone or iPad app (v3.6.7) with cellular connection to view your cameras remotely with the latest camera firmware, latest DLink app, latest IOS.

There is a years-old thread on the issue with entries as recently as last month at

The issue I and other get when connecting to a remote camera via cellular connection it displays “could not connect to the device … Error 0.70_0_2_7_70”

It works if using a WiFi connection, but not cellular.

On a hunch, I tried using my cellular connection in combination with a VPN (Private Internet Access) and it worked fine on both my iPhone 6S and my iPad Air, thereby bypassing any Carrier-to-Dlink internet route,

Which seems pretty clear that Dlink is not playing nicely with traffic from cellular carriers.

Solving [DEPRECATION] last_comment is deprecated when upgrading to rails 4.2.6

We ran into the deprecation warning above when we upgraded to Rails 4.2.6.

The issue was an older version of rspec-rails 3.3.3 and upgrading to 3.4.2 removed the warning.

To resolve all dependencies we edited our Gemfile to:

gem 'rspec-rails' , '3.4.2'
gem "rspec-activemodel-mocks" #, "~> 1.0.1"
gem "rspec-mocks", "~> 3.4.0"

then ran:
bundle update rspec-rails rspec-mocks accept_values_for

Microsoft still not afraid to bait and switch IMO

Sometimes the young ‘uns wonder why old-timers like me despise Microsoft with such passion. The unlucky ones become Microsoft customers and find out for themselves. Like this missive, proving to me that after all these years Microsoft is still unafraid to bait and switch:

“We want to let you know about some upcoming changes to OneDrive. On July 27, 2016, the amount of storage that comes with OneDrive will change from 15 GB to 5 GB. We are also discontinuing the 15 GB camera roll bonus. … We want to apologize for any inconvenience they may cause you.”

An example of when ‘digital’ means ‘inferior’ and ‘wasteful’

I have to wonder how many millions of “partly used” batteries get needlessly tossed simply because of digital (LED) flashlights.

For the kids in the audience who don’t know about ‘bulbs’… as a battery starts to get low, an incandescent bulb simply gets dimmer. At some point, it’s too dim to be useful, so you replace the battery.

Digital, on the other hand is either “on” or “off”… there is no “dim” middle ground.

So, not hypothetically speaking, suppose you are riding your bike through a looooong 1.66 mile pitch-black train tunnel on the gorgeous Hiawatha trail near the Montana/Idaho border, and about half-way your LED flashlight’s batteries hit the roughly 60% full mark. Do the LEDs get dim? No. They go out.

Naturally, you have a spare flashlight and you use that.

But when you’re done, you toss a still-half-full set of batteries you mistakenly assume are dead because your digital flashlight told you so.