This post with tweetable sentences highlighted by Save Publishing. Image: Screenshot/Webmonkey
Ever wish you could quickly scan an article and find all the 140 character or less sentences so you could figure out which to post to Twitter? The idea had never occurred to me, but now that I’ve used the Save Publishing bookmarklet I have to admit, it actually is pretty darn useful.
Save Publishing is a bookmarklet that highlights any tweetable sentences on a given page. You can grab it from SavePublishing.com or head over to GitHub if you’d like to see the source (Save Publishing is written in CoffeeScript).
The bookmarklet is the work of former Harper’s editor Paul Ford, perhaps better known as @ftrain. Ford says the project started as a joke, but “now it’s serious and I use it all day.”
I expected the novelty to wear off quickly after I used it a few times, but now it’s been a few days and I still find myself using it. Sometimes the faintly ridiculous manages to become useful. What would make Save Publishing more useful is a way to use it within Twitter clients like Tweetbot, but thus far that’s not possible.
Good web typography needn’t be difficult, but typography can be a complicated and sometimes intimidating subject for newcomers.
To help you understand typography a bit better — and create better-looking websites with your new understanding — developer Tommi Kaikkonen created his Interactive Guide to Blog Typography. The guide offers a nice hand-holding walk through of the elements that make for good typography on the web, helping you not just make more readable sites, but understand why they’re more readable.
For most suggestions in Kaikkonen’s guide there’s an interactive button to toggle different line-heights, fonts and measures so you can see for yourself why those elements matter and how they contribute to making your site easier to read.
Among the suggestions in Kaikkonen’s guide are to set a readable measure (the number of characters on a line), frame content with white space (to put emphasis on the main part of the page), avoid pure black for text and, unless you really know what you’re doing, stick with just two different fonts.
There is one part of the guide we can’t totally endorse — the last suggestion, which is to use font-variant: small-caps; even if the font you’re using doesn’t actually have a small-caps variant. With some fonts — the traditional six fonts of web design, for example — you can get away with this, but if you’re using fancier fonts like those from Google Web Fonts or TypeKit this can make for some really awful results; proceed with caution on that one.
The move makes WordPress one of the largest, most reputable online services to accept the fledgling Bitcoin currency.
Bitcoin is an online currency that allows buyers and sellers to exchange money anonymously. According to a post on the WordPress blog, the appeal of Bitcoin for WordPress is that, unlike credit cards and PayPal, “Bitcoin has no central authority and no way to lock entire countries out of the network … merchants who accept Bitcoin payments can do business with anyone.”
The anonymous aspect has made Bitcoin a target for law enforcement agencies, but for WordPress it means that users living in any of the over 60 countries currently blocked by PayPal (and many credit card companies) now have a way to pay for WordPress upgrades and services.
While setting up a basic blog on WordPress.com is free, there are paid upgrades available for custom themes, custom domains or to remove ads from your site.
Bitcoin is in your WordPress. Image: Screenshot/Webmonkey.
Automattic, WordPress’ parent company, accepts Bitcoin payments through Bitpay.com, which has now been integrated into the WordPress.com payment interface alongside the PayPal and traditional credit card options. WordPress is foregoing the Bitcoin “confirmations” process, which would help protect the company against fraud. Here’s an explanation from the FAQ:
We could wait for the first confirmation (typically 5-10 minutes) but we prefer to make the customer experience as smooth as possible. Making you wait for confirmations would virtually eliminate our risk but we’re confident that with digital products like ours the risk is already acceptably low.
Note that while WordPress is accepting Bitcoin payments, it may not work for everything just yet. The option to pay with Bitcoin appears to be limited to upgrade bundles at the moment. Purchasing custom themes or domains by themselves is not currently possible due to what WordPress calls “technical complications.”
WordPress adopting Bitcoin is good news for users in countries like Haiti, Ethiopia, or Kenya, which are often blocked by traditional payment systems. It’s also good news for Bitcoin supporters who now have another, very large, every legitimate company on their side.
Yesterday we got a look at a new software service called Branch, and a discussion between several people who used to work for Blogger, and Anil Dash (who, as far as I know, never did).
Daniel Bachhuber, a friend who works at WordPress, oohed and aahed. I asked him why he liked it so much and he said a couple of things.
The discussion was focused on this topic: How do blogs need to evolve?
I wasn’t asked to be part of the discussion, but since this is the open web, and they made their discussion public, I can say what I have to say. It’s up to them if they want to include it in their discussion.
I’ve even provided the “source code” for this post — just the text with a little bit of structure, and some attributes, with an open architecture for more attributes. So they can do more than link to it. They can “include” it.
The advantage of doing it this way is:
I maintain the original.
It can be included in as many places as it’s relevant.
If I want to update it, I can, and it would update in all the places it is viewable.
Because I can update it, that means relative writing will be kept to a minimum. People can say what they think without making an issue of who’s right and who’s wrong. Because they might not stay right or wrong for very long!
In the thread Evan Williams says that Twitter has a big advantage because it already has all the integration tools people want. It’s understandable he would think that, I suppose, having participated in creating Twitter, but I don’t agree. Here’s why.
When I quoted Daniel in the second paragraph, you wouldn’t believe the dance I had to do to get a link to the tweet onto the clipboard so I could link to it from my post. Even though I’ve done it dozens of times, I still made three mistakes for every action that worked.
Twitter has a 140-character limit, which means that for any kind of complex thought, beyond a grunt or snark (which is likely to be misunderstood because there wasn’t room to explain it) I’m going to have to include a link, which of course must be shortened.
As they point out in the thread, Twitter is a company town. The archive belongs to them, to do with as they please. I have no say in the future uses of my own writing.
Finally, the strongest point — even Twitter agrees it’s not self-contained, because they support oEmbed, which allows them to include content that’s hosted on other servers. However, they aren’t even open about being open. You can only participate if you’re a “partner.” I don’t know who pays who for this, or if anyone pays, but they admit that being open to content hosted elsewhere is necessary, but it isn’t available to the people. In other words, we’ve given up all the beauty of the internet, for what exactly? What did we get in return?
Anyway, even if I was invited to participate, all I would do is post a pointer to this blog post. Because here I own the editorial tools and can make them work any way I want to. There is no 140-character limit. There’s no problem getting a permalink. I own the archive. Sure if you want to participate it’s a bit of work, you have to set up a blog somewhere. That’s okay with me. For a little bit of work you get a whole lot of freedom. That’s a good deal.
Dave Winer, a former researcher at NYU and Harvard, pioneered the development of weblogs, syndication (RSS), podcasting, outlining, and web content management software. A former contributing editor at Wired magazine, Dave won the Wired Tech Renegade award in 2001. Follow @davewiner on Twitter.
WordPress has released version 3.3. Dubbed “Sonny” after jazz saxophonist Sonny Stitt, WordPress 3.3 packs in a number of worthwhile upgrades, including a new responsive design that adapts the WordPress admin to smaller screens.
To get the latest version head over to the WordPress downloads page. If you’re already using WordPress you can update from the WordPress dashboard (naturally we suggest backing up your files and database before you upgrade).
Among the changes that make WordPress 3.3 well worth the upgrade is the new responsive admin design. While there are mobile apps from managing your WordPress site on the go, the actual web admin has never adapted to small screens. That changes with WordPress 3.3 and its new responsive admin page, which reflows content to fit the screen you’re using.
Responsive design — that is, using liquid layouts and scaling media to fit any screen size — is moving into the mainstream in a hurry. The past year has seen several high-profile websites relaunched with responsive designs, but WordPress 3.3 is likely the most widely used site yet to embrace responsive design.
Other changes in WordPress 3.3 include a slicker sidebar with “flyout” submenus which put everything in the admin site just a single click away. There’s also a new drag-and-drop uploader, which means you can drag and drop images from your desktop right into the media upload box in the admin (provided you’re using a browser that supports HTML5′s drag-and-drop API). Behind the scenes WordPress is using Plupload to handle the drag-and-drop features. In browsers that support it Plupload will use HTML5; for older browsers it falls back to Flash.
Anyone working on a site with numerous writers and editors will be happy to know that this release features much improved co-editing support. If you’ve ever seen messages like “Warning: [username] is currently editing this post,” you’ll be happy to know that it will now only appear when someone is actively editing a post. Previously the message would often appear even if your co-writer simply left the window or tab open in their browser.
For a complete list of changes and new features in WordPress 3.3, see the release notes.