Your English can be smarter.
真心話時間
如果可以聰明，誰想要看起來呆呆的
你說大智若愚？我說你想太多。讀的人沒讀到大智，只讀到愚
更大的問題是很多人錯也不知道錯了，更不知道自己英文寫得很呆，就像寫中文信不知道自己寫錯字或表達錯誤，讓讀的人一頭霧水或者不把你當一回事
「完美寫手」特訓班除了把重要觀念和原則都搞定，不再犯低級錯誤，還要教你寫聰明英文
底下這些情境舉例：
1. 我代表開會/出差，之後會再補上進度。
「我再跟你說」
你可能會寫：
I’ll tell you about it.
模糊！
I’ll let you know.
好一點。
完美寫手：
I’ll fill you in.
聰明簡單又清楚。
- fill someone in
補上資訊
#memo好用
2. 希望對方在下班前回覆
你可能會寫：
Please reply today.
很沒禮貌。
Please reply at your earliest convenience.
客氣多了但對方可能下禮拜才回你。
完美寫手：
Looking forward to your response by the end of business today.
- end of business 下班時間
也簡稱 #EOB
所以下班前有人寫成 before EOB
3. 感謝對方撥空出席活動
你可能會寫：
Thank you for coming. You’re so busy and you still came.
不糟，就是微呆，可以更好。
Thank you for taking time out of your busy schedule to join us.
不錯，可以更精練。
完美寫手：
We appreciate your support for us amid your tight schedule.
要寫好英文，這些都是基本功的展現而已。懂的人也都在字裡行間讀得出功力。
課程涵蓋多樣文體：
https://bit.ly/3pAyV7F
開課在即，名額有限，快加入吧！
#留言 試試身手
「這次首波產品的推出非常成功！」
浩爾限量幫你批改喔
👨🏻🏫 完美寫手培訓班 👨🏻🏫
開課時間：12/5（六）9:00-12:00
上課地點：台北市大安區／線上班開放報名🔥
來上課囉 >> https://bit.ly/3pAyV7F
response time中文 在 YouTube Data API Overview | Google Developers 的推薦與評價
Introduction
This document is intended for developers who want to write applications that interact with YouTube. It explains basic concepts of YouTube and of the API itself. It also provides an overview of the different functions that the API supports.
Before you startYou need a Google Account to access the Google API Console, request an API key, and register your application.
Create a project in the Google Developers Console and obtain authorization credentials so your application can submit API requests.
After creating your project, make sure the YouTube Data API is one of the services that your application is registered to use:
Go to the API Console and select the project that you just registered.
Visit the Enabled APIs page.
In the list of APIs, make sure the status is ON for the YouTube Data API v3.
If your application will use any API methods that require user authorization, read the authentication guide to learn how to implement OAuth 2.0 authorization.
Select a client library to simplify your API implementation.
Familiarize yourself with the core concepts of the JSON (JavaScript Object Notation) data format. JSON is a common, language-independent data format that provides a simple text representation of arbitrary data structures. For more information, see json.org.
Resources and resource types
A resource is an individual data entity with a unique identifier. The table below describes the different types of resources that you can interact with using the API.
Resources
activityContains information about an action that a particular user has taken on the YouTube site. User actions that are reported in activity feeds include rating a video, sharing a video, marking a video as a favorite, and posting a channel bulletin, among others.
channelContains information about a single YouTube channel.
channelBannerIdentifies the URL to use to set a newly uploaded image as the banner image for a channel.
channelSectionContains information about a set of videos that a channel has chosen to feature. For example, a section could feature a channel's latest uploads, most popular uploads, or videos from one or more playlists.
guideCategoryIdentifies a category that YouTube associates with channels based on their content or other indicators, such as popularity. Guide categories seek to organize channels in a way that makes it easier for YouTube users to find the content they're looking for. While channels could be associated with one or more guide categories, they are not guaranteed to be in any guide categories.
i18nLanguageIdentifies an application language that the YouTube website supports. The application language can also be referred to as a UI language.
i18nRegionIdentifies a geographic area that a YouTube user can select as the preferred content region. The content region can also be referred to as a content locale.
playlistRepresents a single YouTube playlist. A playlist is a collection of videos that can be viewed sequentially and shared with other users.
playlistItemIdentifies a resource, such as a video, that is part of a playlist. The playlistItem resource also contains details that explain how the included resource is used in the playlist.
search resultContains information about a YouTube video, channel, or playlist that matches the search parameters specified in an API request. While a search result points to a uniquely identifiable resource, like a video, it does not have its own persistent data.
subscriptionContains information about a YouTube user subscription. A subscription notifies a user when new videos are added to a channel or when another user takes one of several actions on YouTube, such as uploading a video, rating a video, or commenting on a video.
thumbnailIdentifies thumbnail images associated with a resource.
videoRepresents a single YouTube video.
videoCategoryIdentifies a category that has been or could be associated with uploaded videos.
watermarkIdentifies an image that displays during playbacks of a specified channel's videos. The channel owner can also specify a target channel to which the image links as well as timing details that determine when the watermark appears during video playbacks and then length of time it is visible.
Note that, in many cases, a resource contains references to other resources. For example, a
Supported operationsplaylistItemresource'ssnippet.resourceId.videoIdproperty identifies a video resource that, in turn, contains complete information about the video. As another example, a search result contains either avideoId,playlistId, orchannelIdproperty that identifies a particular video, playlist, or channel resource.The following table shows the most common methods that the API supports. Some resources also support other methods that perform functions more specific to those resources. For example, the
videos.ratemethod associates a user rating with a video, and thethumbnails.setmethod uploads a video thumbnail image to YouTube and associates it with a video.Operations
listRetrieves (
GET) a list of zero or more resources.insertCreates (
POST) a new resource.updateModifies (
PUT) an existing resource to reflect data in your request.deleteRemoves (
DELETE) a specific resource.The API currently supports methods to list each of the supported resource types, and it supports write operations for many resources as well.
The table below identifies the operations that are supported for different types of resources. Operations that insert, update, or delete resources always require user authorization. In some cases,
listmethods support both authorized and unauthorized requests, where unauthorized requests only retrieve public data while authorized requests can also retrieve information about or private to the currently authenticated user.Supported Operations
list
insert
update
delete
activitycaptionchannelchannelBannerchannelSectioncommentcommentThreadguideCategoryi18nLanguagei18nRegionplaylistplaylistItemsearch resultsubscriptionthumbnailvideovideoCategorywatermarkQuota usage
The YouTube Data API uses a quota to ensure that developers use the service as intended and do not create applications that unfairly reduce service quality or limit access for others. All API requests, including invalid requests, incur at least a one-point quota cost. You can find the quota available to your application in the API Console.
Projects that enable the YouTube Data API have a default quota allocation of 10,000 units per day, an amount sufficient for the overwhelming majority of our API users. Default quota, which is subject to change, helps us optimize quota allocations and scale our infrastructure in a way that is more meaningful to our API users. You can see your quota usage on the Quotas page in the API Console.
Note: If you reach the quota limit, you can request additional quota by
Calculating quota usagecompleting the Quota extension
request form for YouTube API Services.
Google calculates your quota usage by assigning a cost to each request. Different types of
operations have different quota costs. For example:
A read operation that retrieves a list of resources -- channels, videos, playlists -- usually
costs 1 unit.
A write operation that creates, updates, or deletes a resource usually has costs
50units.A search request costs
100units.A video upload costs
1600units.The Quota costs for API requests table shows the
Partial resourcesquota cost of each API method. With these rules in mind, you can estimate the number of requests
that your application could send per day without exceeding your quota.
The API allows, and actually requires, the retrieval of partial resources so that applications avoid transferring, parsing, and storing unneeded data. This approach also ensures that the API uses network, CPU, and memory resources more efficiently.
The API supports two request parameters, which are explained in the following sections, that enable you to identify the resource properties that should be included in API responses.
How to use theThe
partparameter identifies groups of properties that should be returned for a resource.The
fieldsparameter filters the API response to only return specific properties within the requested resource parts.partparameterThe
partparameter is a required parameter for any API request that retrieves or returns a resource. The parameter identifies one or more top-level (non-nested) resource properties that should be included in an API response. For example, avideoresource has the following parts:snippetcontentDetailsfileDetailsplayerprocessingDetailsrecordingDetailsstatisticsstatussuggestionstopicDetailsAll of these parts are objects that contain nested properties, and you can think of these objects as groups of metadata fields that the API server might (or might not) retrieve. As such, the
partparameter requires you to select the resource components that your application actually uses. This requirement serves two key purposes:It reduces latency by preventing the API server from spending time retrieving metadata fields that your application doesn't use.
It reduces bandwidth usage by reducing (or eliminating) the amount of unnecessary data that your application might retrieve.
Over time, as resources add more parts, these benefits will only increase since your application will not be requesting newly introduced properties that it doesn't support.
How to use thefieldsparameterThe
fieldsparameter filters the API response, which only contains the resource parts identified in thepartparameter value, so that the response only includes a specific set of fields. Thefieldsparameter lets you remove nested properties from an API response and thereby further reduce your bandwidth usage. (Thepartparameter cannot be used to filter nested properties from a response.)The following rules explain the supported syntax for the
fieldsparameter value, which is loosely based on XPath syntax:Use a comma-separated list (
fields=a,b) to select multiple fields.Use an asterisk (
fields=*) as a wildcard to identify all fields.Use parentheses (
fields=a(b,c)) to specify a group of nested properties that will be included in the API response.Use a forward slash (
fields=a/b) to identify a nested property.In practice, these rules often allow several different
fieldsparameter values to retrieve the same API response. For example, if you want to retrieve the playlist item ID, title, and position for every item in a playlist, you could use any of the following values:fields=items/id,playlistItems/snippet/title,playlistItems/snippet/positionfields=items(id,snippet/title,snippet/position)fields=items(id,snippet(title,position))Note: As with all query parameter values, the
Sample partial requestsfieldsparameter value must be URL encoded. For better readability, the examples in this document omit the encoding.The examples below demonstrate how you can use the
partandfieldsparameters to ensure that API responses only include the data that your application uses:Example 1 returns a video resource that includes four parts as well as
kindandetagproperties.Example 2 returns a video resource that includes two parts as well as
kindandetagproperties.Example 3 returns a video resource that includes two parts but excludes
kindandetagproperties.Example 4 returns a video resource that includes two parts but excludes
kindandetagas well as some nested properties in the resource'ssnippetobject.Example 1
Example 2
Example 3
Example 4
Optimizing performance
Using ETags
ETags, a standard part of the HTTP protocol, allow applications to refer to a specific version of a particular API resource. The resource could be an entire feed or an item in that feed. This functionality supports the following use cases:
Caching and conditional retrieval – Your application can cache API resources and their ETags. Then, when your application requests a stored resource again, it specifies the ETag associated with that resource. If the resource has changed, the API returns the modified resource and the ETag associated with that version of the resource. If the resource has not changed, the API returns an HTTP 304 response (
Not Modified), which indicates that the resource has not changed. Your application can reduce latency and bandwidth usage by serving cached resources in this manner.The client libraries for Google APIs differ in their support of ETags. For example, the JavaScript client library supports ETags via a whitelist for allowed request headers that includes
If-MatchandIf-None-Match. The whitelist allows normal browser caching to occur so that if a resource's ETag has not changed, the resource can be served from the browser cache. The Obj-C client, on the other hand, does not support ETags.Protecting against inadvertent overwrites of changes – ETags help to ensure that multiple API clients don't inadvertently overwrite each other's changes. When updating or deleting a resource, your application can specify the resource's ETag. If the ETag doesn't match the most recent version of that resource, then the API request fails.
Using ETags in your application provides several benefits:
The API responds more quickly to requests for cached but unchanged resources, yielding lower latency and lower bandwidth usage.Your application will not inadvertently overwrite changes to a resource that were made from another API client.
The Google APIs Client Library for JavaScript supports
If-MatchandIf-None-MatchHTTP request headers, thereby enabling ETags to work within the context of normal browser caching.Using gzip
You can also reduce the bandwidth needed for each API response by enabling gzip compression. While your application will need additional CPU time to uncompress API responses, the benefit of consuming fewer network resources usually outweighs that cost.
To receive a gzip-encoded response you must do two things:
Set the
Accept-EncodingHTTP request header togzip.Modify your user agent to contain the string
gzip.The sample HTTP headers below demonstrate these requirements for enabling gzip compression:
... <看更多>