About This Site

"FLAME" stands for "Former Loyal AMD Employee"

The FLAME website was created in 1997 by John McKean, an AMD FAE from Toronto, as a way for former and current AMDers to stay connected. After compiling the suggestions that were sent to him each week, and adding his own commentary, in italics, signed/jm. He published his weekly FLAME newsletter to more than 2,000 readers, around the world, over the past 17 years.

John passed away suddenly in September, 2014. John will be remembered by many for his contributions to AMD as an integral part of the Toronto field sales office from 1981-1996.

Read our tribute to John here.


Financial Support

The cost of operating this site is borne by these members.

Contributions to the site operations can be made through paypal, using the link paypal.me/amdflames.


These members can write articles and upload graphics to the site. If you'd like to do have that ability, contact the editor.

How it Works

The site is hosted by pair.com. I highly recommend them.

The site is written in PHP. Over the years, I keep learning better code-writing skills, so the site is kind of constantly evolving, from spaghetti to structured to objects. Anyone who wants to help is welcome, as I'm still totally an amateur.

Virtually all the pages on the site are php so I can at least check for a login before they display. The admin is pretty much all through web forms and php. I rarely have to manually upload a file or diddle with any html code or data.

The site uses mysql tables to store:

Newsletters date back to 1998. The older ones are self-contained files; the newer ones are each in a directory containing a newsletter template and a bunch of text files that contain the content. This lets me modify newsletter structure without messing up old newsletters.

I generally update the articles several times a week, with the last update on Thursday. Then I run a script that creates a list of all the updates to member data made since the last newsletter, which just drops into the newsletter folder. Preview the newsletter, and if it's OK, publish it , which is mostly just moving the directory. Then build the bulk email. The email can be queued to go out overnight, or if necessary, can go out in real time. Each member gets an individualized newsletter, and they are paced to avoid triggering spam blockers.

There a "sweep" script that runs every night to look for members who have not logged in or verified their email for a year. It sends them an email asking to verify their address. A week later it sends another one. Then a third. Then it notifies me and I try manually sending them something. Then it marks them as Lost. The newly Lost members get listed in the weekly newsletter. A similar sequence is followed when people change their email address, or when I get a vague bounce.

Login is via a unique code for each user, which is basically your userid + password, both machine-generated. Not very secure, but much simpler than trying to have a proper password system. I just include your login in every email you get.

The newsletter is saved as a directory with a php template and a series of text files with the content that get included when the template is run. I've thought about emailing out the whole newsletter as a html file, but the way it is now encourages people to log in, where they can make comments and get reminded to update their profiles from time to time. So nae.

I do all my site admin on my Mac, using the web forms. I do all my development on my Mac, using BBEdit to write the code, and Transmit to keep local folders in sync with folders on the server. PHP and Mysql both run on my Mac, but I don't usually run stuff there because there's too many differences between the local environment and the server. (php.ini for example.) So occasionally I edit something live on the site, and regret it 🙄.