Sunday, December 9, 2012

Spam!

Wow -- Has it been this long since my last post?

I guess dates don't lie!  I wanted to drop a note explaining a oh-so-small change to my support site http://support.loghound.com.

For the last several months I've seen a slow but steady increase in Spam from my site.   It started out very small (maybe one spam in a few weeks) but it's recently spiraled out of control to tens or hundreds of spam posts per day!

Up until now I've used the most friendly spam filter available -- it asks you questions like "what day comes after tuesday".  It worked well but either the spammers have figured out a way to game that system or they are some poor human being somewhere to spam my support forum for items like Ugg boots (why Ugg boots?  no idea)

Anyway yesterday I turned on re-captcha (you know, the super-annnoying one that shows you two pictures that are heavily distorted).  So far it seems to be working, my spam load is down  to zero today!

This does, sadly, come at a small cost of being less friendly to ask your questions but honestly it was tough for me to keep the support site clean with so much spam.

I will continue to monitor the situation -- Perhaps in a month or so I'll turn it off and go back to the friendlier version to see if I can make it work.



-John

Tuesday, July 26, 2011

Notablemeals is a finalist!


I'm happy to say that my newest iphone app (Notablemeals) is a finalist in the evernote developer competition. Please vote for it!

ETC_Finalist_eBadge_300x215px

Monday, July 18, 2011

Evernote Competition

I've been working frantically on an entry for the Evernote Developer Competition -- What I eventually came up with was an idea called "Notablemeals" An app that would let you easily capture any meals that were important for you and store them in Evernote.

This is certainly a scratch your own itch kind of app -- I've always weirdly wished I had more memories of important meals  -- A couple of time while traveling I've tried to take a picture of my food but I'm always disappointed with the results (who needs a bunch of random food snapshots mixed in with a picture of the pope -- who needs that?

Anyway I was on a crazy tight schedule (it was about 15 days until the end of the competition and I had *zero* lines of code written) and I knew that if I wanted any hope at all of  being competitive I need some help in the design department.

Fortunately  KaL MichaeL was available and after a whirlwind two weeks I'm happy to say we were able to turn out app in this last sunday evening with 'hours' to spare :-)

 I don't know how it will do in the competition but I do know that I've never felt better about an app.  It's design is great thanks to KaL, it's  code is some of the cleanest I've ever done and it's one of the more intuitive apps I've produced.

I've not submitted it to Apple yet but I hope to do so in the next day or so...  The website should be up in the next few days and I'm looking forward to getting more feedback on ways to improve it.

Monday, May 9, 2011

Wednesday, March 9, 2011

eshox

If you go to this link

http://www.eshox.com/site/packages/pricing.html

You'll see what appears to be some sort of joint marketing or sales deal -- It's not.

I have no idea why Ralf thinks he can do this but I have nothing to do with it and would strongly recommend you not use this service.

Saturday, November 6, 2010

Won't be on the Mac App store (for now at least)

I've been working on my first 'real' Mac App (real in the sense that it's standalone, not RapidWeaver related as such and will actually be completed)

One thing I've decided (for now anyway) is that I will *not* offer it on the Apple Mac App store.

Why?  I want to actually have a relationship with my customers -- If I go to the Apple Mac App store then Apple is in the middle without adding any real value (except perhaps for a bigger reach)-- I never have details of who my customers are and they feel 'extra removed' from me.

When you buy anything from my store I send you a receipt with (among other things) information about how to contact us if there is a problem, when you download a new version you get it from my server with my release notes (via sparkle) and if I find  a problem I can push out a fix in minutes.  -- No such luck with the Apple Mac App store.

By the way my new app syncs flickr & iPhoto, hit this if you are interested in beta testing.

Saturday, September 4, 2010

Handles Content as Compound Value

Bindings in cocoa are un-freaking amazing -- You can change a model parameter and bada-bing-bada-boom the UI updates... Fantastic!

For the most part they just sort of work but I've always been a little confused by all of the options -- Honestly the only one I ever really played with was 'updates continuously' which does what it says (updates happen instantly and it doesn't depend on hitting 'return' or tabbing out of the field.)

The docs are actually here but I've mostly ignored them, until tonight.

Tonight my nemesis was 'Handles Content as Compound Value'


Why? you may ask -- it's perfectly clear what it does.  From the docs:

Handles Content As Compound Value
A Boolean value that determines if the content is treated as a compound value.
Model objects can store relationship-like data in "compound" values and it may be necessary to use a reversible value transformer to translate those compound values temporarily into smaller pieces, that can be displayed and edited individually. See “Bindings Message Flow” in “Cocoa Bindings Programming Topics” for more information.
If YES, the content of a controller is treated as a compound value and—by using a reversible value transformer—will apply changes as a single value to the master model object if anything changes (edits, additions, removals).

 Errrrr.. got that.  What the docs should have said was

Handles Content as Compound Value
Click this if you plan on binding an NSArrayController to a NSUserDefaultsController.

Yup -- That is the magic trick to get it to all work.  If you don't do that many odd things happen but mostly the bindings don't work right.  Apparently (?) the NSUserDefaultsController applies a value transformer for storing the dictionary entries.  Don't ask me why as it's not documented but that appears to be the case.

Just tossing this out for to the googleverse so some person flummoxed why they can't easily bind up their NSArrayController to a NSUserDefaultsController.