-
Notifications
You must be signed in to change notification settings - Fork 4
W3C Activity Streams
An activity stream is a list of recent activities performed by an individual, typically on a single website. For example, Facebook's News Feed is an activity stream. Since the introduction of the News Feed on September 6, 2006, other major websites have introduced similar implementations for their own users. Since the proliferation of activity streams on websites, there have been calls to standardize the format so that websites could interact with a stream provided by another website. The Activity Streams project, for example, is an effort to develop an activity stream protocol to syndicate activities across social web applications. Several major websites with activity stream implementations have already opened up their activity streams to developers to use, including Facebook and MySpace. Activity streams come in two different variations:
Generic feeds: all users see the same content in the activity stream.
Personalised feeds: each user gets bespoke items as well as custom ranking of each element in the feed.
The standard provides a general way to represent activities. For instance "Jack added Hawaii to his list places to visit". Would be represented as actor:jack, verb:add, object:Hawaii, target:placestovisit.
Implementors of the activity Activity Streams draft include Gnip, Stream, Stream-Framework and Pump.io.
Types of Activity Streams according to W3C[3]
Little "a" activity streams: are a UI paradigm for displaying recent activity within a context. Activities are typically displayed in reverse chronological order and consist of relatively simple statements such as "John uploaded a new photo" or "12 people liked Sally's post".
Big "A" Activity Streams: is a data format for encoding and transferring activity/event metadata. The first version of the specification was published in 2011 by the independent Activity Streams Working Group and is based on extending Atom. The current (2.0+) version of the spec is JSON-based.
When activity streams became standardized, websites became able to get stream information easier from one another. AActivity stream makes it easier to categorize and track the user's activities in a single website, and therefore getting more information about the user experience which results in developing better products for users.
Though activity stream arises from social networking, nowadays it has become an essential part of business software. Enterprise social software is used in different types of companies to organize their internal communication and acts as an addition to traditional corporate intranet. Collaboration software like Jive Software, Yammer and Chatter offer activity stream as a separate product. At the same time other software providers such as tibbr, Central Desktop and Wrike offer activity stream as an integrated part of their collaboration software solution.
🏠 Home
- Requirements Specification
- Project Description
- Logo and project name ideas
- Scenarios and Mockups
- Design Documents
- Project Plan
- RAM
- Practice-app Documentation
- Backend Development Notes
- BUYO Product Data
- Android Development Guide📱
- BUYO API Documentation
- Burak Çuhadar
- Mehmet Erdinç Oğuz
- Koray Cetin
- Eylül Yalçınkaya (Communicator)
- Emre Girgin
- Berkay Alkan
- M. Olcayto Türker
- Çağrı Çiftçi
- Alperen Bağ
- Veli Can Ünal
- Berke Can Gürer
- Meriç Üngör
--- Former ---
--- CMPE 451 ---
Group Meetings
- 1st Meeting - 27.10.2020
- 2nd Meeting - 28.10.2020
- 3rd Meeting - 03.11.2020
- 4th Meeting - 10.11.2020
- 5th Meeting - 17.11.2020
- 6th Meeting - 22.11.2020
- 7th Meeting - 23.11.2020
- 8th Meeting - 25.11.2020
- 9th Meeting - 01.12.2020
- 10th Meeting - 08.12.2020
- 11th Meeting - 15.12.2020
- 12th Meeting - 22.12.2020
- 13rd Meeting - 26.12.2020
- 14th Meeting - 30.12.2020
- 15th Meeting - 05.01.2021
- 16th Meeting - 12.01.2021
- 17th Meeting - 19.01.2021
- 18th Meeting - 24.01.2021
Backend Meetings
- 1st Backend Meeting - 03.11.2020
- 2nd Backend Meeting - 09.11.2020
- 3rd Backend Meeting - 12.11.2020
- 4th Backend Meeting - 16.11.2020
- 5th Backend Meeting - 15.12.2020
- 6th Backend Meeting - 22.12.2020
- Backend-Frontend CI/CD Discussions - 22.12.2020
- Backend-Android : Payment Flow Discussion - 22.12.2020
Frontend Meetings
- 1st Frontend Meeting - 03.11.2020
- 2nd Frontend Meeting - 07.11.2020
- 3rd Frontend Meeting - 17.11.2020
- 4th Frontend Meeting - 28.11.2020
- 5th Frontend Meeting - 8.12.2020
- 6th Frontend Meeting - 15.12.2020
- 7th Frontend Meeting - 22.12.2020
- 8th Frontend Meeting - 06.01.2021
- 9th Frontend Meeting - 14.01.2021
- 10th Frontend Meeting - 19.01.2021
Android Meetings
- 1st Android Meeting - 04.11.2020
- 2nd Android Meeting - 11.11.2020
- 3rd Android Meeting - 17.11.2020
- 4th Android Meeting - 21.11.2020
- 5th Android Meeting - 22.11.2020
- 6th Android Meeting - 01.12.2020
- 7th Android Meeting - 17.12.2020
- 8th Android Meeting - 07.01.2021
- 9th Android Meeting - 20.01.2021
--- CMPE 352 ---
- 1st Meeting - 14.02.2020
- 2nd Meeting - 20.02.2020
- 3rd Meeting - 27.02.2020
- 4th Meeting - 05.03.2020
- 5th Meeting - 11.03.2020
- 6th Meeting - 16.04.2020
- 7th Meeting - 24.04.2020
- 8th Meeting - 01.05.2020
- 9th Meeting - 10.05.2020
- 10th Meeting - 17.05.2020
- Front-end Meetings for practice-app
- 1st Customer Meeting - 02.03.2020