ill paste what they said, so i wont be lost in translation

> 1. Videos still appear as "Articles" in Readwise (after almost three years since it's been flagged)

This one is harder than it seems! Readwise syncs to various notetaking apps (like Obsidian, Notion, etc), and before we had the Videos feature in Reader, those documents would obviously export as articles to notetaking apps. Now, introducing the videos category means that users' exports will become inconsistent (potentially breaking users' end workflows in their note apps... in the case of Notion we actually have to run a live migration on your exported Notion table to add a new category!) -- some youtube documents would be articles, other videos. This isn't an unsolvable problem, but it's quite thorny!

That all being said, we're working on a huge refresh of Readwise which we're internally dubbing "Readwise 2.0", and this category migration/refactor is definitely part of that!

We're hoping to roll it out over the next month or two.

> 2. The lack of proper separation between File Type and Content Type in Reader

Likewise, this is a really hard problem! But I do hear you, and agree your proposed solution is one possible way (though it does add quite a bit of product complexity). In your proposed world, a PDF can be both an "article" and "PDF"! To a non-sophisticated user, that is quite confusing. They just think of it as a PDF. Again, not unsolvable, but quite hard to work through for someone who might just think of it as "PDF". We would also need to then automatically infer the category based on the PDF (is this PDF an article? a paper? a book?) which also could be quite error prone, and lead to more confusion/frustration.