BiteofanApple Archive About Code Twitter
by Brian Schrader
BiteofanApple
Archive About Code Twitter

Twitter's "peace offering" to developers is meaningless

Posted on Mon, 20 Oct 2014

Marco Arment

Companies grow and change. Business needs change. Founders and leaders move on and get replaced.

Especially at Twitter. Twitter started out as a developer-friendly company, then they became a developer-hostile company, and now they're trying to be a developer-friendly company again. If I had to pick a company to have absolute power over something very important, Twitter wouldn't be very high on the list...

Twitter will never, and should never, have any credibility with developers again. Enjoy it while it lasts, but be ready for it to disappear at any moment.

Agreed. Twitter is still a great product, but its not happy with what it is. Twitter is always seeking to ruin itself by trying to be Facebook. I can't wait until something else comes along.

Twitter's "peace offering" to developers is meaningless →

-Thanks for reading,
      Brian Schrader

Making RSS Real-Time

Posted on Sun, 19 Oct 2014

One of the critiques of RSS feeds in a world dominated by Facebook and Twitter is that RSS just isn't fast enough. You can't hope to achieve what Twitter calls "in-the-moment updates" and "watch events unfold" if your client is polling each web site's RSS feed once an hour for new microblog posts.

Luckily this was solved years ago. Many blogging apps (including WordPress) have a setting to "ping" another server when a post has been published. When it receives this notification, the other server can request the RSS feed and make note of the new post right away.

Manon is right. This is actually a huge issue with the Open Microblog spec right now. I'm still trying to come up with a standard way of working around this issue (if you have suggestions, contact me).

Making RSS real-time →

-Thanks for reading,
      Brian Schrader

Site transferred. Email is next

Posted on Tue, 14 Oct 2014

Ok, so I've moved my website off of shared hosting to Linode and everything is great. I haven't added the new features to my blog engine yet, but I'll get to that. First though is the problem of what do I do with my email. Currently, its hosted with my domain provider and part of my shared hosting plan (which I no longer need). I'm looking to move my email off of my domain provider to something more private. I'm thinking about Rackspace or Zoho right now.

If you have any suggestions please let me know. I'm looking to host 2-4 email addresses as cost effectively as possible (calendar and contact syncing is not needed. iCloud does that just fine).

-Thanks for reading,
      Brian Schrader

Some advice on programming

Posted on Sun, 12 Oct 2014

Someone once said to me, "If you ever go back to look at code you've written, and you can't see anything wrong with it, then you haven't learned anything."

-Thanks for reading,
      Brian Schrader

Thinking about redoing my blog engine

Posted on Sat, 11 Oct 2014

I think I've decided to go ahead and ditch my web host and switch my blog over to Linode. I could just move the Git repo and transfer the domain, but leaving a web host for a VPS provider gives me a lot more freedom with how I could run my site.

I'm looking into tweaking my blog engine to support Dropbox integration like Second Crack does. I always liked that system, but my current web host doesn't allow that; Linode does (Linode really doesn't care what I do).

I'm pretty sold on the idea, and I just need to figure out how I'm going to do it. I'd also like to be able to publish posts from my phone and iPad, so I'm going to have to figure out how to do that too. Since the site is run by committing from a local Git repo to the web server (something that wouldn't be easily done on iOS), I'm going to have to come up with something.

-Thanks for reading,
      Brian Schrader

Archive

Subscribe to the RSS Feed. Check out my code on GitHub
Creative Commons License
BiteofanApple is licensed under a Creative Commons Attribution 4.0 International License.