Old Posts

For a long time, my website maintenance has been taking what is actually broken and making it functional again, rather than worrying too much about content. With spare time and a functioning site, I’ve been able to go through my WordPress posts and discover some things. I had several posts, going all the way back to 2011 which were “Uncategorized.” All of them have homes in multiple categories now.

But even more fascinating, I had some posts which were written but never actually published. 31 Drafts, in fact, some of them dating back to 2008. Since I like those things to be seen, here are the seventeen that had enough content to publish, without having to scroll back through years and years of posts.

Some Random Photo Favorites was a post from June 2011 when I was spending the summer hosting Quito Quest teams. It had some great photos which were on my public Flickr page, but apparently I had some trouble with the formatting and although the content was all there, this post never came out of my drafts folder. It is posted now.

I had a Test post from the Apple Store which I did not actually publish, and instead just took a screenshot. But it was entertaining to see that one of the multi-pronged tests I did was logging into my own site and typing a post on an iPad- the first time I had ever even held one. This would have been around May 2o11, because I ended up purchasing an original iPad to blog in Ecuador in summer 2011, planning to sell it on eBay when I got home to the United States. I obviously got attached, because I have never not owned an iPad since. There was a similar draft of a test written from an iPod Touch, which I deleted.

Tolerance, the First Amendment, and Islam was something I wrote out of a sense of anger toward my former Representative, and on which I assume my 2010 self chose not to click “Publish”out of that same sense of anger. Well, 8 years is enough of a cooling-off period, and I think 2010 Danny was pretty smart. I made no edits to it before I made it public today.

Glimpse into an Unexpected Evening was a fun night with the Casa G boys in May 2010.

New Writing Project was about an article I started for Youth World about a mentoring program at AAI. Interestingly enough eight years later, Dani, who was a high school student in the program at the time, now runs Quito Quest, so she’s effectively my boss when I come back to host a Quito Quest team.

I Promise I Can Feed Myself probably speaks for itself. Post from 2010, which I’m guessing was never published because I intended to add photos of other food to it as a went. I guess this post will be unfinished art, but it is public now.

Communication was about our weekend Quito Quest staff scouting trip to Riobamba, Ecuador in January 2010.

Not Atypically Not Ready was about the craziness before my Christmas travel back to the US in December 2009.

Christmas Party to Remember was about my experience with dehydration during the 2009 Youth World Staff Christmas Party.

Emaus Mission Team was about a group of Quiteños and Gringos who journeyed to a ministry site in the jungle in October 2009.

First Office Days was a quick update on the beginning of “real life” in Quito after I finished language school.

On Writing was a post with some musings after an interesting conversation with a guest I was hosting while he was discerning whether to join the Youth World team.

Preparations? What Are Those? was really an admission of how completely unprepared I was to get on a plane and be in a foreign country for a year.

T-Minus 3 was about my last couple of days in North Carolina and my prep before I moved to Quito for a year.

Table for Twelve is more unfinished art about Maundy Thursday 2009.

Afternoon at CFC was about a brief ministry experience in March 2009.

Sermonitos from October 2008.

Travel Prep 2018

March is here again, and with it come plane tickets and a host of technological projects.

First, my ancient iPhone 4s finally gave out. It has a hardware error stemming from an issue with the WiFi antenna. I cannot connect to WiFi at all, which means I cannot disconnect the phone from Find My iPhone, which means I cannot even reset it to factory defaults. Maybe I will get around to finding a SIM card with a data connection so I can fix at least some of these issues, but for the moment, it is simply out of commission. Enter, “new” iPhone.

My iPhone 4s was the first iPhone I ever purchased, and I purchased it Factory Unlocked (which was not a common, nor inexpensive thing back then) and it was with me through three US cell carriers until I finally switched back to Verizon and CDMA service, and a new iPhone 5s. The 4s then permanently became my Ecuadorian phone, replacing a refurbished 3GS I had purchased in the meantime, and I would just keep my Ecuadorian SIM card in it and add a few dollars to my prepaid account every time I was in the country. And the 4s outlasted not just that old 3GS, but the 5s as well. That phone’s battery exploded when I was in California in 2016 and I upgraded to a then-band new iPhone 7. So it has been the Ecuadorian 4s and the North American 7 until today, when my refurbished iPhone 6 arrived.

One of the things I have learned with all these generations of phones is that SIM cards keep getting smaller. At one time, I had what we referred to as the Nokia “Brick” phone (those indestructible candybar phones that we still give to our Youth World interns in 2018 because the cockroaches will be calling each other on them after the nuclear war). That phone had what most people would call a full-size SIM card in it (although that’s technically a “Mini” SIM). I purchased a SIM card cutter way back in the day to slice it down to fit in my 4s, which required a Micro SIM. And that card just got sliced down again with a new cutter into a Nano SIM  for the iPhone 6.

Restored from the 4s Ecuaphone backup, it will be all ready to use when I step off the plane. Or at least it would be if I ever managed to have any saldo left when I finish hosting a team. Hopefully I’ll remember to turn off my cellular data instead of blowing through all my saldo before the team even arrives, which I may have done… two years in a row. My Quito Quest pareja, Caroline, gets a little frustrated with this phenomenon when all outgoing phone calls and texts have to be on her phone until we remember to send someone to the Farmacia to recharge my saldo. I could solve all of this by just using one of the Nokia phones. But what can I say? I am spoiled.

The other tech project has been updating my website. I generally renew my hosting and domain registration in February, so that has been done for a couple of weeks, but parts of the site have been broken for a long time. The DNS records were a little wonky, probably since I switched hosting providers years ago, or possibly since I added Google Apps. At any rate, if you got here by putting a “www” in front of my domain name, then my update worked.

The site was also running a WordPress theme that was at bare minimum 5 years old, and had survived heavy coding updates I did to it throughout that time. The bulk of those coding edits were to incorporate a head image randomizer, the thing that makes the top image change every time you visit the site, click “Refresh,” or go to another page within the site. This option is now something that’s built into the WordPress software. I was just doing it before it was cool, thanks to some PHP script found and then reworked by Mike Turner. The result of all this was that as the underlying software has changed and modernized, my theme would not even display my blog posts on the front page anymore. Obviously, you’re reading this, so I’ve corrected that error. For the moment, I have done this mainly by changing to a less archaic WordPress theme. It will probably change again as I get annoyed at searching for post dates off to the side. But at the moment, I am simply happy that there is no quest required to access my content, or even my site anymore.

Springtime Web Maintenance

I so rarely check look at my own website when I’m not in Ecuador, that the most common occurrence for the last several years is for me to find it totally broken when I do bother to check on it. So if you notice the face-lift, that’s why things are different. I logged on last night, and lo and behold, the front page simply wouldn’t load.

I chalk it up to laziness on my part in updating. Somebody found a flaw in WordPress and exploited it so that the theme I was running got messed up. I switched themes, and most of the content is back. But it doesn’t look like “me” around here at the moment.

I tell you that to tell you this. Once the school year starts and I return to a normal schedule, my plan is to begin a youth ministry blog, and split my website into two sections. One for my Ecuador writings, and one for my musings on the oddities of working with students and getting a paycheck from Jesus. So that face-lift will continue, but hopefully that’s a reason for me to actually create content here more often. And keep my website updated. And not get hacked. Again.

Keep checking back.

Hacking (the good kind)

I’m one of the people nerdy enough to have ready the “Mark Zuckerberg manifesto” in the Facebook IPO filing today. In case you weren’t, he mentioned the negative connotation that exists of the word “hacking” and how really it just refers to problem-solving and building that needs to be quick and tends to be inelegant, but gets the job done nonetheless.  And twice in the last week I’ve referred to myself as a hacker out of pride for fixing a problem, not because I’ve broken into a system to which I shouldn’t have had access1. So I’m going to brag about them here. Partly because of that pride. But mostly because I agree with Zuckerberg’s ideas about sharing information, and this might help some of the less-computer-savvy people out there get into a wireless router one day, and because I had a very specific problem with iTunes/iOS/AppleTV/Airplay/ and Windows 7 tonight that hardly anyone else has written about.

The Router

We were skiing at Wintergreen last week, staying in houses up there for the long weekend, and there was a router in the room. The TV was getting it’s cable access through this router, and there was an RJ45 connection on the back (the plug for an ethernet/network cable) and it had blinking lights for internet and wireless, so it would clearly give me access to the internet on my iPad.When I looked up available connections, the router was even named with our room number to make it clearly identifiable. However, it was secured, and the password was not included in our guest information, and was not printed on the router itself. (Helpful hint if you are ever trying to do this: many times the default password is clearly marked on the router itself, or is the serial number of the route. In my case I was not so lucky).  Fortunately I also had a laptop with me and while I don’t carry a network cable around with me anymore, there was one in a kitchen drawer.

I hooked up to the router with my computer via the network cable, and went to my browser (in this case Firefox), typing in 192.168.0.1 in the address bar. There are other addresses that it could have been, but I got lucky with my first try and Motorola uses this as their default IP address for their routers. The browser opened up the page for the router, but it required another login. While any computer physically plugged into the router can access it, this second layer of security is designed to keep out people like me who are not the actual owners of the router. Fortunately, it does absolutely no good if you leave the router login set to the defaults. I guessed the user name to be “admin” and the password to be “password” and then “root” and then left it blank, as these are all typical defaults. No dice. But since I had internet access via the network cable, I opened a new tab, did a Google search for the Motorola router default login. Turns out in this case, I was right about the user name, and the password should have been my next guess: “motorola.” Bingo, now I had access.

It took a little looking around before I found the right tab. The Motorola interface was unfamiliar to me, but once I clicked through to the correct page for wireless settings, I found the place to change the wireless access password. Now, I could have simply changed it so I would know it. Or I could have disabled the security altogether. But I didn’t want to make a change that I might either forget to change back, or be unable to change back. So I did something even simpler. I unchecked the box under the password that gives the option to “hide characters.” The password popped up, I called out the 10 digits to my roommates, and all four of us were online on iPhones/iPads in another 60 seconds. Without calling the front desk, without making any changes the owners would notice.

The Apple TV

I have an Apple TV. I got it to play my iTunes content (collected because I wanted to watch current shows that I couldn’t otherwise get in Ecuador and because I enjoy taking advantage of my legal right to a digital backup copy of the physical discs I own) on an actual TV, and realized a few days later that I could also use it as an Airplay speaker. I like to be able to wander around and have my music following me, so I take advantage of this all the time to play the same music on my computer and the Apple TV. But I noticed today that when I attempted this for the first time after updating to iTunes 10.5, it didn’t work. I spent a few minutes diagnosing the problem. My computer (running Windows 7) had access to the local network and to the internet. My Apple TV had access also to the internet and strangely enough to the rest of the network including my computer and iTunes content. It would still stream content from my computer wirelessly over the network when I gave it that command from the remote control. But it would simply not work for the specific task of being an Airplay speaker when selected from my computer. These two tasks seemed so similar I could not think why it would not work, especially since iTunes was recognizing it as an Airplay device and an option for my available speakers, but giving me an error message anyway.

The error message told me it was “unknown” and gave me a number of “-15000,” so I Googled something like “iTunes Apple TV error -15000.”  Nothing helpful. I tried it without the minus sign, since this is an old-school modifier for search engine results, but still nothing helpful. So then I added some more useful information. My search ended up including “iTunes 10” “Windows 7” “Apple TV” “Airplay” and “unknown error” and several other things. But after scanning the URLs of the search hits so that I could ignore all the useless official Apple support pages, I stumbled upon somebody with the exact same problem on a PC (the solution for similar problems on a Mac was interesting, and involved the way Macs implement IPv6, but didn’t help me) who published his fix for it.

It turns out the cause is the instructions that iTunes gives to Windows apparently can get mixed up during an update from an older version of the software. That’s what happened here, with the instructions to Windows Firewall about the UDP port being incorrect (the UDP port is basically the place and the method by which iTunes communicates in real-time with Airplay devices, in this case the Apple TV). I had to open the Advanced Settings of Windows Firewall and found the instruction set for iTunes within the “Inbound Rules.” There were three separate ones, so I checked out the properties of each one. The first two were about TCP ports (not used for Airplay because they are based on getting all the information in order, rather than getting the information continuously, for a streaming application) so I accessed the third option and checked the box for “Private” networks. Apparently Windows Firewall was only applying the rule (“allow”) to communication from the Apple TV if it came in over a network connection designated as “Public,”  which my home network is definitely not labelled2.

Immediately after the Firewall-related windows were OK‘ed and closed, I clicked “multiple speakers”  and then “Apple TV” in iTunes, a viola, music from two sets of speakers.

Two problems solved. Nothing insanely hard, and technically no unauthorized access to other systems, but hacking nonetheless.

1I’m not entirely sure I was intended to have access to the wireless internet in the room where we stayed at Wintergreen. There was nothing anywhere telling us the password. This is why I resorted to hacking before calling the front desk and risking being told that the internet was only for the owners and that’s why they didn’t print the network key anywhere. But when there’s a router and a network cable that I can easily access, I interpret that as permission.

2If you tried to do to my router what I did to the one at Wintergreen, you would fail miserably because the router password has been changed from the default. I’d recommend doing this if you don’t want someone like me accessing the  network at your beach/mountain cottage. I still could have done it, though. I’d just had to have left a trace by using the physical reset button on the router. And I was desperate enough for communication with the outside world that I would have done it. We’d switched around rooms, so Alison’s name was on the list instead of mine anyway.

Still here

Some of you might have noticed last week that my website completely went down for about 48 hours. To oversimplify things, it was a miscommunication between myself and my hosting provider. Everything’s back online now, but a side effect has been that for some reason I still can’t access my server (my site, my e-mail, anything) from home. I’m still trying to figure that one out, and if anybody’s got any (intelligent) input, I’ll be glad to accept it.

For now though, I’ll just have to bring all my writing down here to the office to post it. As a brief update in the meantime, though, I’m finishing up two articles for the YW mailing list, been hanging out a lot with Casa G the last couple days (adventures to be posted, I assure you) and am preparing for by far the biggest excitement lately, Megan is coming to visit for about a week, starting tonight. Stay tuned.

Glimpse into and Unexpected Evening

Just so you know that I didn’t drop off the face of the earth, I had a slight problem with my site last week. It’s technically fixed now, but a side effect has been that I still can’t access my WordPress software from home, so everything I’ve written lately is sitting in a file folder waiting to be posted.

So if I can’t write from home, where am I at the moment? I’m so glad you asked. I’m at Emily’s house with her, Chad, and the boys from Casa G eating ice cream and brownies. You’d think that sounds like a pretty normal night, unless you know the guys and how entertaining it is just to have them around. There are random English phrases being yelled like “I’m gonna punch you in the face.” Earlier, Mike was playing guitar and singing while Alejando just stared at him like “What are you thinking?” Emily was worried about having too much ice cream, and we’ll just say it’s basically gone.

Now and then

Today we were supposed to have our first spring sort-term team on the ground. Well, you can guess how that turned out.

Dario and I were on our way to Hostal Bosque in a taxi when we were informed that our team would not be arriving tonight, and we were unsure exactly when they would actually make it into the country. Stuck in Toronto, the team leader finally called to let us know when they had some semblance of an itinerary, and now we hope to be picking them up at the airport at 10:30 in the morning, which means we won’t be headed to Carmen Bajo for church.

It’s funny to look back almost two years ago to the first team I hosted with Sarah. We were in the same situation, having planned for a team that ended up being delayed almost a full 24 hours. I remember sitting in the kitchen at Dana and Ashley’s house, staring across the table at Sarah with absolutely no idea even where to begin dealing with the situation as we learned about it, and knowing exactly how lost I would have been without her. This afternoon, however, Dario got the phone call that our team hadn’t even made it out of Canada yet, and we both shrugged and went about our plans. I mentally pulled up the schedule and knew that the simplest thing we could do was to cut Carmen Bajo totally from our day tomorrow, and we’ll make the calls as we go along about how much touristy Quito activities we do, based on time and how settled our team gets. Dario (since he managed to get some saldo) called Fabian and Rogelio and let them know the revised plan and neither of them freaked out either.

In 2008 I wrote an entry called “Flex and flow”, a manta-like phrase around Youth World, and something Sarah Miller would say multiple times every day. She even has her own personal sign language for it. I think at the time I titled the post that way and talked positively about the concept more to actively teach myself to believe it more than anything. I’m not the most flexible person in the universe, but I’m certainly much more flexible now than I was two years ago. Part of that has been learning what solutions are even available when a schedule crisis like this one occurs. Part of it has been adjusting to how South American life in general just functions. And part of it has been having some really awesome examples.

After a day putting away groceries and setting up the hostal with absolutely no hurry (and then watching funny movies with Dario all night) I can really appreciate all three of those things.

Virus Fixed

As far as I know, I’ve wiped out the virus. Please let me know if you are still having problems.

As far as the new theme, it’s an indirect result of this whole process. I was reminded of the fact that my website has looked exactly the same for over two years now, and I couldn’t find the original source code for my theme anyway. Rather than going through every single file in the theme to manually wipe out the virus (I actually think I manually destroyed the only occurrence, but would have wanted to be sure), I just installed a new theme. It was probably just as much work to re-crop, re-size, and re-upload all the images for my randomized header, but be that as it may, I’m still pretty pleased with the time and effort that went into it, and the final product.

For those of you who are just reading this on facebook or anywhere else this gets imported via RSS, I’d encourage you to cruise on over to dannypeck.net and take a look around. If you haven’t actually been to the original source of my blog before, you may find something interesting. If you have, hopefully you’ll like the new look.

Virus

For those of you who actually read my blog here on www.dannypeck.net, I have a virus. Most of you are probably already aware of this due to the unfortunate side effect of being redirected to some adsite. I’m in the process of fixing it, but I have the odd problem of having TOO good an anti-virus software, and I actually am unable to see the effects of the virus myself.

For the rest of you, you should still be able to use my RSS feed without any problems. Link below, and I’ll be sure to post a “Virus Fixed” post when that statement becomes accurate.

http://www.dannypeck.net/?feed=rss2