Re: [Social-discuss] Features [was Welcome to the proper social-discuss mailing list]

[Pieter Colpaert]

Hi everyone,

I had some thoughts I wanted to share:

* first of all, we should start from scratch. The only way making
something completely agpl and the way we want it 100% is by doing so. I
remember Matt Lee sharing my opinion, don't know if he still does.

* Graphical user interface and coding are two different things, yet
we're discussing how it should look. We should make clear distinction
between all layers and I suggest this:

I.   The way to store all users' data
II.  a dev-side API to access these data
III. User interfaces implementing this API
        - website
              ° 'user'-side API to write daisycha.in plugins
              ° clear distinction between look and coding
        - phone apps
        - other kind of clients
        - ...

So the first thing imo to think about is "what are we going to
store" (and "how are we going to store it"). 

In further stages every kind of developer will be able to participate on
to a layer without having to bother about previous or further layers.

* tight integration with identi.ca and libre.fm might be nice

* Don't think as it being an open facebook or an alternative to
facebook. We don't want to be facebook, we want to do our own thing.

For the rest, just think out of the (face)box. We might do greater
things here than anyone has ever done before. 

Pieter






On Mon, 2009-08-24 at 23:47 +0200, Melvin Carvalho wrote:
> On Mon, Aug 24, 2009 at 11:27 PM, Rob Myers<address@hidden> wrote:
> > On 24/08/09 21:18, Matt Lee wrote:
> >> Here's we'll be discussing the development of GNU social.
> >> [...]
> >> * Create a simple clone of a Facebook-style social site with basic
> >> objects for events, photos, notes, etc.
> >
> > I think a tabbed look is a good idea.
> 
> +1 facebook style tabbed look is great
> 
> >
> > At the data level, I think the most basic objects are -
> >
> > User (and User request if we require email confirmation)
> > Friendship (and Friendship request to allow confirmation by the other
> > person)
> > Photo (because people need avatars if nothing else)
> 
> Yes I think these are key starters.  It would be nice if the profiles
> were machine readable, just as libre.fm are.
> 
> >
> > And then there's various message and status objects that can be added
> > incrementally -
> >
> > Status (A status for a user a la OMB)
> > Public-message-to (A public message on another user's page)
> > Private-message-to (A private, direct, email-style message to another user)
> > Event (with details)
> > Event-attendance (will you be attending?)
> 
> OpenSocial object reference has a few more defined along the lines of events
> 
> http://wiki.opensocial.org/index.php?title=JavaScript_API_Reference
> 
> Though that may not be the ideal solution for this project, it is
> probably some food for thought.
> 
> Some other projects to look at in PHP
> 
> http://elgg.org/
> http://code.google.com/p/partuza/
> http://noserub.com/
> http://knowee.org/
> 
> I'm also working on a sem web style distirbuted soc net, but it's not
> quite in alpha.  I'll post back to the list when it is, but it would
> be great if we could work out an open messaging API so that the
> systems could talk to each other.
> 
> >
> > Photos can have more complexity later -
> >
> > Photo-set (A set of photos, for easy organization)
> > Photo-comment (A comment on a photo)
> >
> > Since we want the system to be federated (or federatable), friendships
> > and various other relationships should refer to a URL rather than a
> > simple ID.
> 
> +1
> 
> >
> > - Rob.
> >
> >
> 
>