Live data from Hacker News

Open for everyone

blog.svbtle.com

111–120 of 281 posts

Re: Open for everyone

#111
post #102

Earlier quoted context omitted.

Don't forget Obtvse! [0] [0] https://github.com/natew/obtvse2

And everybody's favorite new band: Chvrches (Seriously they are pretty great though, impossible not to smile for the whole album).

You've got to give them credit for their SEO strategy.

Re: Open for everyone

#112
Markdown only? That's not "getting out of the way", it's limiting the ways of expression. Getting out of the way is providing simple defaults, why not depraving those who need more tools (HTML/CSS) of richer features.

Re: Open for everyone

#113

Wasn't part of svbtle's appeal being one of the few people to "have a svbtle"? When it first came out - it was beautiful & part of the cache was that only a few people got in. It was super popular for a few months - then fell off completely. Seems strange that the one main differentiator for the network has now been removed.

"catch" or "cachet"

Re: Open for everyone

#114
post #20

Svbtle’s dashboard is designed to work the same way your brain works. It encourages you to dump ideas, links, and thoughts into a flow of draft posts, and then makes it easy to slowly sculpt those ideas into publishable articles. It just feels natural. This isn't the type of marketing copy that makes me want to use the product, and in-fact drives me away from it. Contrast with Medium's more neutral, objective copy: h…

Why does the copy drive you away from it? Serious question since I didn't think one way or the other about it.

I like Medium's better because it's a story. It's got some emotion behind it.

Re: Open for everyone

#118
post #101

What would be the advantages of using this over static site generators?

The UX isn't an utterly terrible developer workflow?

I write code all day. Git is awesome, and you can pry Vim from my cold dead hands. But Jekyll is fiddly and doesn't really match my preferred writing workflow.

Ghost workflow: Visit URL, mash password manager (occasionally), click "new post" and start writing. Change the title whenever I feel like it. A live preview of the post appears on the left, and I click publish when I'm done. Click a little button in the UI to view the finished post on my site.

Jekyll workflow: Open a terminal. Create a new file named with the current date and the post stub. Half the time I don't know what either of those are off the top of my head. Open Vim. Type out the post metadata block. Inevitably get something wrong. Type post. Tab to the terminal and start Jekyll's server. Navigate to local server URL in browser. Alt tab back and forth between browser and editor, hitting F5 every time I want a new preview. Rename file with new stub (optional). Git add, commit, and push. Navigate to my public site in browser to make sure everything came out OK. Mash F5 a few times because Github Sites hasn't compiled it yet. Delete the "We compiled your site!" email from my inbox.

Note that Ghost requires much less prep; the majority of my time in Ghost is just editing my post's text. Jekyll has a larger lead in time to editing, and while editing I have to switch back and forth between my editor and the browser for a preview. Jekyll requires more effort doing busywork that isn't writing. I found my output dropped way off after I switched from Wordpress because the barrier to starting a post was higher.

Re: Open for everyone

#119
Dustin is a little too late on this one. Medium came along and scooped up whatever chance Svbtle had of becoming accepted by the masses. It should have been open from the start, Dustin's elitist attitude got in the way and I think it's only a matter of time before Svbtle dies.

Re: Open for everyone

#120
Really kind of frustrated with this.

Svbtle used to self-identify your work as selected to some extent. Now, what's the differentiator between your work and everything else?

Don't say "content" please. That's obvious. But a link was more dependable to me if it was from Svbtle. Not anymore.

Post reply on HN