learn VS notes

I don't have a way to find and curate audiobooks. Plus, LibGen books are already available on IPFS so all I need is collect links. I have been running https://learnawesome.org/ so books seemed far more approachable.

Fantastic! I'll have a deeper look and see if there's any opportunities for integrating this into https://learnawesome.org (which is also open-source).

I am building https://learnawesome.org

It's an attempt to organize world's knowledge. Right now, it looks like GoodReads-like social network for learning resources organized by topics, formats, difficulty levels etc. But there's a knowledge-graph that separates ideas and the medium those ideas are expressed in. For eg: "Sapiens - the book" and "TED Talk given by Yuval Harari" are connected to the same node.

This idea isn't anything new. Here is Danny Hillis talking about it at OSCON 2012: https://youtu.be/wKcZ8ozCah0

https://github.com/learn-awesome/learn for example

Perhaps https://learnawesome.org/.

I have been dealing with the same problem for curating resources at https://learnawesome.org. Projects like Openlibrary do collect unique identifiers for _books_, but for everything else, it mostly takes manual effort. For example, I collect talks/podcasts by the author where they discuss ideas from their books. Then there are summaries written by others.

This is a fantastic effort! Kudos :-)

I have been collecting learning resources and their reviews by experts at https://learnawesome.org/ (open-source, built with Ruby on Rails and TailwindCSS). Would you be kind enough to share the raw JSON files for their books?

LearnAwesome has its own topic taxonomy so it will still require tagging topics manually, but it can save me some effort on scraping/parsing LSE/Nature sites.

I have been adding a number of these free books at https://learnawesome.org/

Do you really care about the format being PDF or is it about the books being FREE? I'd like to make common queries like yours easier. LearnAwesome is open-source, so of course you're free to contribute: https://github.com/learn-awesome/learn

Is there an easy way to comply with an accountable IPFS block list?

"Implement Allow Lists and Block Lists" (2018) https://github.com/ipfs/notes/issues/284

"IPIP 298: (allow|deny)lists for IPFS Nodes and Gateways" (2022)

As for general gateways, those could be used to pull general illegal content against your will, and allow/block lists were discussed at one point for that reason (https://github.com/ipfs/notes/issues/284). However, in the interim, there is a config option Gateway.NoFetch that causes a gateway not to fetch new content, giving you an allowlist if you also have the content you want to share pinned beforehand.

> IPFS is basically the answer to the question "what is the RIGHT way to decentralize the web?"

There is no RIGHT way to decentralize the web. I don't think IPFS is right way to do it either.

Tim Berners-Lee's Solid (https://solid.mit.edu/) offers a much more practical path to a decentralized web. The advantages with Solid's approach over IPFS is that:

- Solid doesn't throw out what we already have, and recommend a new layer on top of the internet. Example: ipns

- Solid handles access control which pretty much every application needs. Encryption is btw, a poor substitute for access control. https://github.com/ipfs/notes/issues/376

- Solid has the ability to revoke access (very important), delete data

- Solid can work in browsers without extensions.

- Solid is not muddied with talk of the Blockchain. It's disappointing that the cryptocurrency has very nearly hijacked this space.

- Solid is conceptually simple. You own a pod that has a unique address (using familiar schemes). You put your stuff on it and allow access to people; like DropBox but standards based. Companies can offer paid hosting services to run your pod - more space, bandwidth etc.

- IPFS is not commercialization friendly.

- IPFS performance is unlikely to be great, ever.

Disclosure: I am invested in an open protocol similar to Solid, but simpler. So not entirely unbiased.

This, and a bunch of side issues linked from it, is a good discussion: https://github.com/ipfs/notes/issues/281

IPFS is not anonymous and like other p2p protocols shares your ip address.

There's been a bit of effort to get it working over tor for years now but the fundamental design makes this difficult. Also despite all the money that has poured into filecoin this doesn't seem to be a priority.

This issue is nearly 6 years old:

https://github.com/ipfs/notes/issues/37

As I see, this is an open issue to be implemented natively in IPFS: https://github.com/ipfs/notes/issues/339