You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first is great for locating a community's source, but bad if the community is located on an instance other than your home instance.
The second is a remedy for the first's issue, allowing a user to copy the community string so they can place it in their home instance's search field
My recommended 3rd option would skip over the copy/paste step mandatesld by option no.2 , and allow the user to immediately open the remote community in their home instance. After which, the user can just press subscribe.
The text was updated successfully, but these errors were encountered:
I want to allow users to enter or choose their "home instance", and potentially even login.
This would mean the URL from point 1. would be a link to perhaps:
I think a better option would be to see if we can use the JS library client-side to pull the instance's communities and what the user is already subscribed to. (maybe I can also perform searches automatically?)
Add a Universal Link option in the format of /c/[email protected] so that communities will automatically open in the user's home instance.
Currently there are 2 options on a community listing:
The first is great for locating a community's source, but bad if the community is located on an instance other than your home instance.
The second is a remedy for the first's issue, allowing a user to copy the community string so they can place it in their home instance's search field
My recommended 3rd option would skip over the copy/paste step mandatesld by option no.2 , and allow the user to immediately open the remote community in their home instance. After which, the user can just press subscribe.
The text was updated successfully, but these errors were encountered: