Abstract: The present disclosure relates to synchronized sharing of playlists from a source client device to a listening client device. To facilitate synchronized sharing, a current playlist of one or more tracks of digital content is obtained from the source client device. A current playback location within the currently playing playlist is also obtained from the source client device. A shared queue accessible by the listener client device is generated. Further, a shared queue context for the listener client device is identified based in part upon the current playback location. This enables the listener client device to start playback synchronized with the source client device.

Abstract: Generating a customized playlist may include identifying a user account for which a playlist is to be generated, where the user account is associated with a user listening history, a taste profile, and a social profile, identifying one or more friend accounts linked to the user account based on the social profile, obtaining an indication of a plurality of songs associated with one or more of the friend accounts, determining a listening history for the one or more plurality of songs based on the friend accounts, obtaining a subset of the plurality of songs based on the listening history of the plurality of songs, and generating a playlist from the subset of the plurality of songs.

Abstract: The subject technology provides for coordinating output of content during a multiuser communication session by initiating, by a server responsive to a request from a first participant device of a plurality of participant devices that are connected to a multiuser communication session, a media playback session for the multiuser communication session. A network identifier corresponding to the media playback session is generated at the server. The network identifier is transmitted by the server to remainder of participant devices connected to the multiuser communication session. Upon receiving an indication of a selection of the network identifier from at least a second participant device of the plurality of the participant devices at the server, the server causes media for the media playback session to be transmitted to the first participant device and the second participant device.

Abstract: The present disclosure relates to synchronized sharing of playlists from a source client device to a listening client device. To facilitate synchronized sharing, a current playlist of one or more tracks of digital content is obtained from the source client device. A current playback location within the currently playing playlist is also obtained from the source client device. A shared queue accessible by the listener client device is generated. Further, a shared queue context for the listener client device is identified based in part upon the current playback location. This enables the listener client device to start playback synchronized with the source client device.

Abstract: The present disclosure relates to synchronized sharing of playlists from a source client device to a listening client device. To facilitate synchronized sharing, a current playlist of one or more tracks of digital content is obtained from the source client device. A current playback location within the currently playing playlist is also obtained from the source client device. A shared queue accessible by the listener client device is generated. Further, a shared queue context for the listener client device is identified based in part upon the current playback location. This enables the listener client device to start playback synchronized with the source client device.

Abstract: Some implementations allow users to create and share data including playlists. Such playlists may be subscribed to by other users. Changes to such playlists, such as updates by the curator of the playlist, must be propagated to subscribers in a timely manner while efficiently utilizing resources. Some implementations allow updates to be propagated using a push notification to cause client devices to request the update (push). Alternatively, updates may be made when the client devices of the subscribers next accesses the system (pull). An aggregator system may be used to make decisions on which users to send push notifications, and which users to wait to pull updates on their own. Additionally, the aggregator may determine that certain playlist updates should be distributed using push notifications. The aggregator may determine that only certain playlist subscribers should receive push notifications regarding playlist updates.

Abstract: Generating a customized playlist may include identifying a user account for which a playlist is to be generated, where the user account is associated with a user listening history, a taste profile, and a social profile, identifying one or more friend accounts linked to the user account based on the social profile, obtaining an indication of a plurality of songs associated with one or more of the friend accounts, determining a listening history for the one or more plurality of songs based on the friend accounts, obtaining a subset of the plurality of songs based on the listening history of the plurality of songs, and generating a playlist from the subset of the plurality of songs.

Abstract: The present disclosure relates to synchronized sharing of playlists from a source client device to a listening client device. To facilitate synchronized sharing, a current playlist of one or more tracks of digital content is obtained from the source client device. A current playback location within the currently playing playlist is also obtained from the source client device. A shared queue accessible by the listener client device is generated. Further, a shared queue context for the listener client device is identified based in part upon the current playback location. This enables the listener client device to start playback synchronized with the source client device.

Abstract: Some implementations allow users to create and share data including playlists. Such playlists may be subscribed to by other users. Changes to such playlists, such as updates by the curator of the playlist, must be propagated to subscribers in a timely manner while efficiently utilizing resources. Some implementations allow updates to be propagated using a push notification to cause client devices to request the update (push). Alternatively, updates may be made when the client devices of the subscribers next accesses the system (pull). An aggregator system may be used to make decisions on which users to send push notifications, and which users to wait to pull updates on their own. Additionally, the aggregator may determine that certain playlist updates should be distributed using push notifications. The aggregator may determine that only certain playlist subscribers should receive push notifications regarding playlist updates.

Abstract: In some implementations, a computing device can be configured to manage playlist-only media items for a user's media library. For example, when a user adds a media item to a playlist, the user can be presented with an option to add the media item to the playlist as a playlist-only media item. When the user selects to add the media item to the playlist as a playlist-only media item, the computing device can update media metadata associated with the user's media library with data indicating that the media item is a playlist-only media item. When the computing device performs operations (e.g., displaying, searching, etc.) on the user's media library, the computing device can exclude the playlist-only media items from the operations. The computing device can change the playlist-only settings for a media item to add and/or remove a media item from the user's media library.

Abstract: Some implementations allow users to create and share data including playlists. Such playlists may be subscribed to by other users. Changes to such playlists, such as updates by the curator of the playlist, must be propagated to subscribers in a timely manner while efficiently utilizing resources. Some implementations allow updates to be propagated using a push notification to cause client devices to request the update (push). Alternatively, updates may be made when the client devices of the subscribers next accesses the system (pull). An aggregator system may be used to make decisions on which users to send push notifications, and which users to wait to pull updates on their own. Additionally, the aggregator may determine that certain playlist updates should be distributed using push notifications. The aggregator may determine that only certain playlist subscribers should receive push notifications regarding playlist updates.

Abstract: The present technology pertains to automatically providing refreshed versions of personalized playlists of media items based on a refresh schedule. The automatically refreshed personalized playlists can be automatically downloaded to a client device associated with the user account. In some embodiments an animation can be presented to show that a playlist was automatically refreshed. The automatically refreshed personalized playlist can be created based on an assumption that playlists are a collection of media items that go well together in a collection.

Abstract: In some implementations, a computing device can be configured to manage playlist-only media items for a user's media library. For example, when a user adds a media item to a playlist, the user can be presented with an option to add the media item to the playlist as a playlist-only media item. When the user selects to add the media item to the playlist as a playlist-only media item, the computing device can update media metadata associated with the user's media library with data indicating that the media item is a playlist-only media item. When the computing device performs operations (e.g., displaying, searching, etc.) on the user's media library, the computing device can exclude the playlist-only media items from the operations. The computing device can change the playlist-only settings for a media item to add and/or remove a media item from the user's media library.

Abstract: Some implementations allow users to create and share data including playlists. Such playlists may be subscribed to by other users. Changes to such playlists, such as updates by the curator of the playlist, must be propagated to subscribers in a timely manner while efficiently utilizing resources. Some implementations allow updates to be propagated using a push notification to cause client devices to request the update (push). Alternatively, updates may be made when the client devices of the subscribers next accesses the system (pull). An aggregator system may be used to make decisions on which users to send push notifications, and which users to wait to pull updates on their own. Additionally, the aggregator may determine that certain playlist updates should be distributed using push notifications. The aggregator may determine that only certain playlist subscribers should receive push notifications regarding playlist updates.