Welcome to SETT! You're one of the first people to see it and to click the "community" section to see what happens.
In this area you can create posts of your own, just like on a forum or a social aggregation site like Reddit or Hacker News. Please help us put SETT through its paces by posting here!
Sunday night was a scary time for me. After more than a year of work, SETT was ready to be deployed on Tynan.com. Well, maybe not "ready", exactly, but I was sick of putting it off. One line in a configuration file was changed, and my site switched from WordPress to SETT. And then... nothing happened. This was encouraging. The server didn't melt (although there is definitely some optimization that needs to be done), and importantly, most new visitors to my site didn't realize that anything was unusual. Eventually a few people realized that things were different and left feedback. Now, with five days of history, SETT is actually functioning as envisioned. It's an amazing experience to watch our baby start to crawl. Before I get into the details of what makes SETT unique and how to best use it, a quick disclaimer: this is alpha level software. Some parts of it are extremely polished and functional, while others are barely usable (person to person messaging, for example). Right now I don't need bug reports, because I already have a huge list of bugs that I'm working through. What I would LOVE from you is feedback on the experience. What is confusing? Where do you get stuck? What do you hate? What do you like? When designing SETT, we tried to consider the various groups of users that interact with a blog, and how to best serve them. For example, most of my readers are casual readers who stop by, read some posts, and leave. I want their experience to be nearly identical to any other blog-- there shouldn't be any new terminology or steps that they have to go through. The only changes we've made on the reader side are a wide content area for media like images and videos, well formatted text, and (for logged in users) indicators for whether or not they've read a post. For the average casual reader, this is a marginal improvement over a normal blog. Most of SETT's ambition lies with community members. I believe that until now, dedicated readers have been marginalized. I think that out of the 12,000 or so readers I have, there are hundreds who would love to be an important part of the community surrounding this blog, but aren't currently offered any tools to do so. All SETT blogs have two sides to them: the front page and the community view. If you go back to the main page of this blog (click the header at the top) and then click "community" in the action bar, you'll see the posts that have been created by members of the community. This is similar to a forum or message board. Unlike a forum, I can promote any post to the front page with a single click. That's how Brian's post about Pina got there. Besides creating original content, you can also vote things up or down. If you login or register for an account, you'll see voting arrows next to every post. Your votes help new readers see what this blog's best posts are, filter out spam, and indicate to me which community posts I should consider promoting to the front page. There's a lot more that's new with SETT, but I'll keep this short(ish) and let you explore. If you want to help SETT develop, please vote on stuff, leave comments, and create posts in the community section. Please do NOT link to this post (or blog) on any high traffic site just yet. My server can handle it until we implement caching.
Using a domain is very easy with SETT. All you have to do is tell SETT which domain is yours, and then point that domain to SETT.
On the SETT side, just go to Blog Settings and enter in the domain name. You should not include 'www'. Once you hit save settings, SETT will start checking several times an hour to see if the domain has started pointing to it, and automatically switch from sett.com/yourblogname to the domain.
Domain Registrar Settings
You must point the root of your domain to SETT's IP address, which is 126.96.36.199, using an A record. The way you do this varies by registrar.