| Twitter対応 フォトストレージ |
アニメーションGIF | PNG |
|---|---|---|
| Twitpic | ○ | ○ |
| Yfrog | × GIFだがフレーム情報が無くなる |
○ |
| ついっぷるフォト | ○ | ○ |
| img.ly | ○ | ○ |
| Lockerz | ○ （但し画像サイズが小さい場合は拡大される） |
○ |
| MobyPicture | × jpg画像へ変換される |
× jpg画像へ変換される |
| Posterous | ○ | ○ |
| Twitgoo | ○ | ○ |
private String upload(twitter4j.auth.AccessToken accessToken, String photoStorage) throws twitter4j.TwitterException, ServletException{
String url = "";
try {
中略
//アップロードする画像ファイルを取得する
java.io.File imgFile = new java.io.File(imgFilePath);
//Confifgを設定する
twitter4j.conf.ConfigurationBuilder cb = new twitter4j.conf.ConfigurationBuilder();
cb.setOAuthAccessToken(accessToken.getToken());
cb.setOAuthAccessTokenSecret(accessToken.getTokenSecret());
if(photoStorage != null ){
if(photoStorage.equals("mobypicture")){
//アップロード先にMobypictureを指定しAPIキーを設定する
cb.setMediaProvider("MOBYPICTURE");
cb.setMediaProviderAPIKey(MobypictureのAPIキー);
}else if(){
中略
}
}
twitter4j.conf.Configuration conf = cb.build();
twitter4j.media.ImageUpload imageUpload = new twitter4j.media.ImageUploadFactory(conf).getInstance();
//アップロードを実行しURLを取得する
url = imageUpload .upload(imgFile);
} catch (java.io.IOException e) {
//エラー処理
}
return url;
}
private String upload(twitter4j.auth.AccessToken accessToken, String photoStorage) throws twitter4j.TwitterException, ServletException{
String url = "";
try {
中略
//アップロードする画像ファイルを取得する
java.io.File imgFile = new java.io.File(imgFilePath);
//Confifgを設定する
twitter4j.conf.ConfigurationBuilder cb = new twitter4j.conf.ConfigurationBuilder();
cb.setOAuthAccessToken(accessToken.getToken());
cb.setOAuthAccessTokenSecret(accessToken.getTokenSecret());
if(photoStorage != null ){
if(photoStorage.equals("lockerz")){
//アップロード先にLockerzを指定しAPIキーを設定する
cb.setMediaProvider("LOCKERZ");
cb.setMediaProviderAPIKey(LockerzのAPIキー);
}else if(){
中略
}
}
twitter4j.conf.Configuration conf = cb.build();
twitter4j.media.ImageUpload imageUpload = new twitter4j.media.ImageUploadFactory(conf).getInstance();
//アップロードを実行しURLを取得する
url = imageUpload .upload(imgFile);
} catch (java.io.IOException e) {
//エラー処理
}
return url;
}
<iframe allowtransparency='true' src='http://platform.twitter.com/widgets/tweet_button.html?url=ブログのURL&text=ブログのタイトル&related=Twitterのアカウント&lang=ja&count=vertical' frameborder='0' scrolling='no' style='border:none; vertical-align:top; overflow:hidden; width:110px; height:65px;'></iframe> <iframe allowtransparency='true' frameborder='0' scrolling='no' style='width:100px; height:65px; border:none; overflow:hidden; vertical-align:top;' src='http://www.facebook.com/plugins/like.php?href=URLエンコードしたブログのURL（例：http%3a%2f%2fxxxx.blogspot.com%2f）&layout=box_count&show_faces=false&width=100px&action=like&colorscheme=light&height=65px'></iframe> <g:plusone size="tall" href="ブログのURL"></g:plusone>ガジェットのコンテンツ欄では、expr:タグが解釈されず、そのまま文字列として表示されてしまうようだ。そのため、ブログのURLやタイトルも直接入力せざるを得なかった。
<a class='twitter-share-button' data-count='horizontal' data-lang='ja' data-via='Twitterのアカウント' expr:data-text='data:title + ": "+ data:post.title' expr:data-url='data:post.url' href='http://twitter.com/share'>Tweet</a><script src='http://platform.twitter.com/widgets.js' type='text/javascript'/>
<iframe allowtransparency='true' expr:src='"http://platform.twitter.com/widgets/tweet_button.html?url=" + data:post.url + "&text=" + data:title + ": " + data:post.title + "&related=Twitterのアカウント&lang=ja&count=horizontal"' frameborder='0' scrolling='no' style='width:130px; height:20px;'/>iframe版ではsrc属性のみexprを使用。
expr:data-text='data:title + ": "+ data:post.title'としていたが、それを以下のように変更する必要があった。
text=" + data:title + ": " + data:post.title + "" が複雑につながるので注意深く編集しなくてはならない。
<div class='post-body entry-content'>
<data:post.body/>
<div style='clear: both;'/> <!-- clear for photos floats -->
<!-- Tweet Buttonなど -->
<div style='float: left; margin-top:2.0em;'>
<table border='0' cellpadding='0' cellspacing='0'>
<tr>
<td align='left' width='130'><iframe allowtransparency='true' expr:src='"http://platform.twitter.com/widgets/tweet_button.html?url=" + data:post.url + "&text=" + data:title + ": " + data:post.title + "&related=Twitterのアカウント&lang=ja&count=horizontal"' frameborder='0' scrolling='no' style='width:130px; height:20px;'/></td>
<td align='left' width='110'><iframe allowTransparency='true' expr:src='"http://www.facebook.com/plugins/like.php?href=" + data:post.url + "&layout=button_count&show_faces=false&width=90&action=like&colorscheme=light&height=21"' frameborder='0' scrolling='no' style='border:none; overflow:hidden; width:100px; height:21px;'/></td>
<td align='left' width='90'><g:plusone expr:href='data:post.url' size='medium'/></td>
</tr>
</table>
</div>
<div style='clear: both;'/>
</div>
StringBuffer callbackURL = request.getRequestURL();
int index = callbackURL.lastIndexOf("/");
callbackURL.replace(index, callbackURL.length(), "").append("/twitterCallback.jsp");
twitter4j.Twitter twitter = new twitter4j.TwitterFactory().getInstance();
twitter4j.http.RequestToken requestToken = twitter.getOAuthRequestToken(callbackURL.toString());
request.getSession().setAttribute("twitter", twitter);
request.getSession().setAttribute("requestToken", requestToken);
response.sendRedirect(requestToken.getAuthenticationURL());
twitter4j.Twitter twitter = (twitter4j.Twitter) session.getAttribute("twitter");
twitter4j.http.RequestToken requestToken = (twitter4j.http.RequestToken) session.getAttribute("requestToken");
String verifier = request.getParameter("oauth_verifier");
if(verifier == null){
//エラー処理
}else{
twitter.getOAuthAccessToken(requestToken, verifier);
session.removeAttribute("requestToken");
response.sendRedirect(request.getContextPath()+ "/twitter.jsp");
}
twitter4j.Twitter twitter = (twitter4j.Twitter) session.getAttribute("twitter");
twitter4j.http.AccessToken accessToken = null;
try{
accessToken = twitter.getOAuthAccessToken();
twitter4j.conf.ConfigurationBuilder cb = new twitter4j.conf.ConfigurationBuilder();
cb.setOAuthAccessToken(accessToken.getToken());
cb.setOAuthAccessTokenSecret(accessToken.getTokenSecret());
cb.setMediaProvider("TWITPIC");
cb.setMediaProviderAPIKey("TwitpicのAPI Key");
twitter4j.conf.Configuration conf = cb.build();
twitter4j.media.ImageUpload upload = new twitter4j.media.ImageUploaderFactory(conf).getInstance();
url = upload.upload(画像のjava.io.Fileオブジェクト);
}catch(twitter4j.TwitterException te){
//エラー処理
}
twitter4j.Twitter twitter = (twitter4j.Twitter) session.getAttribute("twitter");
twitter4j.Status status = twitter.updateStatus(text);
<iframe allowtransparency="true" frameborder="0" scrolling="no" style="width:130px; height:20px;" src="http://platform.twitter.com/widgets/tweet_button.html?url=URL（UTF-8でエンコード）&text=デフォルトで埋め込んでおきたい文字列（UTF-8でエンコード）&via=Twitterのスクリーンネーム&lang=ja&count=horizontal（ボタン横にカウントを表示）"></iframe>
メッセージ: HTML Parsing Error: Unable to modify the parent container element before the child element is closed (KB927917)
ライン: 0
文字: 0
コード: 0
メドベージェフ大統領がTwitterアカウントを持っていると知り、彼のツイート @KremlinRussia_Eを見てみたら、案の定、国後島を訪れた際の写真がTwitpicに掲載されているorz。There are so many beautiful places in Russia! Here is Kunashir http://twitpic.com/32zmwr
President of Russia
KremlinRussia_E
It is the president's duty to oversee the development of every region of the country, including the most remote ones.President of Russia
KremlinRussia_E
The @KremlinRussia_E and the @WhiteHouse both follow UK Prime Minister David Cameron @Number10gov. These three could actually conduct a direct and secret Twitter diplomacy in 140 characters literally spelling ‘the end of those red phones that have been sitting around for so long’ as Barack Obama recently joked.
Requests to the Search API, hosted on search.twitter.com, do not count towards the REST API limit. However, all requests coming from an IP address are applied to a Search Rate Limit. The Search Rate Limit isn't made public to discourage unnecessary search usage and abuse, but it is higher than the REST Rate Limit. We feel the Search Rate Limit is both liberal and sufficient for most applications and know that many application vendors have found it suitable for their needs.
There isn't a whitelist for the Search API in the same way there is for the REST API. However, under some rare circumstances we have worked with developers to raise rate limiting for their applications search requests.
We do not give preemptive whitelisting for the Search API though. You must have a working application that has proven it requires more capacity before we will discuss whitelisting. If you feel that your application is doing everything it can to limit and combine queries where appropriate you can contact the email address on the API support page to discuss your needs.
Only tweets that are both created using the Geotagging API and are placed from within a tracked bounding box will be included in the stream – the user’s location field is not used to filter tweets (e.g. if a user has their location set to “San Francisco”, but the tweet was not created using the Geotagging API and has no geo element, it will not be included in the stream).
Bounding boxes are specified as a comma separate list of longitude/latitude pairs, with the first pair denoting the southwest corner of the box. For example locations=-122.75,36.8,-121.75,37.8 would track tweets from the San Francisco area. Multiple bounding boxes may be specified by concatenating latitude/longitude pairs, for example: locations=-122.75,36.8,-121.75,37.8,-74,40,-73,41 would track tweets from San Francisco and New York City.
（・・・）and you may specify up to 25 bounding boxes.
Bounding boxes are logical ORs. A locations parameter may be combined with track parameters, but note that all terms are logically ORd, so the query string track=twitter&locations=-122.75,36.8,-121.75,37.8 would match any tweets containing the term Twitter (even non-geo tweets) OR coming from the San Francisco area.