In the end, I kind of want a new phone and watch, but I don't really want them. All I really want is an SE with a better camera.
Trying VSCode with Vim emulation and nvim ex commands and it's kind of great right out of the chute. I will have to dig in more deeply later.
I notice that in this piece about Instant Dave, Dave doesn't mention 1999.io in the context of suggested blogging tools, but does mention his other tools for link blogging and aggregation. Could just be an unintended omission but he's (understandably) not one to miss an opportunity to suggest his own stuff. Doesn't bode well for 1999's viability over the long term, does it?
I've gone and done what I feared I might, I created a new Wordpress blog at jack.baty.net.
As with most things, I want to be the guy who "has always just used [THING]" where THING= a specific notebook, a certain camera, a note taking app, or a blog. I'll never be that guy.
So, stay with me as I tinker and learn and figure out what's what.
I love that static websites can just sit somewhere behind a simple web server and always just work. They're fast and secure. However, I'm beginning to think that for certain sites, blogs for example, the joy of easy hosting loses out to the pain of publishing.
I know, "But it's just a folder full of text files!" I get it, baty.net is currently a folder full of about 3000 markdown files. Still, in order to publish something I have to create a new markdown file in a particular folder, named in a particular way, in a particular format. I have scripts that help, but I tire of tinkering with scripts instead of just writing stuff and clicking "Post".
There are some decent solutions to the problem of publishing static sites. I think Blot.im does a great job of taking the pain out of publishing text files. 1999.io is basically a nice front end to a rendered static blog. Siteleaf looks nice. And so on.
But you know what works pretty well for managing and publishing an active blog? Wordpress. We are supposed to hate Wordpress (oh no, there's a database!), but if I were going to start a new site/blog and planned to publish frequently, especially if posting a lot of images, without too much fuss, I'd probably go with Wordpress. In fact I probably will.
I could play with LaTeX templates all day. In fact, that's exactly what I've done!
I like blogging with 1999.io. I like the flow and I like the output. It makes publishing easy and nice and even fun.
Here are a few things I would like...
1999.io is awesome. I hope Dave continues to support and improve it.
I'm beginning to feel like cross-posting everywhere is rude to readers in many cases. Who wants to see the same content everywhere they turn? My followers on Twitter and Facebook don't overlap much, so most people see my stuff only once.
On the other hand, the type of content that is useful differs on each platform, so sending everything everywhere may not be wanted.
Plus, does everything that comes out of my head really need to be seen by everyone, automatically? I don't think so. I should probably just get over myself and hand-post only the things I think might be welcome or that I'm particularly fond of, in a format suitable to each platform.
My AirPods stopped working properly a few weeks ago. The right Pod was very quiet unless I pulled it slightly out of my ear. (I tested it with regular Ear Buds to make sure it wasn't just a hearing problem.) The overall volume was too low. Then today, they wouldn't connect with any of my devices.
I hopped in a support chat and ten minutes later they're shipping me replacements. A darn fine experience overall.
I wonder what happens when 1999 has hundreds or thousands of posts. My baty.net blog has over 2000 posts and it takes Hugo around 2 seconds to rebuild the entire thing. When I was using Jekyll it could take the better part of a minute. It might be interesting to stress test it a bit. I think Dave uses a similar format and software for scripting.com so maybe it's fine.
Why use the "1999" subdomain? You don't see sites like "wordpress.baty.net" or "hugo.baty.net". I don't like the idea of making the domain reflect the technology. On the other hand, this is a bit of an experiment, and I have a tendency to jump in and out of experiments.
The last time I used 1999.io for a blog I put it at "notes.baty.net" but then later used that domain for an Emacs-driven site, then a Known-driven site, and so on. As those were also experiments, I didn't worry about breaking links, etc. I wish I had worried, as now I've lost quite a few posts there.
Using 1999 as the subdomain should ensure that even if I stop posting here I won't lose anything. And I could always come back without missing a beat. I don't love it, but I'm leaving it as-is for now.
It's a choice between 1999 and Micro.blog. Once I can post images on Micro.blog from the web and Manton allows for posts longer than 280 characters I expect that to win. On the other hand, this site is nearly invisible since I'm not syndicating anywhere. Could be there's room for both, but I suspect that as usual it'll depend more upon my mood than anything else.
Hi! It's a cloudy Labor Day morning in the US and I'm home tinkering with 1999.io and friends. I probably shouldn't be.
I like Dave Winer's publishing tools and have used many of them over the years. I think it's because he thinks like me, meaning that he does things the way I'd do them.
Also like me, Dave has a tendency to forge ahead with whatever idea strikes him. This is great for making progress, but I hope 1999.io stays on his radar, because it really is clever and fun to use.
Anyway, I enjoy running different apps and poking around to see how they work. As I mentioned earlier, everything here ends up as a simple static site so I can stop running the software any time and just drop everything onto any web server.
Another thing about 1999's approach is that it's really just a CMS that renders a static blog. It goes a long way toward removing the tradeoffs between ease of publishing and ease of hosting.
It is rather nice just typing stuff in a box and clicking the "Post" button.
Used the default Ubuntu AMI. Ran through Dave's install instructions
Added a new key pair (1999.pem).
Had trouble connecting the first few tries, but it worked once I selected the correct VPC in AWS. Still don't know why.
Installed Caddy and created Caddyfile at ~/nodestorage/publicFiles/users/jackbaty.
Gave up on Caddy because things break when using https so I installed nginx instead and am running on port 80 only.
Installed a callback script for running everything as a static site
In my opinion a callback script shouldn't be necessary. Why not a config setting that would allow for either the default location or some other folder on the server? Callbacks could still be used for fancy things like pushing to S3.
Had to copy the misc/menubar.* files from the default publicFiles over to the static webroot.
Testing the callback script.