Groups?

[ghost]

tentd-admin displays options for "groups," but I can't find documentation for anything called groups. Can anyone clarify what a group is, or what it could be?

[titanous]

They can be used to implement Twitter-style lists, and permission groups like Google+ circles and Diaspora* aspects. The documentation is coming soon.

[pjesi]

So each profile can create groups and the id of those groups is unique within that profile?
I am asking because I need to persist the group information but there is no documentation available. What I need to know is whether I should associate them with the profile, the post, or globally? What format does the id use? Is it a URL or just something like the post id?

[tobiastom]

Please keep in mind that there should be a way to subscribe to groups from others!

Any comment about when "soon" is?

[beberlei]

Here is the short version:

• POST /groups with {"name": "Name!"}
• GET /groups
• DELETE /groups/{id}
• PUT /groups/{id} with {"name": "Name!"}
• when creating a new follower you can add "groups": ["id1", "id2"]
• You can subscribe to "https://tent.io/types/post/group/v0.1.0" post type with an application

[tobiastom]

How would I subscribe to one group from a user? This seems to be the most common use-case for twitter list users…

Am 03.11.2012 um 22:00 schrieb Benjamin Eberlei notifications@github.com:

Here is the short version:

POST /groups with {"name": "Name!"}
GET /groups
DELETE /groups/{id}
PUT /groups/{id} with {"name": "Name!"}
when creating a new follower you can add "groups": ["id1", "id2"]
You can subscribe to "https://tent.io/types/post/group/v0.1.0" post type with an application
—
Reply to this email directly or view it on GitHub.

[beberlei]

see the second last point, during /follow you pass "groups" with the ids.

@titanous How can i update the api_examples.yaml? I wanted to write the docs for this.

[Nygu]

Tobiastom is talking about public groups (e.g. you create a group which people can sign up to through your profile page). So instead of using groups to share with a limited audience, allow people to choose wether they want to follow you on a certain topic. This is something we really should do.

[tobiastom]

Thanks for clarifying my words. This was exactly what I had in mind.

Am 04.11.2012 um 11:15 schrieb Kevin Kleinman notifications@github.com:

Tobiastom is talking about public groups (e.g. you create a group which people can sign up to through your profile page). So instead of using groups to share with a limited audience, allow people to choose wether they want to follow you on a certain topic. This is something we really should do.

—
Reply to this email directly or view it on GitHub.

[titanous]

The Groups API isn't designed for "public groups", though an app could be created that uses a public profile section to do user lists.

[tobiastom]

As the subscription and notification for this groups would not be quite trivial (inspired by twitter lists), maybe this should be an extension (or something like that) to the protocol. That only if you would like to keep the basic tent protocol small, otherwise having it inside the standard would get a +1 from me.

Am 06.11.2012 um 17:02 schrieb Jonathan Rudenberg notifications@github.com:

The Groups API isn't designed for "public groups", though an app could be created that uses a public profile section to do user lists.

—
Reply to this email directly or view it on GitHub.

[titanous]

Actually, managing subscriptions with the scheme I suggested is totally feasible. Each profile update is published as a post, so an app could manage subscribing/unsubscribing to entities on "lists" quite easily.

[tobiastom]

You are right. The only problem, before I even might write that type, is that this would not provide a notification mechanism about new posts. The idea about lists, as long as I use them, is to keep the number of followings small and put them on a list, which gets new posts automatically, just like followings. As long as I don't follow them, I would not get notifications.

Am 06.11.2012 um 19:57 schrieb Jonathan Rudenberg notifications@github.com:

Actually, managing subscriptions with the scheme I suggested is totally feasible. Each profile update is published as a post, so an app could manage subscribing/unsubscribing to entities on "lists" quite easily.

—
Reply to this email directly or view it on GitHub.

[titanous]

Groups have been refined in #176.

[tobiastom]

This does not actually solve the idea about twitter style lists to organize incoming traffic. Should I create a new issue for this?