Archive for dot com

answerable

I think we are all aware by now that Automattic are generally averse to having official policies on anything much, apart from affiliate links/adsense/spam/miscellaneous profiteering etc. being Teh Evil (unless they are doing it, in which case it is OK). Official policies, like, totally stifle your freedom to make the rules up as you go along. Hence, while having over a dozen tagegories on your posts probably will get you kicked out of the global ad tag pages and labelled a spammer, it’s ‘not a published rule‘ (in fact, the exact nature of the rule is a closely guarded secret) and the FAQ blithely insists there is no limit on the number of tags you can have. Who knows, one day Scoble might experience an urge to tagspam. It’s so much easier to change the rules if they’re obscure in the first place.

Inevitably, however, sometimes the freedom to invent policy on the hoof leads to staff inventing entirely different policies on the same thing without each other’s knowledge.

Last January, Mad at blog-well.com appealed for the ability to redirect traffic from their old wordpress.com blog to their new wordpress.org blog. Matt responded in comments with a workaround:

Did you try adding the domain to this blog, making it your primary URL, and then switching the DNS back to GoDaddy? It should redirect all visitors from blogwell.wordpress.com to the new domain on the new host, at least as long as you pay the 10/yr for parking.

Yay! Mad was very happy and grateful for this solution, as were several people who showed up later in the same comments thread. In response to the support issues arising from this thread, six months later Mad produced a PDF tutorial on how to make the move from .com to .org. Yay again.

Unfortunately, Matt appears to have neglected to tell his head of support that he has been promoting this feature, and when a year on from Mad’s how-to guide somebody shows up on the forums asking for clarification Mark censors the link to the tutorial, says it’s ‘unsupported’ and could stop at any time, then suggests that accounts caught doing it could be nuked. Raincoaster backs him up, having experience of seeing such blogs deleted.

Look, I know it can be hard for everyone to be on the same page because you’re all in different countries in different timezones doing different things, but your communication breakdowns should really not be the users’ problem. The original poster’s question was very simple: is it allowed, or is it not allowed? That should be answerable with ‘yes’ or ‘no’. Qualified ‘yes’ and ‘no’, perhaps, such as ‘you would need to have hosted your blog here for x amount of time’ or ‘you would have to have bought your domain through us’, or ‘only if you opt out of global tags’. Or even, if that would be too boring and straightforward to fit with the way you like to do things, the standard business-blog response of ‘contact support detailing your individual circumstances so a decision can be made’. But still, you know, some sort of reasoning other than the whim of whoever happens to be answering the question today. People who are promoting solutions given to them by your boss can be forgiven for thinking the solution is company-approved.

Comments (13)

slaughtering sandbox?

There are so many responses by bubel on the forums about how you absolutely can NOT use your own themes on wordpress.com that not only am I now convinced the theme marketplace has finally been shelved but I’m starting to think custom CSS must be on the way out as well :( This user wanting multiple themes on the same blog, for example, could have been profitably directed to Sandbox, where anyone with a fair degree of CSS competency can achieve different looks for different types of pages. If it was a volunteer giving that answer, I’d just shrug my shoulders and assume they didn’t know what can be achieved with the CSS upgrade, but if it’s staff you have to assume that they have some other reason for not mentioning it.

This sucks, as I was seriously thinking of offering custom custom CSS skins for a small fee even though such services are officially discouraged. Ah well. I should really apply my efforts to learning Drupal instead.

Comments (16)

never mind the ethics, feel the dollars

Comments (20)

world of penguin

In case you missed today’s bout of penguin spam, I’ve archived it for your viewing pleasure here. If you or your family live in the US and have been personally affected by the issue of allowing children to blog here without parental consent, you may be interested to learn that the FTC have made it much easier to file a complaint about COPPA violations. If you are a staff member of Automattic, they have produced a useful checklist to help you comply with US data protection law and pre-empt any such complaints here.

Perhaps once they have ensured that they’re not going to get hammered with a fine they will be less afraid to deal with children when they misbehave. Right now, when they ban a child they run the risk that they or their disgruntled parents are going to grass them up and let them in for a world of pain. Taking personally identifying information from children and claiming to be unable to delete it? Inadvertent pron on kiddy dashboards? Ads for dating agencies on kiddy blogs? World. Of. Pain. It’s a good thing that penguins and their guardians are neither that smart nor that malicious.

(I’m also not wholly convinced that ‘your mom!‘ is an especially constructive approach to take towards trollkids, but if staff think it’s acceptable who am I to argue?)

Comments (18)

bitchery in slugs

Isn’t it strange how when you write an article slagging off TypePad and praising WordPress you are inevitably ‘honest’ and ‘insightful’, ‘interesting’ and ‘eloquent’, and when somebody from Six Apart tries to make a counterargument they are ‘venomous’ and guilty of ‘falsehoods and misdirection’?

Sadly, my comment on Lloyd’s post is still languishing in moderation. I’m sure this is merely an oversight, since nobody would tell their readers ‘Please challenge me on my views!’ if they were going to censor dissenting comments. I’ll reproduce it here for now, and link to it when it’s published:

I don’t see that Anil’s any more abrasive in his defence than Matt is when people come out attacking WordPress. (That is, possibly a little too forthright, but hey, fanboys are annoying.)

For someone with ‘extensive experience of both platforms’, Michael seemed strangely confused about the distinction between wordpress.com and .org and TypePad and MT, attempting to draw direct comparisons between Automattic’s non-hosted software and Six Apart’s hosted service when it suited him, and switching back to comparing TypePad with wordpress.com when that fitted his argument better.

For example: he thinks TypePad makes it too difficult for people to add third-party widgets, conveniently forgetting that wordpress.com doesn’t let you add any third-party flash or javascript widgets at all. But he thinks it’s cool that wordpress.com won’t let you use Adsense, conveniently forgetting that wordpress.org has dozens of plugins which make it easy.

I’m afraid that by the point where he claimed the separation of WordPress and WordPress MU was ‘a different developmental strategy’ rather than a historical accident I’d lost all patience. WordPress MU isn’t a fork of WordPress; it’s a fellow fork of b2 that got swallowed up by its sibling. Incorporating multiblogs into core would have broken backward compatibility so much it was no longer an option. And it’s not for people who need to run a handful of blogs off a single installation, it’s a specialist tool for site admins who need a blogfarm. It would make more sense to assess it alongside the Livejournal open source code than to pit it against Movable Type. http://mu.wordpress.org makes this perfectly clear, but proselytising fanboys trying to push it as ‘the upgrade to the upgrade’ don’t do anyone any favours.

I left out how he’s praising the 2.5 interface when Matt has already pretty much acknowledged it was a failure. Or how he thinks monthly security upgrades are cool because they’re a ‘a testament to a vibrant developer community’, which comment alone constitutes the loopiest piece of fanboying since ‘the blogging market is c.l.o.s.e.d.’

But no. Mocking the fanboy is a cheap distraction. My point is how nasty things are getting now the market is contracting. I’m not talking about the consumer market so much; people are still starting new blogs, though in the current economic climate they’re going to be less willing to spend money on them and that’s not good for either company. I’m talking about getting more funding, or going public, or finding a parent company willing to take you under its wing and shield you from the hard times ahead. These things are not going to be as easy as they were a couple of years ago. You are competing for increasingly scarce resources. It’s easy to be nice to each other when things are going well, but these days it’s survival of the fittest, and the way these spats are conducted both sides seem about equally worried.

Which would be odd, if Six Apart really were the underdog; but they’ve stolen a march on Automattic by making their anti-spam service free to everyone. Short-term this shouldn’t make too much difference as most paid-up subscribers won’t be interested in switching till they’ve got their money’s worth, but long-term it threatens one of Automattic’s major revenue streams. That’s the real reason the gloves are off again.

And the accusations of being splog-ridden have evidently hit home because they’re, um, true. How could they not be? Akismet can’t hope to catch them all at sign-up and you’re relying wholly on volunteers to report the ones they happen to see. Plus, all reports have to be dealt with individually by support staff, who are generally sort of busy with support. At least they’ve blocked drmike’s wordpress.com account now so they won’t be getting any more of those pesky spam reports from him. That should help with the workload even if it doesn’t help with the splog situation.

Comments (26)

did akismet break or something?

No. I did.

This is unacceptable. Automattic want to control who gets to comment on my blog. Even spam gets sent to a queue where I can approve it if I want. Hence, I have emptied the contents of my Akismet queue onto my front page, since it is clearly more acceptable to our hosts than comments from my readers.

Also, if you must bitch about people in private blogs, I find that spaces or other miscellaneous characters in the url are very good at preventing those embarrassing trackbacks, assuming of course that your readers are au fait with the mechanics of copy/paste. :roll:

I was going to write a post about how it might be a good idea to carry out usability testing before a major admin redesign rather than after, and how it might also be sensible to rip off the Tiger interface before paying Happy Cog to make you something custom, but it will just have to wait.

Comments (31)

radio button bling

Oh, polls. People have only been asking for them for a couple of years. More fuel for raincoaster’s theory that they’re piling on the geegaws in preparation for another date with the venture capitalists.

Also, the forums seem an odd place to put that announcement. Either Mark doesn’t have posting privileges on the news blog or PollDaddy aren’t paying enough to get that sort of linkage ;)

Comments (19)

impossibly related

Is anyone else in love with the fact that the ‘possibly related’ spam links at the end of this encourage us to equate usability testing with a cholera epidemic?

(BTW, Toni’s linked post appears to confirm that Hanni didn’t stick around for long. All 21 staff are now namechecked on the about page. )

Meanwhile, on the .com forums, mikecane and fromtheleft have been unpersoned for hating on Sphere and the new dashboard, and this poor guy got shunted over to wordpress.org before being shoved right back over here, none too politely at that (why yes, it was moshu, since you ask). He asked for help ever so nicely, too. It was quite sad.

Comments (23)

Flash! Aaaah!

I know that nothing this mob do should surprise me anymore, but when options posted a screenshot of wordpress.com showing Flash ads for Scientology I admit it, I was shocked.

But I see your screenshot and I raise you Scientology Flash ads on an anti-Scientology blog:

Naturally, wordpress.com spare themselves the flash on their tags pages and content themselves with loads of links:

TOM!!!!
angelina

Also, if you’re bored of linking to the last set of splogshots, how about some wildly inappropriate text ads?

yeah, that's appropriate

I don’t know in which universe it’s OK to advertise ‘Hot & Sexy Single Women’ on a feminist post about an alleged sexual assault, but it’s not mine. Nor do I think this guy necessarily wanted ads for used women’s knickers on his site:

yum

Obviously I would have contacted support immediately to demand that the Thetans not be given airtime on my blogs, except oh, it’s Sunday, and even though they hired a bunch of support staff what, five months ago now? support is still closed on weekends. And I can’t post to the forum because I once asked Matt whether his email was down. I did send a couple of feedbacks to Google, though. For all the good that’ll do. At least they pretend to care.

Also of note: Snap = popup ads disguised as a ‘feature’. Anyone know why neither this nor the Flash are mentioned in the tiny little chunk of disinformation hidden at the bottom of the features page? Or why they decided to encrypt the x-noads code that told us why ads weren’t being served on a given page? The obvious conclusion is that they’re tweaking their algorithms to serve ads to more readers more of the time, and they don’t want anyone to realise.

And now? I’m going to clear out my spam, make my regular backup, and see whether anyone bothers coming over to try and spin this one. I wouldn’t, if I were them. If there’s a single issue that’s destroyed my trust in Automattic, I’d have to say it’s their repeated failure to be honest about the issue of advertising. I’m some months past believing a word they have to say on the subject.

Even if it’s ’sorry’. Actually, especially if it’s ’sorry’.

Comments (34)

yet another post about ads

Andrew on why the long-promised adsense upgrade remains vapourware.

Here’s what I think the basic problem is. Not all wordpress.com blogs are equal. A personal blog by a housewife or student is in an entirely different league from icanhascheezburger or stuff white people like, and ad revenues will vary accordingly. Automattic are not going to launch any feature which leads to them losing money, therefore the cost of the annual upgrade must equal (and preferably exceed) the annual revenue from the blog. But how do they know the annual revenue? And how do they know what it’s going to be in the future? Your bumpalong bogstandard blog could take off like a rocket overnight. An average figure is going to be far in excess of what the people in the long tail are generating (or willing to pay for), and far below what the handful on the threshold of VIP status can bring in. Pitch it too high and nobody’s going to bother paying up, pitch it too low and you risk losing out. Charging everyone different amounts is an impractical adminstrative nightmare.

On the other hand, the current system is working pretty well for them. People don’t see ads on their own blogs, aren’t informed about them when they sign up, and can blog for months and years in blissful ignorance of their existence. Even if they do leave when they twig what’s going on, Automattic have still profited from the period when they were unaware. In any case, they’re less likely to leave than to stick around grumbling at intervals and waiting for the vapourware upgrade. Far easier just to keep things the way they are and claim to be looking into solutions whenever anybody asks. It ain’t broke. Why fix it?

Comments (2)

« Previous entries