> It lets the person you are talking to have novel, original thoughts, rather than repeating the thoughts they’ve had before.
But only if they're open-minded. I've met many smart people who would rather sound smart than bust their cache.
201 karma · joined March 7, 2022
But only if they're open-minded. I've met many smart people who would rather sound smart than bust their cache.
It's a unique, thoughtful and wholesome gift — something that can be both enjoyed in the moment and cherished long after. So, next anniversary, birthday or Valentine's Day, skip the usual. Surprise your partner with a Wordamour.
Do let me know if it brought a smile to your partner's face and if you've any ideas on making it more wholesome!
Yep, that would be better
> for a conversation a sentence or even a paragraph would be the right unit
Interesting thought, will explore more, thanks!
This is very interesting and something we're still exploring.
See how the button changes the comment box (but yes, need to improve it)
> I'm one of those strange people who would like infinitely nested threads in Slack too
You're not alone!
> I think it might be nice to have every thread "concluded" with a "result" (summary, outcome, to-do list, etc) which is then injected back into the parent where everybody will see it
Maybe instead of injecting into the parent, we could show it in the info box on hovering the text?
> I'd ideally like all the nested threads to naturally turn into a single linear summary of everything important that was decided
That would be beautiful!
> a thread for every single word is too fine-grained
We've seen threads being created out of two words
> who should have the rights for concluding threads?
Not sure, but I guess it could either be anyone or the person who created the thread or the person who was quoted or a specific moderator?. So probably a setting, depending on the team.
> should concluded threads be locked into read-only state?
That sounds a setting too.