Content on 6D

[Wogan]

I'm trying to get my head around the way the content on 6D should
work.

It seems, to me, that it'd make the most sense to structure everything
around Updates. A bit like transplanting Facebook's status update
system, with support for:

* Links
* Statuses
* Blog posts
* Photo uploads
* Linked videos
* Galleries
* File uploads

In terms of the database structure, this reduces every update to a
single line item, with a type, title, and Content - which is either a
post, list of URLs to photos, etc. This also entails a super-compact
interface for posting, since everything is happening at the front of
that site.

Another thing to consider is comments: If they're allowed, where are
they stored, how are they exchanged, and do the content ownership
rights work?

[Joey Guerra]

That's exactly the direction the codebase is going. There's a posts
table that has a type field, indicating the type of content it
contains. I'm in the process of adding the concept of an owner to each
resource now so there'll also be an owner_id field in many of the
tables.

We haven't addressed comments yet. Our preliminary discussions talked
about using Twitter or Discus, not necessarily incorporating them into
6d since comments are mostly public and those services are for public
discussions.

[Keith DiSarno]

Twitter, eh? Seems a bit public and the equivalent to an internet
shouting match.

Relying on 3rd parties can be dangerous as well. Server uptime and
accessibility aside, they would own all the comments. (I've seen that
blue beached whale more than I care to count.) Trapani's ThinkTank
kinda organizes it I believe.

[Joey Guerra]

I totally agree. But until we can get some other developers working on
the project, we're focusing our efforts on multi member support right
now. We still have to get a photo UI built. We've got a long way to go
and short time to get there:)

[Erik Bigelow]

A comments system kinda goes against what we currently think the
direction of 6d should be. The theory is "one person, one site" and
you communicate with each other's site through your own. As we're now
building multi-member support the same still holds true. While each
member is a part of one domain they will still essentially have their
own instance of a 6d site with their own separate addressbooks and
"friends". We did this because having to register at every site you
go to is annoying and silly, there's only one you, so there should be
a way to control that through your site. One of the next steps we
have is probably going to be building in a single-user OpenID server
into the framework also. Again your identity should be completely
under your control.

Now obviously some will want comments on their site and I think that's
best left to a Disqus plugin or maybe twitter. Yeah it sucks having
to rely on a third party, but I think so does registering at sites and
relying on them to host your thoughts.