I went ahead and removed the link to my Google profile from the social media menu at the bottom of each page here, and removed Google+ from the list of tabs I routinely open on my browser.
I used to love email. I still do, except so few people use it any more.
I used to use email almost like people use text messages now. I’d write little, one-topic messages and send them to one (or a few) people. Most of the people I exchanged email with had their email on for most of the day, so they’d get the message in just a few minutes and then be able to respond (or not, if they didn’t want to). If they (or I) didn’t want to be available to be contacted for a period of time, it was easy to put the computer to sleep, or turn off email notifications.
It was also easy to get a little more fancy than that. For example, I often set my email client to check email every hour or every half-hour, instead of the default of every few minutes. I was still able to be responsive to people who sent me email, but I wasn’t constantly interrupted by random notifications from random sources.
That’s half of what I’d like to be able to get my phone to do—batch up alerts, and then give them to me on a schedule that I pick.
The other half is to shut up about telling anybody else about what I’m doing. My email didn’t send any information back to people, except the information I told it to send back. (Sure, my mail server knew when I was connecting and from what IP address, but it kept that information to itself.)
If I was going batch up notifications so that I’d only get them every hour anyway, I’d like my phone to disconnect from the network for the 59 minutes in between. There’s no need for anybody, including Verizon and Google, to know where I am in between.
(Of course if I get my phone out to check something I’d like it to quickly connect to the network so it can do so, but that technology works just fine.)
I could almost do that by just turning my phone off for 59 minutes and then turning it back on, except that obviously doesn’t do the trick unless I carry around another timing device to remind me every hour that I want to turn the phone back on. Plus it’s a lot of fiddling around for the hours in which I don’t receive any notifications (not that there are very many of those).
Admittedly, all kinds of things are made easier by being always connected, such as the ability to prioritize a handful of alerts to come immediately—phone calls, text messages from intimates, tornado warnings, etc. But for me, the mental model of email was vastly preferable to the stupid array of alerts I’ve got now.
In a couple of months the new owners of Flickr are going to delete most of my pictures there, if I don’t pay up for a pro account.
That makes me sad. I’ve used Flickr as my main photo-sharing site since 2004. It was arguably the first social media site, and even though its various owners managed to waste its potential over and over again, it was the best photo-sharing site around—better in every way than Instagram, for example.
I haven’t decided what to do yet.
I could share my photos elsewhere.
I’ve been using the Flickr app to auto-upload my photos to Flickr, which has been very convenient—when a photo doesn’t need much editing, I could just share the photo straight from that auto-upload.
There are two other places that already get my photos auto-uploaded: Google Photo, and (via Syncthing) my home server. Neither of those is a perfect choice.
I’m already more dependent on Google than I’m entirely happy about. (I quit trusting them after they broke Google Reader’s sharing functionality, even before they eliminated the tool completely. Even before that I tried to make sure that I’d be ready to go Google-free at any time if necessary.)
My home server is currently behind some overly restrictive firewall rules that keep it from being useful as a sharing site, although that’s supposed to get fixed. Even then it’ll be a single point of failure, rather under-powered machine with the photos on a single consumer-grade hard drive. It’s just not ready to serve as a production photo-sharing machine, even for a single user.
The most obvious place to share photos from is here at philipbrewer.net, because it’s where I share everything else. The downside is that my photos don’t get auto-uploaded here, and I probably don’t want them to be auto-uploaded here. I can manually upload each picture that I want to share and share it, but it’s not nearly as quick or easy a process as sharing something that’s been auto-uploaded to Flickr.
It works okay, though. Here’s a picture I did that with:
A year and a half ago, my brother gave me a Raspberry Pi 3 as a birthday present, suggesting that I should use it to run my own server.
I used to run my own server. A friend who liked to build such things had built it. It had two ethernet ports, one connected to my cable modem and the other connected to my WiFi router, and it was running OpenBSD (then the most secure OS easily available) and was configured to serve as a firewall.
I used it as a server in other ways. I put an extra disk drive (40 GB!) in it where I could store files that I might want to access from elsewhere. (In particular, when I went to Clarion I copied my latest draft of my current story there each evening, in case of catastrophic computer failure.)
It didn’t require much upkeep, but it required more than none—which turned out to be more than I wanted to devote to it. At some point a serious security flaw was discovered in the OpenBSD release I was running. By then most desktop machines had built-in firewalls as did most routers, and I had Time Machine as a backup solution. It seemed safe to give up my server, and easier than updating it.
In the years since then, the use of cloud services has become ubiquitous, to the point that practically everything I do ends up in the cloud—my photos go to both Flickr and Google. I also use Dropbox (where I have Scrivener stash a backup copy of everything I’m writing) and I stash some amount of my music at both Google and at Amazon.
That’s all great—those services are well backed-up, and the servers are very likely running the latest security patches—but I really like the idea of having my own data on my own machines. But I want that without giving up the advantages of having my data in the cloud. Hence wanting to have my own server.
All that as prequel to my brother coming to visit this past week, and helping me get my Raspberry Pi server up and running.
Once the basic install of Raspbian was up and running, I went ahead and ordered a bit of hardware for it. I got a short ethernet cable to connect it to my router, so that it doesn’t have to do WiFi for basic connectivity (although WiFi and Bluetooth are built in). I also got a slightly more powerful USB power supply for it, mainly because I also got a portable USB hard drive that takes its power from the USB port, meaning that the power needs to be available to the Raspberry Pi. Finally, I got a case for it, so that I don’t just have a naked circuit board sitting on my dresser.
This time the hard drive is 1 TB rather than 40 GB.
For cloud functionality I’m following my brother’s example and running syncthing, which has the advantage of being able to handle being behind a NAT and not having a port exposed to the outside world. I’m running it on my Android phone as well and sharing my photos with a third place: my server. The server then shares them with my desktop machine, so they’re available to use. (That’s how I got the photo above: Taken with the phone and then transferred to the desktop within about a minute.)
I’m still sorting out my sharing strategy. I don’t want to share my whole Music folder with my phone, because it would use all the space there. (I’ll probably end up making a folder with an “essential subset” of my music to share with the phone.) I don’t think I want to share my whole Documents folder on my desktop machine, but I’m not sure yet. For the time being I’m sharing a folder I call “Active writing” with the files I’m currently working on, on the desktop, the server, and my laptop. That way they’ll be available wherever I want to work on them.
Other things are tougher. I’d like to have my own calendar server, but that doesn’t seem easy. I should go back to my post on the google-free option and see what else I was thinking about that I might now be able to implement.
For now, though, I’m pretty happy.
My previous server was rack mount width and maybe four or five inches tall, about the size of a stereo component. This one is maybe 3 inches by 5 inches, rather smaller than the hard drive it’s sitting on.
Over a period of some months I’ve been working to clean up the set of feeds I try to follow. Today I got the unread count down to zero, perhaps for the first time since I started using a feed reader. Certainly for the first time in years.
I did it two ways. First, I did it the legit way, by unsubscribing from feeds that I didn’t actually read. Second, in just a few cases, I did it the cheating way, by just selecting a feed and clicking “mark as read.”
The first permanently reduces the burden of stuff I imagine that I ought to do.
The second just briefly hides the fact that there are some feeds I imagine I want to follow, but that I don’t actually keep up with. Still, I figure this is a test of sorts. Some of those feeds were pretty quiet. Maybe, if they’re not mixed in with all the stuff I’m not keeping up with, they’ll be easy to follow. And, if they’re not, I can always unsubscribe later.
This flurry of feed-pruning activity brought to you by procrastinating on the novel.
I’m in the midst of some tough slogging as I push through the final third. Even after my previous pass through this bit, it is still written a lot like a short story. The scenes are highly compressed, with lots of bits merely referred to. As I reach those scenes, it takes me a while to uncompress them—to see the two or three or four scenes represented by the existing text, and then to compose those scenes, placing them in the right sequence in the story.
I’m actually really enjoying that work, once I get into it, but each new scene is hard to start on—largely because I’m quite proud of the old, compressed versions. The uncompression work feels like taking a finely crafted miniature that I spent days painting, cutting it up into pieces, sticking each piece in the middle of a big canvas, and then trying to paint a new picture that incorporates that bit of the miniature. (It would probably be better to just do the necessary new scene “inspired” by the old scene, and I’ve done some of that, but that turns out to have problems as well.)
In any event, progress continues. It’s just hard.
As I go to click the “publish” button on this post, my unread feed count stands at zero.
Here’s an idea for an app that someone should write. I call it MeetAt. The code should be pretty straightforward—you could easily enough build it on the guts of any location-aware app.
The user interface is simple. You see a short of list of common contacts (but probably also access to the whole contact list). You pick one or more contacts to whom you’ll send a message in the form of “Hey, let’s meet at [location]!”
Next you see a short list of common locations—home, work, the coffee shop, the library . . . Ideally the list would piggyback on some already existing list of locations that you care about, but in any case it would be configurable.
That’s all pretty obvious, but here’s the (slightly) clever bit: At the top of the list would be a button for “somewhere in between,” and when you clicked it you’d get a list of locations that are in between where you are and where your contact is. (This is assuming that you’ve previously approved sharing location information with one another via this app.)
The easiest implementation of that would be simply to draw a line, find the midpoint, and then do a Google location look-up which will present you with a list of named places near that location. (Or, if you want to be Google-free, something based on Open Street Map or something else.
You could, however, enhance that in a lot of ways. For example, your device could detect if one of you is on foot or on a bicycle or in a car, and could suggest locations that could be reached in about the same amount of time by both parties, given relative travel speeds. If one of you is on a bus, it could identify which upcoming bus stop would be the closest walk for the person on foot.
The app would also generate an expected meeting time, based on whatever travel modes it was expecting people to use.
The result would be a message sent that says, “Let’s met at [location] in [n] minutes,” to which the other person could reply “Okay” with a single click. With a few more clicks, the other person could propose an alternative location or time.
Personally, I’d use an app like that all the time.
Google gave me a link to my year in pictures. And they have a lot of my pictures, because they have all the pictures I took with my phone. (But not the pictures I took with my camera, which is what I use if I’m planning to take pictures.)
However, the video that Google produced is hilarious, because way over half the pictures I took with my phone were taken to document the condition of the various apartments we moved into.
Whatever Google’s algorithm for selecting pictures is, it’s is pretty good—many of the pictures they selected are the better ones. So half the pictures Google shows me are pretty good pictures of Jackie and Barbara and Rosie and fall color and interesting things we did.
But about half are pictures of damaged carpets, damaged tiles, damaged plaster, damaged trim, damaged closet doors, etc. Here’s one:
But, now that I think about it, maybe that’s fair. Maybe that’s a pretty good representation of my year.
I’m so glad we’re done moving.
I’ve experimented with various alternatives to Google Reader for quite a while now. I used The Old Reader for a while, and then Hive Reader for a while. Both had limitations. (Hive is still in beta, and isn’t quite ready for prime time. TOR is closer, but had various issues, probably the biggest being that it doesn’t get feeds updated promptly enough.)
I had earlier tried using tt-rss, which also isn’t quite there yet, but has a different set of issues.
It requires a server. Steve had tried to cobble together an instance that ran on the server where we host our websites. It had just almost worked, but kept bumping up into the limits of running as a cron job, rather than a daemon. It eventually had several bad days in a row (which we later traced to an unrelated heavy load on the server), and we gave up.
Now Steve has installed an actual server machine in his house, and is running a tt-rss instance there, and has made me an account on it.
Running on an (essentially) dedicated server with a (reasonably) high-speed connection to the internet, it’s now doing a fine job of keeping all my feeds up to date. I’m having some minor user interface issues, but nothing that would keep me from using it as my rss reader for the foreseeable future.
So, I have officially switched over. You can follow the interesting stuff I share via a feed from that site, and have updated the “interesting stuff” item in my sidebar to draw from that feed.
Zen Habits has a fresh post up on becoming Google-free. It’s a pretty good look at the key resources that Google provides—Gmail, Google Docs, Google Reader, Google Calendar, Picasa, etc.—and for each one provides Leo’s choice for a replacement, along with mentioning a few other alternatives.
On the one hand, this is just the sort of thing I’m a bit too prone to worry about. For me, security, privacy, and reliability are right up there with functionality. On the other hand, it had scarcely crossed my mind that I’m so reliant on Google that becoming Google-free was an important issue. So, seeing Leo’s article prompted me to give it some thought.
To me, the more fundamental issue is choosing to keep your data on your own hardware or to keep it in the cloud.
It used to be that the cloud was a loser on all four issues (security, privacy, reliability, functionality). In just the past few years, the cloud has made great strides in the latter two. I haven’t seen a careful analysis, but my sense now is that the cloud is about as reliable as your own hardware, albeit with different failure modes (less chance of a bad disk drive losing a bunch of data, more chance of the provider deprecating the tool or simply going bust). Functionality is a different kind of question—all you care about is whether the tool provides the functionality you need—but my sense again is that tools like Google Docs do fine at providing the most important functionality.
On issues of security and privacy, though, it seems to me that the cloud can never win. Well, maybe in one narrow sense: Servers in the cloud can be professionally managed with security in mind, so there’s a better chance that security patches will be applied promptly and less chance that they’ll be configured in an insecure way out of carelessness or ignorance. Except for that, though, all the cloud can offer is an unenforceable promise of security and privacy—and it rarely offers even that.
Because of that, I’ve always ended up choosing to keep mission-critical work on my own hardware. I use various cloud services, but they’re all in some way either publishing or else secondary.
Where what I’m doing is publishing (such as this blog, my account on Flickr, my account on Twitter, and so on), the privacy issues are moot—I’m explicitly making the stuff public. I still care about security, but my security interests are closely aligned with the provider’s security interests, so I feel reasonably comfortable relying on the provider to get security right.
All my uses of cloud-provided tools are non-critical. I have a Gmail account, but it’s a backup account for use when my main email account is unavailable for some reason. I have a Google Docs account, but I only use it occasionally to view a Word document or make a graph with the spreadsheet facility. I don’t use Google Calendar (I use iCal). The one Google tool that I’d really miss if it disappeared is Google Reader which I use every day, but even losing that wouldn’t be a catastrophe. I could go back to reading blogs on the websites themselves (!) until I picked out a new RSS feed reader. My latest backup of my subscriptions was really old (I just now grabbed a current one), but I’d be able to recreate the important ones easily enough.
The upshot is that going Google-free seems to be a non-issue to me. I could do it in five minutes and scarcely feel the loss. I’m glad to have been prompted to think about it, though.