Warning:
This wiki has been archived and is now read-only.

Microblogfunctionality

From Social Web XG Wiki
Jump to: navigation, search
  • Account Creation:You need to a W3C account to vote and join groups, and the status.net account will build on top of the central W3C database via LDAP. The connection should be one way between W3C Member Database and LDAP, i.e. status.net gets information from the W3C database. We may have a secondary database that lets additional information (social information) be stored about the user. We may allow the status.net homepage to be the default "homepage" for the user if it improves from the current "microblog" centric version to a more "Facebook" looking profile. We want affiliation and participation in groups added.
  • Group Proposal: A Web form for a new group will require a "name" and "status" as well as "initiators", and a requested "shortname" (like FSW for "Federated Social Web") that . We may want this these to be accnonced via possibly a hashtag like #newidea or #newgroup with an adequate link to a scope and title page. The form should initiate polling activities for the microblog.
  • Polling: Anyone with account can give a thumbs up to that, no definite time-limit (but might want that as optional). No poll reaction necessary. Voting should be capable with a hashag, like "#newgroup #plusone", so that might want to add status.net.
  • Poll Admin: Admins (Team members) should be able to view results of polls, double-check shortnames, close polls, to correct errors etc. Although this functionality does not need to build directly into the microblogging software.
  • Creation of New Groups: Community Group pops into existence automagically when a required number of votes via polling is done, and a certain amount of tooling (mailing lists+archives, wiki, blog) can be automatically launched. The group will need be launched at DBWG. So we'll need a hook to the database (DBWG) so that the group is launched.
  • Group Activity Page: Should have option of adding activity streams to homepage, along with options for joining, links to other pages.
  • Following Groups: When someone joins a group, they should be able (automatically?) to follow its hashtag.
  • Working Group Internal Tweets: Working group members should also have the option of a private hashtag for group internal work and updates. Therefore, some tweets, even if public, should be only given to members of the group.
  • Working Group Automatic tweets (High-level): when group passes major hurdles (new publications, blog posts, moving group to Working Group, etc.) there should be automatic tweet-outs.
  • Working Group Activity Automatic Tweets (Low-level): Automatic tweets on lower-level events, like check-ins to document updates etc. Since there is no document database, we may to check on things via brute force (i.e. checking ETag header).
  • Integration of microtweets: Microtweets should be aggregated from Facebook and Twitter as well, and then archived and searchable. Search capacity may not be critical path, but perhaps can be done via the same mechanism W3C uses for search. Also, maybe when people mention the group hashtag, they should be aggregated and be archived to W3C.org.
  • W3C-styling for Status.Net pages: There should be a W3C-specific styling for the various status.net pages. We will want to integrate this into the rest of the new site designs of community groups.