The idea is here: http://www.splinter.com.au/2020/06/07/chalkinator/
Anyway if anyone has advice i'm all ears :)
The idea is here: http://www.splinter.com.au/2020/06/07/chalkinator/
Anyway if anyone has advice i'm all ears :)
It sounds like a nice idea - a "Live Writer on steroids". Could be neat.
What you're describing seems to be bundling an editor, a static site generator, an S3 syncing service and an S3/Cloudflare onboarding guide.
Haven't tried it but looks good.
More Linux alternatives: https://alternativeto.net/software/publii/?platform=linux
It looks like the Firefox extension isn't around, and the corresponding Chrome one [1] doesn't actually work any more and was last updated in 2014.
I suppose things were simpler back then when services had slightly more open APIs.
[1] https://chrome.google.com/webstore/detail/scribefire/elkkomi...
Anyway, here is one i found out recently and seems to be able to do the job:
And a blog i made with it myself:
http://runtimeterror.com/devlog/
Having said that, the first thing a friend of mine (who has managed a few blogs professionally) asked when i mentioned it to him was "can you make posts from your mobile?". Of course the answer is "no" since this runs as a desktop application, manages everything locally and just generates HTML files that can optionally upload/sync to your server for you. But apparently every single non-technical client he had wanted to use their phone to write blog posts way more often than their computer.
And yes, i know this also explains the "because apparently putting everything in the browser is sexier or something" part i wrote at the top, but, dammit, i do not care about mobiles at all, do not go and kill stuff i (might) like.
(though TBH there are several things i dislike about Publii, e.g. the themes are both ugly and too overcomplicated to work with and modify and the program is written in Electron with for real benefit - it doesn't do real WYSIWYG, just a rich text editor almost with the same capabilities as the one you could find even in Visual Basic 4 and it doesn't even preview the site inside it but launches your browser instead, but there isn't really any other alternative that i know of and at the end it seems to work... though i'm itching to go and write my own :-P)
As for Publii, yes it really does appear to be everything I was thinking of making. Except it's Electron and I was thinking native - which users wouldn't notice likely.
Really interesting to hear that people want to post from mobile. I must be in a developers' bubble - i assumed this kind of thing would be done from a desktop! You've really got me thinking there. I guess you could totally do it from mobile. But then you have to fight the app store's distribution/marketing model. Which isn't appealing - at some point you have to ask yourself 'would I just make an easier living as an electrician than do this?'.
Again, interesting to hear your shortcomings with Publii. I think the killer feature would be doing it all from mobile. Which is fine I guess, but then how do you get your data to desktop, backups, etc etc. Lots to consider!
Thanks again for the food for thought :)
I don't know much about the mobile world, so this may be a stupid question, but could you route around the app store problem by making a progressive web app?
I assume a backend of some sort would be necessary, since JS in the browser is a pretty limited environment, but if Chalkinator Desktop is handling your server setup anyway, it could install a personal backend on it for you, and the PWA could talk to that.
This means that you as the app developer would be out of the loop and couldn't easily sell the user out. You would only be there to provide updates, include more providers etc.
edit: reading the description of you software better, I think this is what you are going for. The thing you haven't added yet is domain management.
Most blogs are as simple as markdown files, with maybe some complexity in referring to other media files like images, and a key/value map in the form of front matter. That's not very difficult to serialize.
Write your articles as plain .txt when you don't need images. Or as handwritten html when you do (use relative links and dump the images into a subfolder) You can simply have pre-made templates for this that you copy and paste manually.
Create an account at archive.org Upload your writings root folder. As suggested here: https://news.ycombinator.com/item?id=23650600
your writings can live on in a url like https://archive.org/download/test_blog_2020/test/blog/
You can even add custom metadata so that it is searchable in some future incarnation of archive.org (doubt they will ever break the existing metadata even if at some decades down the line someone decides to redesign the whole thing)
archive.org is becoming such an important "ark" of knowledge that in theory there will be a very high chance a copy is preserved somewhere for decades to come. (barring some large scale digital societal collapse)
The idea would be: it would read the Markdown as I write it, let Hugo render it, and return the HTML to be rendered in the editor window.
Looking at your editor, it really looks like Zettlr (I'm guessing they're both Electron apps).
I guess you have 2 almost separate problems: the editor and the hosting. On the topic of hosting, I guess if a "blogger" can get his own domain name, the actual infrastructure can be swapped under it (and the data republished from the local machine), as long as the reader can load the blog using the known URL, it's fine.
FWIW: my app isn't Electron, it'd be native macOS, that's just my skillset. Maybe i should just use Electron so it could run on windows/linux to be honest.
Yes, the plan would be for the blogger to get their own domain. Bloggers generally already do that when setting up with Wordpress so i don't think that's a problem.
This way I'm able to keep the markdown completely standard which makes it easier to move to a new platform in the future.
Wouldn't know how to price that, and with RSS often containing just a few items you'd need to think about that when setting up the blog. Though maybe blogspot supports range requests for RSS?
I wish there was a service where you could just buy like, a $1000 US 100 year T-Bill and use the payments from that to guarantee your domain remains alive/hosted for at least 100 years.
I agree about the risk of the blog going away in the future which is something that simply cannot be avoided if you're relying on someone else to publish your content. Anyway, we're going to offer an easy way to export your data (maybe markdown files or HTML files or something like that).
If you want full independence and have the skills then yeah a static site is probably the best option. But even for people with technical skills it's a hassle to setup, design/buy a template, figure out the best hosting, no CMS, etc.
I was thinking the same as you: Having an export to some format (i was thinking Hugo or Jekyll) to give people that assurance that there's a plan B if things go bad.
As for the hassle to setup etc, I totally agree! That's a large part of what my idea would solve. And even with technical skills it's a hassle, i agree - which is why i initially thought posing this at devs would be good. But now i think they tend to DIY these things so perhaps not a great target market.
Or is the idea that the tool registers an account to a server provider for the user? So the user has to pay both you (for the tool) and the server provider (for the server).
Maybe I have misunderstood the aim? In any case, due to what you mentioned, I think it's a difficult niche, since technical people can set up their own and I'd guess most non-technical people don't really care enough.
So yes they'd be paying me and the server. However the server fees would be cents a month. I would aim to present this as a strength to the user: you get billed direct by AWS/Azure because you're not at ransom to me - you hold the keys to the kingdom.
I suspect you're right though: Technical people will DIY, and nontechnical won't care, and will simply use Wordpress (it's the IBM of blogging: "nobody got fired for buying Wordpress")
Indeed.
At some point the desktop app will need updates too. If the developer stops updating it it will be as good as dead.
Exactly. Windows and Android apps last forever. Not so much in Apple land.
It's not only that though. For example, something could be deprecated in the AWS SDK. If the app has to deploy somewhere it will be coupled to that too.