Juhan says hi!
Here's my neighbor Juhan. He's a Google fan that suffers from Macular Degeneration. Every other week I help him with his old Windows XP rig that somehow resets the font sizes back to stock.
He's still on AOL, which doesn't support larger font sizes. So when he receives a "letter" he opens it, selects Forward and uses the message editor to boost the font size. He tried switching to Comcast (Zoho?) Mail but it was a big fail.
Otherwise he does pretty well with video sites, Newspapers and Skype. Watching him use technology has been very instructive. I learned a lot watching him cope with various web sites.
Despite not using our products he's a big fan of Google and wishes us all the best!
https://
#googplus
Two questions come to mind:
- Google, master of the links, should've done this first
- It will probably get spammed to death, but that's a fairly easy problem to solve...
http://
#googplus
Turn on/off new +1 look-and-feel. Coming soon to all Googlers.
http://
http://
Cool new stuff:
- SVG 'G' and Roboto font by @106049961088401964660 's wizardry
- Did I mention Roboto? We'll be priming the font cache for 50% of the sites on the web.
- Elimination of a huge sprite (well, just so long as you're not using IE8)
#googplus
-Priceline- *Intestine Negotiator!*
_...a Priceline like service for the healthcare industry-bringing transparency to the healthcare sector in same fashion as Priceline/Kayak/Expedia did to the travel industry._
....
Your profile seems like a possible fit for our team. I have included management info below my name and I will look forward to hearing your thoughts.
#googplus
<voice style="casey-kasem">
Hot new entrant into the BadgeWidget top-40, slotting in at Number 4 It's Teaser-Trailer.
</voice>
And who knew we were up to Transformers *4*!
http://
#googplus
Mr Jingles is the best thing ever. I fully expect it to help our popularity in APAC where a mascot is almost required.
Pictured below: Toph and TophToph, the SixApart/Typepad mascots.
https://
#googplus
*RWYU* - Request What You Use?
One thing that always bothers me is useless or expensive RPCs, and the various ad-hoc ways of filtering proto fields. So I was inspired by IWYU and came up with these ideas...
** When making an RPC include a 'template' for the response. The simplest possible thing is an actual response object. Fields you want have defaultValue, fields you don't want are empty. Call it the 'Mask' or 'Filter'
FooResponse = fooRpc(FooRequest)
becomes
FooResponse = fooRpc(FooRequest request, FooResponse mask)
** Building up these masks can be tricky. So borrow code from dremel so you can make them look like a SELECT.
mask = MaskMaker.create(fooResponse, "message.*,foo.name");
** A Rpc service can then look at the fields wanted and adjust it's behavior. If a proto message isn't needed you can probably save extra downstream RPCs. The logic is actually fairly clean:
if (mask.hasMessage()) {
if (mask.getMessage().hasField()) {
m.setField(x);
}
response.setMessage(m);
}
[and you could conceive of DSLs or other mechanisms that dispatch producer logic for portions of the response.]
** A client can enforce the filter/mask by stripping out anything the server sends that it did not expect. Tracking mismatches here can identify efficiency wins.
** To make creating masks easier we could sample RPCs and find a maximal mask that includes data that is actually accessed. Just Instrument the getters on the generated proto objects and figure out what your code actually uses. (Obvious caveats apply about exceptional cases, speculative RPCs, etc.)
Anyone tried to solve this problem in a general way? Am I crazy to think that there's a general-purpose solution to this problem?
[Bonus points if we can figure out a way to also specify limits and continuation tokens inside a mask. Maybe with proto extensions?]
#googplus
Now we know why all the Noogler Helium balloons were replaced with pinwheels!
Congrats @105461895807395473744!
Couple of little things:
- Can you spec a better image for the snippet?
- Perhaps add more detail in your title?
- Add a rel="publisher" attribute to your Google+ page link.
http://
#googplus
Back in 1999 I worked with keen.com to provide a 1-900 service for linux support. Today? Well, just look at the snippet below..
http://
#googplus
Paul WFH - Work from Hospital
Unlikely I'll be @standup. Will be in office at ~11:30 if all goes to plan.
Standup Update
- Say hello to Rhidhima as you welcome her aboard as +1 2013 TL.
- Working on getting some SocialGraph CLs through the oz queue
- Followup on +1 deletion issues.
#googplus
#closure boilerplate reduction:
@107106902560384103150 submitted http://
this.getRequiredElementByClass('classname')
Also goog.ui.Component has a domhelper. You can get rid of your local domHelper_ vars in most cases and use this.getDomHelper() (and other dom helpers in goog.ui.Component) instead..
#googplus
Warning, once seen, cannot be unseen.
...
...
...
Go to your profile. Notice that your +1 tab is *+1's* instead of *+1s*.
Maybe we should rename the other tabs to:
Post's
Photo's
Review's
:-P
http://
#googplus
Do you send out emails with a noreply address?
Do you have a plus page?
Then you should consider getting your mappings added to the following bug so people can follow your page when they're reading your email updates.
https://
#googplus
An API generator with shades of Apiary being used by my former coworkers at LinkedIn..
http://
#googplus
And more from James.. Seems like it's moving in a good direction..
http://
#googplus
Was listening to Kreayshawn's Gucci Gucci, heard the shout out to Google Maps and got curious...
http://
#googplus
Actual subject line:
_Subject: traceroute Square, Inc_
Got me thinking about what unix commands one could prepend in front of a company name. Bonus points if they actually execute :)
Subject: mount Netapp.com:/jobs /home
Subject: echo "curl http://
#googplus
Care about standards? From my comment from Jeff Dean's post at http://
Here's some things you can do to support standards at Google:
-- Look at the pages your team generates the way Googlebot does:
http://
Add standard schema.org and html5 markup.
-- Discuss standards with the scant 200 other Googlers at http://
-- Participate in a standards mailing list/group. Plenty available for individuals at IETF or W3C. See standards-discuss if you want to participate as a Googler on corp-oriented bodies. Standards often suck because they're written by the standards/industrial complex instead of actual implementors.
-- Participate in an open-source project that implements a standard. These reference implementations are often poorly or insecurely coded. (For example a few people contributing to Apache Oltu would make Java OAuth that much better)
-- Consider exposing your amazing well-crafted stubby API via Apiary. Be extra careful to not break compatibility for a whole year. Write lots of integration and conformance tests.
-- Be like Vint. Suit up.
-- Above all have fun!
http://
#googplus
It's search actions. Any idea where we are with that project? Hopefully we can converge on a syntax that works for everyone.
http://
#googplus
Broadening distribution. Syncing up the Moments API (aka History API) with schema.org actions and the recent changes for inbox activities would benefit us all.
https://
#googplus
I highly recommend taking some time to set up your own Adwords campaign. It's eye-opening.
There are things I like. [targeted emails are genuinely helpful and intelligent based on your situation]
And things that are not so great. [some confusing web UI for newbies, some difficulty getting keyword/landing page quality matched to bids]
http://
#googplus
Interested in standardizing and coordination of Google's vocabulary and markup efforts? Join here!
<div itemscope
itemtype=”http://
<span itemprop=”name”>Join</span> the
<a itemprop=”url”
href=”https://
Schemarama</a>
Community!
</div>
102693216008518569997
#googplus
Anyone interested in a structured data/markup/schema group to coordinate external facing efforts?
It seems that we're moving in the same directions:
- Publisher Markup (authorship/schema)
- Interactive Posts for Google+
- Moments API
- Inbox Actions (JSON-LD)
- Tools (SDTT, markup helper)
If interested you can plus people into this thread and I'll create a G+ community with these people as seed members...
#googplus
Boswell relevant....
@103827306991532885669 -- just had a chat with the CTO of vizify where I explained authorship.
https://
#googplus
Feedback from my wife who doesn't follow many people.
- didn't like having followers show up in the list of people. She had created circles for design/art/music but they were not set to 'Following'. I think we should ask users to check this on startup. (I'm assuming that following-only circles are not used for hangouts)
- She saw someone she didn't recognize and from a following circle. Her first choice was to remove the person from her circles. That did not remove the person from the chat roster. How does Babel sync circle members and the chat roster? ANything I can tell her? (She reloaded, logged-out, logged-in) etc...
#googplus
Have to give props to the people that go through all the effort to place ads on our site.
Finicky finicky. Or is just that we internally outbid everything with the word 'google' in it?
https://
#googplus
Leafletting a Googler parking lot for low-end android phones?
Hope they're not on commission.
https://
#googplus
Animated GIF of a webpage with animated GIFs, which will go into a slides preso that will be recorded on Youtube.
I'm all out of encapsulations..
https://
#googplus
My I/O talk authorship document (pending legal approval) Improvements welcome.
*Like an H6*
Popping nodes in the dom, like a blizzard
When we code we do it right gettin slizzard
Sippin sizzurp in my box, like 6 px
Now I'm feeling so small like a H6
Like a H6, Like a H6
Now I'm feeling so small like a H6
Like a H6, Like a H6
Now I'm feeling so small like a H6
Gimme that See-SeeEssEss
Gimme that Duh-Duh-OM
Browsers love my style, and my tables gettin wild
Get them browsers scaling, we get that class and that prop
Now give me 2 more nodes cause you know it don't stop
#googplus
Looks like Vimeo embeds are working correctly in v2 now!
http://
#googplus
Compiler experts:
The JS style guide mentions that UPPER_CASE implies @const-- however when I try compiling this code using
/** @type{number}
*@const*/
var FOO = 1;
FOO = 2;
it fails, but
/**@type{number} */
var FOO = 1;
FOO = 2;
succeeds
Oddly enough this succeeds as well, which I would expect to work..
/**@type{number}@const*/
var FOO = 1;
FOO = 2;
Any ideas? These tests were done with http://
http://
#googplus
Achievement Unlocked - deleted top-level google3 directory.
I think we need a code janitors badge on moma. Suggested inspiration below:
http://
#googplus
Salon.com needs to learn
- that they have a http://
- use rel="publisher" in their page markup instead of using http://
Anyone have time to reach out?
https://
#googplus
@111466602600743594987 for the homebrew fork/follow buttons
Everyone else for the font loading technique and IE support
https://
http://
#googplus
Looks like some kind of moduleserver thingie...
https://
https://
#googplus
Can we get Google+ comments activated for the Google+ developers blog?
http://
#googplus
Achievement unlocked -- a bug I filed make the Wonder Bug list.
https://
#googplus