TrickJarrett.com

Obsidian adding tables

I've bounced between Notion, Obsidian and Google Docs for various means of controlling and organizing my digital stuff. I left Notion because it wasn't a format that enabled easy migration. And I am a fan of Markdown (the backend of this blog utilizes markdown), so the idea of this integration with Obsidian is very interesting and I'll definitely be checking it out.

Friday morning code tweak

Sometimes I accidentally save articles from my RSS reader without meaning to. Which means they get captured in the end of day automated post. So, I will go in and remove these errant posts.

And this morning I realized that when I do so, the post gets its HTML stripped out. Which is a bigger issue, but it also made me realize the automated posts inserted HTML rather than markdown text as it should. Old habits die hard I suppose.

So a quick bit of adjusting code and they should now be inserting Markdown properly. I still need to fix the editor stripping HTML, for correctness sake, though it shouldn't be an issue really.

Extending Markdown

I've been running into limitations of Markdown as it comes to this blog, and am finally taking steps to extend it.

First up is a new implementation for links:

[This is a new link{With helpful link titles}](http://www.linkingtosomewherecool.com)

And what that does is create this (hover your mouse over the link):

This is a new link

Glowbug coding morning

I have, for the past 3 days, been banging my head against the wall.

I utilize an app called 'Wallabag' which is a self-hosted version of Pocket, for storing articles for later reading.

The issue I'm running into is that I want to hook a bit of code I'm writing up to my Wallabag. Wallabag has a built-in API setup. It's documented and works for a number of things already. I'm attempting to create my own. But, for some unknown reason, the path /oauth/v2/token, which works on their hosted setup and for other people who are self hosting, is not working for me.

I've been working through possible reasons. I even contacted my webhost to see if there was possibly some sort of intra-server limitation that would stop it. But, no luck.

My current theory is that there is something messed up with my install. I installed it via 3rd-party tool called Scriptaculous. So, in attempting to fix that, I go about installing it via their prescribed way of doing it. And, because this problem has become a huge constant series of obstructions, I end up with errors as part of install. Fun!

When I ran into the wall on it, I turned to some other bits of coding. Namely, getting me closer to the transition to Markdown rather than HTML on the backend. I have just finished the script which will convert all the posts from HTML to markdown, as well as fixing some other issues.

Tonight I'll finish adding the Markdown parsing to publication and then change the admin entry editor from Quill to a Markdown one. Once that's done, we'll run the conversion.

One of my projects today was downloading the entirety of Tim Ferriss's podcast transcripts for my own reading and reference. Interestingly I didn't go for his show's entire archive. Of his nearly 600 episodes, my archive ended up at around 335. This is because I was only really interested in the episodes where he interviews someone else and so I left the other variety of episodes and didn't download the transcript.

I did this thanks to Tim having posted the transcripts on his blog. So I was able to make use of a Firefox plugin which downloads the page as a Markdown text file. Next will come a long process of reviewing the transcripts, making notes, tagging and flagging things, etc.