Show HN: gist.io, blogless writing for hackers (gist.io)

It's kind of like readability for gists.

I'm really liking this use of gists as a backend to more specialized services (eg http://dabblet.com & http://codepen.io ). It's a nice, easy way to get a versioned document store without having to build out the infrastructure. Direct access to the "raw" form is a plus.

Love this. I love writing markdown and I love the ease of creating gists. I've actually used gists for writing too. (http://gist.io/2483505)

I've noticed that some authors will create a public repo like "thoughts" and add markdown files to it (rather than writing gists).

Related: is it possible to edit gists (anonymous or otherwise?) If not, that seems like a functionality that could be implemented here, with a bit of trickery.

feature request: syntax highlighting in code snippets

Author here.

Generally, if you have features you want, file 'em here: https://github.com/idan/gistio/issues

Stuff I'd like to do given the time:

* Add RestructuredText support

* Add a sign-in-with-github option, and turn this into a minimalist blogging platform. Comments (gist comments), index page (showing any gists of yours that have been gist.io'd), authoring (I like writing in IA writer, maybe an experience similar to that, but with auto-saving.)

* Maybe some kind of means for controlling cache (right now gists are cached for one minute).

Could you manage post backups using git in a local folder? I'm adding it to your issues :)

edit: finally I wouldn't like to break your minimalistic idea down

I love this idea. Not sure if this is a direction you'd be interested in, but it would be really cool if this could act as a widget that I could insert into an existing blog site with a single line of code and your service would populate the rest. This would let me use gists for all my blogging, and still have the rest of my site around the outside.

This looks really great, but I have to take issue with your choice of typeface. While the description in the Google font database makes it out to be an award winning face for literature optimized for reading, its exaggerated serifs and uneven rhythm give it a kind of medieval / enlightened manuscript feel that just seems anachronistic and weird. For a general service that integrates with Github and shouldn't really be 'saying' anything with its design, I would recommend a more classic, rhythmic serif face along the lines of Minion, Caslon, Palatino, Baskerville, Hoefler Text, or even Georgia, which reads quite well at 14-16px.

Granted I'm a designer, I personally wouldn't use this service based on the typeface choice alone. It just clashes too much with the neutrality of everything else on my system and on websites I use commonly.

I'm excited about this. Not because it's a beautifully simple web app that provides a helpful service to a lot of us. Rather, i'm excited to see the source of a simple and effective Flask app! I'll be using this as a reference point for some lightweight apps down the road =) Thank you!

Great stuff. I see a great use case for this: when people want to write a reply to a post they can just fork the original gist and write their reply above it, like this: http://gist.io/3140173

In this way you can regard the list of forks at the right of the gist page as the list of comments (screenshot: http://cl.ly/image/1803161N432H).

Had a very similar idea which would use a single gist as a repository for all posts and do it clientside. Never fleshed it out though.

My thinking was to have a different gist per month which could be added too..

Unfortunately, not too friendly for non-js browsers which is kind of the weak point.

http://poyo.co/blog/

Add a noscript tag reminding visitors they need to have javascript enabled. Otherwise they just see a slowly pulsating "Loading..."

What is a gist, really? Is it a versioned, modifiable and referencable publication? Can I store it in my github repo? Should we be using gist as a model for info packet? is there an "API"? If someone could explain their understanding of a gist, I would appreciate it.

awesome. mad props

Instapaper compatibility: Considering the fact that this is for reading writings rather than codes, I think it makes sense to make it compatible with Instapaper and other services similar to it.

Also the <title> element should be the description rather than gist.io#.

> "Sometimes, we just want to share a bit of writing that is neither. Maybe we want to write for a specific audience, but don’t want to address the people who usually read our blogs."

You had me here. But I want to know where the top, featured, and new sections are. Where can I be recommended gists that are similar to those of users I subscribe to? Or are you trying to make this into the sort of imgur.com of stories on HN kind of thing?

Cool! It would be nice if there is some information about the writer available. For instance, their name as registered on Github.

This is great. A lot of people already blog by ftp-ing text file or committing to git, this greatly simplifies the process. Thank you!

I think maruku would be a better alternative than markdown. Currently you cannot make a table of contents inside your gist. But overall, I find this extremely handy. Thanks for contributing this to the open source community.

Please tell me that the end of your scale of permanence with regard to writing isn't blogs :)

This looks awesome. It would be cool if you could build a community around this. I wish I could not only post with this tool, but also read what others are writing. While someone may not want to keep a full blog, they may be willing to write a one-off post. This would be a great place to collect that kind of posts.

This is pretty cool. Mike Bostock, the creator of the d3.js visualization framework runs a service http://bl.ocks.org/ that lets you write HTML and JS code for visualizations and use the website to display them. It is pretty neat. An example can be found here: http://bl.ocks.org/1134768

I like this, but I find the default <code> style to be jarring when mixed with the normal text style. Possibly making it smaller would be sufficient.

It also doesn't handle ```lang ... ``` blocks properly: compare https://gist.github.com/3050085 with http://gist.io/3050085 .