# Invoking a Roam page as main link for Hook bundle

**URL:** <https://discourse.hookproductivity.com/t/invoking-a-roam-page-as-main-link-for-hook-bundle/1119>\
**Category:** Discussion & Help\
**Created:** [January 2, 2020, 4:10am UTC](https://discourse.hookproductivity.com/t/invoking-a-roam-page-as-main-link-for-hook-bundle/1119 "2020-01-02T04:10:09Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![LucB](https://discourse.hookproductivity.com/user_avatar/discourse.hookproductivity.com/lucb/32/2228_2.png) [@LucB](https://discourse.hookproductivity.com/u/LucB)\
**Post date:** [January 5, 2020, 11:58pm UTC](https://discourse.hookproductivity.com/t/invoking-a-roam-page-as-main-link-for-hook-bundle/1119/15 "2020-01-05T23:58:35Z")

</div>

I had forgotten that I had previously answered [this issue here](https://discourse.hookproductivity.com/t/invoking-a-hook-link-in-the-context-of-roamresearch-website/1081/2) ! There, I noted that

> [@Invoking a Hook link in the context of roamresearch website](https://discourse.hookproductivity.com/t/invoking-a-hook-link-in-the-context-of-roamresearch-website/1081/2):
>
> `#` is a reserved character in [RFC 3986 - Uniform Resource Identifier (URI): Generic Syntax](https://tools.ietf.org/html/rfc3986). In the RFC, it’s supposed to introduce a fragment. My reading is that the content after the # should be on the same page. But in their case it’s not.

at the time, Roamresearch told me over email that they would fix this issue.

It would be better for us not to update Hook to deal with non-RFC compliant websites. Customer may wish to ask Roam for status/ETA about when they will change their construction of URLs.

Hook could in the future provide an advanced preference to deal with websites that treat “#” differently (possible involving a service that lists such websites), but I’d rather postpone that.

---

_[View the full topic](https://discourse.hookproductivity.com/t/invoking-a-roam-page-as-main-link-for-hook-bundle/1119)._