<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.6000.16544" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Aldon,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I agree that the availability of micropayment is a
critical success factor. In my view, it would be a honorable
undertaking to implement the technical base for micropayment
because this would allow many </FONT><FONT face=Arial size=2>people,
especially in developing countries, to open up their own small businesses.
However, I think it is not in the scope of this project to develop and
manage a currency or implement a banking system.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>In my view, the is only one easy way to implement
payment: </FONT><FONT face=Arial size=2>Do it off-world: The in-world vendor
specifies the web address of a payment provider. Upon payment, a
remote data channel to the provider is established and </FONT><FONT
face=Arial size=2>a browser window to the provider is opened on
the user's PC. The user pays through secure html. The vendor is notified on
the remote channel when the transaction is complete. </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>What needs to be done to implement this
?</FONT></DIV>
<DIV><FONT face=Arial size=2>- create a standard XML format for the
communication between vendor and payment provider. </FONT></DIV>
<DIV><FONT face=Arial size=2>- Implement an LL command like 'LLRequestPayment'
that opens the browser </FONT><FONT face=Arial size=2>at a specified web address
and sends payment information to the provider.</FONT></DIV>
<DIV><FONT face=Arial size=2>- Accept provider payment notification
through 'money' event. </FONT></DIV>
<DIV><FONT face=Arial size=2>- Since client based payment (prim payment) cannot
be supported without additional parameters, it should be disabled. LLGiveMoney
is also useless because</FONT></DIV>
<DIV><FONT face=Arial size=2>it is not secure.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Would this be OK ?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Ezekiel</FONT></DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=Aldon.Hynes@Orient-Lodge.com
href="mailto:Aldon.Hynes@Orient-Lodge.com">Aldon Hynes</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=opensim-dev@lists.berlios.de
href="mailto:opensim-dev@lists.berlios.de">opensim-dev@lists.berlios.de</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Sunday, November 11, 2007 6:33
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [Opensim-dev] Some more
thoughts on "Friendly teleports"</DIV>
<DIV><BR></DIV>
<DIV><SPAN class=921161717-11112007><FONT face=Arial color=#0000ff size=2>It
seems like slurl is positioned to handle some of this. Their format is
currently</FONT></SPAN></DIV>
<DIV><SPAN class=921161717-11112007><SPAN class=code><A
href="http://slurl.com/secondlife/<region>/<x-coordinate>/<y-coordinate>/<z-coordinate>/">http://slurl.com/secondlife/<region>/<x-coordinate>/<y-coordinate>/<z-coordinate>/</A></SPAN></SPAN></DIV>
<DIV><SPAN class=921161717-11112007><SPAN class=code><FONT face=Arial
color=#0000ff size=2></FONT></SPAN></SPAN> </DIV>
<DIV><SPAN class=921161717-11112007><SPAN class=code><FONT face=Arial
color=#0000ff size=2>It seems as if they could easily replace 'secondlife'
with the name of some other grid. It is also worth noting that current
version of slurl and the secondlife: protocol do not do anything to check
which grid you are connected to, so you can use within to teleport to
places within any grid.</FONT></SPAN></SPAN></DIV>
<DIV><SPAN class=921161717-11112007><SPAN class=code><FONT face=Arial
color=#0000ff size=2></FONT></SPAN></SPAN> </DIV>
<DIV><SPAN class=921161717-11112007><SPAN class=code><FONT face=Arial
color=#0000ff size=2>As to the ID/PWD, it seems as if the approach for other
protocols would seem appropriate for the osap (or whatever it gets called
protocol)</FONT></SPAN></SPAN></DIV>
<DIV><SPAN class=921161717-11112007><SPAN class=code><FONT face=Arial
color=#0000ff size=2></FONT></SPAN></SPAN> </DIV>
<DIV><SPAN class=921161717-11112007><SPAN class=code><FONT face=Arial
color=#0000ff size=2>osap://userid:password@host:port/sim/x/y/z
</FONT></SPAN></SPAN></DIV>
<DIV><SPAN class=921161717-11112007><SPAN class=code><FONT face=Arial
color=#0000ff size=2></FONT></SPAN></SPAN> </DIV>
<DIV><SPAN class=921161717-11112007><SPAN class=code><FONT face=Arial
color=#0000ff size=2>would seem to be the standard. Omitting the userid
and password would mean either anonymous access, use the current access, or
prompt for a userid and password, which is how other protocols do it.
The optional port, would behave similar to ports in other protocol
definitions. It would default to the standard port for the protocol (80
for http, 8002 for osap), unless overridden.</FONT></SPAN></SPAN></DIV>
<DIV><SPAN class=921161717-11112007><SPAN class=code><FONT face=Arial
color=#0000ff size=2></FONT></SPAN></SPAN> </DIV>
<DIV><SPAN class=921161717-11112007><SPAN class=code><FONT face=Arial
color=#0000ff size=2>One of the issues, of course, would be to get various
viewers, like the ones produced by Linden Labs and Electric Sheep to accept
and properly handle these options.</FONT></SPAN></SPAN></DIV>
<DIV><SPAN class=921161717-11112007><SPAN class=code><FONT face=Arial
color=#0000ff size=2></FONT></SPAN></SPAN> </DIV>
<DIV><SPAN class=921161717-11112007><SPAN class=code><FONT face=Arial
color=#0000ff size=2>The other issue that I'm particularly concerned about is
the relationship between authentication and 'money' in world. The built
in microcurrency, I believe, is an important part of where an open second life
needs to go. Yet this raises interesting questions about exchanging
currency between worlds. That is why the authentication, IMHO, is
important, and reasons why looking at currency and exchange rates between
grids may be especially interesting.</FONT></SPAN></SPAN></DIV>
<DIV><SPAN class=921161717-11112007><SPAN class=code><FONT face=Arial
color=#0000ff size=2></FONT></SPAN></SPAN> </DIV>
<DIV><SPAN class=921161717-11112007><SPAN class=code><FONT face=Arial
color=#0000ff size=2>Aldon</FONT></SPAN></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B>
opensim-dev-bounces@lists.berlios.de
[mailto:opensim-dev-bounces@lists.berlios.de]<B>On Behalf Of
</B>ezekiel@daelindor.com<BR><B>Sent:</B> Sunday, November 11, 2007 12:04
PM<BR><B>To:</B> opensim-dev@lists.berlios.de<BR><B>Subject:</B>
[Opensim-dev] Some more thoughts on "Friendly
teleports"<BR><BR></FONT></DIV>
<DIV><FONT face=Arial size=2>Some additional thoughts from a newbie on the
"Friendly Teleports" discussion you had back in September:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>For the OpenSims to be really open, the matter
of adressing sims and locations in sims will need to be given </FONT></DIV>
<DIV><FONT face=Arial size=2>some additional thought. Since, as you state,
OpenSim is intended to be an open network (a web) of Sims
rather</FONT></DIV>
<DIV><FONT face=Arial size=2>than a closed world like SL, there definitely
is the need for a common way of addressing locations from
outside</FONT></DIV>
<DIV><FONT face=Arial size=2>- from the web or any other world that supports
URL-type links.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>LL have a proprietary solution in addressing
secondlife://sim/x/y/z. A comparable open solution would be something
like:</FONT></DIV>
<DIV><FONT face=Arial
size=2>osap://subdomain.domain.tld/sim/x/y/z (osap is for Open
Simulator Access Protocol :)</FONT></DIV>
<DIV><FONT face=Arial size=2>IMHO the current notion of users logging
into grids with ID/PWD falls short of the requirements of an open
network. </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>P.S: I would love to discuss design decisions
that affect the usability and hence success of OpenSim. What you build
today</FONT></DIV>
<DIV><FONT face=Arial size=2>could well be the 'next big thing' that
mayaffect the online experience of millions of people in the
future.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Ezekiel</FONT> </DIV></BLOCKQUOTE>
<P>
<HR>
<P></P>_______________________________________________<BR>Opensim-dev mailing
list<BR>Opensim-dev@lists.berlios.de<BR>https://lists.berlios.de/mailman/listinfo/opensim-dev<BR></BLOCKQUOTE></BODY></HTML>