That's not quite true. There's overall a big, distributed and decentraliszed effort to archive our electronic past, it's not just archive.org. For example, it's fun to look at old newsgroup discussions from 1994, and it's something I can find at Google's archive. And more importantly, it's available to everybody. And it's not the only place to find historical internet stuff.
I do agree though that archive.org is too valuable a resource to ever lose.
Google also isn't perfect. There was a post the other week about how there were no searchable images on Google older than ... I don't remember, 2005?
> All my important information is stored in a personal wiki
Ah, there's the crux, no? I dream of a system that automatically captures and allows me to interact with and query against everything I do, every ebook I download, every image, every document, every video, every site. What you're describing isn't this, it's not even the same ballpark.
Recall, even if it isn't perfect, is in the same ballpark.
> Exactly. So please tell me why I would want to essentially allow something like this on my machine?
Because it's useful. I don't understand this. It's like a circular argument. I want a useful feature, I install it on my PC. The security concerns apply regardless of Recall existing.
I wish the author had given the model of the HDD and pictures of the PCB and connector. I think it'll probably be reasonably simple to hook that up somewhere else to copy the data. I work at a place where we do this sort of thing all the time, even with 30 year old hardware or older, the problem is just getting out of the software solution box. This isn't a software problem and it requires a different sort of expertise for the most part.
I've been wanting something like this for my entire life and it seems like computers are finally heading in a direction of becoming extensions of ourselves instead of just clunky tools we have to adapt ourselves to. This has been the kind of sci-fi I've dreamt of since I was a kid.
I get the privacy concerns. And security concerns. But honestly, if somebody has this kind of access to your computer, they have access to your entire life anyway. Setting up a keylogger, getting all your passwords, getting any vital documents, etc. It's trivial. When is it just pointless fear mongering? It's subject to the same security concerns as everything else and we don't suggest people switch to pen and paper instead.
Ideally OP would keep the source images of the original journal pages around even after transcription. I think ChatGPT (or LLM in general) is probably the best option, but the best overall solution would accept that LLMs are flawed and would require long-term iteration.
A single example of it being done well doesn't have any bearing on all the issues stemming from the use of Discord as knowledge bases, wikis and documentation.
Out of curiosity, is any of that useful information on the Elixir Discord available to be searched for with Google or any other search engine?
Tbh, developers just need to test their site with existing tools or just try leaving the office. My cellular data reception in Germany in a major city sucks in a lot of spots. I experience sites not loading or breaking every single day.
Websites regularly break because I don't have perfect network coverage on my phone every single day. In a lot of places, I don't even have decent reception. This in Germany in and around a major city.
Why do you think this only applies to people on a boat?
Does it? Every time I see DRY'd code, it usually makes the project it's in more difficult to understand. It's harder to understand where values come from, where values are changed, what parts of the codebase affect what. And that's before trying to figure out where to change something in the right place, because it's often unclear what other parts of the code are coupled to it through all the abstractions.
At a high level, at first glance, the code might look good and it "makes sense". But once you want to understand what's happening and why, you're jumping through five different classes, two dozen methods and you still don't know for sure until you run a test request against the API and see what shows up where in the debugger. And you realize your initial glimpse of understanding was just window dressing and actually nothing makes sense unless you understand every level of the abstractions being used.
It's suddenly a puzzle to understand another software developer instead of software engineering.
I actually use pinning, blocking and raising/lowering the value of individual sites every day. I wish this is the direction search engines went in the first place and it's the direction I hope Kagi continues. I want a personalized search engine that's personalized by me, not by a company trying to profile me and make money off of my clicks.
There's a fairly simple explanation for this. We've seen in studies that experts aren't fundamentally any better at remembering things. We just get better at chunking more and more abstract groups of information together. We can never increase the around 7 pieces of information we can hold in short-term memory. But we can increase what and how much those 7 pieces represent.
I do agree though that archive.org is too valuable a resource to ever lose.
Google also isn't perfect. There was a post the other week about how there were no searchable images on Google older than ... I don't remember, 2005?