Philosophically, I’m completely against Google’s AMP project and AMP for Email, too. I will always side with the open web and the standards that power it, and AMP is actively working against both. I’m all-in on a faster web for everyone, but I just can’t get behind Google’s self-serving method for providing that faster web.
Saturday, February 24th, 2018
Tuesday, January 30th, 2018
Famous first words
Thursday, January 25th, 2018
This looks like an interesting alternative to TinyLetter for writing and sending email newsletters, like all the cool kids are doing.
Wednesday, July 19th, 2017
Writing Hacks: The Adafruit Guide to Being Excellent to Each Other in Emails « Adafruit Industries – Makers, hackers, artists, designers and engineers!
Language is a technology. It’s a particularly strange one that’s made of squiggles and sounds and maps of meaning, but like any other technology, it’s hackable.
Good advice on reducing unintended stress via email.
Negativity bias is a tendency for negatives to have a greater effect than positives on our emotional state.
For email this can have radical effects: positive emails seem neutral, neutral emails seem negative, and even slightly negative emails can lead to actual, measurable pain.
Even with the best of intentions we can come off distant — or just plain mean.
Sunday, March 19th, 2017
A free ten part email course on web typography for designers and developers. The end results will be gathered together into a book.
Thursday, February 9th, 2017
Wednesday, August 10th, 2016
There’s this really common use-case I’ve seen at Codebar and Homebrew Website Club, where someone is making a static site, but they just want a contact form that sends data via email. This looks like a handy third-party service to do just that. No registration required: it’s all done via the value of the
action attribute in the opening
Sunday, August 7th, 2016
The ancestors of the Internet were kind enough to give us a communication standard which is free, transparent, and standardized. It would be a shame to see the tech communication landscape move further and further into the world of locked gardens and proprietary schemas.
Wednesday, January 7th, 2015
Dan has started writing up what he did on his Summer hols …on a container ship travelling to China.
It is, of course, in the form of an email newsletter because that’s what all the cool kids are doing these days.
Saturday, December 20th, 2014
This is a nifty little service: if your site has a webmention endpoint, people can comment on your articles by sending an email.
That means you can comment on any post on my site by sending an email to firstname.lastname@example.org (in the email, include the URL of the post you’re commenting on).
Tuesday, November 11th, 2014
Saturday, May 18th, 2013
The litany of open standards that Google has been abandoning: RSS, XMPP, WebDav…
Wednesday, March 6th, 2013
Revolutionising the way you revolutionise email.
Thursday, January 10th, 2013
Trent and I answered a few questions for the Responsive Design Weekly newsletter.
Thursday, December 27th, 2012
Here’s a treasure trove of web history: an archive of the www-talk list dating back to 1991. Watch as HTML gets hammered out by a small group of early implementors: Tim Berners-Lee, Dave Raggett, Marc Andreessen, Dan Connolly…
Monday, October 1st, 2012
CSSquirrel shares my feelings on the email notification anti-pattern.
Tuesday, September 18th, 2012
Jason has set up a mailing list for open device labs. If you are running one, or thinking of setting one up, you should sign up to share ideas and knowledge.
Saturday, September 15th, 2012
My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update) from James Craig on 2012-09-15 (email@example.com from September 2012)
James Craig is a mensch. This is how you give feedback to a working group.
Tuesday, September 11th, 2012
The email notification anti-pattern: a response
Give it to us. I applaud you shouting at us from a rooftop. I also hate defaulting to all notifications and agree that it was a douchebag startup move but can assure it was one made accidentally - a horrible oversight that the entire team feels bad about and will work to amend for you and the rest of our users.
We try to be a site for the common user - nothing like Facebook taking cheap shots wherever they can. I hope we haven’t forever turned you off from our site. Relaunches are hard and mistakes were made but nothing like this will happen again.
Apart from the use of the passive voice (“mistakes were made” rather than “we made mistakes”), that’s a pretty damn good response. She didn’t try to defend or justify the behaviour. That’s good.
She also asked if there was anything they could do to make it up to me. I asked if I could publish their response here. “Yeah, feel free to post”, she said.
I think it’s important that situations like this get documented. It could be especially useful for new start-ups who might be thinking about indulging in a bit of “growth hacking” (spit!) under the impression that this kind of behaviour is acceptable just because other start-ups—like Findings—implemented the email notification anti-pattern.
As Lauren said:
I think every startup manages to mess up one of these at some point in their life, either willingly or unwillingly. A clear listing of all offenses could be useful to everyone.
The purpose of this pattern library is to “name and shame” Dark Patterns and the companies that use them.
- For consumers, forewarned is fore-armed.
- For brand-owners, the bad-press associated with being named as an offender should discourage usage.
- For designers, this site provides ammunition to refuse unethical requests by our clients / bosses. (e.g. “I won’t implement opt-out defaults for the insurance upsells because that practice is considered unethical and it will get you unwanted bad press.”)
The email notification anti-pattern isn’t yet listed on the wiki. I’ll see if I can get Harry to add it.
The email notification anti-pattern
I see you have introduced some new email notifications. I have also noticed (via my newly-overstuffed inbox) that by default, these new email notifications are checked.
WHAT THE FSCK WERE YOU THINKING‽
Sorry. Sorry. I lost my temper for a moment there. And the question is rhetorical because I think I know exactly what you were thinking …“traction”, “retention”, “engagement”, yadda yadda.
I realise that many other sites also do this. That does not make it right. In fact, given the sites that already do this include such pillars of empathy as Facebook, I would say that this kind of behaviour probably has a one-to-one correlation with the douchebaggery of the site in question.
You’re better than this.
Stop. Think. Spare a thought for those of us who don’t suddenly—from one day to the next—want our inboxes spammed by emails we never opted into.
Didn’t anybody stop to think about just how intrusive this would be?
As part of the Services, you may occasionally receive email and other communications from us, such as communications relating to your Account. Communications relating to your Account will only be sent for purposes important to the Services, such as password recovery.
Contrary to appearances, I don’t want to be completely negative, so I’ve got a constructive suggestion.
How about this:
If you’re about to introduce new email notifications, and all my existing notification settings are set to “off”, perhaps you could set the new notifications to “off” as well?
All the best,