Плохая новость - да, это правда. Хорошая: вы можете все удалить.
Google тихонько, не делая на этом никакого акцента для пользователей, подслушивает их разговоры и хранит их у себя на серверах.
И речь даже не о том, о чем вы говорите по телефону: ваш смартфон следит за вами даже когда просто лежит рядышком на столе.
Так что если вы уже давно пользуетесь смартфонами, то можете послушать свои разговоры, которые Google собирал в течение многих лет.
Компания, собственно, этого и не скрывает. Вот только узнать об этом факте можно, только если вы прочитаете огромное многостраничное «соглашение для пользователей». Разумеется, никто этого не делает!
Зачем это Google?
Компания дает всю собранную о вас информацию своему искусственному интеллекту. Тот учится вас понимать, подстраивается под вас и, теоретически, делает продукты Google для вас удобнее.
Вроде как звучит классно. Но есть три «но»:
1. Эта информация может попасть в руки злоумышленников, если кто-то взломает пароль к вашей учетной записи.
2. Эта информация может быть использована против вас, если у вас случится настоящий конфликт с властями.
3. Эта информация используется для того, чтобы показывать вам наиболее точную, «заточенную» под вас рекламу.
К счастью, есть способ во всем этом разобраться и всю эту информацию удалить. Это все можно сделать через специальный, мало кому известный сервис. Надо только авторизоваться и все почистить.
Вот нужные вам адреса:
Вот тут хранятся все данные, которые записал микрофон вашего телефона. Если тут пока ничего нет, значит, вы просто не пользовались голосовым помощником, т.е. никогда не говорили: «ОК, Google».
А вот полное досье, которое на вас собрал Google, основываясь на том, что вы делаете в интернете.
Среди прочего, тут есть информация, где и когда вы были (точнее, ваш телефон); все, что вы искали в интернете; все странички, которые вы загружали.
Но самая полезная функция этого сервиса - возможность быстро все оттуда удалить. Вы можете выбрать флажком записи, которые хотите уничтожить, а можете удалить все сразу - одним махом. Нажмите на кнопку «Выбрать параметры удаления» в левой колонке.
И обязательно покажите друзьям этот пост: они наверняка не в курсе!
Knowledge graphs are among the most important technologies for the 2020s. Here is how they are evolving, with vendors and standard bodies listening, and platforms becoming fluent in many query languages By George Anadiotisfor Big on Data
This may come as a shock if you've first encountered knowledge graphs in Gartner's hype cycles and trends, or in the extensive coverage they are getting lately. But here it is: Knowledge graph technology is about 20 years old. This, however, does not mean it's stagnating -- on the contrary.
First, let's quickly recap those 20 years of history. What we call Knowledge Graphs today has been largely initiated by none other than Tim Berners-Lee in 2001. Berners-Lee, who is also credited as the inventor of the web, published his Semantic Web manifesto in the Scientific American in 2001. The core concepts for Knowledge Graphs have been laid there.
The Semantic Web manifesto was in many ways ahead of its time. Looking back today, we can see some parts of it going strong, while others have faded. Building on a foundation of standards for interoperability, such as Unicode, URIs, and RDF, the core of the vision has always been semantics: instilling meaning in web content.
The Semantic Web technology stack, back in 2001. While its age shows, and some parts have become obsolete, others form the foundations of one of today's most hyped technologies: Knowledge Graphs
The Semantic Web got a bad name for being academic, while some technical choices such as XML did not quite work out. The thing is, however, that crawling and categorizing content on the web is a very hard problem to solve without semantics and metadata. This is why Google adopted the technology in 2010, by acquiring MetaWeb.
In 2012, the term Knowledge Graph was introduced. A very successful rebranding indeed, and that's not all we have Google to thank for. Google employs key people in the domain and is the driving force behind schema.org. Schema.org is the core of Google's knowledge graph. It is, unsurprisingly, a schema.
Knowledge graphs and schemas are foundationally bound. While not all knowledge graphs are as big as Google's, every one of them is based on a schema. Knowledge graph neophytes do not always realize this, but whether it's implicit or explicit, there's always a schema. Which brings us to the point.
Knowledge graphs and graph databases
Knowledge graphs can be stored in any back end, from files to relational databases or document stores. But since they are, well, graphs, it does make sense to store them in a graph database. This greatly facilitates storage and retrieval, as graph databases offer specialized structures, APIs, and query languages tailored for graphs.
In addition, many graph databases today offer a lot more than just a store for data. They come packaged with algorithms for graph analytics, visualization capabilities, machine learning features, and development environments. They have essentially grown from databases to platforms. But there is further nuance here.
Graph databases come in two main flavors, depending on which graph model they support: Property graph and RDF. In general, RDF graph databases emphasize semantics and interoperability, while property graph databases emphasize ease of use and performance.
Graph databases come in 2 main flavors, depending on which graph model they support: labeled property graph (LPG) and RDF. Image: The Year of the Graph
When it comes to knowledge graphs, RDF graph databases are a natural match. It's not impossible to build knowledge graphs on top of property graph databases. Usually, however, this results in having to learn knowledge management fundamentals the hard way, and re-implement relevant features. While lessons don't come for free, building on platforms centered around knowledge management helps.
A key element to bridge the gap is something called RDF* (RDF star). RDF* is a proposal to standardize a modeling construct for RDF graphs, namely the addition of properties to edges. Although this is possible in RDF, there is no standard way of doing it. Standardizing it would not only help interoperability with property graphs but also interoperability among RDF graphs.
From secret handshakes to RDF stars
As Steve Sarsfield, VP of Product in Cambridge Semantics put it, before RDF*, if people wanted to use edge properties in RDF graphs, they had to rely on secret handshakes. This is not ideal, especially considering one of the key advantages of the RDF stack is standardization and interoperability.
In the wake of the W3C initiative, a couple of RDF graph database vendors went ahead and implemented RDF*. Cambridge Semantics is one of them. Its AnzoGraph database supports RDF*, as well as SPARQL*. SPARQL is the standard query language for RDF, and SPARQL* is its extension that works with RDF*.
Cambridge Semantics recently unveiled AnzoGraph DB Version 2, and when discussing the release with Sarsfield, we wondered what their experience from the field has been. Are people asking for RDF*, has it helped adoption? Bridging the gap with property graphs has enabled AnzoGraph to get an implementation of Cypher, the most popular language for querying property graphs, underway.
Sarsfield noted that it's still relatively early days for knowledge graph adoption. As such, many of the organizations that use AnzoGraph tend to have highly skilled people on board. For them, switching between data models and query languages is not much of an issue. For mainstream adoption, however, this is important.
Stardog is another RDF graph database vendor that has implemented RDF*. Mike Grove, Stardog co-founder and VP Engineering, said this has been in the works for a while, and they are very excited about it. Stardog started working on the plumbing as part of the Stardog 7 development effort, and they were very happy to be able to ship the feature.
Regarding its reception, Grove noted that what people wanted was a more user-friendly way to have edge properties: "Neo4j obviously got this right. RDF* does a fantastic job of bringing the same ease of use to semantic graphs." He went on to add that customers are excited, and many are already working on integrating it into their applications.
Technically, RDF* and SPARQL* are not yet standardized. Both have been introduced by Olaf Hartig, a researcher at Linköping University. When inquiring about their status, Hartig noted that while there have been delays, he hopes the standardization process will pick up speed soon.
For knowledge graph platforms, too, GraphQL is a plus
Both Sarsfield and Grove noted that they expect RDF* to boost knowledge graph adoption. Implementation is key, and having early adopters and real-world usage may also catalyze the standardization process. Sarsfield and Grove expressed their support for the process, as well as the need to get the word out.
RDF* can make a difference, but it's not the only thing going on in the knowledge graph world. As knowledge graphs entail several layers and can be a central piece of infrastructure for organizations, graph databases are growing into platforms.
AnzoGraph started as part of the Anzo platform before becoming a product in its own right. Stardog also touts its product as a platform, emphasizing features such as visualization and virtualization built around the graph database core.
GraphQL has benefits, and a new breed of approaches for using it as an access layer for databases is emerging. Image: Nordic APIs
Another RDF graph database vendor, Ontotext, recently announced a new version of its own platform. An interesting feature that Stardog's and Ontotext's platforms share is support for GraphQL. Unfortunately, GraphQL's name does not do it justice. As if there was not enough confusion already regarding graph: GraphQL is not a graph query language.
GraphQL is a replacement for REST APIs. Despite the misnomer, it's very useful, and its popularity among developers is growing. This is why more and more databases are adding support for GraphQL, with names such as MongoDB joining the GraphQL wave. Graph databases are no exception. Stardog has had it since 2017, Ontotext is in the process of adding it.
As Stardog put it, more developers know and are learning GraphQL than all the graph query languages combined. Ontotext on its part put together a rather elaborate post on the use of GraphQL in its platform. Whichever way you approach it, however, GraphQL makes lots of sense for accessing services built around database platforms.
GraphQL plus variants
Stardog reports GraphQL success within its customer base. Grove mentioned that one of the big Silicon Valley tech companies exclusively uses GraphQL to interact with Stardog. Both Grove and Jem Rayfield, Ontotext's Chief Architect, agree that GraphQL can work well in some cases, but by its very design, the expressiveness of GraphQL is quite limited.
Most people who don't know GraphQL assume it's a graph database query language. Most people who know GraphQL wonder how a graph database can be powered by it. This statement comes from Manish Jain, the CEO and founder of Dgraph. Dgraph is a graph database powered by GraphQL -- or something like it.
Most approaches are about what GraphQL can do for knowledge graphs. But to close the loop with the Semantic Web underpinning of knowledge graphs, here's an idea: What if GraphQL resources were annotated with URIs?
URIs are global identifiers, which can denote concepts from shared vocabularies, such as schema.org or other ontologies. This seems like a natural fit, and one that both Grove and Rayfield agree has potential. There is another working group set up to align RDF and GraphQL, although it does not look like it's moving very fast.
Knowledge graphs in the 2020s: We speak your language
It seems we are moving towards a new status quo. If NoSQL stands for Not Only SQL, we could call this NoSPARQL -- Not Only SPARQL. SPARQL remains the language of choice for taking full advantage of knowledge graph capabilities. It also doubles as an API, its expressiveness is beyond what GraphQL can attain, and SPARQL's federated query and data integration capabilities are unique.
But vendors seem set to meet users where they are, be it GraphQL or any other language. Even SQL. As Stardog's Grove put it: "We've always strived to bring our technology to the users. GraphQL was a step in that plan. Supporting SQL is the next step in that journey, not because SQL is better than GraphQL, but because of what that support enables."
Graph database vendors and standard bodies are listening to the market, and platforms fluent in many query languages are evolving
Eventually, even natural language support could be an option. "No matter how you feel about SQL, SPARQL, GraphQL, or any other query syntax/language, natural language is just better. Why ask someone to learn an esoteric syntax when they can just simply type?" said Grove.
We don't know whether conversational knowledge graphs are something everyone would be comfortable with. What we do know is that more options is a good thing, and exciting times are ahead. Stay tuned as we keep exploring the years of the graph.
Google showcased its prototype Augmented Reality Microscope (ARM) platform with a new modified light microscope that can detect breast cancer metastases as well as prostate cancer.
Google showcased its prototype Augmented Reality Microscope (ARM) platform with a new modified light microscope that can detect breast cancer metastases as well as prostate cancer.
Google showcased its prototype Augmented Reality Microscope (ARM) platform with a new modified light microscope that can detect breast cancer metastases as well as prostate cancer. The microscope, powered by Artificial Intelligence (AI) and machine learning algorithms enables real-time analysis. It displays the results directly into the field 0f view, unlike traditional analog microscopes that are need users to view the sample through the eyepiece. The magnifications can be between 4-40x and the result is displayed by outlining detected tumor regions with a green contour.
The prototype was showcased during a talk delivered at the Annual Meeting of the American Association for Cancer Research (AACR), with an accompanying paper “An Augmented Reality Microscope for Real-time Automated Detection of Cancer” which is currently under review. The move is aimed at accelerating the adoption of deep learning tools for pathologists globally. Google’s ARM platform can be retrofitted into existing light microscopes as well, which requires low-cost components. The microscope offers several visual feedback, thanks to machine learning algorithms. This includes text, arrows, contours, heatmaps, or animations.
“While both cancer models were originally trained on images from a whole slide scanner with a significantly different optical configuration, the models performed remarkably well on the ARM with no additional re-training,” reads a Google blog post. “Of course, light microscopes have proven useful in many industries other than pathology, and we believe the ARM can be adapted for a broad range of applications across healthcare, life sciences research, and material science,” the post added.
You entrust a lot of information to Google. Make sure it stays safe.
Your Google account includes email, photos, Drive documents, YouTube videos, and maybe even a Google Maps review or two. Between all those features, you've got a lot of important information packed away behind a single password. If it falls into the wrong hands, you're looking at a lot of unwelcome consequences.
The good news is that Google takes online security just as seriously as you (should) do. The tech giant offers a variety of account protection and security measures designed to keep unwelcome visitors out while letting you easily log in.
Sign in safely
Like many other online portals, Google supports two-step verification. That means logging on to Google on a new device will require an email address, a password, and a code generated by your phone. The process places an extra barrier against anyone who might have gotten hold of your email address and password.
To set up two-step verification, and access all of your other Google account security settings, head to the My Account page on the web. Click the Signing into Google link, and you can configure two-step verification, as well as changing your password and security questions if you need to.
Google sign-in options
Google will take you through its own security check-up if you want to bolster your account security.
Whatever else you do to protect your account, the usual advice about choosing a strong password still applies. Make it at least 10 characters long; a mix of letters, numbers, and symbols; and ensure it's as difficult to guess as possible. Don't reuse passwords either: Choose a code that's specific to your Google account (so a data hack of a different account won't compromise your Google account as well).
While you're adjusting your security settings, double-check your recovery email and phone number options too. These will help you regain access if you ever find yourself locked out of your account. Of course, you also need to make sure these accounts are well-protected and secure, or someone could use them to force a password reset on your Google account.
Choose which devices have access
Between your smartphone, tablet, laptop, and work computer, you probably access your Google account on several devices. On the other hand, if a computer halfway across the world is logged into your account, that's a red flag that something shady is going on. So Google lets you check on the devices that are using your account.
Lower down on that same Sign-in & security page, click the Manage Settings link under the Security alerts heading. This tells Google how you want to be notified if a new computer or mobile device accesses your account. You can set it up to receive immediate alerts about suspicious activity, which can make all the difference in keeping your accounts protected.
Look under Device activity & notifications to see computers, phones and tablets with access to your account. If you see something in the list you don't recognize or that you haven't used for a long time, select it and click Remove. Don't worry about being overly cautious, because you can always sign back in on those devices if you need to.
Device removal
Remove any computers and phones you haven't used in a while.
The security page is not the only place you can find a screen like this. There's also a link at the bottom of your Gmail inbox that tells you where else your account is being used. Click on the Details link in Gmail, and you can sign out of all the other currently active sessions on the list.
We also recommend doing a regular audit of third-party apps connected to your Gmail, which again can be done from the Sign-in & security page. While these apps can be useful for improving your Gmail experience, the fewer you have connected, the better from a security standpoint. So get rid of any apps that you don't use regularly or haven't used in a long time.
Secure your smartphone
If you have an Android phone, your Google account is tied pretty tightly to it, so it's important to review your security settings here too. Whatever type of phone you have, you should be putting up barriers via its lock screen. But on Android phones, you can find some extra security settings specific to your Google account.
From the Settings app, tap Google then Security. You'll see some of the same options we've mentioned above, as well as a few extra ones. You can, for example, turn on the feature that lets you remotely locate your phone from a computer, which can come in very handy if someone else gets hold of it. We'd also advise turning the Verify apps feature on, as this monitors for suspicious activity in the apps you've installed on your device.
Android Smart Lock
Android includes several tricks for keeping your phone secure.
If you go to Settings then Security, you can turn on an Android feature called Smart Lock, which lets you specify certain places where the lock screen is disabled. That way you don't have to bother with a password when you're in the safety of your own home. (You can also set up your phone to be used in place of a password on a Chromebook—perhaps a glimpse of the password-free future we can all look forward to.)
Once someone gets into your phone, apps like Gmail and Chrome are wide open, so it's important to have a lengthy PIN code or fingerprint protection in place to stop that from happening. If your devices do fall into the wrong hands, use Android Device Manager to lock and wipe them remotely before any damage is done.
Preserve your privacy
Sometimes the line gets blurred between security (keeping people out of your account) and privacy (controlling what you're sharing about yourself). Even if you set up solid layers of security to protect yourself from hackers, you might want to put walls between your online identity and Google itself, which collects lots of data about your search habits and more. Luckily, Google has plenty of options you can explore in both categories. From the My Account screen, click Personal info & privacy to make an audit of what Google knows about you.
You'll find lots to explore here: You can wipe your Google search history (even if you regularly clear your browser history, Google logs your searches independently), stop Google from tracking your location, and even personalize the sorts of ads you see on Google services.
Google privacy settings
Google gives you simple controls for limiting the data it collects about you.
For example, click on Go To Activity Controls and then click Manage Activity under YouTube History to review and delete any searches you've carried out on the video sharing site. Meanwhile, if you want to pause any of the data-collecting Google is doing, use the simple toggle switches on the Activity Controls screen. It's easy enough to sift through, and where necessary delete, the information Google has collected about your online habits.
It ultimately comes down to how much you trust Google. For clarification on how it uses that data, you can read Google's privacy policy online. For example, those YouTube searches are used to recommend new videos you might like, and that location history lets Google do smart stuff such as tell you about commute times to the office. But it's up to you where you draw the line.
