Merging of microblog entries.
0 views
Skip to first unread message
LanceW
Sep 23, 2008, 5:26:43 PM9/23/08
to NoseRub
In looking at my social stream I notice a pattern which I am sure is
similar for people who make microblog posts via scripts or services
like ping.fm.
The issue is that I post updates to multiple microblogging platforms,
often identical messages, which means I end up with duplicate messages
appearing in my social stream (I use a script to update twitter, jaiku
and identi.ca).
My thought is that perhaps a method of merging these entries might be
possible/desirable.
I.e. we look for identical entries and merge them in the stream
somehow with some indication that the entry was in multiple services.
The trick I guess is how to define a duplicate (especially as
different services might present an identical message in slightly
different ways. Also how do we "show" that this message is merged
efficiently.
Anyway... thoughts?
Lance
similar for people who make microblog posts via scripts or services
like ping.fm.
The issue is that I post updates to multiple microblogging platforms,
often identical messages, which means I end up with duplicate messages
appearing in my social stream (I use a script to update twitter, jaiku
and identi.ca).
My thought is that perhaps a method of merging these entries might be
possible/desirable.
I.e. we look for identical entries and merge them in the stream
somehow with some indication that the entry was in multiple services.
The trick I guess is how to define a duplicate (especially as
different services might present an identical message in slightly
different ways. Also how do we "show" that this message is merged
efficiently.
Anyway... thoughts?
Lance
Dirk Olbertz
Sep 27, 2008, 4:57:16 PM9/27/08
to NoseRub
Hi,
On 23 Sep., 23:26, LanceW <judoco...@gmail.com> wrote:
> My thought is that perhaps a method of merging these entries might be
> possible/desirable.
> I.e. we look for identical entries and merge them in the stream
> somehow with some indication that the entry was in multiple services.
>
> The trick I guess is how to define a duplicate (especially as
> different services might present an identical message in slightly
> different ways. Also how do we "show" that this message is merged
> efficiently.
When introducing the new Twitter Bridge in the upcoming NoseRub
release, I will also introduce a basic filtering for duplicates. So,
when the content is the same, the older one (because there you would
have "said" it first) is taken, or when it was created locally.
Right now, there would be no marking, that an entry was duplicated.
That would need some work in the design. I would also not find
duplicates across different users. So, if we both bookmark the same
link, it would be displayed two times in the social stream. I'm not
quite sure how to deal best with this. FriendFeed does group those,
too. But that also would need a change in layout and design of the
social stream.
So, a basic duplicate elimination will be in the next release and then
not only for micropublishing items.
Cheers,
Dirk
On 23 Sep., 23:26, LanceW <judoco...@gmail.com> wrote:
> My thought is that perhaps a method of merging these entries might be
> possible/desirable.
> I.e. we look for identical entries and merge them in the stream
> somehow with some indication that the entry was in multiple services.
>
> The trick I guess is how to define a duplicate (especially as
> different services might present an identical message in slightly
> different ways. Also how do we "show" that this message is merged
> efficiently.
release, I will also introduce a basic filtering for duplicates. So,
when the content is the same, the older one (because there you would
have "said" it first) is taken, or when it was created locally.
Right now, there would be no marking, that an entry was duplicated.
That would need some work in the design. I would also not find
duplicates across different users. So, if we both bookmark the same
link, it would be displayed two times in the social stream. I'm not
quite sure how to deal best with this. FriendFeed does group those,
too. But that also would need a change in layout and design of the
social stream.
So, a basic duplicate elimination will be in the next release and then
not only for micropublishing items.
Cheers,
Dirk
Lance Wicks
Sep 27, 2008, 5:08:28 PM9/27/08
to nos...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hash: SHA1
>
Hi,
> ... too. But that also would need a change in layout and design of the
> social stream.
I was thinking about this after writing that initial email. I was
wondering if the way to show the merged records would be to put the
16x16 icons below/to the right of the entry.
This might fit in a layout if the icon was added to all entries based
on service, then for merged ones you might see multiple icons with "+"
between them perhaps?
Thoughts?
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
iEUEARECAAYFAkjeoMwACgkQhMlS5WxqM34SuwCfXsjnpvPpFowIgmXlEg09mbrc
xSUAmItUdDmIcI7V4CjyXFN2fALVU0o=
=zd8V
-----END PGP SIGNATURE-----
David
Oct 22, 2008, 10:44:02 AM10/22/08
to NoseRub
Another partial key for deciding what is a duplicate might be the
source information. This together with a fuzzy comparison of post time
and content should make it possible to fairly accurately decide what
is an actual duplicate.
- David.
source information. This together with a fuzzy comparison of post time
and content should make it possible to fairly accurately decide what
is an actual duplicate.
- David.
Reply all
Reply to author
Forward
0 new messages