Writer: science fiction and fantasy, personal finance, and Esperanto
In fact, I’ve gone ahead and set up a Lychee instance at my site. I’ve just started populating it, but there’s a few recent photos there:
https://images.philipbrewer.net/
I’d be very interested to hear if people can see it when they’re not logged in as me….
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:
Eating low-carb has been a useful tactic for me—when I watch my carbs, my allergy symptoms are greatly eased—but that doesn’t change the more fundamental truth of Michael Pollan’s basic rules: Eat food. Not too much. Mostly plants.
That first rule is the most important, and would be very nearly enough all by itself, if followed strictly. Probably the way in which “low-carb” helps me as a tactic is that it eliminates whole categories of “foods” which fall short of being food, but which were in my diet for so long, and which I enjoy so much, that I’m otherwise inclined to eat them anyway.
By “food,” I’m referring to industrially produced food-like substances. And, of course, it’s not so simple as that. Twinkies and Doritos are out at the far end of the “ultra-processed” spectrum, but what about the near end? I used to eat a lot of children’s breakfast cereals—which with all the fiber removed and large amounts of sugar added are clearly ultra-processed. But what about more grown up breakfast cereals—processed, but made from whole grains, maybe with a bit of fruit or nuts added? What about granola?
Really it’s just about impossible to eat food without processing. A green salad is pretty minimally processed, but I like my lettuce picked, washed, cut or shredded into bite-sized pieces, and drizzled with a bit of olive oil and vinegar (each of those latter two somewhat processed in its own right). Maybe if you get down on the ground and chomp down on a live lettuce plant you could say you were eating unprocessed food.
I started thinking about this when I saw a pair of lists—processed foods and unprocessed foods—in “Nutrition Action,” a publication which aims to be evidence-based, but which has some striking idées fixes, particularly as relates to low-fat, as illustrated in these lists: generally unremarkable, except that they bizarrely included 2% milk as an “unprocessed” food.
Now, raw milk from a single cow is arguably unprocessed. Mix it with the milk of another hundred cows, pasteurize it, and homogenize it and I think it’s already a bit of a stretch to call it just minimally processed. But to then remove half the milk fat and call that “unprocessed” to me is a bridge too far.
With ragweed season in full swing, my allergy symptoms have clicked into high gear. I’ve belatedly gotten back on very low-carb diet and am already (after just one day) feeling much better.
This time I’m trying to keep more of an “eat food” perspective on the whole thing. I don’t want to fear fruits, just because they’ve got carbs. (I am staying away from fruit juice, at least until I’m sure I’ve got the inflammation fully back under control.) I’m being even more cautious of grains, but not hesitating to include a little rice. I haven’t eaten any lentils yet, but I won’t hesitate to include them either.
I don’t want to say it’s not the carbs, because it is. But with a very few exceptions (like honey and potatoes) it’s only with ultra processing that it becomes at all appealing to eat excess carbs. If I eat food, I’m not going to have to worry about the carbs.
Here’s a photo of Jackie minimally processing some okra for the gumbo pictured at the top of this post
Jackie counts the number of lilly blossoms every morning, and provides that day’s #lillycount.
On my Flickr feed I shared several pictures of the rocky canyon paths that Jackie and I hiked in Utah with the tag “vitamin texture.” Katy Bowman uses the term to talk about how always walking on flat, level paths fails to provide some of the “movement nutrients” our feet, ankles, calves, knees, and other body parts need to be healthy and capable.
There’s not much in the way of rocky terrain here in Central Illinois (although there are some forest paths with enough exposed roots to produce a reasonable degree of ruggedness). There’s also not much in the way of ordinary hills unless you’re willing to drive for at least half an hour, but I do have one reasonably convenient hill: the highest point in the county is just a couple of miles away—a man-made hill in Colbert Park.
Jackie and I walked there a couple of days ago and climbed up and down the hill a couple of times. The image above is the view from the top of the hill, and here’s an image of Jackie walking up:
It’s not like the climbs in the canyons:
But it’s steep enough to provide a good calf stretch.
I’ve thought to use the Colbert Park hill for running hill repeats, but it’s just far enough that I’m generally not up for running there, running hill repeats, and then running home. (I think I did that one time, about two years ago.) I could drive to the park, but that just seems too lame. Still, my running is coming along okay this spring, so maybe I’ll be in shape to do hill repeats in the middle of a five-mile run pretty soon.
I used to play on the monkey bars all the time when I was a kid. My mom encouraged it. She knew it built upper-body strength, and that the ability to traverse monkey bars was an important capability for any human. (She could traverse monkey bars herself, when I was a boy.)
I quit doing the monkey bars, probably when I was college age, and quickly lost the capability. Then for three decades would have been afraid to even try, because I’d definitely have hurt myself. A few years ago I wanted to regain that capability, so I started looking for monkey bars to practice on, and found that they’ve gotten quite scarce. Many playgrounds don’t have them at all.
Winfield Village has a playground in every quad, but the only playground with any sort of monkey bars is the big one close to the office, and it has a rather strange curving monkey bar that over the course of 5 rungs makes a 90° turn—a particularly challenging version. (Like most these days, this one has weird triangular bars hanging from a single support, rather than a series of rungs supported on both sides.)
The reason for both the near disappearance and the switch to triangular bars seems to be that monkey bars are “dangerous.” Many playground safety experts recommend that monkey bars be excluded from playgrounds altogether, and I think the weird shape is designed to make them harder to climb on top of, in the hopes that kids would then not do so.
I spent a chunk of yesterday afternoon at an “alignment play day” with folks from CU Movement (and kids), getting some hanging and balancing and barefoot walking on various textures. One thing I did was traverse the monkey bars at Clark Park in Champaign—an old-style set of monkey bars, rather like the ones I remember as a kid.
One of the kids in our group—small enough that it was a challenge to reach the next bar, and at a height that the experts would no doubt claim was “too high” for a kid of that size—did the monkey bars, and then immediately wanted to climb on top of them. He asked for help getting on top, which his mom declined to provide—except that she pointed out that one of the supporting poles could probably provide the necessary foot purchase for him to get on top on his own. And he did manage to find two ways to get up there. Having gotten up there, he decided against traversing the top of the monkey bars, and simply swung back down under them.
A new school of thought is emerging (finally!) that “dangerous” playground equipment offers valuable opportunities for kids to do exactly what this boy did: evaluate a hazard and decide how much risk was appropriate. The only way to learn to make that sort of evaluation is to actually practice it. Making playgrounds so safe that children cannot hurt themselves reduces their opportunity to develop a good sense for what is safe and what is dangerous, and what is and is not within their capability.
It has also made it a lot harder for me to find a set of monkey bars to practice on.
I crossed the monkey bars three times in the afternoon, but I forgot to attempt my next big trick: Cross from one end to the other, turn around (without putting my feet down) and cross back again.
I’ll do that next time.
Goslings. The open mouth on the goose on the right was because he was ready to start hissing at me for getting too close. I didn’t try to get any closer.
The reason that a well-regulated militia appealed to the founding fathers was that they hoped it would eliminate the need for a standing army.
If you had the whole body of young adult men armed and trained, it was hoped you could raise an army very quickly in case of need. If that were true, Congress could insist that the standing army be run down to just a cadre of specialists and officers. Then, in the event that you needed an army—because you were invaded, or needed to invade someone else—you could mobilize (i.e. draft) the militia to fill the ranks with soldiers.
The founders knew perfectly well that a government with a standing army could not be resisted by the people, even if the people were armed. A standing army was always going to be more disciplined, more highly trained, and better equipped than a militia could possibly be.
So, the purpose of the militia was to eliminate the need for a standing army. If you could make a militia work that way—quickly go from a bare cadre to a fully mobilized army simply by calling up the militia—then you’d be in a position where Congress could insist that the the army in fact be a bare cadre, meaning that neither presidents nor generals could use the army until Congress actually raised one.
It’s an appealing idea, particularly to someone like me who is very doubtful about trusting presidents or generals. Sadly, the evidence is pretty good that it doesn’t work.
This was clear even before the sorts of modern, high-tech weapons and other equipment that take extensive training to learn how to use, and then nearly constant on-going training to preserve the capability. It took five years to go from a 16,000-man army to a 1,000,000-man army during the civil war. The ramp up for WW I was quicker but also smaller—manpower grew by 16 times in two years rather than 62 times in five years, but that was from a much larger base—basically, a smallish standing army, not merely a cadre waiting to be filled out.
The experience of the U.S., at least as far back as the civil war, is that fielding an army by mobilizing a militia simply can’t happen fast enough to respond to an enemy with a standing army. (The experiences of Switzerland mobilizing to resist a possible Nazi invasion and Finland mobilizing against the Soviet Union at around the same time are interesting, but do not I think make the contrary case.)
Given all that, I’d have to say that a militia is pretty much obsolete, and has been for a couple of centuries at least.
Watching the sunrise out my study window.
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.
