iKimbo patents process of inviting people to join "communities" of discussion/interaction
"Bob Wyman" <[email protected]> Tue, 11 Feb 2003 13:14:36 -0500
| Newsgroups | gmane.network.jabber.im-patents |
|---|---|
| Message-ID | <000701c2d1f9$6fb8f750$6401a8c0@BOBDEV> |
This is a multi-part message in MIME format.
------=_NextPart_000_0008_01C2D1CF.86E2EF50
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
iKimbo (www.ikimbo.com) today received a patent on a method for
inviting people to join "communities" which include chat or instant
messaging systems. The method covers the process of creating a
"community" which is composed of various messaing and data sharing
services and inviting people to join that community (e.g. by sending an
email message). The claims seem to restrict the scope to only those
invitations that contain an executable component. However, it would seem
that even just a little bit of javascript would be enough for an
invitation to join a chat session to infringe on this patent.=20
Users of Groove will be familiar with the idea of "inviting" someone
to join a "community" of discussion. Quite a variety of other systems
have implemented similar capabilities in the past, (eMeetings,
invitations to Yahoo Groups, etc.) however, for obvious reasons, none of
these are cited as prior art. iKimbo is clearly looking for a hunting
license. Licensing fees will undoubtedly be lower than the cost of
invalidating this bad patent.
This patent is another example of why we all should be watching more
carefully the applications that are published every Thursday and
providing prior art to the PTO to stop these bad patents from being
issued.
=20
h <http://patft.uspto.gov/netacgi/nph-Parser?patentnumber=3D6519629>
ttp://patft.uspto.gov/netacgi/nph-Parser?patentnumber=3D6519629
United States Patent 6,519,629 iKimbo, February 11, 2003 =20
------------------------------------------------------------------------
--------
System for creating a community for users with common interests to
interact in=20
Abstract
An Information and Application Distribution System (IADS) is disclosed.
The IADS operates, in one embodiment, to distribute, initiate and allow
interaction and communication within like-minded communities.
Application distribution occurs through the transmission and receipt of
an "invitation application" which contains both a message component and
an executable component to enable multiple users to connect within a
specific community. The application object includes functionality which
allows the user's local computer to automatically set up a user
interface to connect with a central controller which facilitates
interaction and introduction between and among users.=20
------=_NextPart_000_0008_01C2D1CF.86E2EF50
Content-Type: text/html;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE>Message</TITLE>
<META content=3D"MSHTML 6.00.2800.1141" name=3DGENERATOR></HEAD>
<BODY>
<DIV><!--StartFragment --><FONT face=3DArial size=3D2><SPAN=20
class=3D265220418-11022003> iKimbo (<A=20
href=3D"http://www.ikimbo.com">www.ikimbo.com</A>) today received a =
patent on a=20
method for inviting people to join "communities" which include chat or =
instant=20
messaging systems. The method covers the process of creating a =
"community" which=20
is composed of various messaing and data sharing services and inviting =
people to=20
join that community (e.g. by sending an email message). The claims seem =
to=20
restrict the scope to only those invitations that contain an executable=20
component. However, it would seem that even just a little bit of =
javascript=20
would be enough for an invitation to join a chat session to infringe on =
this=20
patent. </SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D265220418-11022003> =20
Users of Groove will be familiar with the idea of "inviting" someone to =
join a=20
"community" of discussion. Quite a variety of other systems have =
implemented=20
similar capabilities in the past, (eMeetings, invitations to Yahoo =
Groups, etc.)=20
however, for obvious reasons, none of these are cited as prior art. =
iKimbo is=20
clearly looking for a hunting license. Licensing fees will undoubtedly =
be lower=20
than the cost of invalidating this bad patent.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D265220418-11022003> =20
This patent is another example of why we all should be watching more =
carefully=20
the applications that are published every Thursday and providing prior =
art to=20
the PTO to stop these bad patents from being issued.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D265220418-11022003></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><FONT><FONT face=3D"Times New =
Roman"><FONT=20
size=3D3><SPAN class=3D265220418-11022003><A=20
href=3D"http://patft.uspto.gov/netacgi/nph-Parser?patentnumber=3D6519629"=
>h</SPAN>ttp://patft.uspto.gov/netacgi/nph-Parser?patentnumber=3D6519629<=
/A><BR>United=20
States Patent 6,519,629 iKimbo, February 11, 2003=20
<BR>---------------------------------------------------------------=
-----------------<BR>System=20
for creating a community for users with common interests to interact in=20
<BR>Abstract<BR>An Information and Application Distribution System =
(IADS) is=20
disclosed. The IADS operates, in one embodiment, to distribute, initiate =
and=20
allow interaction and communication within like-minded communities. =
Application=20
distribution occurs through the transmission and receipt of an =
"invitation=20
application" which contains both a message component and an executable =
component=20
to enable multiple users to connect within a specific community. The =
application=20
object includes functionality which allows the user's local computer to=20
automatically set up a user interface to connect with a central =
controller which=20
facilitates interaction and introduction between and among users.=20
</FONT></FONT></FONT><BR><BR></DIV></FONT></BODY></HTML>
------=_NextPart_000_0008_01C2D1CF.86E2EF50--