3 ms·
You're sort of right, insofar as a CMS doesn't enforce a blog's reverse-chronological sorting... but that's not quite what I meant; a CMS is still fundamentally
by derefr 11y ago
You're sort of right, insofar as a CMS doesn't enforce a blog's reverse-chronological sorting... but that's not quite what I meant; a CMS is still fundamentally about having a collection of things by the same editorial staff put together—e.g. on the same domain.
What I was picturing is to throw out the level where you could infer "same editorial staff", so instead you just get the shared hosting service (http://example.com/ http://example.com/) and then directly under that, articles (http://example.com/foo http://example.com/foo). Like a pastebin: there's no source attribution to a given post, even implicitly.
The lack of internal attribution is important, because any internal attribution mechanism—e.g. mentioning the author in a <meta> tag, or putting their name in the URL—can be used to build an index of posts by author (just googling "site:http://example.com/author" http://example.com/author" gets you half-way there), which people might then treat as canonical instead of relying on the microblog.
So, I'm not against self-hosting a CMS, but my requirement that articles have no article-internal attribution—not even implicitly based on where they're hosted—means that self-hosting is kind of moot, unless I know a bunch of other people I can invite to also post on my self-hosted CMS until it turns into its own pastebin.
(Also, I have other, more fanciful requirements, like the ability of articles to effectively have their own embedded code and databases, turning them into their own little one-page web-app, like NYT's fancier long-form data-science articles are. CMSes don't really go there; they expect code you want to use in an article to be added to the site as a plugin, rather than being treated as part of an article and thus isolated+not-run when on any other article, deleted when the article is deleted, etc. The only thing that could pull this off right now is hosting each article as its own Heroku app; and even then it's not a perfect fit. You could theoretically write a blogging engine that posted articles by creating Heroku apps, though... hmmmm, now there's an idea.)
- tyingq 11y agoBelieve or not, I did get that. That's why it says "If you can't find one, there are tools made to build that sort of thing" Meaning, perhaps if you couldn't find a trustworthy 3rd party that would host it, it might be worth $5 a month to host it yourself, and make it available to others. Edit: On your other points: There's nothing stopping you from buying a generic sounding domain like "pastethings.io". Not sure why that doesn't separate it far enough. As for "code in a post", not sure what you mean. Javascript that runs in the browser? Formatted source code for viewing? Server side code that actually runs, but embedded in a post?