<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 29 December 2014 at 08:18, Markus Sabadello <span dir="ltr"><<a href="mailto:markus@projectdanube.org" target="_blank">markus@projectdanube.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><span class="">
<div>On 12/28/2014 11:51 PM, Melvin Carvalho
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 28 December 2014 at 22:45, Markus
Sabadello <span dir="ltr"><<a href="mailto:markus@projectdanube.org" target="_blank">markus@projectdanube.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On
today's call we talked about whether Plinth or jwchat
should be the<br>
start page.<br>
And we currently have Owncloud at the path /owncloud.<br>
<br>
I think this question of "URI namespace layout" will
become more<br>
important as we add more applications to the box.<br>
<br>
One pattern I have been experimenting with is creating
subdomains for<br>
each new application which has a web interface.<br>
I think this is more reliable than using folders, since
some<br>
applications may assume they are installed at the root /.<br>
<br>
So if my PageKite name is <a href="http://markus.pagekite.me" target="_blank">markus.pagekite.me</a>,
I could have:<br>
- <a href="http://owncloud.markus.pagekite.me" target="_blank">owncloud.markus.pagekite.me</a><br>
- <a href="http://plinth.markus.pagekite.me" target="_blank">plinth.markus.pagekite.me</a><br>
- <a href="http://jwchat.markus.pagekite.me" target="_blank">jwchat.markus.pagekite.me</a><br>
- <a href="http://radicale.markus.pagekite.me" target="_blank">radicale.markus.pagekite.me</a><br>
- <a href="http://diaspora.markus.pagekite.me" target="_blank">diaspora.markus.pagekite.me</a><br>
- <a href="http://mailpile.markus.pagekite.me" target="_blank">mailpile.markus.pagekite.me</a><br>
- etc.<br>
</blockquote>
<div><br>
</div>
<div>I was doing something similar with one of my domains.<br>
<br>
</div>
<div>It's important in the domain that contains your profile
page that the document and the person entity are
delineated. This will facilitate ability to link to our
other properties, and also more easily add future proofed
things such as a public key for PKI.<br>
<br>
</div>
<div>Note: indieweb, owncloud, diaspora do *not* use this
pattern. They are all neat systems but I suspect will run
into scalability issues for this reason. I also hope
there may be some work in fbx and/or debian to support
WebID.<br>
<br>
</div>
<div>The traditional way to do this separation is with the #
character. Unfortunately in HTP this char is overloaded
to mean many things (anchor, linked data subject, media
control, hiding device from server) so it can be very
confusing. I use #me in my profile, but #i is sometimes
used, user can choose.<br>
</div>
</div>
</div>
</div>
</blockquote></span>
I remember in Cool URIs, the other way of doing it was 303 URIs, but
that is not the preferred way anymore?<br></div></blockquote><div><br></div><div>I dont think it was ever "preferred", indeed timbl pushed back against this idea.<br><br></div><div>303s are difficult to configure, at least they are probably beyond my skill, and I dont see how to include something like a public key in the document.<br><br></div><div>That said, now, It is an accepted pattern, but timbl still warns against it (at least he did when we met at TPAC 2012) -- I'd say use at your own risk!<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF">
In general I think support for RWW/LDP/WebID/etc would be great.<br>
<br>
At some point I might want my root domain name (e.g.
<a href="http://markus.pagekite.me" target="_blank">markus.pagekite.me</a>) to support a range of different services, e.g.:<br>
- When opened in the browser, an IndieWeb-compatible site such as
Known (<a href="http://withknown.com" target="_blank">withknown.com</a>)<br></div></blockquote><div><br></div><div>sure, I do this too, using my homepage as identity for indie web apps, then #me for linked at apps -- best of both worlds<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF">
- Accessible with LDP protocol backed by gold or rww-play, etc.<br></div></blockquote><div><br></div><div>i use gold and is excellent, HTTP PATCH support coming in Jan, and websockets on the roadmap<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF">
- Smart webfinger service that points to my remoteStorage, OpenID
Connect, Mozilla Persona<span class=""><br></span></div></blockquote><div><br></div><div>sure, each have their uses, not sure if persona will survive tho<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF"><span class="">
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>Also note that serving up mixed content over different
domains, and htp vs https is something browsers have
enormous problems with. Even something as simple as using
the web crypto API will be problematic cross origin. Same
applies to a lesser extent for AJAX meshups. <br>
</div>
</div>
</div>
</div>
</blockquote></span>
But if you install completely separate applications on subdomains
such as mailpile, owncloud, diaspora, etc. then why would there be
mixed content across domains?<br></div></blockquote><div><br></div><div>just if you want to use the mashup/meshup pattern. For example, I'd like to with my fbx.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF">
Wouldn't it actually be a big security feature rather than a bug if
those separate applications can't <a href="http://en.wikipedia.org/wiki/Cross-site_scripting" target="_blank">XSS</a>
each other?<span class=""><br></span></div></blockquote><div><br></div><div>Perhaps. But you may trust the content from your own site. This is kind of use case dependent.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF"><span class="">
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>So, while I like subdomains, at least today it poses
implementation challenges. Possibly best to avoid, unless
you're providing fbx entry point for family members and/or
friends.<br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
These should also work with an "internal"
(dnsmasq-provided) domain when<br>
I access the box from within my home network, e.g.:<br>
- owncloud.freedombox<br>
- plinth.freedombox<br>
- jwchat.freedombox<br>
- radicale.freedombox<br>
- diaspora.freedombox<br>
- mailpile.freedombox<br>
- etc.<br>
<br>
In Plinth, I may want to have an option to set a "default"
one, i.e.<br>
which one should show up at <a href="http://markus.pagekite.me" target="_blank">markus.pagekite.me</a><br>
<br>
When using subdomains rather than folders, we also need
different Tor<br>
.onion addresses for each application, which is probably
preferable anyway.<br>
<br>
Thoughts?<br>
<span><font color="#888888"><br>
Markus<br>
<br>
<br>
</font></span><br>
_______________________________________________<br>
Freedombox-discuss mailing list<br>
<a href="mailto:Freedombox-discuss@lists.alioth.debian.org" target="_blank">Freedombox-discuss@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss</a><br>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</span></div>
</blockquote></div><br></div></div>