Earlier quoted context omitted.
my blog is literary criticism of literate programming, and so most of the content of my blog is also the code from your blog.
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.
Own your work
111–113 of 113 posts
Re: Own your work
#112Earlier quoted context omitted.
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
#113The best solution is what the Indieweb folks called POSSE: Publish on your Own Site , Syndicate Elsewhere: https://indieweb.org/POSSE For instance, I might publish a clip on my own site first, then mirror it to places like YouTube, TikTok and Reddit so more people find it. Or post an article on my own site first, then repost it on Medium and Substack (with a canonical saying my own version is the original if possible…