I was thinking about this, because either the user would have to select between an opaque user 1 and user 2 offering the skill/tool, or otherwise creating group chats for a skill, which I think has many other implications. The main ones I can think of off the top of my head are needing to add or remove someone from a group chat, or turn off notifications, @ people, etc. Technically, it turns a currently one-to-one relationship into potentially many-to-many.

With collectively owned tools, I could see group chats being useful, but for a skill, I would expect the group chats to mostly have single drivers. The collectively owned things question is a separate discussion, but currently we're encouraging/handling it with a collectively owned account, rather than building complex role functionality into the app.

There's also another discussion that could be had about how much ToolPool.Garden should look to replace a group's mode of discussion on certain things, and the current model for better or worse is more as a supplemental solution that only supports the communication through the proper channels and process to support anonymity, rather than being the place people eventually want to hang out in.

I would expect multiple copies of tools to be more or less the same, but especially for tools, I think multiple copies would be a good opportunity to better describe how exactly one person's way of doing something is different than another's.

I think this is also related to just copies in general, if there's 10 hammers in the group, maybe we don't want to display 10 hammers in a row, but that's how it would currently work right now. However, for someone who wants a specific flavor of a tool or skill, allowing people to just "me too" could be a downside for them.