Archive for April, 2009

Refills: A Sustainable Solution

Thursday, April 16th, 2009

What if you could get refills for all of the products that you buy that come in containers?

We’ve become accustomed to the notion that every product must come in its own packaging, that this is “obvious” and that it’s the only way things can be done.

Every day I use a variety of container-based products (CBPs for short): shampoo, face-wash, toothpaste, liquid soap, orange juice, etc. etc. The list of CBPs goes on. This causes a huge strain on the environment. Companies use giant factories across the world to manufacture hundreds of thousands, and in some cases millions of CBPs. For each CBP resources and energy are used to create the container, then all of these little containers are shipped all over the world in an inefficient manner.

Wouldn’t it be great if we could get rid of most of them? I think such a world is possible.

This brings up several questions: Could this cause difficulties for brands to compete? After all, you recognize that this particular brand of sugar-water belongs to Pepsi because it comes in a CBP that has the Pepsi logo on it. And how are you to know what’s in your shampoo if it doesn’t have a container to list the ingredients?

Imagine the following:

A Different World

A consumer walks into a local grocery store in search of body wash. He grabs a sleek bottle of Product 5eX promising to make him more attractive to the opposite sex. Except, this isn’t a CBP, in fact, while the store’s isles are packed with various bottled products much as they are today, there’s not a single CBP to be found, what our gullible protagonist holds in his hands is actually an RBP—a refill-based-product.

After weeks of usage and several unsuccessful attempts at attracting a mate, our friend runs out of Product 5eX and decides that perhaps he hasn’t used it long enough and so drives back to the grocery store in search of more. However, instead of going back to the isle where he originally found it, he places the empty container, along with empty containers of toothpaste, face-wash, and 9-liter bottle of cola on a conveyor belt at the front of the store while swiping his credit card. After shopping around for various food products inside he’s ready to checkout, and so are his RBPs.

In such a world there are many possibilities. Perhaps you could use a generic container and simply use the product’s unique ID number to refill it. There could be a huge online database that matches product IDs with detailed information about each product such as nutrition facts, ingredients, etc. All with the latest information on each ingredient and links to further information.

Not So Different

In fact the concept of an RBP is not so foreign. Recently my local OfficeMax began offering refills for all ink cartridges. Refills have existed at restaurants as long as I’ve known.

While many of today’s containers are recyclable, recycling is not nearly as good as reusing and reducing. Recycling takes energy, and many of the things that you put into your recycling bin don’t actually get recycled for one reason or another. It does not really tackle the core issue.

Instead of creating and shipping millions of little bottles, companies could send entire vats of refillable goop all over the world. The RBP model is not just a giant win for the planet, it’s a boon for consumers and producers alike, as it would drive down the cost of production and therefore the cost of products.

Challenges

There are certainly many questions that need to be addressed for such a world to become a reality. For example, the question of sanitation. How can you guarantee that a refilled product will be as fresh as a brand new one if the container has been opened? I’m sure that through various techniques and technologies such challenges can be overcome. Perhaps each major reseller can have its own mini-sanitizing doo-hickey that cleans the insides of containers. Like all engineering problems, the solutions are out there as long as someone is willing to put in the effort.

Think it’s a good idea? Pass it on. :-)

Espionage 2.0.5/2.0.6 Released + Dropbox note

Monday, April 13th, 2009

A maintenance release for 2.0.4:

  • FIXED: Bug in 2.0.4 that could prevent a volume with an espionage’d folder from unmounting (thanks Neil!)
  • FIXED: Bug in auto-backup where backup wouldn’t start if backup folder was in a subfolder of the drive
  • FIXED: Auto-enable-on-mount only enables folders if they are on the device that was mounted
  • IMPROVED: Warning for “can’t find folder” now disappears instead of sticking around waiting to be clicked on
  • IMPROVED: Minor change related to custom folder icons
  • IMPROVED: Updated BWToolkit to 1.1

2.0.6 was shortly released after 2.0.5 due to an oversight on our part related to PPC machines.

Note on Dropbox

While testing Espionage’s compatibility with Dropbox, we noticed that one of the recent updates to Dropbox causes the Finder to change its behavior a bit, causing the password prompt to come up when it shouldn’t. Therefore for now we’re recommending that our users do not use Dropbox as a method of syncing espionage’d folders, but you can still safely use it as a backup destination for Espionage’s built-in backups. Better Dropbox support is planned for the future.

Update (12/14/09): See here: Instructions on how to safely use Espionage with Dropbox.

Espionage 2.0.4 (aka FinderPwn) Released!

Saturday, April 11th, 2009

This release brings fixes to some long-standing bugs in Espionage with its Finder integration, as well as two new features!

  • NEW: Full support for custom folder icons! To add a custom icon to an existing espionage’d folder, disable it, and use the Get Info panel
  • NEW: Automatically begins backing up folders if backup drive is mounted
  • FIXED: Bug where locking a folder with the ‘Lock’ CM could cause the Finder to claim it no longer had permission to access the folder
  • FIXED: Many situations where password prompt would appear randomly.
  • FIXED: Bug introduced in 2.0.3 that prevented moving an encrypted folder to a parent directory
  • IMPROVED: Prevents encryption of folders inside of an already encrypted folder (which can cause problems and is unnecessary)
  • IMPROVED: Reveal in Finder menu item now selects the folder even if it’s locked (because now the prompt won’t appear)
  • IMPROVED: Folders backup setting is turned on by default now
  • IMPROVED: Warns users to not use iDisk as a backup destination

Overview of Significant Changes

Finder ‘Pwnage’

This bug has been with Espionage since day one, and we’ve finally nailed the sucker. Now, when you re-lock a folder on some systems, the Finder will not claim it doesn’t have permissions to access it when you double-click on it again. This bug only appeared in certain specific situations, and was fairly easy to get around by doing something as crazy as “nudging” the folder a bit, but we’re glad to have finally fixed it nonetheless, and I’m sure our users are too. :-)

Additionally, we were able to fix several scenarios where the password prompt could randomly appear. This turned out to be quite the challenge in pattern recognition actually, which is why we’re dubbing this release “FinderPwn” due to the rather hackish nature that this must be done in.

Custom Icon Support

Now you can give your folders pretty custom icons! When you encrypt a folder that has a custom icon, Espionage will automatically copy that icon to the newly encrypted folder. If you’d like to change the icon for a folder that you’ve already encrypted, first disable it, set its icon as you normally would via the Get Info panel, and then re-enable the folder.

Auto-backup on mount

This new feature is aimed at users who use Espionage to encrypt folders on external drives. Now if you plug in a drive that has an Espionage’d folder in it, it will automatically be enabled so that you can immediately begin using it without having to re-enable it from the application.

Enjoy! :-)

Tao Effect Forums Open!

Thursday, April 9th, 2009

To allow our users to share ideas and help each other out (read: send us less support email), we’ve created the Tao Effect Forums!

Come on in for all the exciting action! Sorry. Maybe it’s not all that exciting, BUT—to start things off there are three Espionage Tips that you might be interested in reading:

Enjoy!

Taking inqueries for iSpy

Wednesday, April 8th, 2009

Espionage owes its existence and unique capabilities to a little known system that we’ve developed in-house called iSpy.

iSpy is a low-level, generic system for detecting and moderating events on the filesystem. It is comprised of three main components: a kernel extension, a system-wide daemon, and an application framework.

Brief History

I originally became interested in the problem of watching the filesystem when I had an idea for an application that would automatically clean your Desktop as files were added to it, moving downloaded files to their proper locations for you, thus resulting in an uncluttered Desktop. It would be possible to generalize such an application to perform various other tasks as well. It wasn’t until I discovered that such an application already existed that I turned my sights to another problem: password protected folders.

As I studied the available systems that I might be able to use to solve this problem (fs_usage, FSEvents, Spotlight, and others), I realized why this problem hadn’t been solved before: none of these systems allowed you to detect when a file or folder was accessed. And “just like that”, iSpy was born.

Not only can iSpy detect when a folder or file is accessed, written to, read from, executed, or deleted, but it actually detects and reports these events before they happen. This gives iSpy the unique capability of allowing events on the filesystem to be moderated by a user-land application.

Using iSpy

Using it is actually very simple. The API consists primarily of only 3 significant functions that register, modify, and unregister events, respectively.

Licensing iSpy

Originally we were planning on keeping iSpy firmly in the hands of Tao Effect, but we’ve recently decided to head in a new direction. That is why we are considering licensing this system to trustworthy third-party developers, so that it may be used to create more unique software instead of being monopolized by Espionage.

This does not mean that we will be abandoning its development, to the contrary an update to it is scheduled for the near future, and it will continue to be supported and maintained by Tao Effect for quite some time. However, as we are working on software that will not make use of the system, it is unlikely for the time being that Tao Effect will create any significant new software using it (other than Espionage, which is in active development, and will continue to be for quite some time).

While we haven’t hammered out exactly how we plan to license it, we’re curious to see if there’s any interest out there. Whatever the final terms, we’ll do our best to make sure that they are fair to both parties, and that the cost of licensing would be less than developing it in-house. If you’re wondering whether iSpy is the right event system for your project, let us know by sending email and any questions to:

To:      contact (at) taoeffect (dot) com
Subject: Interested in iSpy

Programmers: Win a license to Espionage!

Saturday, April 4th, 2009

I’m part of the newLISP Fan Club. I consider myself a fan. :-)

Over on the boards there is a challenge, and whoever solves it first wins a license to Espionage, just because that’s something that I can offer to the winner. :-D

Contest ends when someone posts the solution on that forum, or on the 11th of April.