alec

I work for Google, but not on anything related to Meet. I'm most excited about this because the video/audio quality is much higher.

When I use Zoom with friends, everyone is usually 320x240, or maybe 640x480 if there's only one person. Doom was 320x240 in 1993.

In Google Meet, I usually see people at 1280x920. A 4k monitor will fit 6 people at that resolution.

I value this higher resolution because it makes me feel more connected to people.

I recently got a Pebble Time Round and love it. Never wanted a watch before.

Few watches provide vibrating alarms, but Pebble's helps keep me on track during the day without disturbing everyone around me with beeps. I wrote a tiny app to vibrate at different points of a meeting so I know how much time is left without boorishly checking a clock, and the development experience was smooth.

With the Android Light Flow app, I can control which contacts for which apps can send notifications, which helps keep me aware of things I need to be aware of without being a firehose of alerts.

Saving half a pound (225g) on a backpacking trip is a enough that a frequent hiker would notice.

I don't think this offers an "incompatible experience" - my reading of the post is that the experience is fully compatible and that users of non-Chrome browsers will still be able to use Google Search. Currently, some/all non-Chrome browsers won't do the extra prefetches.

> there's nothing in this analysis that suggests they're doing otherwise

The article included a decompiled code snippet showing it running methods like "sendMMSLog" and "sendPhoneCallLog", apparently logging a bunch of private data and sending it back to Uber.

Google talks a fair bit about their internal systems at this level of "descriptions but not code" - Bigtable, MapReduce, Spanner, Flume, Chubby, and more have been influential.

Works for me - I have a StartSSL personal cert and an Android phone (Nexus 5 / KitKat), and all of Chrome, Chrome Beta, and Firefox load up the site without any sort of warning or other indication. I also dug out a Jelly Bean phone (Galaxy Nexus) to try with the stock Android Browser and didn't have any issues.

Thanks! I don't really know when the website has a problem, when goread has a problem, and when I have a problem, so I end up assuming that it's goread problem. I like how the desktop web version gives a "last refreshed" and "next refreshed" indication.

Interesting writeup, thanks.

I'm a user and have been negatively impacted by the feed fetching optimizations - daily feeds are often a few days behind and come in bunches. Two examples:

- Penny Arcade updates its comics Monday, Wednesday, and Friday, always at 7:01AM UTC, and then news other times during the week. It's Wednesday at 4:25PM UTC - 9 hours after - and goread hasn't picked it up.

- Dinosaur Comics is updated weekdays. I'll eventually get all of them, but usually two or three at a time. For example, yesterday I marked all my feeds as read; today, I have entries from Monday and Tuesday, but not from Wednesday.

I had hoped that the move to the everyone-pays model would give you the resources (either developer or quota) to fix these issues, but they've gotten no better or maybe worse.

I haven't looked at what you're doing, but I believe Google Reader used pubsubhubbub where available to reduce/eliminate polling for many popular feeds.

I honestly didn't have a great experience with my last bug report, so I haven't tried again.

I'm with you. I tried tmux but didn't find any benefit and several serious drawbacks.

Many of the purported benefits - better configuration language, more maintainable code - don't matter to me:

- Screen is done and isn't going to change. Debian has had the vertical splits patch for so long I was surprised it was a patch.

- My configuration of screen is not going to change. It's five lines that I copied and pasted 10 years ago. There's just not that much that needs to be configured.

The "Multiple Clients Sharing One Session" thing is important to me and screen gets it right by default. It's useful to have a few fixed xterms on my screen and a bunch of multiplexed terminals in screen. I use one screen session per task.

I think "screen contents persisted through full-screen programs" is screen's "altscreen on" setting. Or at least that's my note from the person whose screenrc I stole.

I think he's asking what happens if you have two panes side-by-side and try to select text in one to copy. Does it also select text from the other one?