Anyone can see catalogs' products; wearing needs membership
Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
1 parent
355002ec79
commit
0a4268bb62
1 file changed
+3
-6
+3
-6
@@ -154,9 +154,8 @@ age, not verified) and `tagline`.
|
||||
|
||||
Any combination works: a public catalog can still require approval; a private one can be open to anyone who has
|
||||
the link.
|
||||
- **Seeing versus wearing** (proposed): membership is needed to get and wear a catalog's products; anyone can *see*
|
||||
them on someone else (subject to age settings), or outfits would break depending on who's looking. A catalog can
|
||||
choose members-only viewing, at the cost of members' items showing as defaults to everyone else.
|
||||
- **Seeing versus wearing** (**Decided**): anyone can *see* any catalog's products on someone else (subject to their
|
||||
own age settings); getting and wearing them needs membership where the catalog requires it.
|
||||
|
||||
## Outfits
|
||||
|
||||
@@ -296,7 +295,5 @@ The proxy streams and adds no waiting.
|
||||
|
||||
## Open questions
|
||||
|
||||
- Seeing versus wearing private catalogs' products (proposal above).
|
||||
- The takedown contact and legal entity for the hub itself.
|
||||
- Hosted rooms: how much of IMQ and the room-joining calls the client needs (being investigated; see
|
||||
docs/imq-rooms.md when it exists).
|
||||
- Hosted rooms: how much of IMQ and the room-joining calls the client needs (see docs/imq-rooms.md).
|
||||
Reference in new issue
Block a user