71–80 of 141 posts
Can somebody please help me out? I'm confused here. I thought Posterous (before being acquired by Twitter) was doing quite well and was seen as the biggest competitor to Tumbler. It would seem that Posterous had a ton of users (would love to know details) and that they could monetize those users fairly simply through display ads. So, with a ton of users creating content and even more viewing that content, I would ima…
To be totally honest, I'm surprised it's taken this long. Everyone knew a year ago when they were acquihired that Posterous would be discontinued. Why do I say this? Well, Twitter's bread and butter is in 140 characters, if they wanted to look at branching out into micro-blogging they wouldn't need to acquire a company, of whom the majority of their customers already use Twitter. (It was borderline a zero-value gain…
Tumblr and twitter both USV companies. Surprised they didn't just segue users to tumblr.
I'd also assume that Twitter doesn't really care about what users or an abandoned blogging platform do now. I'm not saying that that's right, but it is what it is.
Obligatory link to "Posterous launches new tools to switch from dying platforms: A new importer per day for the next 15 days" http://blog.posterous.com/make-the-switch-to-posterous
Earlier quoted context omitted.
What about developers who are also bloggers?
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…
Can you do a writeup/tutorial for your setup?
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…
What about bloggers that want to be developers? Can you do a writeup/tutorial for your setup?
Sure. I can just open source the site after I remove some private stuff and improve the documentation a bit.
I have a similar site (my old web design partnership vertstudios.com) that already has an open source mirror[0], but it doesn't have source file inclusion or tags like my joequery site.
[0]: https://github.com/joequery/Vert-Flask
The article linked in the repo has information on setting up nginx and uwsgi when it comes time to run the thing live.
Keep in mind that my site's workflow isn't perfect by any stretch, but it's perfect for me. That was my main point.
Earlier quoted context omitted.
Wordpress is for bloggers, Github is for developers. Why not keep things simple?
What about developers who are also bloggers?
1. Does not cost me anything
2. Lets me use my custom domain name
3. Gives me control over the generated HTML, but also gives me a starting point in the form of some decent looking themes [3].
4. Actually works (I'm looking at you, bitbucket).
5. Gives me control over my content. Github decides to close its service? No problem, I got all my content and its history in my local git repo, so I can migrate it to anything I think is better.
If there is another option that fulfills these criteria I would like to know.
[1]: http://octopress.org [2]: http://pages.github.com [3]: http://octopressthemes.com