Paul Lindner

At first I thought this was a menswear catalog and almost tossed it in the recycling bin....

#googplus

"When a measure becomes a target, it ceases to be a good measure."

https://en.wikipedia.org/wiki/Goodhart%27s_law

#googplus

I finally made it to the Allyship Fundamentals course. Recommended.

https://sites.google.com/corp/google.com/allyship/home

#googplus

I think it's time for a Legal Deposit scheme for Games.

- Game publishers would put their games in Escrow when they publish.  
- Game Services could publish a spec on how to interpret the game contents.
- 'Orphan' games would actually be preserved.- Users that purchased the Game would then be entitled to a copy of the escrowed item, plus the design on how to run them.

This, combined with an export of user-generated data would allow for usability after Stadia or the Game Publisher sunsets the service/game.

And to be honest I'd love to see this extended to all Online "Stores" that don't let you export usable contents.

Barring that Game Services could enter a Ulysses Pact with users if they are serious about the long-haul.. 

 For each purchase a user makes put 10x in a locked escrow fund.  When the service cancels that money can be used to migrate the games to a new provider or payout back the user.

- If a Game Service gets few users it's not a lot of money to exit and actually would increase satisfaction.
- If a Game Service does get popular then there's an explicit feedback loop that reinforces the durability of the system and alignment of interests.

Evernote announced something like this, but never really followed through.   A small company called Forever actually does have a preservation fund that is purpose driven.

[crosspost from industryinfo..]

One thing we at Google could do is advocate for a https://en.wikipedia.org/wiki/Legal_deposit scheme for Games.

- Game publishers would put their games in Escrow when they publish.
- Google could publish a spec on how to interpret the game contents.
- 'Orphan' games would actually be preserved.
- Users that purchased the Game would then be entitled to a copy of the escrowed item, plus the design on how to run them.

This, combined with an export of user-generated data would allow for usability after Stadia or the Game Publisher sunsets the service/game.

And TBH I'd love to see this extended to all Online "Stores" that don't let you export usable contents.

Barring something like that Google could enter a https://en.wikipedia.org/wiki/Ulysses_pact with our users if we're serious about the long-haul.. For each purchase a user makes put 10x in a locked escrow fund. When the service cancels that money can be used to migrate the games to a new provider or payout back the user.

- If Stadia gets few users it's not a lot of money to exit and actually would increase satisfaction.
- If Stadia does get popular then there's an explicit feedback loop that reinforces the durability of the system and alignment of interests.

Evernote announced something like this, but never really followed through. A small company called https://www.forever.com/guarantee actually does have a preservation fund that is purpose driven.

#googplus

And yes some of these games are lost forever...

But one good idea is the magazine to build community.

https://twitter.com/retrohistories/status/1138020709320613888

#googplus

Happy to see this project. Looking into ways to support it, because they face a steep climb.

Inspired by the folk hero John Henry....Because, despite intelligence, physical strength and an incredible will, (1) he lacked a complete understanding of the system he was challenging, (2) he struggled alone, and (3) he struggled with outdated technology.

https://sites.google.com/corp/google.com/project-john-henry/home

#googplus

https://twitter.com/TeamYouTube/status/1136341801109843968

This is at least a graduated response, wonder what changed in the last 12 hours?

#googplus

Today I attended the "Designing for At Risk Users" course. I find it incredibly galling to hear what Youtube did today given the targeted harassment and doxing.

It flies in the face of what was taught and own standards about giving targets the means to "make it stop".

https://standards.google/guidelines/google-material/usability/at-risk-users.html#user-identities

While anyone can experience a privacy or security event, at-risk users face a variety of life circumstances that might put them at unusually greater risk:

.....

Who they are: Anyone could be targeted at some point in their lives simply based on a personal characteristic such as age, gender, ethnicity, reputation, financial stability, sexual orientation, or education.

.....

Active Event

Where possible, users should be able to quickly and easily access practical guidance as they experience a privacy or security event, such as cyberstalking, online impersonation, surveillance, spear-phishing, or account hijacking. Users will likely want to understand what is happening and take steps to respond. They are likely to feel high levels of stress in this state, so easy-to-use designs will be especially helpful.

#googplus

state of denial

#googplus

Updated to latest MacOS. Yay!

Repeated prompts to "unlock keychain". oh no!

I was determined to not reset my login keychain, because then you lose the TouchID gnubby and have to reimage the whole laptop. (May only apply to santa exceptions, maybe not..)

I finally got lucky and found a way to work around it. (and yes, I've let Techstop know about it)

1) Open Keychain app.
2) Click on login item in left pane.
3) Right click on login item, select 'Change settings for Keychain "login"'
4) In my case the Lock After setting was checked and had a large number
5) Change the timeout value and save.

You'll need to enter your keychain password a few times. But once you're done the keychain will possibly be updated and uncorrupted.

To verify you can run the gcert command in your terminal. You should not be prompted to unlock the keychain and touchid should be requested.

Theory: changing the expiration setting forces the keychain app to rewrite the keychain data structures fresh.

#googplus

BRB ... bringing Enron style accounting to the resource economy...

#googplus

Interesting:

https://wicg.github.io/ad-click-attribution/index.html

Of course you have to trust your User Agent (Browser) to keep your browsing secret..

#googplus

One of the better public Postmortems I've seen.

Keep those SSH keys safe!

https://matrix.org/blog/2019/05/08/post-mortem-and-remediations-for-apr-11-security-incident/

#googplus

[actually it's the exploded wiring cabinet for my neighborhood that's transitioning to AT&T fiber...]

#googplus

Would be nice if all of our products supported Alt text as well as Mastodon does...

And if sharing with Louis Gray I'd say "Image of a rack mount server with long fsck times"

#googplus

Red Hat turns 20 so they asked former folks for their memories. Here's something I dug up that might be of interest to folks 'round these parts..

... I never got a response on this email; but that might be because Red Hat was always late paying Google Invoices..

Looks like Joan is still here. Ray does not show up in Epitaphs.

#googplus

"stories" from. "GitHub"

In the developer ecosystem, branch conflicts are considered especially heinous.

On Github, the dedicated developers who resolve these vicious conflicts are members of an elite squad known as the Special Merge Unit.

These are their stories.

Dun Dun

#googplus

https://googleblog.blogspot.com/2014/03/introducing-auto-awesome-photobombs.html

#googplus

""What we found was that the majority of news outlets had not given any thought to even basic strategies for preserving their digital content, and not one was properly saving a holistic record of what it produces.""

https://www.cjr.org/tow_center_reports/the-dire-state-of-news-archiving-in-the-digital-age.php

#googplus

Before we bury G+ it might be worthwhile to collect some memorabilia...

Marc Weber from the Computer History Museum asked if we wanted to contribute Google+ artifacts to CHM. They don't care about swag, but I could think of a few things that they might be interested in:

- The Obama + Dalai Lama framed print.
- The Buffalo? (Too big?)
- The Emerald Sea painting (did anyone save it?)

Open to suggestions....

[Too bad the Apiary whiteboard is long gone....]

#googplus

So I thought I'd write an apps-script macro to help find Twitter profiles of my G+ circled people. [I'm assuming these contacts will go away on April 2nd, right Greg Wolfe ?]

Code works, but App Script barfs on the Twitter javascript used to render the follow buttons. So I just grabbed the html output and stuck it on a server and clicked the follow bu
tton...

If someone wants to poke at it and/or publish it (I have no time for either) have at it...

You can access it here:

https://script.google.com/macros/s/AKfycbz8RJl6qIS6x1PTQss_O1Xz69l1_bp1QcyJPoxnW9qITvFYTEI/exec

And the xss-riddled code looks like this:

function doGet() {
var html = '<!DOCTYPE html>';

do {
var pageToken;

var connections = People.People.Connections.list('people/me', {
pageSize: 100,
personFields: 'names,urls',
pageToken: pageToken
});

connections.connections.forEach(function(person) {
// Skip people without URLs in their profile.
if (!person.urls) {
return;
}
person.urls.forEach(function(url) {
if (url.value && url.value.match(/twitter.com/)) {
var name = url.value;
if (person.names && person.names.length > 0) {
name = person.names[0].displayName;
}
html += '\n<br><a class="twitter-follow-button" href="' + url.value + '">';
html += 'Follow ' + name + '</a>\n';
}
});
});
pageToken = connections.nextPageToken;
} while (pageToken);

html += '\n<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>'
var output = HtmlService.createHtmlOutput(html);
output.setTitle('Google+ Follower Finder');
return output;
}

#googplus