TFW you move three existing projects forward while avoiding starting a new one.
https://jasongullickson.com/preposterous-as-community-media-engine.html
TFW you move three existing projects forward while avoiding starting a new one.
https://jasongullickson.com/preposterous-as-community-media-engine.html
I know I say this every few months, but maybe it’s time for me to fix-up #preposterus .
https://github.com/jjg/preposter.us
As-is, it can do so much:
…with so little:
…and with almost no effort (just send it an email!)
But it is a little buggy and the code is very rusty and each time I try to fix it up I wind-up about half-way there and decide “bah, it’s good enough as-is”.
But if I took even a little time to make it right maybe it would be useful to others and not just me? It would be trivial to setup a server robust enough to host a few dozen or hundred users and not a lot more effort to host thousands. And it’s trivial to self-host if anyone decides they want to do it themselves.
The big question to me is whether or not anyone else appreciates the email-based publishing workflow. For me it is amazing because I can publish from any device, be it one I own or something I borrow, GUI or command-line, hell even a feature phone can publish a blog or podcast this way. And it avoids all the auth/login/password bs that adds one more layer of friction to publishing something. It’s also very well-suited for offline and intermittently-connected work.
Maybe this should have been a blog post 🤔🤔🤣
All this talk about self-hosting blogs makes me wonder if it's time to get https://preposter.us back in shape?
Got to spend a couple hours working on the successor to #preposterus: #apreposterus.
It’s basically Preposterus rewritten in #golang to output an #ApresWeb blog.
https://code.jasongullickson.com/jjg/preposter.us
https://code.jasongullickson.com/jjg/apreposterous