1999.io is pretty much ready to go, now the question is -- how to roll it out.
First of all, what is it?
It's a blogging system. It's the blogging system I might have released in 2006 or so if I had stayed on the job instead of having my life take a sharp turn. Instead, we got WordPress from Matt, and Twitter/Medium from Ev. And Tumblr sold out to Yahoo, so that's not going anywhere. And Facebook is sort of a blogging system, but the posts don't have titles and can't have HTML markup, or links, so it's pretty limited.
Now I like all these guys, so this isn't personal, but I think WordPress is a pretty bad blogging system. It's command structure is designed to make sense to programmers. You have to be a programmer to modify a template. It's good for consultants, they love it because you need one to get a system up and in some cases to keep it running.
Twitter has that awful 140-char limit, and Medium is like a closed box with a few little windows here and there, so you can see some light, but neither really fully embraces the open web.
Bottom-line, the blogging world I left behind is actually considerably behind where we were when I took my leave.
First, I wanted a box at the top of the page where I can enter something new, start typing, and take it all the way to a finished post.
I wanted to be able to edit the template for my site, easily, giving me full control of how the pages look, without having to do any programming.
The server should be as easy to set up as possible. And it should get easier over time.
If I have a group project I want all the members of my group to be able to post to the blog. But one user retains ownership, control over the appearance and the server.
The server should be open source, so there can be a million servers if that's what the world wants. I don't want to try to capture the writing of others in my silo. I don't even want to host their stuff, if there's any way I can avoid it.
And I want to be able to continue to hack at the product, factoring, adding features, but retaining its simplicity and performance.