Not sure if you were one of the people who shot me an email or not, but I don't think pdfgrep captures the essence of the project. It's more annotations/note-taking/human labor review of pdfs than regex/search. Although that's not to say that OCR of the pdfs would not be involved - I'm a big fan of OCRmyPDF.
But this is also not intended to have any command-line interface. I can do it, but that's definitely not the audience I'm building for. Quite the opposite.
You can conditionally deploy resources by setting the count on most resources. So you can have an environment variable with something like has_cache. Then in your terraform use a ternary or something to set the count to 1 if has_cache is true and 0 if it’s false. I have done this without much fuss.
I’ve been reading the Economist digitally using their app for years. They had a few issues over the years - I think they prevented copy/paste for a minute. I was pissed about that.
But now I love the app. The typography is decent, they support light/dark themes, you can play human-read audio of every piece individually, etc.
I know you might be looking for something more DIY, but this simple service has been really refreshing to me: https://bearblog.dev/
It’s so simple and easy. If you want to focus on content instead of tinkering with your blog endlessly (like I have done several times), this is a great option.
I've seen a few different Bear Blog blogs, and I think the feature-set would be sufficient. One unlisted requirement of mine is to be able to use a custom domain. GitHub makes this easy, so that's one reason I selected GitHub for the other blog.
Not seeing an option right off bat to do this with Bear Blog, but I will poke around. Thanks!
> Instead of storing the data on-chain, NFTs instead contain a URL that points to the data. What surprised me about the standards was that there’s no hash commitment for the data located at the URL.
I've been recently exploring the Solana[0] NFT ecosystem. The situation is similar there and I admit it took me by surprise at first. However upon further inspection, there's more to the story.
As others here have mentioned, most serious ETH collections address this problem using IPFS. But on Solana, Arweave[1] is a popular solution. I had never heard of Arweave before and it's a seriously cool concept. In a nutshell, it's a system that allows you to pay for 200+ (potentially much more) years of storage _up front_. I won't pretend to understand it all, but it effectively pays the network of miners to host your assets indefinitely. The up front payment - which is steep when compared to traditional hosting - provides a "sustainable endowment" for these mining rewards. This allows you to guarantee that the asset will be available without counting on some random hosted storage system.
It seems that NFTs are the main use case for such a system at the moment. However I can imagine other use cases could emerge for an answer to this question I never really thought to ask: "How can I ensure that an asset is hosted "forever?" Interesting problem and an interesting solution that a network like this - with its marriage of decentralized technology and economic incentives - is uniquely poised to address.
I often find it useful to relate the Web3 movement to the introduction of the internet. What problem was did that attempt to solve?
The internet solved problems that were only apparent in hindsight. The same could be true of Web3. It could also be nonsense, but I don’t think so. The absence of a particular problem to solve doesn’t necessarily render it useless.
This is an interesting comment because I disagree completely. Web3’s binding of economics and technology is _exactly_ what makes it compelling.
Free versions of things are often impractical. Good things take time and effort. How many users host their own email servers or have their own mastodon instance for example? Most people prefer to pay (in fees or in ad attention) for premium versions of these services that are built/maintained by private companies in a closed/centralized manner.
At its best, Web3’s marriage of economics and technology allows for a hybrid model where people pay for premium versions of these products built by people/companies in an open manner. The closed vs. open is key here. Without Web3 you can build something open/decentralized for free or something closed/centralized for profit. Web3 allows building services that are open/for profit.
Imagine the power of capitalism harnessed by open projects. Maybe I’m crazy, but that’s what excites me about Web3.
I was also confused about this. It appears this library includes components specifically geared for travel-oriented applications. Still seems like most of the components are pretty generic, but here are some examples that stood out to me:
My company has been using PhoneGap to deliver enterprise mobile apps for years. Though we have long realized that PhoneGap will not be be around much longer, the migration has been quite a pain for us.
We have been able to move to Ionic without many code changes, so that's our de facto solution. I'm curious to hear about others' experiences with PhoneGap, Cordova, and Ionic in the real world. Ionic seems to be the best path forward as the "spiritual successor" to PhoneGap, but I have also been looking into React Native (possible with Expo).
After a quick search, I found pdfgrep[0] which sounds like one simple way to solve this problem. But I think it only runs on Linux.
[0] https://pdfgrep.org/