First of all, having a Google Scholar profile requires a Google account.
There is no technical necessity for this, Google already indexes my papers and other databases (like the aforementioned dblp) manage to create per-author pages just fine without authors having to have an account.
But, of course, this is a great way for Google to tie more people into their ecosystem -- few kinds of pressure are as effective as when this directly affects hiring decisions.
-I have so far successfully avoided having a Google account, even if that means having to solve reCAPTCHA in hardcore mode all the time (yet another way in which Google not-so-subtly nudges people to "opt"-in to them tracking their every step).
+I have so far successfully avoided having a Google account, even if that means having to solve reCAPTCHA in hardcore mode all the time (yet another way in which Google not-so-subtly nudges people to "opt"-in to them tracking their every step in the web, joining other pieces like Google Analytics, Google Ads and AMP).
There is a reason I am running my Android phone with [F-Droid](https://f-droid.org/) and [microG](https://microg.org/), and [Yalp store](https://github.com/yeriomin/YalpStore) for the rare case that I need a (free) app from the Play store.
At this point I was ready for the compromise of creating an account (that I'd never use) using only [publicly available information](https://people.mpi-sws.org/~jung/contact.html) about me.
projects / web.git / blobdiff