Tags: google

In AMP we trust [↗]

Jeremy Keith on AMP, concludes with:

Google says it can’t trust our self-hosted AMP pages enough to pre-render them. But they ask for a lot of trust from us. We’re supposed to trust Google to cache and host copies of our pages. We’re supposed to trust Google to provide some mechanism to users to get at the original canonical URL. I’d like to see trust work both ways.

And there lies the rub. My trust levels for Google are very low. I’ve been around long enough to know that hosted Google services/projects come-and-go with little regard to their users. Wave, Jaiku, Buzz, Reader, Knol, the list is quite impressive.

I know AMP is different from the services on the aforementioned list, but the trust damage has already been done. For me, AMP will need to fully establish itself and showcase real benefits, before I trust it enough to invest any development time in it. I’m doubtful that’ll ever happen.

248: AMP – ShopTalk [↗]

Getting AMP’d with AMP. We’re going to talk about the #hotdrama about AMP with a couple of AMP experts.

Before listening to this episode, I was completely uninterested in AMP. After listening, I’m still uninterested. The proponents did nothing to sell it to me.

That said, I can imagine how AMP could be good for end users. For example, last night I was listening to a podcast and browsing the web on my iPhone, I had just started reading an article on Boing Boing when a video advert started playing, which in-turn muted the podcast that I was listening to. Grrr. I’m thinking that AMP could have prevented this annoyance, but then again, I’m also thinking the owners of Boing Boing could also have prevented it by not deploying obnoxious ads.

 

Google Debuts ‘PhotoScan’ App for Scanning Old Photos With iPhone [↗]

Google today launched a new app called PhotoScan, which is designed to make it easy to scan printed photographs using your iPhone’s camera.

PhotoScan instructs users to take four separate quick images of a printed photo, stitching them together to create a perfect high-resolution digital copy. Google’s multi-image capture method eliminates issues that normally plague digital photos of print photographs, including glare and distortion.

This looks pretty cool, I’m looking foward to giving it a try.

Web-Font-Load [↗]

Install all Google Web Fonts onto your local machine.

There are some awesome fonts available from Google Fonts, but I’m not sure I’d want all them installed locally. Still, it’s nice to know that I can have them, if I change my mind.

Material Palette [↗]

Choose your favorite colors and get your Material Design palette generated and downloadable.

I’m liking the preview that’s available after selecting a couple of colours, a nice touch.

google-webfonts-helper [↗]

A Hassle-Free Way to Self-Host Google Fonts. Get eot, ttf, svg, woff and woff2 files + CSS snippets!

I’ve been using localfont for this purpose, but this looks good, so the next time I need to self-host some Google Fonts, I might give it a try.

How Google obliterated my 4 year old Chrome extension featuring 24k+ users [↗]

After 3 months of trying everything I could think of, I give up. I don’t think I will ever develop anything for the Google ecosystem again. I’m not angry, I’m not doing this out of spite. I just don’t think it is worth it to put any amount of effort to build something on a platform that turned out to be so unreliable.

I’m not sure what to think about the “trademark infringement” stuff, but I totally feel this guy’s frustration at attempting to get in contact with someone at Google. I’ve experienced similar frustrations when my Adsense account was disabled a few years back. At the time, my Adsense earnings paid for my project’s hosting costs, which added up to approx $500 per month. I was given no reasonable explanation for why my account was disabled and my attempts at trying to get in touch with someone at Google were fruitless. It was very frustrating and I felt like I was talking to a Python script. Grr!

Google will punish sites that use annoying pop-up ads [↗]

Google is about to deal a small blow to some of the most annoying ads on mobile: pop-ups and interstitials. It’s not a stretch to argue that readers don’t like these ads. So Google is making a call that websites that use pop-ups and interstitials are worse search results and may rank them lower because of it.

In general, I’m not a fan of letting Google dictate how developers/designers should create their web pages, but in this case, I’m all for it.

Google announcement here.

Google’s undocumented favicon to PNG converter [↗]

I came across this whilst looking for the best method of converting favicons to PNG files in PHP. I’m not sure if I’ll use it for my project, but I thought it was pretty nifty. Basically, just throw a domain at it and it’ll return a PNG image of the domain’s favicon. If the favicon does not exist, it’ll return a default PNG image.

localfont.com [↗]

Download fonts from googlefonts.

Because sometimes it’s good to load resources from your own server.

◀ Older