Are these multibillion companies so incompetent to not think about it?

Are you an AI bot? Modern X11 server using DRM are more than 20 years old. You are talking about how X11 servers worked in the 90's

Is a version of DuckDuckGo without Javascript. Very fast and compatible with minimalistic web browser like lynx.

He updated it later on:

"Update: On June 8th, 2024, I submitted this privacy policy to Google, and on June 10th, they accepted it. I take this to mean that they found it to be 100% factual and endorse it entirely. XScreenSaver was restored to the "Play" [sic] store, and people were able to again downloaded and enjoy it freely.

But then!

Barely 6 weeks later, on July 24th, 2024, Google instituted yet another new policy: basically they told me that if I didn't give them a sample of my blood a copy of my driver's license, they would remove XScreenSaver from the "Play" [sic] store, again.

Obviously that's never going to happen. Do I, the person who wrote the above list cataloging Google's various predations, seem like the sort of person who would willingly give Google my private details? On purpose? I do not think so.

Having distributed XScreenSaver for over a decade to I-don't-even-know-how-many users (I actually don't know, I never looked) Google suddenly decided that it was a huge problem that they don't have a lock of my hair.

Since I enjoy wasting the time and money of multinational superpredators, I spent a few weeks going back and forth with what passes for developer "support" over there. You can read about it over on my blog. Eventually they just started ignoring my emails, and in November 2024, XScreenSaver was again de-listed from the Google "Play" [sic] store, presumably this time for good.

However, we can take solace in the fact that Google endorsed the above privacy policy, and found no fault with it whatsoever."

Comments URL: https://news.ycombinator.com/item?id=43104241

Points: 1

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=38026103

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=37854995

Points: 289

# Comments: 255

https://github.com/mirror/busybox/blob/master/shell/ash.c

"In early proposals, the KornShell-derived emacs mode of command line editing was included, even though the emacs editor itself was not. The community of emacs proponents was adamant that the full emacs editor not be standardized because they were concerned that an attempt to standardize this very powerful environment would encourage vendors to ship strictly conforming versions lacking the extensibility required by the community. The author of the original emacs program also expressed his desire to omit the program. Furthermore, there were a number of historical systems that did not include emacs, or included it without supporting it, but there were very few that did not include and support vi. The shell emacs command line editing mode was finally omitted because it became apparent that the KornShell version and the editor being distributed with the GNU system had diverged in some respects. The author of emacs requested that the POSIX emacs mode either be deleted or have a significant number of unspecified conditions. Although the KornShell author agreed to consider changes to bring the shell into alignment, the standard developers decided to defer specification at that time. At the time, it was assumed that convergence on an acceptable definition would occur for a subsequent draft, but that has not happened, and there appears to be no impetus to do so. In any case, implementations are free to offer additional command line editing modes based on the exact models of editors their users are most comfortable with."

[1] https://pubs.opengroup.org/onlinepubs/9699919799/utilities/s...