Employee Perks and Unlimited Paid Time Off

paid time offBy Lindsay Bell

The last ten years or so have seen dramatic change for many industries and organizations.

Millenials want better and more flexible working environments. Competition is high for those who are digital whizzes.

And many bosses, where they can, are realizing that ‘work from home’ setups actually work, and are often more efficient when it comes to employee satisfaction and the amount of work that gets done during an average work day.

Treehouse, an online education company that teaches people about technology, even instituted a four day work week! They pay their staff the same as a five day week, and they don’t “force” them to work 10 hours per day to make up for the day lost – BUT they still have set goals and everyone works their butts off to be sure those goals and weekly work assignments get done in four days instead five.

As mentioned in the article, their CEO believes his company benefits from better output and morale. “The quality of the work, I believe, is higher,” he said. “Thirty-two hours of higher quality work is better than 40 hours of lower quality work.” [Read more...]

New: Closed Lists for Paid Mailings and Memberships

Up until now, any active mailing list at FeedBlitz has been fully open; i.e. anyone could join.  Today we’re announcing a new capability: Closed lists.

A closed list acts like any other mailing list here, except in one key aspect: Subscribers can only be added via the API, a parser, a trigger, or by the list administrator.  So the general public can’t join, unless you allow them to.

That extra degree of control is great for membership sites, or if you want to charge people to join your list.  For paid lists, you can wait for the payment to come through and add the new subscriber via the list’s dashboard, or you can integrate your shopping cart via a parser and automate that as well.

Switch a list from open to closed via the list’s “Settings” button, then click the “Anyone can join this list” to flip the setting in the “Subscriber Interactions and Notifications” section.

So: If you wanted to create a closed or paid email newsletter through FeedBlitz, now you can!

P.S. Although this is obvious, it’s worth mentioning: Once a subscriber is on your closed list, they can forward that email to anyone they like, because that’s true of any email.

Featured Images, Thumbnails for your Blog Mailings

Images are a powerful form of communication. The phrase “a picture speaks a thousand words” exists for a reason, after all, and many of you use images to great effect in your blogs.

Sometimes images in mailings can pose something of a challenge, however. Large images on your blog can be resized by your blog’s software, or theme, or a plugin – but when that image shows up in your RSS feed or mailing, the components necessary for that resizing aren’t always there. Or, sometimes the email app will get the image resized incorrectly (I’m looking at you, Outlook).  Result: Ugly emails.

Images also come in unpredictable sizes, varying heights and widths, which can look OK in a blog, but in a multi-post mailing, can also yield aesthetically displeasing results (or: Ugly emails).

Or perhaps you only want one image in your mailing, not all of them.

Enter FeedBlitz’s Advanced Template Editor (a.k.a. the ATE) and three new tags designed to help you, or your email graphic designer, deliver consistently sized and located images in your mailings. If you’re impatient, you can see these tags at work in this image here (and click through to the current, live preview of the Krazy Coupon Lady’s latest finds).

There are three new tags which you can now use in the ATE, all of which should be placed between the <$BlogPosting$> tags which demarcate where the post content goes into the layout.

<$BlogItemThumbnailImage$>

This is the all-singing, all-dancing tag that, in one fell swoop, drops a perfectly sized thumbnail image into your mailing.

It has four optional attributes: width, height, background, align.  Most of the time, you will only need to specify the thumbnail’s width, as in the following example, which makes the thumbnail 160 pixels wide:

<$BlogItemThumbnailImage width="160"$>

Here are the available attributes and parameters:

Width Force the image to be this many pixels wide. Optional.
Height Force the image to be this tall. Optional.
Background Specify a background color for any space in the thumbnail slot the image doesn’t occupy. Optional: leave blank for transparent, which is the default. Color specification is HTML / CSS, so for red you can use “background=#FF0000″ or “background=#F00″ or “background=red”
Align Force the image to float left or right. Optional: the default is left aligned.

 

The image will be resized to conform to the parameters you give. Specifying both width and height can lead to some email apps stretching the image oddly (hello again, Outlook), so we don’t recommend that. Pick one! If there is no image in the post, FeedBlitz will substitute in and resize your RSS feed’s logo, if there is one. If that isn’t specified, FeedBlitz will insert a transparent image of the appropriate size to keep your layout consistent.

The thumbnail image tag is a hard working template element. It goes on to link the thumbnail image to the post’s page on your site, so clicking the thumbnail takes the visitor back to the post itself.  It uses the first non-trivial image from your post (using the <$BlogItemFeaturedImage$> tag I’ll get to next), and makes sure that the image doesn’t appear on landing pages the template powers, such as hosted subscription forms.

If you include the blog’s copy in the mailing (which 99.9% of bloggers do), this tag also removes the discovered featured image from the copy, because having the same image appear in the email twice would be silly. All the other images are left alone.

Caveats, warnings and quid pro quos: Using a thumbnail fixes the image size in the mailing; thumbnails therefore won’t resize responsively on mobile devices, unlike other images in the mailing. Or, put another way, specifiying the thumbnail’s width (which is actually what we advise) has the side effect of specifying the narrowest your email can become as FeedBlitz’s responsive design code resizes it on phones and tablets. So specifying a really large thumbnail is possible but perhaps not that smart (Yes, judging. Deal with it). If the first image in your post is smaller than the specified width or height, it will resize up and pixelate. Make sure your thumbnail width is smaller than the images you typically include in your posts.

<$BlogItemFeaturedImage$>

The thumbnail tag above is really a lot of custom HTML wrapped around another new tag, <$BlogItemFeaturedImage$>.

This tag does two things. Firstly, it finds the first non-trivial, non-FeedBlitz-originated image in the post, and then then inserts the detected image tag, or your feed’s logo, or a blank 1×1 pixel if there isn’t one, into the template. Secondly, it then removes the featured image from the post before the post is inserted into the mailing by the <$BlogItemBody$> tag.  It takes no parameters, it just extracts the image and slams it in as-is, which is why the <$BlogItemThumbnailImage$> exists to surround that inserted image with HTML that restricts its size, adds backgrounds, etc.

<$BlogItemText$>

One of the great things about FeedBlitz is that we have smart summaries. Unlike every other email service out there, when you truncate a post, we retain formatting, images, links etc., which increases the subscriber engagement with the email because people like formatting and images. Win, right?

But there are some – a very few – cases where actually, no, this isn’t useful at all. Enter the <$BlogItemText$> tag, which adds a plaintext version of your post’s copy, truncated according to your list’s settings, instead of the usual formatted version.  A great use of <$BlogItemText$> is together with the thumbnail image tags. Use the thumbnail tag to extract the image and locate / resize it consistently, then provide a simple plain text excerpt to go with it.  Easy, elegant.

Galling as it was, though, we had to dumb FeedBlitz down to make this happen.

Of course, we didn’t dumb it down too much ;)

Unlike other services, we still preserve line and paragraph breaks. Even if your post is presented as plain text, it should still be readable, and FeedBlitz makes it so.

How to Get There From Here

The Advanced Template Editor is accessed from your mailing list’s dashboard via the “Design” button.

Candle in the Dark: How Unsatisfied Customers Help Business Growth

customersBy Sookie Lioncourt

The most significant aspect of any business is its consumer base.

Without them, your business will not generate any income. But, if you have customers – chances are, you’ll also have unhappy customers. Unless you’re perfect. Which, let’s face it, no one is.

Unhappy customers (whether it is product related, price related or customer-service related) can be very challenging to handle, especially when they are active online.

But, just because they aren’t satisfied with your services does not necessarily mean that you can’t turn them around. Dissatisfied customers can be your most valuable assets.

Below, we’ll discuss how you can benefit from your discontented customers. [Read more...]

FeedBlitz and the Heartbleed vulnerability

We’ve been asked this a few times recently, so for the record: FeedBlitz isn’t vulnerable to the Heartbleed vulnerability.

FeedBlitz doesn’t use the platforms affected, and we don’t use OpenSSL for SSL encryption on our servers.

Does that mean you shouldn’t change your password here at FeedBlitz? Not exactly. If you use the same password here that you do on an affected service then maybe you should, yes.

But ZOMG. Can we talk a little about risk here, please? Do you hand your credit card to a waiter to pay for your romantic dinner? Do you give your card number over the phone when ordering something from a local business? If you have ever done so, you’ve willingly given your payment information to a complete stranger and probably thought nothing of it.

How risky is that?

Which is not to belittle the scale of the potential risk that Heartbleed poses to the Internet’s security infrastructure. But on an individual level, you’re probably more likely to have your wallet lifted at the next major league ball game you go to.  I’m personally currently unaware of any proven cases of this vulnerability having been exploited successfully for any kind of mass compromise.

Sturm, drang and panic. A heady, volatile and newsworthy combination to feed into the 24 hours cable news cycle.

How about some facts, instead of could haves and might haves. Wouldn’t that make a pleasant change?

As a  reminder, here’s the one thing hackers and phishers know: They get more mileage by phishing, spoofing and social engineering (i.e. pretending to be someone, or something you trust; or simply conning you into willingly handing over secret information).

Which segues nicely into my planned DMARC post, which I’ll probably get to on Thursday now.

Authenticating your Emails with SPF

Following up on last week’s post about Yahoo’s DMARC policy change, here’s how to authenticate mailings that (a) you send, and (b) we send on your behalf.  Before going into this, I want to make this point abundantly clear:

FeedBlitz automatically authenticates email we send; you don’t HAVE to do anything.

And for the vast majority of our clients, that’s perfect! That said, let’s say you want to authenticate email you send for your site’s domain anyway, and email we send for you as well. OK, sure, can do. In order to make that happen, you must have the ability to add a TXT record to your DNS settings, because that’s how SPF (the authentication protocol we’re going to set up) works.

Got that ability? Ok, good. Here’s what you have to do.

If you don’t have an SPF record already in place, you can simply add this as a TXT record to your domain’s DNS:

v=spf1 include:mail.feedblitz.com ~all

What this says is “hey, I’m an SPF authentication record for <my site’s domain>, anything that mail.feedblitz.com sends on my behalf is OK, anything else you should look at closely.”  This SPF entry in your DNS will authenticate email sent by FeedBlitz for your site based on your SPF records (remember, FeedBlitz’s emails already authenticate based on our SPF records, and your SPF entry won’t change that). It also invites providers to look more closely at other emails that purport to be from you. If this makes you nervous, replace “~all” with “?all” but then the SPF record doesn’t really say much of anything; it’s effectively a test entry that will, in the real world, have no effect at all.

You should therefore think about email sent by, or through, other systems on your behalf. Let’s say that you’re using Google Apps, and you send email for your site through your Google Apps account. Here is what Google help says should your SPF record be:

v=spf1 include:_spf.google.com ~all

So, to tell receiving ISPs that it’s really OK for your domain to have email sent on its behalf by both Google Apps and FeedBlitz, here’s what you should set your SPF record to be in your DNS:

v=spf1 include:_spf.google.com include:mail.feedblitz.com ~all

In other words, you simply add include:mail.feedblitz.com to any current SPF record (or the example given to you by your provider), and email we send on your behalf will authenticate using both our SPF record and yours. So for the above record, Google Apps will authenticate as well as FeedBlitz. The same approach works whatever ISP or service you use to send your site’s emails through. All you need to do is find out is what you need to have for your SPF record for the system you typically send email through, and then add the include:mail.feedblitz.com text to it. Your provider should be able to help you with the record you need to add for their systems.

Now, if you research SPF, you will see that some recommend using “-all” (dash all) instead of “~all” (tilde all) at the end of the SPF record.  It’s a critically important difference, and I really don’t like that advice for bloggers and businesses without dedicated and email-savvy IT staff. You should think very hard before using the “-all” version. Here’s why.

The tilde version “~all” says “Look closely at email that doesn’t authenticate, but we’re not saying it’s definitely bad” — effectively leaving ISPs to use their best judgment to determine whether email that purports to be from you but doesn’t authenticate is spam (or not). I certainly recommend using this option, at least at first. It’s the safest way to avoid valid email from you being accidentally junked. ISPs are really pretty good at blocking junk based on things like IP reputation, content filters and other techniques. Most of the time, this is going to be A-OK.

Switching to the dash version “-all” says something very different: “Any mail that does not authenticate is definitely junk.” That’s something you should only set if you’re really, really sure that statement is true, because now you’re saying anything and everything else is absolutely spam.

How could this possibly go wrong? Well, for example, say you send an email from home via your cable provider’s email servers instead of Google Apps or FeedBlitz for your blog’s domain, assuming that is how you’ve set up your SPF record. The “-all” now says that the email you just sent is junk. As a result, it might not be accepted by your recipient’s email provider at all, and if it is, it will certainly be routed to their spam folder. The same might happen if you use a third party service, such as a shopping cart or help desk system, that sends mail on your behalf, but not using the mail systems you identify in your SPF record. Or, say you switch hosting services or email providers and forget to update the SPF record you created several years ago. All your email will be junked, thanks to that “-all”, until you fix your SPF record.

So you need to be very, very sure that email will only be sent from the domains and IP addresses that you specify in your SPF record before you switch to the “-all” version of SPF. And you need to remember to update it as you add, switch or drop online service providers.

Now you know how to set up SPF for your domain. After you do this, you should ensure that emails we send on your behalf are from an address on that domain, and not a generic consumer provider, so that the authentication you set up can take effect.

The flaw with SPF, which is why it’s imperfect, is that other spammy systems might authenticate correctly for themselves (because of their own SPF records) but still spoof your address. That’s the situation DMARC addresses, (and what caused all the problems with Yahoo), and I’ll cover that tomorrow.

FeedBlitz: Rewind the Week

FeedBlitzIt’s time again here at FeedBlitz to Rewind the Week, and bring you some of the tech and business news you might have missed while you were busy taking over the world (that’s what you’ve been doing, right?).

This week, headlines were dominated by tech news, and not all of it was bad. Maybe it’s best to start with the good news—well, it’s good news for Dropbox, anyway … [Read more...]

Cop Out of Content Creation With 10 Great Content Curation Tools

Content

By Sharon Hurley Hall

Have you started curating content yet? Content curation has become an important part of the content marketing mix and it seems that everyone’s doing it. It’s a way to collect what’s most interesting about a topic and share it with others.

It might seem a cop-out to make your mark with other people’s content (and yes, let’s face it, it’s a way to connect with your target audience without having to do the heavy lifting of creating all the content yourself).

But there are lots of different ways to curate content, as Moz points out, and in the best case, you can add value to the content you collect with your own commentary.

In this roundup I’ll bypass those that are simply aggregators to focus on tools that allow you to add your own insight. Here they are: [Read more...]

DMARC’s (Un)intended Consequences: Why Yahoo is Bouncing Your Emails

Let’s get straight to the point. Over the weekend, possibly last Friday night, Yahoo changed a key DNS (domain name system) entry. The effect was brutal: It started bouncing out every email that said it was from a yahoo address, but had not been sent by a yahoo server.

So, if your email said it was from blogger@yahoo.com but was in reality sent by a third party, such as FeedBlitz (bear in mind this is not targeting FeedBlitz specifically, and is not a blacklisting; this applies to any third party service and I’m using us as an example), then if you sent your email over the weekend, it was bounced by Yahoo.

That’s bad, and it gets worse. It was also bounced by Gmail, because they are paying attention to the DNS record Yahoo changed, called a DMARC record. Bottom line: Your emails didn’t get through, if you specified your “from” address to be a Yahoo email.

They didn’t get routed to junk or the spam folder.  They were bounced out and never accepted for delivery, if (to repeat ad nauseam) you specified your “from” address to be a Yahoo email account. [Read more...]

FeedBlitz: Rewind the Week

FeedBlitzIt’s that time again, time to rewind, and take a look at some of the stories you might have missed this week in the world of tech, business, or sometimes, even the beauty of art.

This week’s FeedBlitz: Rewind the Week touches on all three of the above, with a special ‘hat tip’ towards innovation, and how young people are using today’s latest technology (Google Glass, 3D mapping) to foster change – even if that change is just in how we see ourselves.

Let’s get started. First, nothing says Friday like a ‘tech scandal’, right? [Read more...]