Magic FAQ

+1  

Personal information exchange - the essential missing part of social networking profiles.

YAML 想法

When people communicate face to face, it is natural for them to reciprocate and exchange information bit by bit. For example, if the other person asks me where I'm from, I ask the same in return; if I ask the person's occupation, I expect to be asked bout mine, and so we continue disclosing detail after detail to each other.

This trading of information (in barter) happens naturally when we communicate face to face, but we have no time-efficient way of doing this on-line. All what modern social networks provide is the possibility to set visibility of your static information of your profile, and if you want to share something else, you have to retype or copy-paste the information you want to share each time you want to do it, and that's a waste of time.

So, here is an idea: profiles should contain a "magic FAQ." Any visitor of your profile should be able to add a publicly invisible question to your magic FAQ; you would be notified, and have an option to answer it, both replying the questions and building your FAQ at the same time (one shot-two birds). The publicly invisible conversation could continue much like a hierarchical comments, forming a hierarchy that you possess. The next time someone asks a similar question (i.e., adds a question to your FAQ), you could tell the system that it's just another way to ask the same thing, and reuse your previous answer with a click of a button. A different follow-up question? No problem -- the data structure like pHTN (probabilistic hierarchical task network, which is just hierarchically arranged lists with probabilities of each element in the lower level of the hierarchy) can handle this, and even learn to auto-suggest you to reuse your most preferred answer (three birds?).

An expected result of this idea, is that even celebrities, who don't have enough time to chat with every fan, would suddenly have time to communicate personally, in this semi-automated manner.

P.S.: This idea is a result of mass spamming, and at the same time thinking of how to save people's time.

[Reminded by Profemaile, 2005]

Credits: Inyuki of HalfBakery.



(别通知) (可选) 请,登录

嗨[Kocmoca],欢迎访问该网站! :)

//首先,例如,我不想每次收到消息时都收到通知,我希望它使用“自动回复”。

很公平。我们想最大化我们的空闲时间。但是,正如您所提到的,还可以最大程度地提高唯一性,以便他人获得价值。同意这意味着,该模型应该非常擅长弄清楚应将其作为响应发送给现有知识库的哪些部分。所有有效点。

Hi [Kocmoca], and welcome to Homebase! :)

// First, for example, I don't want to be notified every time I get a message, I would like it to use "auto-reply".

Fair enough. We want to maximize our free time. And yet, as you mention, also maximize uniqueness, -- so that others do get the value. Agreed. Which means, the model should get pretty darn good at figuring out what parts of existing knowledge base it should send as a response. All valid points.


好主意啊!

我想知道几件事...

首先,例如,我不想每次收到消息都会收到通知,我希望它使用“自动回复”。

其次,如果将要“自动答复”,则可以减少通信联系和信任。保持唯一性和与用户的连接很重要。

That's a great idea!

I am wondering about couple of things...

First, for example, I don't want to be notified every time I get a message, I would like it to use "auto-reply".

Second, if it's going to be "auto-reply" then this can reduce the communication bond and trust. It's important to preserve uniqness and connection to the user.


语言