AuburnChris

Really starting to jones for our spring break trip in 60 days!
Found this great old home movie, said to be found at an estate sale.  So many cool long one things at the Fort.  
Posted only a few days ago.
Enjoy!
 

From a Fiend On The Scene, here's some information on what's planned at the Fort for Fourth of July.

Here's the March 2019 Fort Wilderness recreation calendar. 

Here it is:

Good news: it lives! 
Even better news: now I can start cleaning it up and adding the missing new loop. The work continues!

Good news: it lives! 
Even better news: now I can start cleaning it up and adding the missing new loop. The work continues!

OK so working on 6-year-old code that Apple's development environment "helpfully" updated to modern times is cool and good and entirely not making my hair turn greyer at a faster rate than my teenager does already.
Here's where we're at:
The old, busted version of the app that was released lo these many years ago still works great- if you haven't upgraded past iOS version 10 or so. (I think that's right, might be version 8, your experience may vary, consult your dealer for details, for external use only, etc.) But nobody's using that who has anything close to a modern iPhone, so you probably don't even see it in your app store yet.
So I have to figure out what is making it not work. Most of that work is so boring that even I don't want to get into it. Just clearing out digital cobwebs, mostly.
But the big stopper was that we store the site images on this very site, hidden off in an obscure corner of our web space. And the URL to get to it was a plain old http:// address, just like everything else. Apple had the fabulous idea a couple of iOS versions ago to require any app that makes a call to the web to retrieve something must make it via a secure connection. Since that was failing, no images were coming through, which is a Bad Result. So I had to fix that. I think I have that working now, and I'm about to try switching it on, so we can throw two stones at one bird (to coin a phrase):
As a result of all that back-end mucking around, we're going to flip the switch and make fortfiends.net light up your browser as a secure site. This is a Good Thing, because it will help our Google rank, and hey, it's secure. Secure is good, and I have it on good authority that it's at least somewhat better than Not Secure.
And if all that works, one of the main barriers to having an app update out that actually works for everyone will be gone. I don't like giving myself deadlines, but I would say that before the week is out, you Apple folks should have a little gift waiting for you.
Thank you, once again, for reading all the way through another episode of Chris Talks Way Over Everyone's Head About Web Stuff. I love you.

Still working, folks.
Good news: I have a working version under iOS 11.4 and below now uploaded to the App Store.
Bad news: I have to update all the screenshots that go into the App Store page and write all the update copy, and then we have to wait on Apple to review the whole business and post it.
I have no idea how long that takes these days. Used to be at least a week or so, but that was back in the day, and this is an update and not a brand new app, so things may be different.
I'll keep everyone posted.

OK so working on 6-year-old code that Apple's development environment "helpfully" updated to modern times is cool and good and entirely not making my hair turn greyer at a faster rate than my teenager does already.
Here's where we're at:
The old, busted version of the app that was released lo these many years ago still works great- if you haven't upgraded past iOS version 10 or so. (I think that's right, might be version 8, your experience may vary, consult your dealer for details, for external use only, etc.) But nobody's using that who has anything close to a modern iPhone, so you probably don't even see it in your app store yet.
So I have to figure out what is making it not work. Most of that work is so boring that even I don't want to get into it. Just clearing out digital cobwebs, mostly.
But the big stopper was that we store the site images on this very site, hidden off in an obscure corner of our web space. And the URL to get to it was a plain old http:// address, just like everything else. Apple had the fabulous idea a couple of iOS versions ago to require any app that makes a call to the web to retrieve something must make it via a secure connection. Since that was failing, no images were coming through, which is a Bad Result. So I had to fix that. I think I have that working now, and I'm about to try switching it on, so we can throw two stones at one bird (to coin a phrase):
As a result of all that back-end mucking around, we're going to flip the switch and make fortfiends.net light up your browser as a secure site. This is a Good Thing, because it will help our Google rank, and hey, it's secure. Secure is good, and I have it on good authority that it's at least somewhat better than Not Secure.
And if all that works, one of the main barriers to having an app update out that actually works for everyone will be gone. I don't like giving myself deadlines, but I would say that before the week is out, you Apple folks should have a little gift waiting for you.
Thank you, once again, for reading all the way through another episode of Chris Talks Way Over Everyone's Head About Web Stuff. I love you.

Still working, folks.
Good news: I have a working version under iOS 11.4 and below now uploaded to the App Store.
Bad news: I have to update all the screenshots that go into the App Store page and write all the update copy, and then we have to wait on Apple to review the whole business and post it.
I have no idea how long that takes these days. Used to be at least a week or so, but that was back in the day, and this is an update and not a brand new app, so things may be different.
I'll keep everyone posted.

OK so working on 6-year-old code that Apple's development environment "helpfully" updated to modern times is cool and good and entirely not making my hair turn greyer at a faster rate than my teenager does already.
Here's where we're at:
The old, busted version of the app that was released lo these many years ago still works great- if you haven't upgraded past iOS version 10 or so. (I think that's right, might be version 8, your experience may vary, consult your dealer for details, for external use only, etc.) But nobody's using that who has anything close to a modern iPhone, so you probably don't even see it in your app store yet.
So I have to figure out what is making it not work. Most of that work is so boring that even I don't want to get into it. Just clearing out digital cobwebs, mostly.
But the big stopper was that we store the site images on this very site, hidden off in an obscure corner of our web space. And the URL to get to it was a plain old http:// address, just like everything else. Apple had the fabulous idea a couple of iOS versions ago to require any app that makes a call to the web to retrieve something must make it via a secure connection. Since that was failing, no images were coming through, which is a Bad Result. So I had to fix that. I think I have that working now, and I'm about to try switching it on, so we can throw two stones at one bird (to coin a phrase):
As a result of all that back-end mucking around, we're going to flip the switch and make fortfiends.net light up your browser as a secure site. This is a Good Thing, because it will help our Google rank, and hey, it's secure. Secure is good, and I have it on good authority that it's at least somewhat better than Not Secure.
And if all that works, one of the main barriers to having an app update out that actually works for everyone will be gone. I don't like giving myself deadlines, but I would say that before the week is out, you Apple folks should have a little gift waiting for you.
Thank you, once again, for reading all the way through another episode of Chris Talks Way Over Everyone's Head About Web Stuff. I love you.

I'll take the free publicity, honestly. Wouldn't dream of bugging them about using our name like that. I'm happy to see people writing about the Fort thinking enough of us to use us for research! Complaining at them about name-dropping us seems counter-productive on every level I can imagine.

I'll take the free publicity, honestly. Wouldn't dream of bugging them about using our name like that. I'm happy to see people writing about the Fort thinking enough of us to use us for research! Complaining at them about name-dropping us seems counter-productive on every level I can imagine.

I'll take the free publicity, honestly. Wouldn't dream of bugging them about using our name like that. I'm happy to see people writing about the Fort thinking enough of us to use us for research! Complaining at them about name-dropping us seems counter-productive on every level I can imagine.

No, TCD, it's not. But I don't consider what has been disclosed here about Hilda to be an invasion of privacy the way you appear to. If I did, I'd have to police every time someone posted what site number someone else was staying in, and that's kind of ridiculous.
 
Edit: You know what? None of this is going anywhere. Keeping this discussion going only serves to draw attention to information that none of us, apparently, are interested in drawing attention to.

No, TCD, it's not. But I don't consider what has been disclosed here about Hilda to be an invasion of privacy the way you appear to. If I did, I'd have to police every time someone posted what site number someone else was staying in, and that's kind of ridiculous.
 
Edit: You know what? None of this is going anywhere. Keeping this discussion going only serves to draw attention to information that none of us, apparently, are interested in drawing attention to.

No, TCD, it's not. But I don't consider what has been disclosed here about Hilda to be an invasion of privacy the way you appear to. If I did, I'd have to police every time someone posted what site number someone else was staying in, and that's kind of ridiculous.
 
Edit: You know what? None of this is going anywhere. Keeping this discussion going only serves to draw attention to information that none of us, apparently, are interested in drawing attention to.

We've been watching all day. If you want to get our attention, you can use the report button, it's much better at getting our attention than downvoting people who aren't us.
As far as this thread is concerned, I don't see the foul, frankly. Once the phone number was removed, I don't think there's anything wrong here. I don't see any bad intent on the part of the original poster, and I'm on record for quite a long time now as being generally against mods deleting posts. If the OP wants to delete, that's his prerogative.

We've been watching all day. If you want to get our attention, you can use the report button, it's much better at getting our attention than downvoting people who aren't us.
As far as this thread is concerned, I don't see the foul, frankly. Once the phone number was removed, I don't think there's anything wrong here. I don't see any bad intent on the part of the original poster, and I'm on record for quite a long time now as being generally against mods deleting posts. If the OP wants to delete, that's his prerogative.

We've been watching all day. If you want to get our attention, you can use the report button, it's much better at getting our attention than downvoting people who aren't us.
As far as this thread is concerned, I don't see the foul, frankly. Once the phone number was removed, I don't think there's anything wrong here. I don't see any bad intent on the part of the original poster, and I'm on record for quite a long time now as being generally against mods deleting posts. If the OP wants to delete, that's his prerogative.

TL;DR: Photobucket is evil and stupid now, use Imgur instead.
So Photobucket, a site a lot of you use to host pictures here on the site, is currently committing corporate suicide by preventing people from using their service for exactly what they've been using it for since forever. To post pictures from Photobucket here on Fort Fiends, the fine folks idiots at Photobucket have decided that you need to pay them $400 American dollars a year for the privilege.
That's dumb. And it's going to break a lot of links here on Fort Fiends. I wish there was something that we could do about that, but there's really not, from our end. Everyone's posts that link to Photobucket are going to break, unless they pay, which I wholeheartedly do not recommend.
WHAT DO I DO?, I hear you ask. Here's what you can do:
1. Go download everything you can from your Photobucket account, while you still can. I'm hearing horror stories of people whose accounts are being locked for "violating your free Photobucket account's terms of service" for third-party linking. Once your account has been locked, you apparently can't get to your photos until you pay up, which again DO NOT GIVE THIS DUMB COMPANY YOUR MONEY.
2. USE IMGUR. Imgur is my image host of choice, because it was built for hosting images. That's what it does, and it doesn't charge its users to do it. They're at imgur.com, and I'd write up a whole thing on how to use it, but I don't really have the time at the moment. They're pretty easy to figure out, though. I'm confident that you can do it- you certainly can if you were linking from Photobucket before.
3. Once your previously-hosted-on-Photobucket pictures are now on Imgur, you'll have to manually edit your old, broken posts to point to the new ones. This is the part which will be tedious, and hard, and unfortunately nobody will do it.
I'm not going to put too fine a point on this: This sucks, and it sucks a lot. It's going to decimate our Trip Reports forum, which is very image-heavy. I am filled, at this moment, with righteous anger at the morons at Photobucket who thought any of this was a good idea. 
TL;DR: Photobucket is evil and stupid now, use Imgur instead.

Our friend Ken asked me to delete his account. I have complied with his request. I think there's nothing else to see here (except for possibly some questionably-replicated pastries).

Our friend Ken asked me to delete his account. I have complied with his request. I think there's nothing else to see here (except for possibly some questionably-replicated pastries).

Our friend Ken asked me to delete his account. I have complied with his request. I think there's nothing else to see here (except for possibly some questionably-replicated pastries).

Thread reopened. Please try to keep things civil around here, won't you? Thank you.