-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for hidden rooms (by link/by invite) #478
Comments
Ie the url would be obfuscated so it won't be as easy to find out about it? |
Yes! Actually there's a couple of different patterns that I'd love to think through. First, worth noting that I think we want the ability to hide at the room level, not just locations writ large. Second, I can imagine uses for both an obfuscated URL approach and whitelist approach. The use case I have heard most often is folks who have a room they want to make available to an "inner circle" or known set of people, and their fear is usually that a landlord will get wind of it. So in that case the whitelist approach seems most natural. But in practice the inner circle may not already have an account... so perhaps a bonus feature would be to route an invited email through signup (like we do for bookings) when they are invited to a room. I suppose we could always start with this and then add the obfuscated url approach after if it seems desirable (a similar thing already exists for inviting third-parties to pay invoices for bookings, which is a feature on the site already). Thoughts? |
Cool :)
That makes it a lot clearer what is actually wanted / needed.
In summary
* be able to whitelist a user / email for a room.
* if that email is not associated with a user, the user will be taken
through a sign-up first
* an email needs to go out when you whitelisting happens.
* possibly use of obfuscated url after this. Though with whitelisting it
kind of seems unnecessary
Not too much to add.
--
Sent from Gmail Mobile
|
Yes great summary :). |
eg. sigil, autumn's house.
The text was updated successfully, but these errors were encountered: