Chief Alchemist - Business Consulting For The 21st Century Via A Holistic & Intelligent Approach
Share RSS 2.0 feed for Sign up for the mailing list. Follow Chief Alchemist on Twitter. 'Like' the Chief Alchemist's page on Facebook. See what Chief Alchemist has been Q&A'ing on Quora. Chief Alchemist bookmarks & highlights on Follow the Chief Alchemist on Chief Alchemist channel on Chief Alchemist on Flickr. Mark 'Chief Alchemist' Simchock on LinkedIn. Free Initial Consultation. Email Chief Alchemist. Phone Chief Alchemist.
  • Mark ‘Chief Alchemist’ Simchock
  • 'Email me.Email => ca .at. ChiefAlchemist .dot. com
  • 'Phone me.Alchemy United => 732 997-0028
  • Free initial consultation.Free => Initial Consultation
  • Please be sure to subscribe to your communication channels of choice.
  • Click To Close => The small green (consultation), red (email) or blue (phone) icons in the top upper right.
Business Consulting For The 21st Century Via A Holistic & Intelligent Approach

Quick tip on updating profiles via email

If you’re updating any of your social media profiles and/or page via email here’s a little security tip. Since I’m working with Facebook Pages at the moment that’s the example I’m going to use.

Instead of storing the actual FB update via email addresses where I’m might use them, I actually creating a Forward-Only email for each of them and using the Forward email address. The reason being, if for some reason the Forward-Only address is breached I can just squash it and create a new one but still use the same FB update via email. My assumption is, my web host’s email server is going to be more secure than most places where I might need to “leave” the update via email address. For example,  I trust WordPress and AU_WPing but they a probably more hackable than a hosting company.

This Forward-Only approach would also be useful if you want to give multiple people the ability to update the same page via email but then have to “decommission” one of them. If the the actual update via email address was hidden from everyone, then instead of having to create a new update via email address for the Page and then turn around and update everyone who’s using it, you can just delete the Forward-Only email that you no longer want accessed. The only person who will know where that Forward-Only is being forwarded to are the Page’s Admin and the person who manages your email accounts. Ideally those roles are “secure”.

BTW, FB does allow you to create a new update via email address but apparently there’s some sort of limit on the number of times you can that. Unfortunately, they don’t specify what that limit is. I’d rather not take my chances so I’m trying to manage these emails as tightly as possible.

Make sense?

You’re probably wondering why I would want to use update via email. In short, has locked down their API. Until time unspecified, they are not releasing any public access keys, only single use developer keys are still active. In addition, in the course of developing AU_WPing, I found out that Twitter was blocking the Dreamhost IP my sites were being hosted on. In other words, no API access there either. I was able to work around that by getting a Virtual Private Server but in theory that server’s IP could eventually be blocked as well.

The bottom line, as primitive as email might be, it works (I hope) and avoids all these stressful API issues.

Will not be published. Required.
Please include http://