Why does #Microsoft want to implement #Recall? It's not about images. It's about modelling what workers do on Windows, and then replacing them.
The most expensive part of a computer is the fallible feelings-filled unpredictable meat sack that operates it.
Google has YouTube, Google Photos, Maps, and a bucket load of search data, Google Analytics, advertising, as well as it's #GCP data (e.g. #STT transcriptions). And a bunch of data from Android services. From this data they can model speech, model videos and model advertising systems, and how humans respond to them.
But they can't model what people do on computers.
Amazon has Prime data, and a bucket load of compute. But no operating system data. They can build models based around e-commerce and advertising systems.
But they can't model what people do on computers.
Meta has waves hands enough analytics to model human behaviour in the Metaverse.
But they can't model what people do on computers.
Microsoft has GitHub.
Microsoft has LinkedIn.
Microsoft has SharePoint.
Microsoft has Teams.
Microsoft has Dynamics.
Microsoft has O365.
Microsoft has Windows telemetry data.
Microsoft can model what people do on (Windows) computers. Like fill out spreadsheets.Write emails. Synthesize web pages of research. Interact with colleagues on Teams. Create and edit documents.
Microsoft wants #MicrosoftRecall data so they can model what people do with operating systems.
Then replace them.
Imagine a CoPilot that doesn't just write buggy code. Imagine one that also does spreadsheets. That creates documents on SharePoint. That communicates with colleages on Teams. That has a customer pipeline on Dynamics.
That's what Recall is about - 360 degree surveillance of the worker, to model their functions, make them fungible, replicable - and replaceable.
I've got cloud-sql-proxy running on 3306 of my bastion vm. I can SSH to said vm, and I can bind port 22 of that vm to a local port via Identity Aware Proxy (IAP).
But I can't bind port 3306 of it to a local port. Even though my firewall rules for IAP allow 22 and 3306 TCP traffic 🤔
"Error while connecting [4003: 'failed to connect to backend']. (Failed to connect to port 3306)"
We're building pipelines in #trivago that analyse, verify and normalise the content coming from partners, to deliver them clean to the rest of the company.
I am looking for a pragmatic engineer engaged for quality and stability, that takes the challenge to process big volumes of data. We use ATM #Python and #ApacheBeam in #GCP, but you don't need them to apply if you are using other data tooling.
We offer a competitive salary, a constant challenge, a very enthusiastic team and an authentic atmosphere of multicultural colleagues.
We're based in #Düsseldorf, and we work in english in an hybrid scheme of 2 days #homeOffice / 3 days in person. Also unlimited vacation days, 20 days per year fully remote, kitchen, coffee, daily fruits...
Here is my toot resume in case anyone has open positions:
Experience: staff software engineer, #backend#webdeveloper, #python, #django, #postgresql, #terraform, #redis, #rabbitmq, #kubernetes, #aws, #gcp
I get things done and worked with pretty much any tech out there. I learn fast, have no problem coding in other languages. I have experience leading teams. I helped growing an engineering team from 10 to 150 engineers. I know how to scale things. My code is resilient and has tests. #fedihire
Apparently, in Google Cloud / Kubernets Engine you can grant privileges to users in the "system:authenticated" group. That group includes all users with a Google account. And because you can, some people have done so.
Finally finished Country of the Blind. Great #book, funny and well written. It’s an interesting take on disability which is neither depressing nor uplifting. Out of curiosity I tried to do some work with the NVDA screen reader just to see “how bad would it be if I lost my sight”.
Boy it’s a damning indictment of my own work. Some of the pages on services like #gcp either don’t work or leave out pretty important information. Even sites and services I’ve written don’t work correctly.
It’s a surprising sales pitch for #ai since it basically returns a block of text without formatting that worked great. Even if you hate AI it’s so much better than trying to navigate normal websites.
I got so annoyed with the #GCP IAM reference docs that I made an ugly but easy to search one that lets you copy and paste the permissions easily without going between two pages. https://gcp-iam-reference.matduggan.com/
And unlike #Discord it's not a #centralized shit they host with #VC money on #aws, #GCP or whatever but instead you can #SelfHost and even write your own client because it has an actual #API...
Leider sind von den 1484 Diensten 668 von AWS. Davon die Hälfte Level 1. 21 Dienste sind immerhin Level 2. Natürlich ist kein Dienst Level 3. Bleibt genau die Hälfte, die nicht den Anforderungen der GAIA-X entsprechen. Es stellt sich etwas die Frage, warum diese Dienste dann in einem Katalog von GAIA-X enthalten sind.
#Cloudflare is really impressing me with how transparent they're being with their recent outage. Not only did they write a great post-mortem, but they're letting customers hear directly from leadership on what happened.
It's one reason I really like the #GCP take on a status page. People complain about how many "outages" there are, but it's great that I have a high degree of confidence that if a problem is present in the stack I'm going to see it there vs #aws where their status page is legendarily useless and false. #devops#infrastructure
Would you like to have a way to find out have much disk storage you are using in #GoogleCloud across all your projects? I just wrote a quick #bash script for that!
Caveat: It makes a lot of calls and takes a long time to run. It also assumes one zone per project for now, but that's easy enough to patch. The list call doesn't require zone but the describe call does.