Key part is *where reliability matters*, there are not that many cases where it matters.
We tell stories of Therac 25 but 90% of software out there doesn’t kill people. Annoys people and wastes time yes, but reliability doesn’t matter as much.
E-mail, internet and networking, operations on floating point numbers are only kind of somewhat reliable. No one is saying they will not use email because it might not be delivered.
Reliability matters in lots of areas that aren't war. Ignoring obvious ones like medicine/healthcare and driving, I want my banking app to be reliable. If they charge me $100 instead of $1 because their LLM didn't realize their currency was stored in floating point dollars and not cents, then I may not die but I'd be pretty upset!
As we give more and more autonomy to agents, that % may change. Just yesterday I was looking at hexapods and the first thing it tells you ( with a disclaimer its for competitions only ) that it has a lot of space for weapon install. I had to briefly look at the website to make sure I did not accidentally click on some satirical link.
Main point is that there is many more lines of code of CRUD business apps running on AWS and instances of applications than even non-autonomous car software even though we do have lots of cars.
I thought it was exaggerated but reading the archive, yeah that’s something that should not pass even glancing over by public communication person, or even like any manager like senior product manager…
As much as I know the story MSFT was basically driving limousines in front of Borland headquarters and showering developers with money to jump the ship.
When web apps took off there was nothing that would save Delphi. Web stack was awful back then and I also enjoyed Delphi an building interfaces with it.
But web stack unfortunately had many more upsides than desktop apps and nowadays tooling for web sucks less.
Can you elaborate on what big potatoes you're seeing? Genuinely asking. The Android app, for example, writes everything to the app's storage, and runs only when your phone is plugged-in and is connected to wifi. To me that generally means "when I'm sleeping". What's the big potato in this scenario?
The torrents are coming directly from Anna's Archive torrents list generator, which suggests their torrents based on how rare their content is. There's currently 177TB of data that is only seeded by 4 computers around the world, which I personally find worrisome.
People seem to be very concerned, but putting aside the legal risks (which I accept - don't use this if you're in one of the ~10 countries it could get you in troubles for), I don't really get it. The idea is to support Anna's Archive. If you do not trust the project, why support it? Levin is meant for people that want to support Anna's Archive, and my assumption was that this implies some kind of trust in their torrents.
Edit: just adding that "finding the list of what you want to seed and vetting that list yourself" is extremely not practical and not won't really help anyone. Torrents work because we're all seeding the same torrents. If I'd seed a torrent of my 5 favorite books and you seed a torrent of your 5 books, our torrents will forever have 1 seeder each. And good luck manually vetting all the files in one AA torrent. I am planning to let people manually add/remove torrents from Levin, but I highly suspect it will be used by very, very few.
Please, go to https://annas-archive.li/torrents and check their torrent list generator. It will recommend you torrent files that need help seeding. Pick one, and see for yourself that it's practically impossible to audit its content. I just checked and the average torrent size is around 125GB. With a typical file in it being around 0.5mb, you're looking at auditing 250,000 files. And the filenames are all hashes.
I would honestly love to know what you see as an alternative to trust here; an alternative that can still be helpful.
If you are seriously this upset about such a tool, why don't you just avoid using it? Instead of commending the author for their work you're trying to tear them down and prove them wrong in every reply. Why not just move on with your day and avoid using it?
I'm sorry if it sounded like I was being dismissive. FWIW, people suggested that I'll add some information to the README and even implement some kind of a "country-check" to warn the user, and I think these are all great ideas. I still don't think that auditing AA torrent files make much sense however.
As my first comment mentioned, the project is WIP. I posted it here because it seemed relevant, but if you're looking for bugs, I'm sure you'll find them both in the code and in the README. I assumed that people realise that a combination of torrenting + AA requires some precautions, but if your point is that I can make it clearer - I don't disagree.
CSAM is not something to scare people away. In P2P networks like Perfect Dark there are TBs of CSAM sitting in everyone's disks and we just get along with them.
Any iOS or Android app could in fact, download arbitrary content without you noticing, but corporations conditioned people to only raise alarms on torrents and other community efforts.
Not only downloading, but also uploading. Your ISP (in America) has a policy about how many DMCA strikes you get before they disable your internet permanently.
These are beautiful analogies, but I'd appreciate an answer my original question. Your package can explode, these torrents cannot (as far as I am aware). If you want to send me a CD to store at my house, feel free to email me.
Assuming you are referring to non-books kind of content: I assume that if this happens to anyone, we'd learn about it and all stop seeding AA's content until they explain what happened and how they're making sure it doesn't happen again. The poor person this happened to will have to explain that this wasn't at all what they thought the software was doing.
As I said in other comments - yes, this requires some kind of trust in the AA project. Personally, I tend to have more trust in this kind of projects than in big corporations, of which people are happily running their binaries without blinking. However, I'm not trying to convince people to trust AA - this project is simply meant for those who want support them.
AA has plenty of illegal and gray content. It's not something laypeople should help to seed. You need to go in eyes wide open and protect yourself if you're participating, which I do not feel you are sufficiently emphasizing in this pitch.
To clarify your question, are you asking if "AA actually distributes stolen content" (one could argue no, since it is only available by Torrent) or "the stolen contents of AA" (essentially every published book in existance)?
Honestly, in these HN discussions, I am disappointed that people seem very casual about mass piracy of copyrighted works.
Neither of those. It's generally violating the law to distribute that copyrighted content, but the content itself isn't illegal. They're asking about what's in there where the actual content is the problem.
As far as being casual about mass piracy, I think the preservation outweighs the damage, and on top of that copyright is too restrictive in the first place. If we could massively boost the internet archive and have dozens of similar institutions, and didn't paywall science articles, and brought copyright down to a reasonable duration, then after that I would be much easier to convince that instances of piracy are bad.
You could say that cameras want to be free. A camera left unattended is likely to walk away.
Some rules are about adjusting incentives and disincentives to maximize value for everyone.
There is a lot of room to argue where that balance is. But the "its easy to copy stuff" argument isn't even grappling the kinds of context that result in more creations.
Most copyrighted material doesn't hurt you in any way if you can't have a copy. So someone creating something and not sharing with you should not be something to complain about.
Nor should it be a problem if they are willing to share with you, if you do something for them.
You are also completely unfettered to create anything for yourself that you feel you are missing.
> Why do none of you understand that this is for Anna's archives official torrents only?
Because you are on the site where people who have no understanding of the domain or the problem still feel it necessary to share their opinion on things they don't understand.
It is first time I see name of that project. I don't know anyone who is involved in that project. On Wikipedia I see it "shadow library launched by pseudonymous Anna".
"Anna's archives official torrents only" - doesn't put me at ease and it is far far from SETI@Home that was ran by highly regarded university and it wasn't storing any torrents on people hard drive.
Random people should not "just try it out because it is as easy as SETI@Home" - it should be, people who already know the project and would like to contribute but it was a hassle for them to set it up.
> Your package can explode, these torrents cannot (as far as I am aware).
Sure, but what if the scenario was slightly modified, with explicit 100% guarantees regarding rhe package you would receive in the maile:
1. It could only contain either an SSD/hard drive or a usb drive. The storage device has not been tampered with. It was only ever used as a regular storage device out of the box.
2. There is no malware or any malicious executables on the storage device. The only types of data that it could contain would be text/html, structured data/document files (json, csv, office suite files, pdf, etc.), and media files (audio, video, images, etc.). None of those files will exploit any vulnerabilities in the software that opens them (neither through the parser nor anything else)
This makes it nearly a perfect 1:1 analogy to the torrenting scenario, both involving the exact same set of imo the most important dangers.
Which, for me personally, is the fear of ending up with illegal content (CSAM, stolen credit card dumps, etc.) on a storage device in my possession through no fault of my own.
Even if it could be a winnable battle in the end, it would be pretty much over reputationally way before it gets to the legal resolution. Just being accused of having any illegal content of that nature is not something I would want to ever deal with at all.
You gotta realize how it would sound and how you would appear to most uninvolved average people in real life, when your legal defense isn’t even something like statement #1 below, and is way closer to the statement #2:
> “I am not guilty, the accusarions are false, those files were never present on any of my storage devices.”
> “I am not guilty, despite those files being actually present on a storage device in my possession. That’s all due to how torrents inherently work, so, let’s start from the basics…” [and now we gotta explain simplified basics of torrent technology and how it works to the DA, the judge, as well as anyone else observing the trial, and pray they will try to actually understand]
I would love for the authors of in-print books to be paid - even when it's usually not a lot. Buy books - they are cheap, or borrow them from libraries - they buy books. If you need books for not-reading, and at scale, you should still be paying - especially if you can afford to pad Nvidia's fat margins.
Even if you're self-interested, I would urge you to pick your crimes carefully, and to remember to commit one crime at a time. If distributing copyright material is your chosen hill - more power to you! Just don't sleep walk into it thinking it's harmless.
Allowing anonymous people to host files on your server is a great way to collect (and distribute!) illegal porn, stolen data, stolen software, police warrants, etc...
Everything with the power to protect the innocent, also has exactly the same power to protect the guilty. The two facets are inseperable.
Observing only the negative side, or only the positive side, is a null argument. The fact that a tool can be used for bad is exactly cancelled out by the fact that it can be used for good. Neither is a valid basis for any kind of policy.
Except that on balance, it's better for everyone that we have tools and capabilities and knowledge than not.
It's better that we have knowledge of say, poisons, than not, even though some people apply the knowledge to do harm.
This manifests in at least a couple different dimensions. The simplest one: there are more good or neutral people using knowledge and tools for good things than not. A less direct way: It's better for you to have options to help yourself and others deal with problems and meet needs than not.
Even if someone can use a tool against you, you are still better off having a lot of useful tools at your disposal in general than not, including to counter the one going against you, which zeros that out, and then also to deal with everything else, which becomes a net positive.
The alternative is to be an animal. Either a wild animal totally at the whims of nature, or worse a voluntarily domesticated animal that knows that tools exist, but has abdicated all responsibility for their own welfare to some farmer claiming to take care of them. And you still have the exact same bad guy problem, only now without any ability to deal with it.
Acting like the bad side of a useful thing is the only side, or even the most important side, is simple bad math.
Aside from any other unflattering quality that results in fear of any obvious easily identified harm being one's highest priority that outweighs all other considerations.
There are Japanese-specific darknet networks (using different technology?) that have existed for decades, or are you referring to Japanese language content on Tor, etc.?
When React launched in 2013, its defining idea was strict one-way data flow: parents pass data down via props, and updates happen in a clear, explicit place. Children can't mutate parent state directly; they signal changes through callbacks. The result is predictable, traceable state changes.
This contrasted with MVVM frameworks like early AngularJS, Knockout, and WPF, which relied on two-way data binding. That automatic syncing felt convenient for small apps, but at scale it often led to hidden coupling and hard-to-trace update chains.
Over time, many developers came to view pervasive two-way binding as a design mistake in complex systems. React's unidirectional model gained traction because it favored clarity and control over "magic."
Thanks GPT but I know all of that. I was expecting some eye opening new evidence because person I was asking seemed really confident and using strong words.
But that’s just generic „blablabla”. MVVM is not a mistake and is still plenty useful.
Because that’s pretty much any freaking thing - oh Python, oh PHP, oh driving a fork lift, oh driving a car.
Once you invest time in using and learning it is non issue.
I do get pissed off when I want to use some Python lib bit it just doesn’t work out of the box, but there is nothing that works out the box without investing some time.
Just like a car get a teenager into a car he will drive into first tree.
Posting BS on Facebook shouldn’t be benchmark for how easy things should be.
I am quite sure live band will definitely sound worse than most sound systems.
My experience is I hanged out with one band in a garage where they were practicing and I attended couple live music shows in pubs.
Main upside of those live music shows is that they are not "perfect" like playing a record and each one of the gigs will be off here or there, tempo somewhere will be off or a tune will be off - or you are just having enough beers you don't care pick your way :)
We tell stories of Therac 25 but 90% of software out there doesn’t kill people. Annoys people and wastes time yes, but reliability doesn’t matter as much.
E-mail, internet and networking, operations on floating point numbers are only kind of somewhat reliable. No one is saying they will not use email because it might not be delivered.
reply