Thanks for pointing it out, README is outdated, .rapel-state.json is not being used anymore, as the current state is now calculated from the chunk files downloaded. It doesn't detect remote file changes.
I tried using existing solutions like aria2, but rapel is built to work on constrained machines with limited storage, like a raspberry pi running 24/7. You can use the post-part argument so that after downloading a chunk, you can do something with it (eg. upload it) and remove it afterward. Then, on another bigger machine, download the chunks and merge them
This is similar to what happened with smartphones and the people going back to cellphones without touchscreen.
AI coding hurts your ego. People keep forgetting this is just a tool that accelerate what you want to do. If you leave decisions to the AI you'll be probably disappointed or surprised.
just asked chatgpt to write one in python, and used md5 digest slicing, what might be a common approach to simulate several hashes just from the base md5 digest. I guess fine for not critical use cases
That's a site I've made to track satellites. Yet another one! It's a 2D map, where you choose / fast-forward time, see the ground track prediction, and horizon radius.
I've been reading this forum since years, and generally its perception of photography is rather technical and very proud to achieve perfect photos with the right color balance and all that. Sure it's nice to know all those technical concepts, so you can be conscious when destroying them, and have fun.
Concerning photography tech, it's great to talk about sensors, how mobile camera is being achieved nowadays, like explained in those Pixel blog posts, or even about analog photo development works.
Hey HN, enjoy bad photos, take pictures with the worst camera you can find. I've read in some comments here that you need to take at least 10k photos first until you get better, this is not a sport
I'd like to know how a newcomer would feel after reading the tutorial of the monster you created, React.
Take React hooks at its purest for example. I can't imagine the WTF feeling in a newcomer's mind, when the useState(<default-value>) helper function returns the "reactive" variable and a function you have to use to update it (!) do you realize how tricky you end up with your technical DOM optimizations?
Same with useEffect(), where you probably will have your whole function defined right into the first argument, and a list in the second one, very lost in your IDE. Who would expect that an empty array of dependencies would trigger it once? Why we should track all those dependencies at first place?
When recommending a frontend framework, I found Vue to be more dev friendly. However, it's currently in a long migration crisis, because documentation shows the 2 different APIs you can choose. I know that the differences are well explained (although they don't even say that's to be retrocompatible with Vue2 mindset), but for a newcomer's mind, it's like asking: which pill do you want to take? red or green? Choose your own adventure!
I'm in favor of privacy and dns over HTTPs/TLS, but here, plain text dns queries have been useful to see how Signal went up (not surprised though). I wonder how Telegram being a Russian product is playing in this war
Another thing about this is that artists permit themselves to not fully understand the technology of things, so they just use it, in a way that maybe the ones who understand how it works doesn't because they are already fascinated with how it works
It's even freaking funny that "SEO" appears as a Related search at the bottom of that search url. It has nothing to do other than a lot of people (we) come from a SEO article