Re: [buddycloud-dev] email metadata

Hi All,

Very interesting ideas indeed.
I'm doing my Msc research on a similar topic : Reputation Management in
Email Networks in which I aim to implement a reputation management network
among peers using email systems.
Each user will have an index of reputation scores for his contacts (based
on email content analysis as per his personal context, spam/not-important
messages sent by contacts). This reputation scores can be shared among
peers to deliver a collaborative reputation network. And I'm planning to
use an extended SMTP protocol to share reputation attached to email users.
Planning to use Apache James <http://james.apache.org/>, James
Mailet<http://james.apache.org/mailet/index.html>projects for the
project.

I believe reputation management is an  essential part of social networks.
Below is the architecture I have in mind for reputation management via
email networks. Reputation Server, ReputationBox are analogous to the email
IMAP/POP servers and MBox of users. I highly appreciate your ideas on my
project and wish to incorporate your suggestions on how to extend this in
federated social network domain.


[image: Inline image 1]
Regards,
Dileepa


On Fri, Jul 26, 2013 at 12:59 PM, Melvin Carvalho
<melvincarvalho@gmail.com>wrote:

>
>
>
> On 26 July 2013 09:12, hpl <hpl1989@gmail.com> wrote:
>
>> I also very like the use of EMail. EMail has been a success for dozens of
>> years. It's natural federation. If we can overlay the social functions on
>> top of it, a decentralized social network is readily available. It's hard
>> to ask your friends to create new accounts on a DSN, but everyone has email
>> and we only need more social functions.
>>
>> Another advantage is that, email can **gracefully degrade**. You don't
>> need everyone to adopt a protocol to jumpstart the system. People who use
>> social enabled clients can extract more meta data from the multipart
>> codings. People who do not use that can still get information in degraded
>> format, e.g. plaintext, HTML.
>>
>> We have been trying this in SNSAPI. Since email is a less active channel
>> than others, we have not designed the meta data. Currently, only plaintext
>> data is sent. Looking forward to sophisticated design.
>>
>
> +1 for integration of email
>
> There can be a danger to take this paradigm to far tho, and use email at
> the exclusion of all else.  email has it's place as part of an overall FSW
> strategy, mainly as a message delivery address an as one of a few memorable
> identification strings.
>
>
>>
>>
>> Pili
>>
>>
>> On 25/7/13 6:34 PM, Andreas Kuckartz wrote:
>>
>>> Thanks for that link. I agree that the *integration* of mail with other
>>> distributed social media protocols makes a lot of sense (network
>>> effects!).
>>>
>>> I think it might also be interesting for other FSW people.
>>>
>>> Cheers,
>>> Andreas
>>> ---
>>>
>>> Simon Tennant:
>>>
>>>> This poppped up on Hacker News and is a very interesting idea. I'm
>>>> guessing
>>>> you could bolt it onto email and hope for the best. Better yet, we have
>>>> channels and ATOM formatted posts.
>>>>
>>>> https://github.com/samsquire/**ideas#1-email-metadata<https://github.com/samsquire/ideas#1-email-metadata>
>>>>
>>>> I liked this example:
>>>>
>>>>     - receive an invoice? it is added to your accounting software
>>>>
>>>> We get this for free in buddycloud because of the atom container type.
>>>>
>>>> Nice nice.
>>>>
>>>> I'll make sure to list this as a benefit on the bc website.
>>>>
>>>> S.
>>>>
>>>>
>>
>>
>