Bring back personal blogging This post from the Verge appeared on my feed this morning: Twitter is creaking. Social media seems less fun than ever. Maybe it’s time to get a little more personal. In the beginning, there were blogs, and they were the original social web. We built community. We found our people. We wrote personally. We wrote frequently. We self-policed, and we linked to each other so that newbies could discover new and good blogs....
In my last post, The end of social media, I lamented the decline of social media, and my feelings of weariness regarding the interaction and general lack of sociability on social media in the last couple of years. In an attempt to lower my stress level and concentrate on more productive things I am stepping further back from this charade and moving into a quieter corner of art and code. These are the two things I love and have been doing for a very long time....
Unfortunately Symbolic Links and shortcuts don’t work within Typora’s file listing. I found a work around though: Create a symbolic link to the folder you wish to add in the default Typora markdown directory, this will then show up in the the file listing, it won’t do anything though if you click on it, as it isn’t implemented or supported in Typora yet. But, if you right click on the icon link in the file list and choose Open in New Window it will load the linked directories contents....
I seem to have let this site go unloved for a long time. The main reason I suppose is a lack of motivation in posting and a bigger lack of interesting things to post. I have been quite busy though, both with Blender and in the last month, or so, with Moi3d. I hadn’t used Moi3d in a long time and was starting to miss the little tool, so took a few weeks to refresh my muscle memory and get some practice in....
I recently set up a addon for Visual Studio Code, for editing Markdown files in HUGO. The addon was from Elio Struyf called FrontMatter. I got it working quickly enough. Although I had problems with the media paths not showing correctly in the media browser. The reason for this was, I’d used the default setting (as mentioned in the documentation) which assumes media will be in the root static folder, where as I had media in an assets folder under the content folder....