Comments for ALBj.net

Comment on Understanding Ingredients by Lee Bennett

Lee Bennett — Fri, 20 Aug 2010 22:01:08 +0000

D’oh! Sure enough. Fixing it now.

Comment on Understanding Ingredients by Mandy

Mandy — Fri, 20 Aug 2010 15:41:11 +0000

imply hell-bent? Sorry had to point out that during your rant you dropped an s. ;)

Comment on Hey Subway—wanna make more money? by mary

mary — Thu, 29 Jul 2010 03:51:37 +0000

Hey Subway, get rid of the plastic bags too. At least for non-take out.

http://www.facebook.com/pages/Just-say-NO-to-Subway-sandwich-bags/145641622116084

Comment on The Agency by Jim

Jim — Wed, 14 Jul 2010 00:35:22 +0000

I always knew there was a secret agency running McDonald’s playgrounds as a front!

Comment on AppZapper seems devious to me by Lee Bennett

Lee Bennett — Wed, 21 Apr 2010 21:56:25 +0000

You might remember that I conceded that perhaps you indeed do not sell lists of customer e-mail addresses. Yet, you were adamant about the fault likely being with my domain host service rather than agreeing that there’s at least some chance it was your system that the address came from. Logically to me, it simply doesn’t make sense that that the address could have been “found” from any other source. I understand what I claim is information you cannot verify, but I can 100% assure that an e-mail has never been sent out by me with the e-mail address alias in question. My aliases are only used for incoming messages. I entered the alias once, either on your web site or within the application itself, I don’t recall. Nor do I recall whether your system e-mailed registration information back to that alias, but if it did, it would only have been that one time. Given that NO other alias I’ve used for other products have been spammed, and that for myself, I know beyond doubt that a message has never been sent out from my computer using that address, I really have a hard time believing any other scenario. If the breach was indeed my domain host, it’s reasonable to assume more of my aliases than just yours would have been scraped.

Comment on AppZapper seems devious to me by Brian Ball

Brian Ball — Wed, 21 Apr 2010 21:28:11 +0000

Lee,

Brian here from AppZapper – I’ll have to disagree with you here. If creating aliases for email were the answer to SPAM, do you think it would be a problem?

You assert that SPAM is caused by people selling email addresses.

This is ridiculous.

WIth you solution, Google or any ISP could provide a simple tool that allows people to use disposal email addresses and SPAM wouldn’t be a problem for anybody – we’d all have single use emails that reverted back to a main account – which you think you are so cleverly doing.

If it works 100% of the time, why don’t you patent it?

It sounds like an amazingly genius solution.

Before you go accusing somebody of doing something, that you can’t prove, why don’t you do the research yourself?

Because you get some piece of spam in an inbox that YOU created with our name on it – you blame it on us?

Let me know if you sell your alias solution – I’ll be the first in line to buy it.

Warmly,

Brian Ball

Comment on AppZapper seems devious to me by Lee Bennett

Lee Bennett — Tue, 20 Apr 2010 15:32:33 +0000

The multiple alias practice has worked really well for me. Aids in sorting/filing as well as identifying compromised addresses. It’s nice when I know I can simply filter messages that have XYZ as the e-mail address and know they all pertain to one particular service or product. As for alternatives, I found that I used AppZapper sparingly. It was handy when I used it, but I didn’t use it enough to justify switching to a different product. In fact, I’m skilled enough at finding relevant files to delete on my own. The utility just aided the process to go a little faster.

Comment on AppZapper seems devious to me by Randy

Randy — Tue, 20 Apr 2010 15:04:13 +0000

Not sure if it does everything that AppZapper does, but I’ve been using AppTrap with good results. Although I don’t go so far as creating a separate alias for each account but rather one dummy for all so to pinpoint to one defiler would be difficult/impossible.

Comment on Hey Subway—wanna make more money? by Lee Bennett

Lee Bennett — Thu, 01 Apr 2010 17:56:40 +0000

So maybe it is just one particular store that is bone-headed. I was in another store today and asked about the tea. Turns out that prior to 4pm, the corporate instruction is to continue making it as needed. After 4pm, a store may, at their discretion, only make one additional batch, but are not restricted to only one batch. In any case, the store in question has *definitely* misunderstood the corporate instructions in thinking they can only make one batch PER DAY!

Comment on Seven-year blogging anniversary by Lee Bennett

Lee Bennett — Sat, 20 Mar 2010 03:03:47 +0000

I’ve managed to collect a great many of them. Where I used to see albums I didn’t have pop up on eBay all the time, I probably only see one or two a year any more that I don’t have—if even that many. If there are some I’m missing, though, I’d be interesting in browsing what’s available.

Comment on Seven-year blogging anniversary by Bob

Bob — Sat, 20 Mar 2010 01:45:52 +0000

Found an old blog requesting old Coulors CD’s. If you still have an interest, let me know.

Comment on Six letters by Joe Williams

Joe Williams — Thu, 17 Sep 2009 16:05:02 +0000

Slow love woos elves.

Comment on User registrations by Tanner Lovelace

Tanner Lovelace — Tue, 15 Sep 2009 15:07:59 +0000

You could always switch your comments to using one of the comment plugins that handle user registrations (i.e. I use Intense Debate on my WP blogs).

Comment on Eight years ago… by Lee Bennett

Lee Bennett — Fri, 11 Sep 2009 16:04:43 +0000

A few photos of my then-newborn nephew as well as at Mount Rushmore are at http://photos.dtpbylee.com/Washington2001

Comment on Apple, please stop removing pre-existing functionality by Lee Bennett

Lee Bennett — Tue, 01 Sep 2009 15:27:21 +0000

I haven’t confirmed this yet, but apparently, people are finding that while the relocation of QuickTime 7 Player to the Utilities folder is automatic if you’d already had a Pro license, but that the Optional Installs on the Snow Leopard disc includes the QT7 player that you can install if you didn’t previously have QuickTime Pro. All that remains to be confirmed is whether this QT7 Player includes all the pro features even if you didn’t previously have QuickTime Pro.

Comment on Apple, please stop removing pre-existing functionality by Lee Bennett

Lee Bennett — Mon, 31 Aug 2009 20:39:47 +0000

The deal with playback speed, both forward and backward, was more beneficial to me just for quickly navigating around to find specific points to do editing, especially since this method let me still hear the audio track. No audio scrubbing when simply dragging the playhead around. For general playback, no, I seldom had much use of playing at the wrong speed.

Comment on Apple, please stop removing pre-existing functionality by ssp

ssp — Mon, 31 Aug 2009 08:15:11 +0000

The inability to play backwards at 1× speed does seem odd (but, frankly, for a playback application I never understood the point of playing back at the wrong speed anyway, particularly as modern compression formats make performance when doing so horrible). I found that you can option-click the rewind button to play backwards at ?1.1× which should be close).

I am not into video editing, so I don’t mind too much in practice. Perhaps this scrapping of features can be seen as a way to make the _Player_ in the application’s name more dominant. In a good case scenario Apple will reinstate the ‘Pro’ tax and start selling a QuickTime app that’s aimed at simple editing and a bit less clumsy than the old QuickTime Player. That could turn in into a ‘win-win’ situation.

Comment on Iconfactory missed the point by Lee Bennett

Lee Bennett — Tue, 19 May 2009 05:00:51 +0000

Craig – thanks for your answer. I acknowledge that there’s probably a lot of frustration that TwitPic uploads frequently error out. That part was never in dispute. The point of contention I had, according to my understanding, is that, by handling it the way Twitterrific currently does, the tweet would appear, sans TwitPic URL. This means that a tweet could appear on my timeline such as, “Have a look at this weird guy I saw on the street,” but there’d be no picture to go along with it. Yes, it would be fantastic if the picture sites, like TwitPic would collaborate with Twitter clients such as yours to send the text after the fact. For the present, however, which is the lesser of two evils? Your feeling seems to be that it’s better to only have one of the two halves (the picture) fail, whereas I, and others I’ve chatted to, feel like the two–the tweet and the picture–make up a whole and one shouldn’t appear without the other.

Comment on Iconfactory missed the point by Craig Hockenberry

Craig Hockenberry — Tue, 19 May 2009 03:42:31 +0000

Lee, we have never supported the uploading of tweets to TwitPic or any other service. We only upload photos and then link to them.

The scenario we’re trying to avoid is this:

1) You upload your photo and text to TwitPic.
2) TwitPic has an error and doesn’t forward your tweet to Twitter.
3) You and your followers never see the tweet or the picture in your timeline.

The root of the problem is that step #2 happens A LOT.

Our long term goal is to change how posting text to the photo service works — we’d like to send them the text AFTER we know that the photo was successfully uploaded AND the tweet was posted to Twitter.

-ch

Comment on Finally got the iPhone WordPress app working by Lee Bennett

Lee Bennett — Tue, 19 May 2009 02:20:24 +0000

I think the “Tanner” route is the case for most people. It just happens that I use a web host that has a slightly different approach to security than others. Probably wise and safer, but at the expense of having to find a few workarounds. Yes, I do like the app. While I admittedly haven’t had any real need yet, I like knowing I have an iPhone-optimized interface for posting an entry—something I could conceivably do. I would have done so during my trip to Macworld San Francisco if the app had been working when I took that trip. Probably the only thing that bugs me is that even though I can read and manage/approve/disapprove comments made to my blog, I cannot use it to post comment responses.