tristanho

Hey all, founder of Readwise here, happy to chat about this if anyone is interested :)

Thanks! Kobo is hard because it's proprietary software, but we would like to...

However, there is a wide range of eink devices that already exist that run Android (check out Boox, Meebook, Daylight, though there are many others) -- we've optimized Reader to run great on these devices :)

No, unfortunately their API doesn't return the actual html content of the saved articles :( just the urls and all the metadata: highlights, title, author, image, tags, location, etc

I really wish they did :/ some things aren't even on the internet archive and are probably saved uniquely on Pocket's servers. Would be sweet if they could open source that data.

Cool! The import should auto-retry, but in case something gets snagged there you can also always do `cmd+k -> pocket` to retrigger a full import.

Totally hear you on price.. Reader is built for people who spend a lot of time reading and can justify it (and the sub also comes with access to our Readwise product too).

We also have a 50% off discount for students as well folks in countries with depressed currencies (eg India, South American countries, etc) which might help.

We try our best, but are also bootstrapped and have to charge enough to keep the company sustainable!

That is definitely one of the biggest painpoints, and we feel it ourselves for whatever it's worth!

However, if you're just looking for a replacement for Pocket, you only need the Reader app/extension and it shouldn't be clunky at all.

It's only if you want our highlight-specific reviewing/exporting functionality that you would also need the Readwise app... still not ideal, but merging two complex products like this without making the experience janky/complicated for new users is a really really hard problem!

You can connect Pocket to Readwise Reader ( readwise.io/reader ), via Pocket's API, which will let Reader view all the tags, metadata, highlights, etc.

Even if you didn't want to use Reader, you could then export from inside Reader and Readwise to pull out CSVs of all of your articles+highlights -- no subscription required.

(full disclosure: founder of Readwise here, obviously if you want to try our Reader app that would be sweet, but at least wanted to offer this way to get a more complete export)

This is basically our exact experience at readwise.io too. Originally, everything was through Heroku.

We started by moving our heroku redis and postgres to redislabs and crunchy respectively, which were 10x+ better in terms of support, reliability, performance, etc. Then our random addons.

We recently moved our background job workers (which were a majority of our Heroku hosting cost) to render.com with ~0 downtime. Render has been great.

We now just have our web servers running on Heroku (which we'll probably move to Render next year too)...

End of an era. Grateful for Heroku and the next generation of startups spawned by its slow decline :)

Honestly just loading all vectors in-memory (and stuff like sqlite, pgvector) is totally fine when you're dealing with O(100k) vectors, but beyond that all the workable options like pinecone get gnarly, slow, and ridiculously expensive.

The best option by far I know of is turbopuffer.com , which is like 100x cheaper than pinecone and seems to actually scale.

Since it's not listed in the suggested vector dbs section of the slides, wanted to lob it in as a solid suggestion :)

Sort of off topic, but for diagrams like the author seems to want (well, maybe a little lower fidelity, but good enough for any software system mapping I do), I love using Kinopio (kinopio.club)

Didn't see any mentions here.

Hmmm yes, I wonder if this project was discovered/shared here before it was really ready to be published.

Very excited for the code/demo when they're ready!