# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 13
# self = https://watcher.sour.is/conv/tk673aq
prologic
twtxt.net
View Thread
On the topic of Programming Languages and Telemetry. I'm kind of curious... Do any of these programming language and their toolchains collect telemetry on their usage and effectively "spy" on your development?

- Python
- C
- C++
- Java
- C#
- Visual Basic
- Javascript
- SQL
- Assembly Language
- PHP
prologic
twtxt.net
View Thread
On the topic of Programming Languages and Telemetry. I'm kind of curious... Do any of these programming language and their toolchains collect telemetry on their usage and effectively "spy" on your development?

- Python
- C
- C++
- Java
- C#
- Visual Basic
- Javascript
- SQL
- Assembly Language
- PHP
prologic
twtxt.net
View Thread
On the topic of Programming Languages and Telemetry. I'm kind of curious... Do any of these programming language and their toolchains collect telemetry on their usage and effectively "spy" on your development?

- Python
- C
- C++
- Java
- C#
- Visual Basic
- Javascript
- SQL
- Assembly Language
- PHP
prologic
twtxt.net
View Thread
On the topic of Programming Languages and Telemetry. I'm kind of curious... Do any of these programming language and their toolchains collect telemetry on their usage and effectively "spy" on your development?

- Python
- C
- C++
- Java
- C#
- Visual Basic
- Javascript
- SQL
- Assembly Language
- PHP
xuu@dev.txt.sour.is
dev.txt.sour.is
View Thread
@prologic I get the worry of privacy. But I think there is some value in the data being collected. Do I think that Russ is up there scheming new ways to discover what packages you use in internal projects for targeting ads?? Probably not.

Go has always been driven by usage data. Look at modules. There was need for having repeatable builds so various package tool chains were made and evolved into what we have today. Generics took time and seeing pain points where they would provide value. They weren't done just so it could be checked off on a box of features. Some languages seem to do that to the extreme.

Whenever changes are made to the language there are extensive searches across public modules for where the change might cause issues or could be improved with the change. The fs embed and strings.Cut come to mind.

I think its good that the language maintainers are using what metrics they have to guide where to focus time and energy. Some of the other languages could use it. So time and effort isn't wasted in maintaining something that has little impact.

The economics of the "spying" are to improve the product and ecosystem. Is it "spying" when a municipality uses water usage metrics in neighborhoods to forecast need of new water projects? Or is it to discover your shower habits for nefarious reasons?
xuu
txt.sour.is
View Thread
@prologic I get the worry of privacy. But I think there is some value in the data being collected. Do I think that Russ is up there scheming new ways to discover what packages you use in internal projects for targeting ads?? Probably not.

Go has always been driven by usage data. Look at modules. There was need for having repeatable builds so various package tool chains were made and evolved into what we have today. Generics took time and seeing pain points where they would provide value. They weren't done just so it could be checked off on a box of features. Some languages seem to do that to the extreme.

Whenever changes are made to the language there are extensive searches across public modules for where the change might cause issues or could be improved with the change. The fs embed and strings.Cut come to mind.

I think its good that the language maintainers are using what metrics they have to guide where to focus time and energy. Some of the other languages could use it. So time and effort isn't wasted in maintaining something that has little impact.

The economics of the "spying" are to improve the product and ecosystem. Is it "spying" when a municipality uses water usage metrics in neighborhoods to forecast need of new water projects? Or is it to discover your shower habits for nefarious reasons?
prologic
twtxt.net
View Thread
@xuu I _think_ in this case, the "spying" is more problematic because it is proposed to be deeply embedded in the Go toolchain 😢 We're not talking about measuring high-level "counts" here, but being embedded deep within go ... commands. That's not great for me 🤦‍♂️
prologic
twtxt.net
View Thread
@xuu I _think_ in this case, the "spying" is more problematic because it is proposed to be deeply embedded in the Go toolchain 😢 We're not talking about measuring high-level "counts" here, but being embedded deep within go ... commands. That's not great for me 🤦‍♂️
prologic
twtxt.net
View Thread
@xuu I _think_ in this case, the "spying" is more problematic because it is proposed to be deeply embedded in the Go toolchain 😢 We're not talking about measuring high-level "counts" here, but being embedded deep within go ... commands. That's not great for me 🤦‍♂️
prologic
twtxt.net
View Thread
@xuu I _think_ in this case, the "spying" is more problematic because it is proposed to be deeply embedded in the Go toolchain 😢 We're not talking about measuring high-level "counts" here, but being embedded deep within go ... commands. That's not great for me 🤦‍♂️
abucci
anthony.buc.ci
View Thread
@prologic @xuu they're setting up the infrastructure and developer buy-in to stick more and more insidious garbage in there. Before you know it they'll propose "training AI" on this data or you'll find they've been doing it all along.

Always say no to more data collection. Always, no matter how good it may seem. These companies are institutionally unable to control themselves. Whether this Russ guy personally has bad intentions is irrelevant. The company and culture he's embedded in has repeatedly demonstrated they are untrustworthy. *Especially* when it cones to data like this.
abucci
anthony.buc.ci
View Thread
@prologic @xuu they're setting uo thr infrastructure and developer buy-in to stick more and more insidious garbage in there. Before you know it they'll propose "training AI" on this data or you'll find they've been doing it all along.

Always say no to more data collection. Always, no matter how good it may seem. These companies are institutionally unable to control themselves. Whether this Russ guy personally has bad intentions is irrelevant. The company and culture he's embedded in has repeatedly demonstrated they are untrustworthy. *Especially* when it cones to data like this.
abucci
anthony.buc.ci
View Thread
@prologic @xuu they're setting up the infrastructure and developer buy-in to stick more and more insidious garbage in there. Before you know it they'll propose "training AI" on this data or you'll find they've been doing it all along.

Always say no to more data collection. Always, no matter how good it may seem. These companies are institutionally unable to control themselves. Whether this Russ guy personally has bad intentions is irrelevant. The company and culture he's embedded in has repeatedly demonstrated they are untrustworthy. *Especially* when it comes to data like this.