Enhancement request: Add originating user to the activities that appear in the user's activities stream.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 254
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
Title: Enhancement request: Add originating user to the activities that appear in the user's activities stream.
Issue found of: March 26th, 2022
Endpoint(s):
GET /me/activities
Scope(s):
- None (application is not using authentication i.e., implicit flow)
Steps to reproduce:
curl --request GET \
--url 'https://api.soundcloud.com/me/activities?access=playable%2Cpreview&limit=20" -H "accept: application/json; charset=utf-8'
Expected behaviour:
It would be great if the /me/activites endpoint returned a field to identify which of the users that the authenticated user follows has caused that activity to appear in their stream.
Actual behaviour:
Activites are currently returned without the originator flagged and so activities appear in the stream without context.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the GET /me/activities endpoint and review the documented response shape for activity items. Define how the originating followed user should be identified in each activity, then verify that the response provides enough context for consumers to explain why the activity appeared.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100