I remain a WhatsApp curmodgeon

My six days in Barcelona for MWC had me using one app far more than usual: WhatsApp. But while I often delight in seeing people route their communications out from under the control of incumbent telecom operators, every time somebody asked me to message or call them in that Meta-owned app, I felt a little more grumpy.

That’s because WhatsApp continues to lack a feature found on any 1970s Trimline phone or on a turn-of-the-century, five-line-display cell phone: You cannot text or call a random set of digits unless you first let this app ingest your entire contacts list.

My phone's screen shows the Android system permissions dialog asking if WhatsApp should have access to my contacts, with MWC attendees in the background.

As WhatsApp says in two of the more shameful dialogs around: “To make a call, allow WhatsApp access to your contacts” and “To help you message friends and family on WhatsApp, allow WhatsApp access to your contacts.”

I got tired years ago of apps making sweeping demands for my data and don’t see any reason for contacts upload to be a prerequisite to pinging somebody I just met and may never run into again, so I keep declining that request.

WhatsApp’s FAQ item about contact upload makes a respectable argument for its stewardship of this data, saying it doesn’t collect non-phone-number contact details and deletes the numbers of non-WhatsApp-using people after saving a cryptographic hash of their digits for future cross-referencing should they join later.

But WhatsApp’s parent firm has racked up quite a list of privacy violations, some of which led to the Federal Trade Commission hitting it with a $5 billion fine in 2019 that still stands as a record penalty.

And that WhatsApp FAQ item doesn’t even try to answer why without contacts permission, the app won’t let you punch in any random phone number to start a chat or call. Or how if you revoke that permission, it will stop showing the names of contacts–a creepy move that in 2019 Fast Company’s Michael Grothaus called “one of the most manipulative things Facebook does with WhatsApp.”

In the U.S., being a WhatsApp contacts-access refusenik isn’t so bad, because most people still use carrier texting services. But in the rest of the world, historically higher carrier prices for messaging have made WhatsApp far more widely used. And at MWC that led to some awkward moments.

Most of the time, I could socially engineer my way out of them by asking my new acuaintance to message me from their copy of WhatsApp, at which point I could reply from my copy. One MWC attendee then pointed me to the option to have WhatsApp show a QR code that other people can scan to add you to their contacts lists.

And after coming home, I learned of the click-to-chat option in which you can type in a wa.me Web address in your phone’s browser that ends with a contact’s number (no dashes or spaces) to have the app open a chat thread with that individual.

It’s good, I guess, that WhatsApp provides workarounds for its own demand for the data of people who may have zero interest in seeing their numbers get uploaded even briefly. It would be better if WhatsApp would show a little humility and end this gropey, growth-hacking nonsense.

Advertisement

CES 2022 travel-tech report: a new phone and a renewed laptop

Uncharacteristically light attendance at CES this week allowed me to pack uncharacteristically light. With so many tech-news sites canceling plans to send journalists to the Consumer Technology Association’s annual gathering, I knew I wouldn’t need my traditional CES accessory of a travel power strip to free up outlets in any crowded press room.

I also opted not to pack any of the WiFi hotspots I had sitting on my desk from the last update of Wirecutter’s guide to same. Even in the likely event of the show’s WiFi being its usual inadequate self, I figured I had sufficient backup bandwidth in the form of the new Pixel 5a in my pocket, the expanded mobile-hotspot quota on my account, and the T-Mobile 5G network my previous phone couldn’t use.

Photo shows my HP Spectre x360 laptop sitting on the wood floor of my home office, on top of which sit my CES badge, the laptop's charger, a USB-C cable to charge the phone, a USB-to-Ethernet adapter, headphones and my Pixel 5a phone.

My other smart move before heading out to Vegas was replacing my late-2017 HP laptop’s battery with an aftermarket unit, a bit of laptop surgery I did in October. All of this helped make CES much less of a gadget-abuse scenario in my return to covering it in-person after last year’s distanced, digital-only conference.

The Google Pixel 5a, the only new device in my messenger bag, acquitted itself especially well. On a good day, its battery can run well into the next afternoon, and even at CES–where I did rely frequently on the phone’s mobile-hotspot feature to get my laptop online–I never saw this Android device’s battery get into the under-33% state that would get me nervous. My charging the phone at lunch happened out of habit, not necessity.

I also quickly grew to appreciate how the 5a’s wide-angle lens helped capture some of the bigger exhibits on and off the show floor. The sole quibble I can think of: The phone reported that it restarted overnight Friday morning, and I’d like to know what caused that crash.

My HP Spectre x360, meanwhile, was one of the oldest items in my bag but felt much newer with that replacement battery. It was nice to sit down to watch a panel and not need a spot next to a power outlet. And for whatever reason, this computer ran much more reliably than it had at CES two years ago, without any mysterious reboots sometimes interrupted by boot-device-not-found errors.

Lower CES attendance, estimated by CTA Friday at “well over 40,000,” did not banish CES bandwidth struggles. My laptop did not always connect to conference WiFi networks–have I mentioned that Windows 10’s “Can’t connect to this network” is not a helpful error message?–but all three press rooms had abundant Ethernet cables. The $10 and change I spent on a USB-to-Ethernet adapter in 2012 has turned out to be an exceptional deal.

As before, I took all of my notes in Evernote, but this time the app generated a few note conflicts when I switched from phone to laptop and back. If I could click or tap a “sync now” button before each device switch, I would–but Evernote removed that bit of UI out of a belief that its automatic sync is now reliable enough to make it obsolete.

The other app I leaned on heavily during my time at CES was the conference’s own mobile app. I hadn’t bothered with that in previous years, but learning that CTA had hired Web Summit to provide this event’s digital platform made me want to try it. Unsurprisingly, the CES app looks and works like the Web Summit and Collision apps, so I didn’t have much to figure out.

As at those other conferences, I leaned on this app to manage my schedule while ignoring in-app connection requests in favor of the kind of networking impossible at last year’s CES: masked-face-to-masked-face conversations that ended with an exchange of business cards.

More pandemic-recovery milestones: Northeast Corridor travel, a journalism conference

This week brought me back to two things I’ve missed badly since February of 2020: hanging out with other journalists at a conference in another city, and taking the train to and from that destination.

The Online News Assocation’s decision to host its first IRL gathering since 2019 in Philadelphia made those things possible. And by scheduling Insights as a two-day event, it also made it surprisingly affordable compared to this journalism group’s other events–aside from the 2017 conference in D.C., at which even my badge was free courtesy of my panel proposal getting accepted.

Photo shows the footings of the footings railroad bridge in the Susquehanna River as seen from the current bridge, with the sun obscured by fog and part of the overhead catenary visible.

There was no question I was going to take Amtrak to Philly and back, only one of which trains to book. I decided to head up Thursday morning, at the cost of having to wake up early and miss any day-before networking but with the advantage of only needing to take my messenger bag, with a change of clothes stuffed into it alongside my laptop. That then led me to realize that the fees tacked on to every Airbnb reservation nearby would make my usual money-saving business-travel tactic more expensive than just staying at the conference hotel.

That worked out even better than I expected after my productive ride on the 7:05 a.m. Northeast Regional out of Union Station–in the Quiet Car, of course, with the only distraction being looking at scenery I hadn’t glimpsed in 18 months. I got to the hotel before 9:30 a.m., and it had a room ready when I checked in. So not only could I unpack immediately, the 11 a.m. video podcast that I hadn’t been able to schedule for another day could take place in a quiet spot with good lighting.

The conference itself was great. I learned a bunch of things about my job and how to do it better, and being in the room (even if some speakers were not) allowed me to focus on the talks instead of having every other browser tab and app on my screen ready to divert my attention. I took copious notes–which I wrote up for my Patreon readers, since their contributions covered my conference costs–and live-tweeted panels like in the Before Times. And Insights had enough breaks for me to file two stories, one that I’d mostly finished on the train up and another I banged out in an hour.

And yes, it was lovely if at times weird to commune with fellow journalists. The organizers had color-coded wristbands at the registration table that we could wear to signal our openness to face-to-face interaction: the green one I picked meant I was okay with handshakes and hugs, red would signal no touching, and yellow would mean no more than elbow bumps, if I remember correctly.

Insights required everybody to submit proof of vaccination and wear masks anyway… except that the reception Friday evening took place indoors, and quite a few attendees visited one bar or another Thursday night. I think my risk was about as low as imaginable for any gathering–certainly lower than at other events I’ve attended over the last few months–but it does exist.

The conference ended with enough free time for me to wander around Center City for a bit before boarding the 7:10 p.m. Acela back to D.C. I had to look up how long it had been since I’d last taken the Amtrak train that’s become a label for a certain Northeast Corridor demographic, and the answer was 616 days.

SXSW 2013 by the numbers

Modern science provides an extraordinary number of ways to quantify one’s participation in the South By Southwest Interactive festival that wrapped up Tuesday (its sleep debt is still with me, to judge from the hour-long nap I just woke up from). Here are a few:

  • SXSW 2013 badgeSteps taken, as recorded by a Jawbone Up: 98,610 steps, adding up to 51.64 miles. This includes mileage at home Friday morning but leaves out my walk to the bus that took me to the airport Wednesday morning.
  • Tweets sent while in Austin: 178, excluding retweets of other people’s thoughts but including tweets about non-SXSW news.
  • Data usage on my phone from March 8 through March 13: 739 MB, 192 MB of which came from tethering my laptop to my phone.
  • Food truck check-ins on Foursquare: seven
  • Bar check-ins on Foursquare: 14. (Some of those stops were mainly for food. Don’t judge me!)
  • SXSW sessions attended, or in one case watched from an overflow room: 11. Sadly enough, this is considered a pretty good showing in some circles. There are least as many that I seriously regret missing.
  • Business cards collected: 33. Yup, still waiting to see some app make this printed product obsolete.
  • Business cards handed out: not enough to exhaust my supply, fortunately.

After the jump, a Flickr slideshow from the festivities…

Continue reading