> In order to offer an "ad-filled experience" and maximize our profits, LinuxReviews would very much like you to allow our Google AdSense ad-partner to use tracking and cookies so we can show ads from them on our website.
I'm obviously old and cynical. The idea that the script that sends updates to GitHub should break, and that nobody noticed for a year, sounds entirely plausible. Likely, even.
I haven't checked the repo more thoroughly though. They really should give a public explanation; the idea they didn't this when multiple people have asked is not believable.
This is a very weird article. It is like the author really wants to believe that this was just an accident.
> forgot to update the GitHub repository
I don't think they "forgot". It was well discussed and people at signal were aware.
> That makes it look as if Signal has been pushing their code updates to git all along
It seems that someone doesn't really understand how software development on teams works if they thought that the whole team just "forgot" to commit their changes and no one noticed. It was expected to everyone I met that they were still using an internal repo.
9 comments
[ 2.1 ms ] story [ 30.9 ms ] thread> In order to offer an "ad-filled experience" and maximize our profits, LinuxReviews would very much like you to allow our Google AdSense ad-partner to use tracking and cookies so we can show ads from them on our website.
resist ALLOW
https://news.ycombinator.com/item?id=26721749
I haven't checked the repo more thoroughly though. They really should give a public explanation; the idea they didn't this when multiple people have asked is not believable.
I like Signal. I want to like Signal. But I find myself making an increasing number of excuses for behavior inconsistent with their roots.
I wonder if there is enough energy out there to propel a thin-client fork.
> forgot to update the GitHub repository
I don't think they "forgot". It was well discussed and people at signal were aware.
> That makes it look as if Signal has been pushing their code updates to git all along
It seems that someone doesn't really understand how software development on teams works if they thought that the whole team just "forgot" to commit their changes and no one noticed. It was expected to everyone I met that they were still using an internal repo.