Re:Own your work
by breck on Sunday April 02, 2023 @03:12PM
(#35414038)
I must build static site compilers and markdown dialects so that my children may have liberty to write prose and poetry.
[ Parent
| on HN ]
Re:Own your work
by lisp-pornstar on Sunday April 02, 2023 @06:18PM
(#35415879)
This, and also "The blog is about literate programming, and the content of the blog is the code that produce the blog"
my blog is literary criticism of literate programming, and so most of the content of my blog is also the code from your blog.
Re:Own your work
by lisp-pornstar on Sunday April 02, 2023 @07:40PM
(#35416616)
My blog is about the creation of a coding language that, once finished, could allow for the compilation of the text of the whole blog into a program that would erase the blog. Which is total nonsense.
My new blog forks your language so it still results in compilation of the text of the whole blog into a program that would erase the blog, but it's a quine, so as the blog deletes, it's simultaneously punched out on the cardpunch, a nice neat deck waiting to spawn the next iteration. Oh, hold on, looks like Banksy is calling me.
Re:Own your work
by lisp-pornstar on Thursday April 06, 2023 @02:29AM
(#35464906)
My new blog is a palindrom program that does what I said first when read, and that does what you said when read backwards.
Oh, hey, it seems like Marcel Duchamp has resurrected.
Re:Own your work
by AzzieElbab on Sunday April 02, 2023 @08:42PM
(#35417099)
Hosting is the easy part. Monetization is the hard part. Substack writers indirectly promote Substack. With a static site, you are on your own. Although, I admit I do not fully understand the concern. Does substack establish any exclusivity? Can I not simply repost my content if I decide the leave or the site goes away