Notices by see shy jo (joeyh@octodon.social)

@alcinnz and yet here I am fixing my concurrency bug in haskell

third bug of the day is, of course brought to me by concurrency

the third horseman

discovered that the #golang
telemetry promoters are intentionally wanting to shift the goalposts so compilers are normalized in sending privacy violating telemetry

This is unacceptable and should kill the language.

Another one by a Google employee: https://research.swtch.com/telemetry-design

"Opt-out: The system is enabled by default [...]
I hope that other open-source projects will be interested to adopt this approach"

This is an attempt at overton window shifting.

How to implement telemetry in a way that actually preserves privacy:

* off by default
* common opt-in configuration prompted at OS install time (replacing eg Debian's popcon prompt, which FWIW I helped develp)
* clear specification about behaviors allowed when opted in. Software that violates that to be considered on the par with an intentional back-door

This is not a path that Google, or apparently the #golang developers, are constitutionally able to understand or take.

@alcinnz I agree, this is something worth getting in front of.

In debian development I very often found myself using popularity-contest to drive some kinds of decisions. Always having to factor in that it's off by default and we don't know what percentage or kinds of users choose to enable it, but that does not prevent it from being useful.

#google could do us all a favor by not using pagerank at all in training the ML that they are going to destroy their search engine with.

That would open up pagerank to be used by small marginalia-class search engines, once enough of the existing SEO spam bitrots away.

I realize this is dreaming, but it would be nice to be able to search the web again with a reasonable algorithm.

"Function signatures tell a story but the computer hasn’t been listening"

seen in today's leading OMG AI WTF blog post

Headdesk