News for hackers. Stuff that matters.
Re:Introducing Tent - the decentralized social web by mbreese on Wednesday August 22, 2012 @03:11PM (#4419023)
Why is it that every new protocol seems to want to piggy back on HTTP? It seems to me that maintaining state would be a useful feature for a social protocol.

Another issue is that this assumes that the web will be the client of choice in the future... with mobile apps being as big as they are in the social space, this seems a bit shortsighted.

Don't get me wrong, I like the idea behind having a "social server", but I don't necessarily think that starting with HTTP is the way to go.

I don't have any particular argument with using JSON for data transfer though... I think that is probably a good choice. Also using SSL for all connections is probably a good call too.

Re:Introducing Tent - the decentralized social web by Titanous on Wednesday August 22, 2012 @03:17PM (#4419064)
HTTP accomplishes all of our design constraints via REST and long-lived streaming connections. It is a very reliable, mature protocol, and the security and performance are very well understood. Also, if we invented a new binary protocol, users wouldn't be able to host their Tent servers on easy-to-use platforms like Heroku.

Developers may implement other protocols in the future, but we are targeting HTTP as an accessible starting point.

We are definitely anticipating heavy mobile use, both through mobile web apps as well as native. There will eventually be iOS and Android frameworks to handle all of the communication with Tent servers.

Re:Introducing Tent - the decentralized social web by flatline3 on Wednesday August 22, 2012 @03:55PM (#4419236)
HTTP is a huge, hefty, inefficient and complex protocol whose only advantage is that HTML/JS supports it by default. Arguments that 'websockets' solve this are ridiculous in the face of the fact that we can just use 'sockets', like we always have. WebSockets are a work-around for the constraints of the browser.

As a mobile/desktop/server engineer, I would love the opportunity to work with other server-side teams that aren't wedded to the web/HTTP via historical accident and thus don't force us to use HTTP.

Re:Introducing Tent - the decentralized social web by icebraining on Wednesday August 22, 2012 @04:52PM (#4419511)
HTTP implements an architectural style which ensures reliability, scalability, decoupling of systems and support for hypermedia for a complex network of disparate, unreliable systems and networks.

Do you have any suggestion that provides the same features, or should we forgo them because HTTP is "hefty"?

Re:Introducing Tent - the decentralized social web by flatline3 on Wednesday August 22, 2012 @06:07PM (#4419879)
> Do you have any suggestion that provides the same features

Message passing.

That's all HTTP really is, but it's dressed up in a bunch of historical complexity and inefficiency centered around supporting web browsers.

Re:Introducing Tent - the decentralized social web by icebraining on Wednesday August 22, 2012 @06:38PM (#4420003)
But do you have any concrete suggestions of protocols, or are you criticizing the choice based on an hypothetical protocol that would be very similar but incompatible with HTTP and all its existing tools (millions of tested and deployed caching servers, load balancers, etc), and for which whole new libraries would have to be written, just so you can make it somewhat more efficient?
Re:Introducing Tent - the decentralized social web by flatline3 on Wednesday August 22, 2012 @08:02PM (#4420227)
I think you're grossly over-estimating the difficulty of defining a protocol. It's no more difficult than defining the protocol for which you'll use HTTP as transport.

Load balancers know how to load balance straight TCP. HTTP caching servers are an HTTP-centric idea.

The 'libraries' you'll need can be much, much smaller when all you need is a bit of framing and serialization, instead of a complete complex RFC compliant HTTP client stack.

Re:Introducing Tent - the decentralized social web by icebraining on Thursday August 23, 2012 @03:08AM (#4421258)
I think you're grossly over-estimating the difficulty of defining a protocol.

It's not writing the protocol that I find the most difficult. It's reimplementing everything the uses the protocol.

Load balancers know how to load balance straight TCP.

Which is only useful if all the nodes are exactly the same, but that prevents you from distributing the data across them based on the user profiles, and then load balance according to the user id, as (if I'm not mistaken) Netflix does. Since they're using subdomains as user identifiers, you'd get that for free using an existing, well-tested HTTP load balancer.

HTTP caching servers are an HTTP-centric idea.

That's a tautology. The question is: are they a useful idea? Is being able to take advantage of existing and deployed solutions like CDNs useful? Seems to me like it would be.

The 'libraries' you'll need can be much, much smaller when all you need is a bit of framing and serialization, instead of a complete complex RFC compliant HTTP client stack.

I think you underestimate the advantages that some of the core HTTP concepts provide.

Re:Introducing Tent - the decentralized social web by flatline3 on Thursday August 23, 2012 @10:54AM (#4422685)
> Which is only useful if all the nodes are exactly the same, but that prevents you from distributing the data across them based on the user profiles, and then load balance according to the user id, as (if I'm not mistaken) Netflix does. Since they're using subdomains as user identifiers, you'd get that for free using an existing, well-tested HTTP load balancer.

I'm not sure what you think makes that complicated to implement without HTTP, or why you consider it 'free'. Netflix had to write custom code to support that, and could have just as easily done so on top of a message passing architecture ala ZeroMQ or even AMQP.

> That's a tautology. The question is: are they a useful idea? Is being able to take advantage of existing and deployed solutions like CDNs useful? Seems to me like it would be.

Not really, no -- neither a tautology nor are they particularly useful for API implementation. Their primary value is in caching resources for HTTP requests in a way that meshes well with the complexity of HTTP.

If you need geographically distributed resource distribution than HTTP may be a good idea simply because:

- There's widespread standardized support for HTTP resource distribution.

- Its inefficiencies are easily outweighed by the simple transit costs of a large file transfer.

We're largely talking about server "API", however.

> I think you underestimate the advantages that some of the core HTTP concepts provide.

No, the core concepts are more-or-less fine. It's the stack that's inefficient and grossly complex, largely due to browser constraints and historical limitations.

Re:Introducing Tent - the decentralized social web by icebraining on Thursday August 23, 2012 @11:08AM (#4422770)
I'm not sure what you think makes that complicated to implement without HTTP, or why you consider it 'free'. Netflix had to write custom code to support that, and could have just as easily done so on top of a message passing architecture ala ZeroMQ or even AMQP.

It's free because it already exists. Load balancers for hypothetical protocols don't.

Not really, no -- neither a tautology nor are they particularly useful for API implementation. Their primary value is in caching resources for HTTP requests in a way that meshes well with the complexity of HTTP.

If you need geographically distributed resource distribution than HTTP may be a good idea simply because:

- There's widespread standardized support for HTTP resource distribution.

- Its inefficiencies are easily outweighed by the simple transit costs of a large file transfer.

We're largely talking about server "API", however.

Isn't the whole point of this system to transfer people's content - posts, pictures, videos, etc - between servers? I would think pure API "calls" would be a small part of the whole traffic.

No, the core concepts are more-or-less fine. It's the stack that's inefficient and grossly complex, largely due to browser constraints and historical limitations.

But to implement them, you need more than "a bit of framing and serialization".

Re:Introducing Tent - the decentralized social web by flatline3 on Thursday August 23, 2012 @11:50AM (#4423010)
> But to implement them, you need more than "a bit of framing and serialization".

I posit you're still grossly overestimating complexity based on your own experience with HTTP, coupled with grossly underestimating the complexity, time costs, and efficiency costs of the stack HTTP weds you to.

A TCP stream is simple. It's as simple as it gets. Load balancing it requires a few hundred lines of code, at a maximum. It only gets complicated when you start layering on a protocol stack that is targeted at web browsers, grew over the past 20 years, requires all sorts of hoop-jumping for efficiency (keep-alive, websockets, long-polling), requires a slew of text parsing and escaping (percent-escapes, URL encoding, base64 HTTP basic auth, OAuth, ...), cookies, MIME parsing/encoding, so on and so forth.

All this complexity is targeted at web browsers, introduces significant inefficiencies, and requires huge libraries to make it accessible to application/server engineers.

What's the gain? Nothing other than familiarity, as evidenced by your belief that the core of what HTTP provides is so incredibly complicated, and you couldn't possibly replace it.

No -- it's the complexity of HTTP that's complicated, not the concepts that underly it. Drop the HTTP legacy and things get a heckuvalot simpler.

Re:Introducing Tent - the decentralized social web by icebraining on Thursday August 23, 2012 @01:22PM (#4423632)
It's not so much that you can't replace HTTP, as that you can't replace all the thousands of tools and packages that already work with HTTP, and that can be very useful for a project like this. And you can't easily replace the knowledge that people have to HTTP either. (Claiming that OAuth is part of HTTP doesn't help with your credibility either, I'm afraid.)

Furthermore, I think that even if the developers of this project could replace the required tools and forgo the rest, I doubt it'd make sense.

Frankly, you'd need a working prototype to convince me of the contrary, so I guess we'll have to leave it at that. I'm a stubborn man ;)

Re:Introducing Tent - the decentralized social web by phillmv on Wednesday August 22, 2012 @11:45PM (#4420784)
Yes, but who cares? You're just sending json down the wire. Fuck it.
Re:Introducing Tent - the decentralized social web by lmm on Thursday August 23, 2012 @09:13AM (#4422130)
If you really want a particular concrete protocol to compare to, how about AMQP?
Re:Introducing Tent - the decentralized social web by icebraining on Friday August 24, 2012 @05:09AM (#4426832)
While iMatix was the original designer of AMQP and has invested hugely in that protocol, we believe it is fundamentally flawed, and unfixable. It is too complex and the barriers to participation are massive. We do not believe that it's in the best interest of our customers and users to invest further in AMQP. Specifically, iMatix will be stepping out of the AMQP workgroup and will not be supporting AMQP/1.0 when that emerges, if it ever emerges.

By the way, the AMQP spec is roughly the same size as the HTTP spec, and the latter spends a lot of pages listing just status codes.

And of course, AMQP uses a model based on Sessions, which is great if the components of the system are static, but not that great if you're talking to a lot of nodes who come and go, since you'll end up with uneven load distribution on your servers. Regardless of HTTP as a particular implementation, I think statelessness makes perfect sense in a unreliable network of nodes.

Re:Introducing Tent - the decentralized social web by TazeTSchnitzel on Wednesday August 22, 2012 @04:21PM (#4419364)
WebSockets also have the advantage that they pass through corporate firewalls and open wifi networks, as well as many proxies, as they masquerade as HTTP traffic. And a nicer frames mechanic than raw socket, something I love. (nowhere near as low-level, but for me it's essentially stateful UDP that's reliable, i.e. TCP except with datagrams)
Re:Introducing Tent - the decentralized social web by flatline3 on Wednesday August 22, 2012 @04:28PM (#4419404)
Corporate firewalls are the general boogieman, but in reality, I haven't seen evidence that they're much more than that.

To test this, we implemented fallback-to-HTTPS behavior in a very widely used previously non-HTTP client. We then observed the number of clients that failed to connect via our custom protocol, but succeeded in falling back to HTTPS.

The numbers were negligible.

It's ridiculous that we'd seriously believe that we can't trust that TCP works on the internet. We joke about it being the "interweb", but I see no reason to sow fear, uncertainty, and doubt, and thus and actually turn the interweb into reality.

Re:Introducing Tent - the decentralized social web by TazeTSchnitzel on Wednesday August 22, 2012 @04:50PM (#4419500)
Perhaps, but open wifi often only allows 443 and 80.
Re:Introducing Tent - the decentralized social web by flatline3 on Wednesday August 22, 2012 @06:10PM (#4419900)
That also breaks IMAP(S), SMTP(S), Jabber, AIM, and a slew of other applications.

I don't see that we should model the internet architecture on bad technical choices made on a limited number of open wifi networks.

Or, we just frame our standard protocol over websockets as an (unfortunate) fallback, if it ever is revealed to be a real problem.

Re:Introducing Tent - the decentralized social web by ynniv on Wednesday August 22, 2012 @05:04PM (#4419565)
Port numbers are not protocols.
Re:Introducing Tent - the decentralized social web by cdcarter on Wednesday August 22, 2012 @08:03PM (#4420231)
Yes, but many open wifi hotspots at commercial institutions only have 80 and 443 open.
Re:Introducing Tent - the decentralized social web by flatline3 on Wednesday August 22, 2012 @09:42PM (#4420495)
I believe his point is that you can generally carry whatever protocol you want over port 443 (and often port 80).

Given how many other things are broken by networks that foolishly only open port 80 and 443, and their (in my experience) relative rarity, I'd suggest that it's not worth bothering with, except possibly as a fall-back to measure the actual number of people trying to use your service behind such a network.

Re:Introducing Tent - the decentralized social web by gizmo686 on Wednesday August 22, 2012 @08:44PM (#4420354)
Who says port 80 has to be http?
Re:Introducing Tent - the decentralized social web by cturner on Thursday August 23, 2012 @10:15AM (#4422450)
I think 443 will be a better example because (I think) it's harder for a middle party to profile https and see that it is indeed https and not something else.
Re:Introducing Tent - the decentralized social web by gizmo686 on Thursday August 23, 2012 @04:47PM (#4424753)
I don't think so, even with https, you still have the handshake which middle parties can see.
Re:Introducing Tent - the decentralized social web by fusiongyro on Wednesday August 22, 2012 @04:50PM (#4419501)
> HTTP is a huge, hefty, inefficient and complex protocol

It's starting to sound like you've never used CORBA.

Re:Introducing Tent - the decentralized social web by flatline3 on Wednesday August 22, 2012 @06:08PM (#4419888)
No, I just have worse things to say about CORBA and the notion of distributed objects in general.
Re:Introducing Tent - the decentralized social web by darkhorn on Wednesday August 22, 2012 @06:31PM (#4419983)
You can use DSNP but I cannot because shared hosting do not provide that much support. I wish everybody could use it.
Re:Introducing Tent - the decentralized social web by mbreese on Wednesday August 22, 2012 @03:27PM (#4419114)
You wouldn't have to invent a new binary protocol, a simple text protocol can work wonders (see: memcached or Redis). I'd personally look more towards SMTP for inspiration (not security wise, of course). Since you're going to mainly be passing messages back and forth, not resources.

You really should also think about two separate protocols... one server-to-server, the other server-to-client.

At least, that's how I've been working on it :)

Re:Introducing Tent - the decentralized social web by danielsiders on Wednesday August 22, 2012 @03:36PM (#4419157)
Actually, we do support passing resources back and forth and for a lot of use cases doing so saves quite a few round trips in the long run.

Our protocol has two distinct parts, one server-server, the other server-app. It's just easier to manage a single "API" than having some support server-server but not server-app--we're hoping to avoid ecosystem fragmentation into those who don't want to support apps or vice versa.

Re:Introducing Tent - the decentralized social web by mmahemoff on Wednesday August 22, 2012 @03:50PM (#4419208)
I upvoted this as it's good to question the assumption and it's easy to imagine this working better without HTTP. In practice though, I feel the project is orders of magnitude more likely if it's built with HTTP and REST. A social product needs to reach critical mass and any hurdles you're putting in front of users and developers need to be seriously justified. In this case, workarounds like cookies are Good Enough.
Re:Introducing Tent - the decentralized social web by flatline3 on Wednesday August 22, 2012 @03:52PM (#4419227)
I'd argue that -- for native client authors -- HTTP and REST are actually larger barriers than a simple non-HTTP protocol.

I also don't understand the concern over "inventing" a new binary protocol. It's not like it's any more complicated or difficult than "inventing" a non-binary protocol. The framing rules just don't use ASCII/UTF-8 field delimiters. There are plenty of existing encodings to use, no more difficult than JSON.

Re:Introducing Tent - the decentralized social web by TazeTSchnitzel on Wednesday August 22, 2012 @04:23PM (#4419373)
Only if you're using C/C++ and only native OS libraries (or on windows, afraid to use WinHttp for fear of lack of SP1 support)
Re:Introducing Tent - the decentralized social web by flatline3 on Wednesday August 22, 2012 @06:08PM (#4419886)
Marshalling back and forth between HTTP requests and in-app models via the like of NSURLConnection is far more ugly to do cleanly and efficiently than a simple state machine modeled on message passing over a socket.
Re:Introducing Tent - the decentralized social web by TazeTSchnitzel on Wednesday August 22, 2012 @06:12PM (#4419911)
That's only for Objective-C, it's nicer in Go.
Re:Introducing Tent - the decentralized social web by bickfordb on Wednesday August 22, 2012 @03:30PM (#4419128)
People build things on top of HTTP because HTTP is a pretty general, reasonable, easy to implement protocol; most alternative protocols tend to re-invent something like it or not become popular. Most protocols resemble or can be implemented on top of (Action, URI, Headers, Body) => (Status, Headers, Body). Most of the improvements suggested to HTTP tend to come in the form of encoding messages more efficiently at the cost of extensibility. Reasonably efficient HTTP servers exist for every platform.

I'm not sure exactly what you mean by maintaining state, but if you mean long-lived connections: this already exists in HTTP with chunked-encoding and the new web socket extensions. Stateful protocols tend to be more difficult to write programs for and load balance.

Re:Introducing Tent - the decentralized social web by exact-ly on Wednesday August 22, 2012 @11:39PM (#4420769)
My thoughts are similar. All due respect, this is a brittle approach and vary narrowly targeted.

Relying on HTTP, SSL, Ruby, JSON does not inspire confidence . When I see "Ruby 100%" on the github page for something that aims to move us forward out of centralisation, it makes me shudder. You need to think beyond the web, and get lower level (Tor hidden services, being outside the centralised web, are the right idea, but Tor has a certain stigma). You do need to get below the level of partisan languages- for a number of reasons, one of which is to make it open and easy for anyone to build on, not just web developers and people who know certain languages. That's a given. Get people connected (stateful) and all that will follow.

Something more like cjdns. It's the connection that's important, not the web or whatever else you chose to use the connection for. A webserver is one of many things that can be offered over a connection. I don't want to make the connection through an all-purpose application like a web browser, written by some company (Chrome in all its complex glory is trying to supplant your OS's DNS fer chrissakes, wake up- in the end, it's all about control). I want a very small and simple open source app that handles the connection to my peers and which works via the OS, not "the web". It makes the connection, keeps it alive and otherwise stays out of the way.

I think these kids need to go back to the drawing board. But anyone working on stuff like this should not give up!

Whatever the successor to centralised social networking is, it will largely be a matter of timing. The best solution might not prevail. Instead it might be the one that hits the news at exactly the right time and catches on for some unexplainable reason.

There will be more to come. That's a promise.

Re:Introducing Tent - the decentralized social web by icebraining on Thursday August 23, 2012 @04:52AM (#4421479)
What centralized web? Barring DNS - which is not mandatory for the web - there's no such thing. The web is completely decentralized. Using the web essentially means, "when making a request, use a client-server model and communicate using HTTP", nothing more, really.

Tor hidden services, being outside the centralised web, are the right idea

But most Tor hidden services are as much as the web as normal web services! They talk in a server-client model using HTTP - that's the web, right there.

I don't want to make the connection through an all-purpose application like a web browser

Using the web doesn't mean using a web browser.

written by some company (Chrome in all its complex glory is trying to supplant your OS's DNS fer chrissakes, wake up- in the end, it's all about control).

...and it certainly doesn't mean using Chrome or other browser written by some big company; there's Amaya, Arora, Camino, Dillo, Dooble, ELinks, Flock, Galeon, GNU IceCat, K-Meleon, Konqueror, Links, Lynx, Midori, Firefox, SeaMonkey, Shiira, Uzbl, Luakit and more.

I want a very small and simple open source app that handles the connection to my peers and which works via the OS, not "the web". It makes the connection, keeps it alive and otherwise stays out of the way.

Which is completely feasible using HTTP - the web - as a core protocol.

Re:Introducing Tent - the decentralized social web by exact-ly on Thursday August 23, 2012 @05:31AM (#4421563)
"centralised web" was a poor choice of words. And I thought about that but let it go. You caught it. You're paying attention. That's good.

But the point is the same - the control is concentrated in middlemen (e.g. DNS, Hosting - why do I need them?[1]) - and you articulated this correctly: client-server. Calf-cow. Not peer-to-peer. That's what I'm keen to get past.

1. That's my point about Tor's hidden services. You need Tor's help of course but those services are free from the need for DNS and Hosting - free from the middlemen that control "the web" (not to mention controlling email- does anyone send email using IP numbers anymore? the spam fighting fanatics think every revolves aroudn DNS and domain names- your mail might well get rejected because you lack a "domain name"). I must confess I've never actually used the hidden services. I only read the docs and source code.

"Using the web doesn't mean using a web browser"

Not sure what you mean here. You need to use HTTP. So you need an http client. Chances are you'll be fed heaps of html and other garbage. Parsing it is a PITA. And eventually, if you want to view tables and such, you'll be using a "browser".

Then there's the matter of state. So you're saying HTTP but not in a RESTful way? You just like HTTP headers, chunking and what not? HTTP is popular but it is not exactly unique. There are hundreds of other protocols in the RFC's, all of which would probably work just as well. HTTP is aimed at the client-server concept. That's fine. But it's a limited use for a network with so much potential. Something like a telephone conversation is not "client-server".

I'm talking about making connections that are application agnostic. Like Ethernet. If you're suggesting tunneling everything in HTTP I think that's unnecessary. There are ways to deal with firewalls. HTTP tunneling is a last resort.

So why HTTP? Why does it have to be at that layer? Why something that tied to specific applications that presume so much about what I want to do?

I want freedom from applications. I can write my own apps, thanks.

I want freedom to create new protocols, just for me and my friends. I want my own network, that we control. [This is possible using stuff that's been around for many years, and I have a working prototype. You folks are a bit too cynical to be beta testers, it's command line driven. Maybe someday.]

I've tried nearly all those "browser" options you mentioned, believe it or not. All except for one suck.

And if I had my way I'd extract the html table parser from it and have that as a standalone filter. I'd make it a UNIX utility.

The whole "browser" concept is outdated. People want to watch video, listen to audio, look at photos and read plain TEXT (with great fonts of course). I don't need html to do any of those things. And I don't need html or other HTTP junk to do search to find video, audio or images. I need a tcp (or other) connection and a video player/audio player/image viewer/typesetter, as the task requires.

All that said, hypertext is neat. But it's not world-changing. I can still do great research without "hyperlinks". Hypertext is the great benefit of HTTP. But at this stage, it is so weighed down with cruft and used in so many silly ways, making everything dependent on a monstrous abomination of a program called a "browser" (Firefox is freakin HUGE), it has become more of a burden than a benefit. It is a limitation, not a path to the future.

Re:Introducing Tent - the decentralized social web by icebraining on Thursday August 23, 2012 @06:06AM (#4421627)
But the point is the same - the control is concentrated in a small number of points (e.g. DNS, Hosting) - and you articulated this correctly: client-server. Calf-cow. Not peer-to-peer. That's what I'm keen to get past.

But the client-server is only for a single request, it's not a static property of a node. You can be both a client and a server simultaneously, making and accepting requests at all times.

Not sure what you mean here. You need to use HTTP. So you need an http client.

Yes.

Chances are you'll be fed heaps of html and other garbage.

No, HTML is definitively not necessary. Think of what it's commonly called "Web Services"; they're often only available using structured data encoding formats like JSON and they serve a whole lot of applications that are not web browsers: native mobile apps, for example.

HTML is just one of the many formats that can be transported by HTTP, nothing forces anyone to use it in order to use the web.

Then there's the matter of state. So you're saying HTTP but not in a RESTful way?

REST doesn't prevent state. It just prevents session/context state from being stored on the server. You can still store it on the client (which, again, would just be one of the roles of a node) and permanent state on both.

If you're suggesting tunneling everything in HTTP I think that's unnecessary.

If you mean tunneling as in SOAP, definitively not. I suggesting using HTTP as it's supposed to be used. Something similar would have to be reimplemented anyway, and HTTP is already there and supported by plenty of tools, services, etc.

Why does it have to be at that layer? Why applications? (...) I want freedom from applications.

I don't get what you're saying.

And if I had my way I'd extract the html table parser from it and have that as a standalone filter.

The whole "browser" concept is outdated. People want to watch video, listen to audio, look at photos and read TEXT. I don't need html to do any of those things. And I don't need html or other HTTP junk to do search to find video. I need a tcp (or other) connection and a video player.

Again, no HTML is needed. And no, a TCP connection and a video player is definitively not enough. You need some way to identify the video you want to watch, to decide what part of the video you want (e.g. if you already watched the first half), of knowing if that video still exists on the server, possibly some way to authenticate yourself (I don't want to share my personal videos with the world), and it would be nice if the video player could tell what formats it supports so that the server could send it the right version or say that none exists without having to download it.

HTTP is well known, ubiquitous, provides all that and it certainly doesn't need HTML for it.

Re:Introducing Tent - the decentralized social web by gnaritas on Wednesday August 22, 2012 @03:31PM (#4419130)
> Why is it that every new protocol seems to want to piggy back on HTTP?

For the same reason cars all want to drive on the same roads.

Re:Introducing Tent - the decentralized social web by pwf on Wednesday August 22, 2012 @03:15PM (#4419051)
They describe it as a 'protocol' on top of HTTP; I don't think that assumes much about the 'client of choice'. Most apps I've worked with already use HTTP and JSON anyway.
[deleted]
Re:Introducing Tent - the decentralized social web by mbreese on Wednesday August 22, 2012 @03:19PM (#4419071)
These aren't meant to be run from personal workstations behind firewalls, they are meant to run on servers. Firewalls in this instance shouldn't be an issue.

If firewalls were actually an issue, you could always run the service on port 443. I don't know how you'd tell anyone else that you're running on a non-standard port, but it would be possible. That's actually another potential problem... this is a server that is masquerading as an HTTPS server... I hope that it plays nice with non-Tent HTTP clients. It isn't nice to hijack ports like that.

They are seem to be assuming a web-based client, so that traffic (which does need to worry about firewalls), should pass though a firewall without issue.

Edit: parent got deleted, it was

    One word: Firewalls
Re:Introducing Tent - the decentralized social web by notatoad on Wednesday August 22, 2012 @10:37PM (#4420623)
Http gets let through firewalls. Other protocols don't.