GreenReaper's Bibble
[Most Recent Entries]
[Calendar View]
[Friends]
Below are the 20 most recent journal entries recorded in
GreenReaper's LiveJournal:
[ << Previous 20 ]
| Sunday, May 20th, 2012 | | 2:01 am |
The inevitable conclusion
In retrospect, it's obvious - as books become increasingly less relevant to daily life, they are relegated to being design accessories. Still, I'm not quite sure which is more horrifying; that you can buy books by the foot, or that they had to put green on sale. Current Mood: horrified | | Thursday, May 17th, 2012 | | 12:00 am |
| | Thursday, May 10th, 2012 | | 8:08 pm |
American Express's Serve needs some work Serve is (roughly speaking) American Express's response to services like PayPal and Dwolla. I became a member through RevolutionMoney, which they bought out. ( Here's my recent (poor) experience )Don't get me wrong - this was initially my mistake. However, the end result was not a good support or product experience. It compares poorly with competitors and I am more inclined to use and recommend them as a result. I do not really blame the support representatives for this, more the system that they are interacting with, which does not appear to empower them to do their jobs, any more than it empowered me to avoid a support request in the first place (by, say, letting me retarget a pending transaction, or telling me the address wasn't linked with a Serve account). Oh, and the kicker? The third-party support response survey I was sent about the phone call timed out (who lets sessions recycle after thirty minutes?!). When I tried to return, I was told I couldn't submit "another" survey, even though I hadn't finished. So I'm posting it here, for all to see. Update (11 May): Serve's social media group apparently has greater access than the front-line support; my issue was escalated and resolved earlier this afternoon. I hope the underlying issues can also be resolved eventually. Current Mood: aggravated | | Sunday, April 29th, 2012 | | 2:06 am |
Headed to Califur?
I'm planning a trip to Califur at the start of June; I've never been, and it's now relatively close. It's also the site for this year's Ursa Major Award ceremonies, and as there's a chance the sites I work on might win, I'd like to be there in person. I know how I'm getting there, and when - Friday evening to Sunday afternoon - but I don't yet have a place to stay. So: if you happen to have a room for Fri/Sat night, and need to fill some space in it, let me know! (I'll also be at Anthrocon, Thursday night until Monday afternoon, but I've got accommodation for that.) Current Mood: organized | | Sunday, April 22nd, 2012 | | 8:45 pm |
| | Monday, March 26th, 2012 | | 6:25 pm |
| | Thursday, March 22nd, 2012 | | 5:15 pm |
MediaWiki 1.17.3: $bytes != $buffer
Heh. Patched to MediaWiki 1.17.3 on WikiFur - I start testing and getting a strange notice whenever I try to login. Fortunately I know where to go . . . #mediawiki! After talking with the developer concerned, it seems I ran into a bug in the new mcrypt code. Good that we found it, but bad in that it'll need another patch of MediaWiki - and because they're about to make another release, there are three versions that need patching (1.17, 1.18, and the 1.19 beta, plus the trunk). Edit: Found another! Broke email confirmation on 1.17, probably just the display of the expiry time on later versions. Current Mood: geeky | | Monday, March 19th, 2012 | | 3:29 am |
| | Friday, March 9th, 2012 | | 12:22 pm |
| | Saturday, March 3rd, 2012 | | 3:14 pm |
GreenReaper live on FurCast
I'm going to be interviewed on tonight's FurCast. The show starts at 8PM Eastern (in about four hours), though my interview's around 9PM. Wish me luck! (If you have any burning questions that you want answered, you can ask them here.) Edit: The show is over now, but my answers to the above questions are up, and you can catch the actual interview (with more details) at 73:16 into show FC-76. Current Mood: pensive | | Sunday, February 19th, 2012 | | 2:47 pm |
| | Wednesday, February 15th, 2012 | | 10:25 am |
| | Friday, February 3rd, 2012 | | 1:23 am |
Amazon trying to reduce associates' income
Here's some recent changes in Amazon's associate agreement (for people who earn money off links pointing to Amazon's products). Amazon's announcement of these changes focused on the benefit to associates who used a link to myhabitat.com, who have 30 days to earn rather than the usual 24 hours. They failed to highlight the change that stops you earning if a user who clicked your link follows any other link to Amazon, not just that of another associate. Is this reasonable? Arguable. I suspect they've run the numbers and found quite a few people look around before putting an item in their cart, and in that case you might well lose out on what would otherwise have been a valid sale. They are also forcing all non-small-claims disputes to go through arbitration. Wonder which lawsuit that was inspired by. Current Mood: annoyed | | Tuesday, January 31st, 2012 | | 9:50 pm |
Post to Google+ via email
Did you know you can hack together Google Voice and Gmail to post to Google+ via email? I tried it and it works. Now, if only it worked for Pages! I already have an email trigger that fires when people submit to Flayrah - I could easily do one that had the post teaser in it as well. (Of course, if G+ supported RSS import, this wouldn't be an issue . . .) Current Mood: geeky | | Saturday, January 28th, 2012 | | 5:11 pm |
| | Friday, January 6th, 2012 | | 10:29 am |
| | Saturday, November 26th, 2011 | | 9:07 pm |
| | Monday, November 14th, 2011 | | 3:26 pm |
Pre-publication pitfall for contextual advertising
The idea of contextual advertising used by Google AdSense/AdWords is great - match ads to the content, and readers are more likely to be interested. Of course, you'll only get relevant ads if Google can see your content - and this goes beyond robots.txt. For example, many content-based sites have some kind of review process. The editors and submitter may be able to see the submitted piece, but anyone else trying to view the page it's on will get a 403 error - including the 'Mediapartners-Google' AdSense bot. This doesn't work so well if that page is at the same URL as the one your readers access. The bot will try to crawl the piece when it's first submitted, fail, and won't try again until it's "old news", leaving your users with ads irrelevant to the page content. Whoops. The solution is not to show the ad block until the article is published - or provide a crawler login, but do you really want it basing ads off the first draft? Current Mood: nerdy | | Monday, October 24th, 2011 | | 4:56 pm |
| | Thursday, October 20th, 2011 | | 1:09 pm |
|
[ << Previous 20 ]
|