-
Notifications
You must be signed in to change notification settings - Fork 4
Feature: Removal or Tweaks to remove online dependency #25
Description
Is your feature request related to a problem? Please describe.
Earlier today, my ISP went out for a few hours. I figured that I'd work on my vault during that time, and I soon realized that over half my vault was nonoperational. I could not load a single file that relied on this plugin, which is well over 200 notes.
Describe the solution you'd like
Either to prioritize the removal of the online dependency, or at least a way for us to download some type of manual package / library that we can slap in our Obsidian folder, and host the dependency ourselves. Either one, doesn't matter.
Describe alternatives you've considered
Not really another option. I haven't seen if the other plugin has this online dependency, but I'd rather not have to jump / migrate plugins.
Additional context
Maybe a new setting which allows us to specify either remote hosting of the dependency, or local. It can be as simple as a package we drop in our local .obsidian folder. I don't mind carrying it around.
Or if you could make a docker image with the required files, we could host that docker image, and then just specify a URL in the plugin settings so that it runs on a local copy. IE: code.domain.local
Or in offline use, I don't mind being stuck with just one theme if that makes it easier. (Preferably a dark theme), but anything which allows the notes to load.