6 ms·
"PRs and Status" is a very optimistic headline for a list of rejected pull requests. I like the idea, but the execution leaves a lot to be desired. I can under
by wongarsu 5y ago
"PRs and Status" is a very optimistic headline for a list of rejected pull requests.
I like the idea, but the execution leaves a lot to be desired. I can understand why some Homebrew devs think it's just an attempt from someone to pad their resume. It's essentially a single person setting up a website, then submitting a bunch of untested pull requests to a bunch of projects.
I imagine this would work much better if a large distro like Debian would adopt this first. They have the credibility and weight necessary for such a project, they can make it much more useful by asking for the desired setting during OS setup, and they can make sure it's universally respected via patches in the packaging process. From there it would have a chance at wide adoption.
- sneak 5y agoChicken and egg problem, naturally. I'd love it to gain more traction. It was an idea and I thought it would be better an idea and a website than just an idea. It was strange to see it get labeled as a marketing attempt during my attempts to gain some traction, considering I'm not selling a damn thing. I have severe focus issues, so it had to be a one-day project unfortunately, which is why a couple of the patches weren't tested very well. Treasure your flow state when you get it. Ultimately I didn't invest any more time into it as developers who put default-on spyware in their apps don't actually want more people opting out. It's a doomed concept.
- alpaca128 5y ago> It's a doomed concept. Indeed, because it assumes developers who are doing opt-out tracking will respect this voluntarily. I disagree with the poster above about Debian adopting this. They shouldn't adopt DO_NOT_TRACK, they should ban any package that does tracking by default from their repo; in distros that already keep non-free software out of the standard repository this wouldn't be that much of a leap. This seems necessary, as there's no sign that a "please don't track me?" flag will work better in the terminal than it does now in the browser.
- sneak 5y ago> They shouldn't adopt DO_NOT_TRACK, they should ban any package that does tracking by default from their repo Debian maintainers are amazing and they go one step further: they patch it out when they distribute it. They also patch out old version time bombs and all manner of other phone-home.
- dralley 5y ago> They also patch out old version time bombs As an open source software developer, I do have some sympathy for the upstream devs here, and some frustration with distro maintainer policies. I'm not interested in getting a bunch of bug reports for issues that were fixed 4 years ago, or introduced because Debian maintainers "patched out" something they shouldn't have.
- yunohn 5y agoExactly. Distro maintainers do not face the same issues that the upstream software developers do. Maintainers only make their job harder.
- account42 5y ago> Maintainers only make their job harder. That's unnecessarily harsh. Distro maintainer's primary responsibility is making the Distro as a whole work together and sometimes that means choices that are not optimal for individual programs/libraries on their own. But packaging itself does already reduce the burden on upstream a lot by preempting any build-related support requests from users as well as many compatibility-related ones. Sometimes upstreams interest is also not aligned with the user's interest (e.g. the topic of this thread) and there the distro will tend to choose the user's interests - that's a good thing. As for time bombs specifically, those don't make much sense when the software is installed via a repository that has an update mechanism. Not wanting bug reports for old versions is no excuse for planned obsolence. If you think a distro is increasing your support burden it is quite acceptable to tell users from that distro to use the distro's bug tracker.
- enumjorge 5y agoCan’t say I’m surprised that putting one day’s of work into getting the industry to adopt a proposed standard you came up with yourself didn’t really work out. Based on your other comments you also seem to have some level of contempt for some of the projects that you were trying to influence. Those probably didn’t help your cause.
- sneak 5y agoYes, contempt is an accurate assessment. Shipping nonconsensual spyware is unethical, and there are too many devs in our industry who are happy to behave unethically so long as their boss tells them to. Creating more social and reputational consequences for individual worker bees who make such commits on the job is also on my to-do list. Ultimately the opt out vars are token efforts by developers anyway. These projects only do the bare minimum of opt-out-ability because they have to be able to point to the opt-out setting as justification for their shipping of spyware-by-default. Making it easier to opt out isn't something they want, regardless of how much I do or don't mask my contempt for such unethical, user-hostile practices. The way the Audacity thing is playing out is instructive. Many devs simply feel entitled to take over your machine as if it is theirs and your double-click is a blank check. My PRs against autoupdates have run in to similar developer resistance. https://github.com/signalapp/Signal-Desktop/issues/4578 https://github.com/signalapp/Signal-Desktop/issues/4578 https://github.com/bitwarden/desktop/issues/552 https://github.com/bitwarden/desktop/issues/552
- deleted 5y ago[deleted]
- UncleMeat 5y agoDNT has already failed. It is long gone. A lot of people spent a ton of energy trying to make it work but it isn't going to succeed. Discussion around it now is not productive and should instead be focused on new initiatives. > I have severe focus issues, so it had to be a one-day project unfortunately, which is why a couple of the patches weren't tested very well. Treasure your flow state when you get it. This isn't really an excuse. Imagine how somebody on the other side of a broken PR sees this? This 100% reads as "I don't care about your project enough to do the work and instead am doing this solely for my personal satisfaction".
- 542458 5y agoI think there is useful discussion to be had as to why DNT failed. IMO it’s largely because people approached the problem from a purely tech-oriented standpoint and ignored any differing ideologies and incentives at play. An allegory to this project could be drawn.
- jefftk 5y agoFrom my perspective, a major issue with DNT was that it wasn't very clear to websites what a DNT request was asking for. The specification explicitly doesn't handle this: "This specification does not define requirements on what a recipient needs to do to comply with a user's expressed tracking preference" https://www.w3.org/TR/tracking-dnt/ https://www.w3.org/TR/tracking-dnt/
- latexr 5y ago> It was strange to see it get labeled as a marketing attempt during my attempts to gain some traction, considering I'm not selling a damn thing. Clicking on your HN profile, I see “I am available for hire”. It was clear to me that’s what the maintainers were referring to: you marketing yourself, which you’d have been able to do with greater effectiveness as the originator of a feature adopted by popular open-source projects (had it worked). Note I’m not claiming that’s what you did, I’m explaining what you found strange.
- hnlmorg 5y agoSprinkling in the website URI into the source code of the PRs was definitely a bold move. I get the logic behind why it was done but one website does not constitute as a standard. If DO_NOT_TRACK were to be standardised then adding a URI to the published standard would have been more obviously intended as a constructive comment. But when the URI is a hobbyist's personal website, as well intended as it was probably meant to be, I can completely sympathise with why maintainers were sceptical about the sincerity of the PRs. That all said, there has to be a path for unknowns to contribute good ideas back FOSS and I do think this is actually a pretty good idea that deserves to gain attention.
- holtalanm 5y agoI liked the Gatsby comment/suggestion a lot better: a tool for automatically setting the do-not-track env flags for all different dev tools.
- traverseda 5y agoBecause what I really want is a ton of different random bullshit enviroment variables next time I go to debug something :/
- holtalanm 5y agowell, good luck getting buy-in from the cli tool devs, then? the other option requires absolutely zero buy-in from homebrew, gatsby, dotnet, or any other cli.
- argvargc 5y ago> I can understand why some Homebrew devs think it's just an attempt from someone to pad their resume. I can't. That suggestion seems the product of desperate reach for an ad hominem attack. There are clear, plausible and obvious reasons for the projects existence that require no seeking of hidden motive to understand or explain. I'd agree OS-level integration for this stuff would be better, supposing OS manufacturers would also elect to include their own telemetry under such an umbrella.
- cmsj 5y agoHomebrew devs are small in number and high in stress. They tend to be very protective of their time and sanity.
- deleted 5y ago[deleted]
- formerly_proven 5y agoFrom the Netlify PR: > 1. User runs a cli command with —telemetry-disable flag > 2. CLI sees the flag, and sends one telemetry request to note that it was disabled Wow. The first thing the "Hey, please don't send telemetry" flag does is send telemetry.
- sneak 5y agoVSCode (and maybe Atom?) also send a telemetry event along the lines of USER_HAS_DISABLED_TELEMETRY.
- an_opabinia 5y ago> I can understand why some Homebrew devs think it's just an attempt from someone to pad their resume. It's one Homebrew dev.