Closed ooker777 closed 1 year ago
I have a feeling that this is a limitation within Discord's API. I found the following digging through their code:
Only three types of URL schemes are currently supported:
https://
,http://
anddiscord://
I'm going to keep thinking on this though and I'll see if there are any ways we can work around it.
I think the simplest solution is to change the URI from obsidian:\\
to https:\\somedomain.com\
, then redirect it from there back to obsidian:\\
. However I don't know how to get the URI of the current note from the console
I'll keep thinking about this. I'm not sure this plugin is the right place to handle externally configured redirects. In the meantime, I've tested a workaround:
You can set up a Replace String Rule
in an app like Requestly. For example, I set up the following:
https://obsidian-discord-share.com/
with obsidian://
Since this is using a proxy, it doesn't care that https://obsidian-discord-share.com/
isn't a real URL and correctly redirects back to the Obsidian vault.
It is proxying your traffic. Not ideal and something to be aware of.
After further research, I think it's best to leave this as-is. To get around Discord's restrictions, folks can follow the workaround above or set up their own redirects.
I try to use the Obsidian URI:
But it doesn't work. Is there any reason for this?