tags: author

Action executed in 0.000

Each Tag


Common tags - number of posts

web design (1), performance (1), Etsy (1), SSL (1), registration (1), comment (1), device (1), lab (1), TrickleUp (1),


Blog | Lara Hogan

Lara Hogan head shot

I'm a Senior Engineering Manager at Etsy and the author of Designing for Performance and Building a device lab. Follow me on Twitter, read my blog.

I champion performance as a part of the overall user experience, help people get comfortable giving presentations, and believe it's important to celebrate career achievements with donuts.

url: http://larahogan.me/blog/

type: person, format: blog

Minor Author Changes to TrickleUp

I've made some minor changes to TrickleUp. For those of you blinking, it's the software that runs my site. The change is to the author information of posts and it's really just aligning the author ascpect of posting for a much larger authentication change later.

Previously the comment forms had 3 fields: name, email, and website -- just like most blogs. Now on those blogs, i have a problem with how easy it is to impersonate somone. I doubt it would happen among my friends, but if TrickleUp ever entered widespread usage, some other people may appreciate that feature.

When someone entered their name, email, and website trio, TrickleUp would create an account in the database, and send a cookie to the user. This is great for new users, but most people posting to my site are returning users.

I realized this form is not the new user registration form, even if it was a form within a form. So the registration form is separate. The comment form always allows an anonymous posting. If you're logged in to my site you may also attribute your comment to yourself.

In terms of code, it's cleaner this way.

With all that cleared up, i can focus on the real work, SSL client authentication. Just think, if we each had an SSL certificate, we wouldn't need numerous passwords.