Earlier quoted context omitted.
Roll your own! It's fun. My site is a custom made file-based blogging platform written with Python Flask, and it's a joy to use since I made it exactly how I wanted it to be made. One feature that I really enjoy is being able to call source files into the post. This allows me to create/update code snippets extremely easily. Markdown + calling includes on my source files is exactly what I needed to efficiently produce…
Wouldn't security be an issue?
Posterous will turn off on April 30
121–130 of 141 posts
Re: Posterous will turn off on April 30
#122> We’d like to thank the millions of Posterous users who have supported us on our incredible journey. Yeah, right. How was that "incredible", BTW? I feel I've read that same story many many times. As a Posterous user, I'm so glad I used my own domain.
Oh come on, have some empathy! They started their own business. They gave it a go! They had a decent degree of success. Just because they didn't make it work doesn't mean it's ok to be so dismissive.
They left their users out to dry, and instead of telling them (us) that they are sorry and that maybe they understand our situation of being burned yet again, they sound like they're very happy with themselves, "building features to help [us] discover and share what’s happening in the world – on an even larger scale".
I don't even know what that means.
You may argue that the world doesn't end with Posterous shutting down, and you'd be right. But the tone of that post is not ok.
Re: Posterous will turn off on April 30
#123Re: Posterous will turn off on April 30
#124Any solid alternatives HN could recommend?
Wordpress. That might sound obvious, but it works and it's easy to setup. I left Posterous after they launched Spaces and went back to hosting my own Wordpress install. I host about 20 low traffic sites on a single Bluehost.com shared server that costs under $100 per year. Never had any issues. One click Wordpress install via SimpleScripts. It really doesn't get any easier.
Hosting companies come and go, do whatever they please with your data.
Nothing like having as much control as possible.
Sadly this is not possible for non-technical users.
Re: Posterous will turn off on April 30
#125Re: Posterous will turn off on April 30
#126I know that this may be good for founders, but it let me against trying new companies which doesn't have a clear monetization strategy.
Re: Posterous will turn off on April 30
#127Re: Posterous will turn off on April 30
#128This is yet another reminder of how important it is to own your content, and why a blog is best hosted at a domain you control.
Re: Posterous will turn off on April 30
#129When Posterous emerged I had high hopes for it. But I quickly understood that their service wasn't meant to improve at all. Every problem I reported to them was dismissed (directly or indirectly). I thought about the idea of posting via (plain-text) mail seriously, but they weren't sharing my mindset. I left posterous long time ago and I see it was a wise decision.
This isn't fair at all. Posterous was very responsive to user feedback and reported bugs. Posterous engineers spent much of their time answering support emails directly and finding solutions for users. As a matter of fact, support emails go directly to engineers inboxes. Perhaps the problem was that there just weren't enough engineers. Posterous may not have found a way to make money but the site was definitely meant…
Re: Posterous will turn off on April 30
#130Earlier quoted context omitted.
I like the idea of Octopress and Jekyll, but the few times I've tried them, it seems that they don't easily scale. My blog has over 2900 entries. Build from scratch. chug chug chug That I understand. Now add a new entry and try to get an incremental rebuild in less than 30 seconds. Has anyone tackled this in either project??
I use a makefile. Only rebuilds the pages that have been added / modified (which, of course is the point of a makefile in general).
Yes, I do remember that years ago I read about a static web management system that was makefile-centric, but think it lost popularity as more advanced CMS's came out.
Also I have trouble thinking about how a makefile can help you manage the 'Prev' and 'Next" attributes on a page. This is, not only make HTML from the page I just generated, but also go back to the previous writeup and update it to add a 'Next' link to it.