All posts tagged tutorial

google_logo

If you haven’t heard, Google is updating their privacy policy.  You have until March 1st to clear out your previous browser history before all bets are off and they own it.  Forever.

I’m not talking about your local browser cache on your computer.  I’m talking about Google’s massive database of browsing history.  Because, they’ve been tracking everything you do and saving it for a rainy day.  It’s time to break out your galoshes.

In a highly controversial move, Google announced that it’s changing it’s privacy policy to allow it to collect, store and use your personal search history data for its own purposes.  And it’s extending that policy to cover the entirety of the search history it has already been collecting.  It plans to leverage this information across all of it’s properties (e.g. YouTube, GMail etc.) and not just on the Google search engine itself.

This data will not be held anonymously – it will now be tied directly back to you.  In perpetuity.  The things that you do anonymously today will, in the future, be directly associated with your name, email address and/or phone number.   For example, private details sent in email can crop up later in Google Maps searches.  Imagine an off-color video viewed on YouTube informing your search results a week later at a client meeting when trying to demo an unrelated business application.

You can turn this off (opt out) and pause Google from continuing to collect your private browsing history.  Follow these steps:

1. Go to Google.com and log into your Google Account.

2. Next, go to  https://www.google.com/history

3. Click “Remove all Web History”

4. Click OK

 

Doing this will not only clear out your browser history, but it will automatically “pause” Google from collecting and storing your history over the long term.  To be clear, they will still collect record of your actions, but it will be anonymized and not tied back to you personally, but just used in aggregate with other users to inform general trends and analytics.

Years ago when I heard Google touting their mantra as “Don’t Be Evil” I thought it was cute and clever, and I was hopeful.  But I was also extremely cynical.  I knew that if they grew enough, the day would eventually come when the growth slows, competition heats up, the suits take over, and pressure to perform (financially) starts to mount.  These things have a way of changing.

To mix metaphors, “the road to hell is paved with good intentions.”  So much for “Don’t Be Evil.”

 

Mac_OSX

One of the very nice things about working with multiple platforms and technologies, not to mention just having longevity in the business (which is a nice way of saying I’m old!), is that you get exposed to a lot of different ways of solving problems.  “Oh, I’ve seen that before.  Back in the DOS days we used to…”

Administering FTP services on Mac OSX server has always left me wanting something better.   The built-in services work, but they have a few drawbacks:

1. I don’t like having to bounce around multiple places to administer things.  Over to the User section of the System Settings to add users.  Back over to the Server Admin to manage FTP Server settings, etc.  I always liked the all-in-one console approach with things like FileZilla on Windows servers.

2. I don’t like having to create real, actual user accounts in the system for FTP users.  I have multiple web hosting clients who need access, each to their own specific web site directories.  I don’t like creating “real” user accounts on the machine for them.  Partially a security concern, and partially just “…something bothers me about it.”  The Windows Server OS has FTP services built-in, but they are woefully inadquate and they too are all integrated and require actual user accounts.  For years I’ve used the open source FileZilla Server for Windows.

3. FTP access is SOOOOOO SLOOOOOOOW.

The very first thing I had done, when I first installed the Mac OSX Server, was to look for an OSX version of FileZilla.  Alas, they don’t make an OSX version of FileZilla.  I poked around didn’t find a suitable alternative.  So I stuck with the built-in services.

We hadn’t been using FTP all that much on the OSX Server, so we dealt with the slowness issue.  But more recently we’ve had the need to use it a bit more, and the time lags made us want to stab our eyes out.  So less we go blind, I started searching around for a cause and hopefully solution.  And to my great pleasure, I found TWO solutions!

First, it turns out that the slowness issue is very easily solved.  It’s merely a configuration setting that really ought to be part of the default installation, but isn’t.    Go here to find the full write-up from Apple.  But in a nutshell, I just needed to open the file   /Library/FTPServer/Configuration/ftpaccess    in a text editor, and then add the following line:

  passive ports Server_IP_Address 49152 65535

Then restart the server.

That’s it!  The slowdown was because when trying to go to passive mode, it was banging its head against the wall trying to find a valid port to use.

However, it gets even better…

In my travels, I also got clued into a FileZilla -like open source FTP Server!

pureFTPd is an active, open source FTP server project for the BSD unix / linux families including Mac OSX.  And there’s a GUI interface called pureFTPd Manager for OSX!    Just click the preceeding link, and you can download the GUI interface and ftp server all bundled up in one since installation package.

This software will allow you to setup multiple different username/password combinations, locking each into a specific set of “home folders”.  But these are all accounts setup within the software, and NOT actual system accounts.  Its much better security approach, and much “cleaner”.   And the software is FAST too, with better system monitors.

Enjoy!

I have been working on a post along the lines of “How to Troubleshoot Web Site Problems” but it started to get mired down in the details of DNS servers.  Thus, I decided to break the topic out into a separate posting to lay some groundwork first, THEN post the original tutorial.  So without further adieu, a primer on DNS:

Read more…