1,716 karma · joined March 19, 2013
You may be thinking of the optional -depth switch, which allows you to create shallow clones that don't have the full history. If you don't include that, you'll get the full history when cloning.
However, for the sake of devil's advocacy, I do also want to point out that the first thing a lot of people used to do after downloading and extracting a source tarball was to run "./configure" without even looking at what it is they were executing - even people who (rightly) hate the "curl | bash" combo. You could be running anything.
Being able to verify what it is you're running is vitally important, but in the end it only makes a difference if people take the time to do so. (And running "./configure --help" doesn't count.)
I hate it when sites do this. I don't want my window decorations to be restyled in the name of aesthetics. I need them to be usable.
In this case, there's an explicit middle point - chatgpt.com resolves to a CloudFlare server, so CloudFlare is actually one of the ends here. It likely acts as a reverse proxy, meaning that it will forward your requests to a different, OpenAI-owned server. This might be over a new HTTPS connection, or it might be over an unencrypted HTTP connection.
It really is super important to emphasize this point. End-to-end encryption is not simply that your data is encrypted between you and the ultimate endpoint. It's that it can't be decrypted along the way - and decrypting your HTTPS requests is something that CloudFlare needs to do in order to work.
(To be clear, I'm not accusing CloudFlare of anything shady here. I'm just saying that people have forgotten what end-to-end encryption really means.)
This is not a reason to sit idly back, of course. GrapheneOS is in danger, as you say - it's just not necessarily from this particular decree.
(I'm not complaining, mind you - I did find it very interesting to read. It just doesn't strike me as typical AT content, or at least not the kind that people typically share for it. Thank you to OP for doing so!)
Still, though, I wonder if that mindset is still going to be around.
(I do agree with your position; I just wanted to throw that out there.)
I'm not entirely sure why the article didn't talk about this.
I'm reminded of another project called Gemini[0], which aims to solve a similar problem in a different way. The Gemini protocol is very, very simple to implement (with the exception that it uses mandatory modern encryption like Gurted does, so you need encryption libraries), and it's intentionally difficult to extend, in an effort to make it a simpler and more efficient alternative to the Web that is resistant to takeover by corporate desires, in a way that I'm not sure Gurted achieves.
Archives can be searched fairly easily, although admittedly most will be incomplete (hence Deja and Google Groups back in the day).
Some newsgroups are still active, but not many. Why? What went wrong?
Sounds like it's as legitimate as running the sync command - ie. ideally you should never need to do it, but in practice you sometimes do.
A lot of the reason for that is because yt-dlp explicitly makes it easy for you to update it, so I would imagine that many frontends will do so automatically - something which is becoming more necessary as time goes on, as YouTube and yt-dip play cat and mouse with each other.
Unfortunately, lately, yt-dip has had to disable by default the downloading of certain formats that it was formerly able to access by pretending to be the YouTube iOS client, because they were erroring too often. There are alternatives, of course, but those ones were pretty good.
A lot of what you see in yt-dlp is because of the immense amount of work that the developers put in in order to keep it working. Despite that it now allows for downloading from many more sites than it originally was developed for, they're still not going to give up YouTube support (as long as it still allows DRM-free versions) without a fight.
Once YouTube moves to completely DRM'd videos, however, that may have to be when yt-dlp retires support for YouTube, because yt-dlp very deliberately does not bypass DRM. I'd imagine the name would change at that point.