News for hackers. Stuff that matters.
Re:Gitlab ‘rethinking’ third-party telemetry by chrisseaton on Thursday October 24, 2019 @11:26AM (#21345582)
What's the difference to you between a second-party script, and a third-party script?
Re:Gitlab ‘rethinking’ third-party telemetry by etatoby on Thursday October 24, 2019 @11:53AM (#21345862)
With the second party (Gitlab in this case) I have a contact, give them money regularly, and have other such leverage in case they screw up. Third parties generally could not case less what damage they may cause.
Re:Gitlab ‘rethinking’ third-party telemetry by GetOutOfBed on Friday October 25, 2019 @01:27AM (#21352151)
But what's the difference? You PAY gitlab in both instances and your leverage is the same. Do you want to be involved in reviewing their motherboards for spyware chips as well?
Re:Gitlab ‘rethinking’ third-party telemetry by skywhopper on Thursday October 24, 2019 @11:42AM (#21345744)
If you are self-hosting the product, you can control changes to the environment. If you are pulling in third-party scripts on the fly, then that control is gone.
Re:Gitlab ‘rethinking’ third-party telemetry by chrisseaton on Thursday October 24, 2019 @11:56AM (#21345891)
Ah I guess the real problem is 'on the fly'.
Re:Gitlab ‘rethinking’ third-party telemetry by TeMPOraL on Friday October 25, 2019 @05:38AM (#21353285)
The problem is that the resource the URL points to resides on a system that's neither under your control, not under counterparty's.
Re:Gitlab ‘rethinking’ third-party telemetry by type0 on Thursday October 24, 2019 @11:31AM (#21345639)
No difference really, but fourth party scripts are the worst :-/