对于许多开启 Android 和自动备份功能的用户来说，Google+ 照片曾是默认选择……所有照片都会集中存储在一个在线位置，提供免费存储空间等等……我习惯于在 Google 页面打开它们，然后将照片拖入 Discourse。照片的 URL曾经看起来像这样：
这个链接可以正常实现一键预览：
现在我们有了 Google 照片（他们去掉了 Plus）……并且他们改变了照片 URL 的运作方式。
同一张照片，新的 Google 照片 URL：
这个无法实现一键预览，因为它不是以“.jpg”结尾。我不知道如何从该字符串中提取原始 jpg 位置。它似乎是一个完全不同的存储位置和 ID，并且末尾包含了照片尺寸信息。
能否请一位比我更聪明的人研究一下如何添加或修复这个问题？
Sure @techapj can you add this to your list?
There might be a few things to consider here in terms of where users get their URL’s from.
Here are 4 links:
Just checking in to see if there’s been any movement on this? I recently ran into the same problem for a user.
It would be great if we can get these https://goo.gl/photos/KKiG8XvS4o9BXy2r9 style links oneboxed. Both the photo and gallery versions.
Thank link doesn’t seem to work for me, can you paste a working version in Generate responsive embed codes - Iframely to see if it is even supported? (particularly for gallery versions)
Cool they seem to work actually. I added goo.gl to my site’s onebox settings and they work now. I don’t know why I thought I didn’t need to do that.
I also edited the link as I copied one of the ones above but with the link count number at the end by mistake.
Only drawback it seems is that Google shows only the top of portrait images.
There is no way URL shorteners would be expected to work here. None whatsoever.
It does work if you whitelist goo.gl. Also if you share a photo from Google Photos it generates a special goo.gl link (similar to the maps specific one) that’s just for photos. So it’s not a standard shortened link. On my site I white-listed goo.gl and if you post this link it puts the photo in.
Only problem is that portrait mode photos are cut-off. But I think that’s something wrong on Google’s end.
See this:
That photo should look like this, but it’s only showing the top part.
You would be correct. If you look at the meta tags they generate, it links to a photo that only shows the top portion of the portrait photo
We covered this in another topic, the pain here is that our “onebox any image” code depends on file extension instead of doing a HEAD/GET and pulling out the mime type.
I think we should just bite the bullet here and look at mime types cause it cleans up a bunch of places where this is the case.
(note, slack does this)
Seeing how Instagram oneboxing is working nicely, any chance the same could be applied to Google Photos albums?
Here is the link that Google produces for sharing an album with 3 photos in it:
https://photos.app.goo.gl/OPDpevnR0XUHTqA33
And here is how a Google Photos album with 3 photos is presented in Discourse:
I don’t see that used as much as Instagram, so it isn’t as much of a priority.
Onebox 现在 拥有专为 Google Photos 设计的引擎，支持相册、图片和视频链接。演示如下：
相册：
https://photos.app.goo.gl/pXA7T8zBX4WZWVMT7
图片：
https://photos.app.goo.gl/GrJbrCUDUw6JUUSv8
视频：
That is AWESOME. Thank you!!
It seems that the Onebox is cropping the image in my case. Am I doing something wrong?
https://photos.app.goo.gl/1j3E4exAQUeBSDEn7
Onebox
Full image
Onebox uses og:image tag to get image link and in above case the cropped image is what Google is linking to as per:
<meta property="og:image" content="https://lh3.googleusercontent.com/6nA9fLdVMC1TzVwZbLYSRW7LUGoe8Gm9kQ_eKktYVALvfULRzYwbd2l4tb54oUG_khyUJuP16Dha1muAT7fAKssGBcqHiFXDwlBVRvvrajaJ2Xy2hJ8HusnoHj1vnDZa3XhzW1ORZsa11AnG_zRfOii8ejgoA9SsobPJXoO3xBq9M7CDPzrOkHHhzG50bslo0FeHhN5S8TrHXmykxLSerV1879tiFo4VrvafHGyRI6iHLjaZvXVNWd-VlD58bM7lgvefBoJe8YlYCGL67cqmcL7XCRjutf6c0jKq7lY0nI9q3nZTDXssgnrvHT-jt0cLzkA8r-ODBtGG9-zhuhTpZqSS4CBsduVckZLtS8wbBPXriyWq7bWn9joynQd-vqgTLj6qdpQqCif62OZclPYr2IO4pOiAK6Fcuns6eMiEYFvv4A1DHu-9ZQ7YMkZqRjNUT8tei0pTmqw7pKUMIEqD21xFiCtF4r3rI3YiO94EaKyJZW2lNAOnIieSPG_n0sdYYT4ciCj0yGbVbdwqaF8Fq77o2AENiFhp8VVqfYbKPtt8PvAdZsoSdpasdVafkxLIPD1iGlkiMljXX9-BpjZGeUNKeLBbHp--IRi3wnbal-3OW6GxwO_H_bmed2xa8hXGfwcbyzmWS35FkkXClZhVnbWyePrYXM298Bhft5C-OZSl0R-OuGiC6rmM52Z_wWfx5njtwWIu_Xuyr35TQqAvroPi=w600-h315-p-k">
No image cropping is happening on discourse/onebox side.