Here’s my Web-services budget

The annual exercise of adding up my business expenses so I can plug those totals into my taxes gave me an excuse to do an extra and overdue round of math: calculating how much I spend a year on various Web services to do my job.

The result turned out to be higher than I thought–even though I left out such non-interactive services as this domain-name registration ($25 for two years) and having it mapped to this blog ($13 a year). But in looking over these costs, I’m also not sure I could do much about them.

Google One

Yes, I pay Google for my e-mail–the work account hosted there overran its 15 gigabytes of free storage a few years ago. I now pay $19.99 a year for 100 GB. That’s a reasonable price, especially compared to the $1.99 monthly rate I was first offered, and that I took too long to drop in favor of the newer, cheaper yearly plan.

Microsoft Office 365

Getting a Windows laptop let me to opting for Microsoft’s cloud-storage service, mainly as a cheap backup and synchronization option. The $69.99 annual cost also lets me put Microsoft Office on one computer, but I’ve been using the free, open-source LibreOffice suite for so long, I have yet to install Office on my HP. Oops.

Evernote Premium

This is my second-longest-running subscription–I’ve been paying for the premium version of my note-taking app since 2015. Over that time, the cost has increased from $45 to $69.99. That’s made me think about dropping this and switching to Microsoft’s OneNote. But even though Microsoft owns LinkedIn, it’s Evernote that not only scans business cards but checks LinkedIn to fill in contact info for each person.

Flickr Pro

I’ve been paying for extra storage at this photo-sharing site since late 2011–back when the free version of Flickr offered a punitively-limited storage quota. This cost, too, has increased from $44.95 for two years to $49.99 a year. But now that Yahoo has sold the site to the photography hub SmugMug, the free tier once again requires serious compromises. And $50 a year doesn’t seem that bad, not when I’m supporting an indie-Web property instead of giving still more time to Facebook or Google.

Private Internet Access

I signed up for this virtual-private-network service two years ago at a discounted rate of $59.95 for two years, courtesy of a deal offered at Techdirt. Absent that discount, I’d pay $69.95, so I will reassess my options when this runs out in a few months. Not paying for a VPN service, however, is not an option; how else am I supposed to keep up on American news when I’m in Europe?

LastPass Premium

I decided to pay for the full-feature version of this password manager last year, and I’m already reconsidering that. Three reasons why: The free version of LastPass remains great, the premium version implements U2F two-step verification in a particularly inflexible way, and the company announced last month that the cost of Premium will increase from $24 a year to $36.

Combined and with multi-year costs annualized, all of these services added up to $258.96 last year. I suspect this total compares favorably to what we spend on news and entertainment subscriptions–but that’s not math I care to do right now.

Advertisements

Sharing stories from Apple News considered harmful

Last Tuesday, Google delivered some news that open-Web advocates have long awaited: Stories posted in the speedy, Google-developed Accelerated Mobile Pages format and served up via its even-faster caching service won’t zap onto the screens of mobile devices at google.com addresses, not the domain name of their publisher.

The avoidable but common facet of the AMP experience has bothered me since my early encounters with Google’s attempt to make the mobile Web less janky–it led the explainer I wrote for Yahoo two years ago. Google is now moving to fix the problem it helped create, which is welcome news in any publishing format.

(Specifically, Google will adopt a new page-packaging standard to preserve site domain names. In last Tuesday’s post, AMP project tech lead Malte Ubl says we should start seeing the results on our phones in the second half of this year.)

This, however, leaves another address-eating annoyance on the mobile Web: Apple News. This iOS app is a pleasant way to browse and read stories; like the open-source AMP, this proprietary format cuts out the cruft that can clog mobile reading.

But when you tap its “Share” button, Apple News serves up an apple.news address. And unlike even Googled-up AMP addresses, this one offers no hint after the domain name of where you’ll go.

The text Apple News pre-populates in a tweet or Facebook update–the story headline, an em-dash, and then the publication name–does. But on Twitter and Facebook, many people decide to replace that text with their own words, leaving users to guess what’s behind that apple.news address.

Apple appears to be doing this to ensure that other iOS users can read the story you shared in Apple News as well–its developer documentation even lists a story’s canonical address as a “not required” bit of metadata. But in the context of a button that can share a story on the public Web, that’s an absurd inversion of priorities.

Apple could fix this by coding Apple News to share a story’s original address when available, perhaps with an identifier to tell iOS devices to open it in Apple News. But knowing this company, I wouldn’t expect that any sooner than the arrival of a reborn Mac mini at my neighborhood’s Apple Store.

Instead, you’ll have to solve this problem yourself. If you’re sharing a story from Apple News, keep some reference to the publisher in your description. If that would cramp your social-media style, please take a moment to tap the share sheet’s “Open in Safari” button–then share the story from that browser, from whence it will have its real address.

Weekly output: blog hosts, QAM, Kojo Nnamdi, iPad rumors, Web chat

This week involved more real-time interaction with readers than usual.

2/12/2012: Tip: For a personal Web page, keep it simple, USA Today

First a reader e-mailed to ask about the easiest way to host a blog under a personal domain name; then, between my filing this piece and USAT posting it, two friends asked me the same question. I guess the timing was right for the topic. The column also offers a tip that emerged from a comment thread here: You can recharge an iPad over any random charger with a USB port, not just a higher-powered model labeled as iPad-compatible.

2/14/2012: Qualms Over QAM, CEA Digital Dialogue

Here I discuss the cable industry’s proposal to encrypt the local, public, educational and government channels that “QAM” (Quadrature Amplitude Modulation) tuners in digital TVs can receive without a box. Would you trade that–cable operators say encrypting QAM will free new customers from having to wait for the cable guy to show up–for the Federal Communications Commission making its “AllVid” proposal for box-free reception a standard for both cable and satellite? For further reading: The National Cable & Telecommunications Association’s Paul Rodriguez explains why cable operators don’t like the “traps” they now use to control access, while venture capitalist Fred Wilson argues for keeping clear QAM and providing the broadcast channels for free.

2/14/2012: Our Love/Hate Relationship with Email, The Kojo Nnamdi Show

I discussed ways to tame an overloaded inbox with WAMU host Kojo Nnamdi and two other guests, etiquette author Anna Post and IBM social-computing evangelist Luis Suarez. You hear more of me in the second half of the show, after Suarez’s call-in segment ended. (Tip: You can speak in paragraphs on public radio, but they have to be newspaper paragraphs.)

2/17/2012: The Only ‘iPad 3’ Story You Need To Read, Discovery News

The headline I wrote may oversell this story a bit–but, really, the feature set on the next iPad should not be that hard to figure out. And if this post isn’t the only next-iPad piece you elect to read, it’s certainly the only one I plan to write, just as I only wrote one next-iPhone post last year.

2/17/2012: Living a Connected Life (Web chat), CEA Digital Dialogue

My second monthly chat for CEA started a little slow, but I wound up getting enough questions from readers to stick around for an extra 15 minutes. One query I got confirmed my decision to devote next week’s CEA post to the upcoming reallocation of some spectrum from TV to wireless data mandated by this week’s payroll tax-cut bill. Another may yield an item for my USA Today column: how to connect an ’80s-vintage Nintendo NES (no, really) to an HDTV.