Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Posterous will turn off on April 30

blog.posterous.com

Post reply on HN
Print view View original

91–100 of 141 posts

Re: Posterous will turn off on April 30

#91

Post by wmf »

dreamfactory wrote: post #83
chrisacky wrote: post #8

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…

Real time publishing is essential if you have a competitive SEO requirement. Google has got good enough that seconds count for web publishing operations. Static page-based content management is also anathema to a content services approach, which is needed for multi-channel, reuse, and dynamic page generation (and is the emerging requirement in content management systems).

In other words, you're a spammer.

Re: Posterous will turn off on April 30

#93

Post by johnnyn »

_2xb0 wrote: post #63

When 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 to improve IMHO. Email, Groups, Spaces, slideshows, sharing to multiple social networks -- the list goes on.

Re: Posterous will turn off on April 30

#94

Post by pav3l »

samstave wrote: post #75
RegEx wrote: post #64

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?

>Can you do a writeup/tutorial for your setup?

Actually, Flask tutorial uses a blog application as example

http://flask.pocoo.org/docs/tutorial/introduction/

Re: Posterous will turn off on April 30

#95

Post by mkr-hn »

sbierwagen wrote: post #92
mkr-hn wrote: post #89

Earlier quoted context omitted.

Ctrl+F, type plugin

http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=php

A quick skim shows a lot of applications that use PHP and some libraries available with or for PHP. What does this have to do with WordPress?

Re: Posterous will turn off on April 30

#96

Post by [deleted] »

wmf wrote: post #91
dreamfactory wrote: post #83

Earlier quoted context omitted.

Real time publishing is essential if you have a competitive SEO requirement. Google has got good enough that seconds count for web publishing operations. Static page-based content management is also anathema to a content services approach, which is needed for multi-channel, reuse, and dynamic page generation (and is the emerging requirement in content management systems).

In other words, you're a spammer.

[deleted]

Re: Posterous will turn off on April 30

#97

Post by dreamfactory »

wmf wrote: post #91
dreamfactory wrote: post #83

Earlier quoted context omitted.

Real time publishing is essential if you have a competitive SEO requirement. Google has got good enough that seconds count for web publishing operations. Static page-based content management is also anathema to a content services approach, which is needed for multi-channel, reuse, and dynamic page generation (and is the emerging requirement in content management systems).

In other words, you're a spammer.

In other words you're a troll or you don't know how web publishing works :p I'm talking about major news and media organisations. Immediacy has always been a key differentiator in news and financial data for example (look at trading co's who pay a fortune for systems that will shave milliseconds off getting figures from exchanges). A publishing system that isn't at least near real-time isn't a fit for very many use cases (most commercial publishing, anything with UGC etc).

Re: Posterous will turn off on April 30

#98

Post by jamesgeck0 »

dreamfactory wrote: post #97
wmf wrote: post #91

Earlier quoted context omitted.

In other words, you're a spammer.

In other words you're a troll or you don't know how web publishing works :p I'm talking about major news and media organisations. Immediacy has always been a key differentiator in news and financial data for example (look at trading co's who pay a fortune for systems that will shave milliseconds off getting figures from exchanges). A publishing system that isn't at least near real-time isn't a fit for very many use c…

It's safe to say that the vast majority of Posterous users don't care about anything you just mentioned. Static HTML blogs are just fine for them.

Re: Posterous will turn off on April 30

#99

Post by sbilik »

danso wrote: post #38

This has only been mentioned once in the thread, but if Jekyll seems like too much work to setup, I highly, highly recommend Octopress: http://octopress.org/ It's based off of Jekyll but handles a lot of the boilerplate, including rake tasks to deploy to Github pages. I've been following the github/octopress project for awhile and have seen a lot of activity in the past few weeks, so hopefully version 2.1 is just aro…

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??

Re: Posterous will turn off on April 30

#100

Post by BiosElement »

dreamfactory wrote: post #97
wmf wrote: post #91

Earlier quoted context omitted.

In other words, you're a spammer.

In other words you're a troll or you don't know how web publishing works :p I'm talking about major news and media organisations. Immediacy has always been a key differentiator in news and financial data for example (look at trading co's who pay a fortune for systems that will shave milliseconds off getting figures from exchanges). A publishing system that isn't at least near real-time isn't a fit for very many use c…

In other words, you're talking about something totally different then this entire topic and are in reality, the actual troll.
Post reply on HN