Diaspora, Powered by Tent
Sean Tilley
Public
Seen by 70
This is a discussion pertaining to the attached proposal to work with Tent developers to put Diaspora's frontend on top of Tent's backend architecture.
Poll Created Mon 17 Dec 2012 5:26PM
Diaspora, Powered by Tent Closed Sun 6 Jan 2013 8:41PM
Motion abstained for now. Thank you all for your feedback. We will explore this again in a few months when a Diaspora-Tent prototype reaches feature parity and tentd can scale to support our pods.
The current proposal is here. Part of the point of this proposal is to see what our community thinks of it, and whether or not we would like to make this a part of our project's future.
Regardless of our involvement or not, the Tent developers are interested in making this port happen as a side-project. The point is not to do all of this refactoring in our own upstream, but rather to develop a working use-case on the side, get it developed to a point of being capable of replacing our current implementation of Diaspora, and in the future, deciding to move to it when Diaspora-Tent is ready.
By working together, we can bridge the Tent community with the Diaspora community, and work towards a higher goal of interoperability and decentralization. It is also worth noting that by switching to Tent's architecture, Diaspora would finally be capable of delivering on its original promises of things such as:
- Third-party API
- The ability to export your data to a different pod
- The ability to authenticate with Tent apps
- Improvements to how our search system works
- Federation with other web apps that use Tent's protocol.
It's also worth noting that the Tent devs are willing to help come up with a strategy for converting existing Diaspora accounts into Tent users, so that all of a user's posts, messages, and contacts could be converted over to Diaspora-Tent with nothing lost.
Results
| Results | Option | % of points | Voters | |
|---|---|---|---|---|
|
|
Agree | 23.1% | 3 |
|
| Abstain | 23.1% | 3 |
|
|
| Disagree | 53.8% | 7 |
|
|
| Block | 0.0% | 0 | ||
| Undecided | 0% | 44 |
|
13 of 57 people have participated (22%)
Petar Petrović
Mon 17 Dec 2012 5:36PM
I'm all for this.
Tom Scott
Mon 17 Dec 2012 5:51PM
This is like when Rails chose to replace their HTTP calls with Rack, under the hood. I've always felt that DIASPORA can and should be a more complex wrapper around tent's federated nature, and should at the least interoperate with Tent. Let's do it!
Jonne Haß
Mon 17 Dec 2012 6:35PM
Developing a separate branch and maintaining two diverging trees in such a small development community is the totally wrong approach. Lets focus on http://www.loomio.org/discussions/612 instead. Also way to early to decide on this.
Kevin Kleinman
Mon 17 Dec 2012 7:28PM
From a strategical perspective I think it's a great idea but it may be too early from a technical and organisational perspective. I hope the Diaspora community will do some prototyping. Based on those outcomes, we can continue our discussion. ;-)
Kevin Kleinman
Mon 17 Dec 2012 8:03PM
From a strategical perspective I think it's a great idea but it may be too early from a technical and organisational perspective. I hope the Diaspora community will do some prototyping. Based on those outcomes, we can continue our discussion. ;-)
Dennis Schubert
Mon 17 Dec 2012 8:03PM
See Jonne. Also:
- Tent is still owned by a company (yes, they may have plans to change that, but I just care whats fact right NOW)
- Tents HTTP-based profiles could work, but would require some hacks
- Some stuff we need is "not done yet"
- mor
Dennis Schubert
Mon 17 Dec 2012 8:04PM
See Jonne. Also:
- Tent is still owned by a company (yes, they may have plans to change that, but I just care whats fact right NOW)
- Tents HTTP-based profiles could work, but would require some hacks
- Some stuff we need is "not done yet"
- more
Flaburgan
Mon 17 Dec 2012 10:24PM
What is the real question ?
(see my post above)
Steven Hancock
Mon 17 Dec 2012 11:50PM
I can see some potential problems with this (like scalability), but if the Tent developers are putting in the work to make this happen anyway, I think we should see where this goes.