🚀 I'm happy and proud to launch Actions for Obsidian on iOS!
After several months of work, hundreds of hours of cumulative testing in TestFlight ✊🏼, a ton of customer feedback 🙏🏼, and several reviews by Apple we're finally here ✨
I'd be delighted if you'd check out its ~40 #ShortcutsApp actions for #Obsidian and see if & how it might fit into your #PKM life on #iOS and #macOS.
What would make your life easier when working with your vault on your Apple machines? Is there anything you have trouble getting to work? What are you missing on AFO's roadmap (https://forum.actions.work/t/development-roadmap/16)?
ℹ️ I’m afraid interactive widgets are currently out of the question, the mix of Obsidian API + iOS is not very forthcoming in that regard…
NEW VIDEO 🎉 Today I will show you how to turn those note-to-self emails into #Obsidian notes, locally, using your existing email account. All you need for that is the built-in #macOS Mail app (set up with your email account) as well as Actions for Obsidian.
I'll give an intro to the Apple Shortcuts automation system and how #Obsidian can benefit from being a part of it.
I will showcase my app #ActionsForObsidian, which brings the two together, and build a few short workflows to give you ideas for how to connect your existing Mac and iOS apps to your Obsidian vault.
Dear #macOS users of Actions For Obsidian, if v2024.1 wasn't the first version of AFO you've installed, could you please check your Applications folder and let me know whether there are two versions of AFO, or just one?
The app was renamed in the last update, to proper titlecase ("Actions for Obsidian" → “Actions For Obsidian”), and I just got a report that for some customers, the App Store installation didn't remove the old version correctly.
FYI: The string-based vault parameter (i.e. "type in your vault name") will be removed in Actions for Obsidian 1.5.
For most customers, this won't be of interest, because since version 1.3 introduced the vault menu (which 1.5 builds upon!), the text-based parameter was only available in existing pre-1.3 workflows. Meaning: You couldn't even access it when adding a fresh AFO action to your shortcuts!
> Today we’re excited to announce that the Obsidian Canvas file format is now called JSON Canvas and has its own site, specification, and open source resources at jsoncanvas.org.
Support for saving files is pretty convenient! For example, creating a workflow which snaps a picture, stores it in your vault, and then creates a note referencing/embedding the new photo is trivial.
If you want to archive your Mastodon or other app/site feed posts into Obsidian as separate post entries, I wrote a post about how to use the Simple RSS plugin to do that. I cover Mastodon and Grav RSS feeds. I've done the best I can do for now with instructions and a big thank you goes out to simple rss dev Monnier Antoine for being super helpful.
I'm very much at the point where I’m pulling my hair out, yelling at the screen. Because just like with v2024.1.1, this EXACT SAME BUILD works a-okay locally and in TestFlight.
But if I propagate the build to the App Store, the buttons stop working. There is nothing in those buttons that is checking for AppStore/TestFlight. 🤬
App Store review taking 2 days every time isn’t helpful, either.
My own #ObsidianMD setup for #DnD and #TTRPG has evolved significantly over the years. So I’ve updated one of my more popular articles to reflect that:
I just released a full rewrite of my #ObsidianMD plugin Logstravanza, and I think it's solid. It's still mainly a plugin for #Obsidian plugin devs, as it writes console.*() messages to a file.
New in 2.0:
Adds additional output formats, such as NDJSON
Adds support for setting the output folder for log files
Changes output base file name, w/ optional date stamp
New settings tab
Logs unhandled exceptions in main thread Promises now (not in workers)
#ObsidianMD#TTRPG Lastly, two ways I've handled embedded secrets within notes (knowledge that I have as the GM but players don’t yet).
HTML comments. Keeps it right within the note and won't render in read mode or on a website! I'm tending to prefer this method.
Linked previews. This abstracts secrets into their own notes but renders a preview in the related note. This works great with tools like Obsidian publish because they won't show up if you don't publish the secret's note.
#ObsidianMD#TTRPG As mentioned in my article on tags, I favor tags over custom properties. So recently, I've been cleaning up an old custom property for Campaign and replacing it with a nested tag: campaign/{campaign-abbreviation}. You can see an example in this image.