[…] blogged about surprising bits of the C++ object model before, and I’m back with […]

[…] Mozilla code has provided and promoted a PodZero function that misuses memset this way. So when I built with gcc 8.0 recently (I usually […]

[…] allows implementations to treat Strings beginning with a 0 character as octal values.”), but it will take a while to change browser behaviors (even if I’m sure that nobody does use octals intentionally in parseInt()). And Internet […]

In reply to Fenn.

My assumption is people not thru-hiking, looking for advice, will want sections of trail that are either easier with some payoff, or have a good payoff for the effort. Hence my suggesting avoiding sections without payoff, or very strenuous sections without similar payoff. But of course as I said in the last paragraph, people should do with this information whatever they want, to hike wherever they want.

In reply to John Krystof.

As it turns out — and there being a bit of difference doesn’t surprise me — Snoqualmie Pass to Stevens Pass took me a bit less time than the five days you suggest. I left Snoqualmie Pass at ~16:50 on September 10, and I was at Stevens Pass by ~14:15 on September 13, so maybe three days total. 7.17mi from a late start the first day (camping by Ridge Lake), 22.30mi the second day (camping shortly after the fragile area surrounding a couple lakes), 27.59mi the third day (to Glacier Lake), then 13.59mi the fourth day to Stevens Pass. Syncing up pace with a thru-hiker isn’t easy!

Thanks! I was always woundering why stuff like {some} = Object.assign({}) didnt work untill I read this.

In reply to John Krystof.

I’ll keep you in mind! Of course at that point I might be doing high-20s days at a consistent 3mi/h pace, and syncing could be an issue. Or maybe schedules don’t match up. Or I don’t know. Anyway, miles to go before then, tons of other challenges to address first. When I’m a while lot closer, we can talk. 🙂 Gotta not die in the Sierras first, at a minimum!

In reply to Zéfling.

Yeah, if I were posting from a computer and not a phone I’d surely have fixed this myself.

In reply to Alan Jenkins.

A tagged feed wouldn’t help, because I’d tag everything that way as a matter of course. I strongly dislike a Planet where its participants self-censor what they share, and I get only a narrow slice of their lives that way. The long tradition of planets such as Planet GNOME and others is that you get the entire lives of the participants, to the extent they chose. It is very helpful to get this – people’s lives outside Mozilla are very relevant to understanding them, relating to them, and being able to recognize why they might argue for particular proposals for how Mozilla should work. Narrowing that, harms that ability greatly. I refuse to participate in that narrowing. (It also leaves a very bad taste in my mouth that the narrowing, as I’ve observed it, seems to have been viewpoint based in response to particular expressed views, not on neutral grounds, giving it an even greater tinge of censorship.)

It’s also definitely worth noting that I know of a significant number of Mozillians who are interested in my progress, even if technically there’s no specific Mozilla hook, who absolutely justify posting this stuff to that broad audience.

No, the real solution is just figuring out something to ensure images in posts are shrunk. Maybe the WordPress web version provides the necessary controls and is at least that minimally usable on a mobile device.

I’ve seen some people use tags to limit which posts they send to a Planet.

Presumably that’s what’s described as using a “tagged feed” here: https://wiki.mozilla.org/Planet_Mozilla

(It says this is supposed to be required now, for new people who want to be on Planet Mozilla).

Google turned up the wiki for Planet Openstack, which has some instructions for WordPress: https://wiki.openstack.org/wiki/AddingYourBlog#Separating_Content