The pace of change in web development, particularly with APIs and browser updates, is overwhelming. The constant deprecation and breaking changes cause friction and highlight a lack of empathy for developers struggling to keep up. While frequent updates are important, the current model, exemplified by Chrome, feels too aggressive. This blog post will explore this tension, examining whether we've pushed developers too far, and discuss strategies for a more sustainable pace of change. It will also touch on platform-specific resources like web.dev and the challenge of balancing innovation with support for the broader developer community.
I'm incredibly frustrated with Technorati! It's not updating my blog's information despite numerous ping updates and support emails. This is really impacting my blog's visibility.
I contacted Feedburner support about a full text feed issue, and received a helpful and quick response within 10 minutes. They explained that feeds are limited to 256k and suggested reducing the number of posts or post size to stay within the limit. I am very impressed by their responsiveness to public feedback.
I'm consistently impressed by Yahoo's web service team and their responsiveness to users. In contrast, Amazon's web service support is practically non-existent. My simple question about UK support for the TextStream parameter in AWS has gone unanswered for ages, and I know I'm not alone. Amazon, please step up your game!
My Wikipedia-based AJAX Tag and AJAX Tag 2 scripts were temporarily broken due to an issue with Yahoo's service. Big thanks to the Yahoo developer team, especially Toby Elliot, for quickly resolving the problem! Of all the Web 2.0 APIs I've used, Yahoo's has the most helpful and responsive support.
My blog, Ping Goat, is having trouble getting indexed by Technorati, similar to the issues I've faced with Tagger.com. It seems Technorati might remove blogs from their index if their crawler encounters unresponsive parts of a site. I'm unsure how to resolve this besides raising the issue publicly, as their email support is very slow or non-existent.
I'm continuing my rant about Technorati. While my posts eventually get indexed, I agree with Zoli Erdos's point about their terrible communication. Technorati desperately needs better customer support, including a FAQ or knowledge base. Emailing the CEO shouldn't be the only way to get a response. While I appreciate Technorati's free service and API, the lack of support is a major problem.
In this follow-up post, I want to clarify the issue I had with Technorati. While some of the search results I was looking for are now appearing, my main concern remains the lack of communication from Technorati Support. A simple email explaining the situation, such as a blacklisting, a temporary problem, or an indexing issue due to site downtime, would have been sufficient. Despite this, I still appreciate Technorati.
Technorati is experiencing performance issues and support backlogs, impacting users like myself. Despite sending a support request weeks ago, I haven't received a response. While I appreciate Technorati's free service and its positive impact on my blog's readership, they need to address these support issues. I'll continue using the platform regardless.
