<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://uberthings.com//teaching/dap/index.php?action=history&amp;feed=atom&amp;title=Location_based_chatting</id>
	<title>Location based chatting - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://uberthings.com//teaching/dap/index.php?action=history&amp;feed=atom&amp;title=Location_based_chatting"/>
	<link rel="alternate" type="text/html" href="https://uberthings.com//teaching/dap/index.php?title=Location_based_chatting&amp;action=history"/>
	<updated>2026-06-15T17:58:16Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.39.17</generator>
	<entry>
		<id>https://uberthings.com//teaching/dap/index.php?title=Location_based_chatting&amp;diff=409&amp;oldid=prev</id>
		<title>Jsd: New page: L.B.C. is an idea for a simple combination of the loki wifi SSID location framework and the XMPP protocol to establish chat rooms based on geographic vicinity. Previous work in this genre ...</title>
		<link rel="alternate" type="text/html" href="https://uberthings.com//teaching/dap/index.php?title=Location_based_chatting&amp;diff=409&amp;oldid=prev"/>
		<updated>2008-09-23T21:34:38Z</updated>

		<summary type="html">&lt;p&gt;New page: L.B.C. is an idea for a simple combination of the loki wifi SSID location framework and the XMPP protocol to establish chat rooms based on geographic vicinity. Previous work in this genre ...&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;L.B.C. is an idea for a simple combination of the loki wifi SSID location framework and the XMPP protocol to establish chat rooms based on geographic vicinity. Previous work in this genre is mainly based around chat software on the same TCP/IP network, such as the ichat [[http://en.wikipedia.org/wiki/Bonjour_(software) bonjour]] functionality. The issue I have with that is that it doesn&amp;#039;t designate location as the main parameter, but instead designates participation in the same  ntwork which implies location. However, unless the network has a simple topology with a small number of radio beacons (for wi-fi), the geographic correlation becomes complicated and more of an abstraction. &lt;br /&gt;
&lt;br /&gt;
A different way to observe this is with an example. If mary and dave both use ichat bonjour on the NYU campus, they know exactly two things. the first is that they both have active NYU network accounts and hence are either faculty, staff, or current students. The second piece of information is that they are currently accessing the NYU network infrastructure. However, if they want to meet or have a more specific locational awareness, they need to ask &amp;quot;where are you&amp;quot;. The benefit of the the two previous pieces of information in this case is that the answer to &amp;quot;where are you&amp;quot; will be part of familiar territory for the questioning party, e.g. a building on washington square park, or one of the cafes in the west village close to campus. &lt;br /&gt;
&lt;br /&gt;
My proposed solution is to do a proof of concept implementation of the Openfire XMPP server using the Loki location information as a way of enabling users to participate in different chat rooms. This way, chatrooms can be specifically tailored to geographic radius, and the question where are you is implicitly answered in a more a specific way.&lt;/div&gt;</summary>
		<author><name>Jsd</name></author>
	</entry>
</feed>