Live data from Hacker News

Show HN: Tumbless, a Tumblr-like blogging platform running on Amazon S3

github.com

21–23 of 23 posts

Re: Show HN: Tumbless, a Tumblr-like blogging platform running on Amazon S3

#21

Have you tested this on mobile safari? It jumped around a lot before sort of displaying ok, but then the jumping issues returned. I query it because your page makes a point of mentioning the fully responsive layout - but personally if I visited a page which displayed the behaviour on mobile like yours did, I would immediately leave and not come back.

Unfortunately I have no iPhone to test it on. I'll see if I can borrow one... On Android it renders smoothly.

Re: Show HN: Tumbless, a Tumblr-like blogging platform running on Amazon S3

#22

This is almost perfect... It just needs support for more text based content. If it's already supported then the demo needs some examples of it. Text or HTML posts ? oEmbed based links? Link in a txt file would be simple enough. I'm not sure the best way for integrating these things, but I'm mentioning them because I'm always looking for simple blog tools, and it doesn't get simpler than files in a bucket. So this app…

Text posts are, of course, supported: just fill title and description while omitting the media. A rich text/markdown editor integration is on the roadmap, I haven't looked into it yet.

Re: Show HN: Tumbless, a Tumblr-like blogging platform running on Amazon S3

#23
post #16
post #14

Amazon S3 transfer costs can be problematic, though. Personally, I would pair a tool like this with a CloudFront configuration. If you configure CloudFront to expire objects after 24 hours, using a A/B release model for an S3-backed site works pretty well.

I use the --cf-invalidate flag(s) with s3cmd -- but for something with the usage patterns of tumblr, might be better to use a * invalidation so you don't have to pay too much for them. 24 hour invalidation would be confusing for tumblr-type things. I see the article posted today but the homepage doesn't have it? Very confusing.

My understanding, via limited testing, (might be wrong) of CloudFront's content behavior is that new things show up pretty quickly (hour?). Changed things would be subject to the expiration time limit. So, edits of old posts won't go live until the original objects expire - unless you invalidate the cache for them.
Post reply on HN