ayoayco / cozy Goto Github PK

Let's start with respecting the system theme preference!

• summary
• emotions
• Political inclination

An article could contain several assets/ links

• Images
• Other articles

Links to other articles can be cached in a different temporary cache, and they could either be:

• Moved to the main history cache when user views them; or
• Deleted when user closes current view without viewing

Display a score of the completeness of information available for article readability

On home, only show recent 5 or 10 items then show a link to "see all"

The Article data we receive contains img elements, add all src attribute values to the cache. See example of how to add to the cache in Library.astro component

just an idea to have some mechanism to cache a recent request via an API middleare an article so if user requests again it will be faster. Still not sure how to approach this with current stack

Following are examples of articles that does not work on Safari's reader view

1. https://cozy-reader.netlify.app/?url=https://www.windowscentral.com/best-and-most-reliable-hard-drives-synology-nas
2. https://www.videogamer.com/tech/apple/can-you-play-diablo-4-on-mac/
3. https://game8.co/games/Triangle-Strategy/archives/368856

See: https://cozy-reader.netlify.app/?url=https://www.gamesradar.com/diablo-4-battle-pass/

After we implement #21 we can let users opt-in with their chosen cloud (DropBox, GDrive, or iCloud) to sync (ie., export -> sync -> import) their favorites

Prompt of user wants to add

library on the side

Uno or Tailwind

For back we can use the browser back button which will work seamlessly because we update the browser history now as needed

The Article data we receive contains links array of URLs, add all URLs in this array to the cache. See example of how to add to the cache in Library.astro component

Ask user if they want to send a webmention -- that is, let the website they fetched from know they "bookmarked" / "liked" the content

Disable when on home

• Delete entry
• Refetch
• Clear all

-Add to favorites moved to #20

From "home", when opening a cached article the "back" button doesn't go to "home"

In this issue,

• Reload home on "back" click and restore scroll position
• preserve the scroll position of home on "unload". See: https://stackoverflow.com/questions/29203312/how-can-i-retain-the-scroll-position-of-a-scrollable-area-when-pressing-back-but

Lateral reading is a fact-checking technique where the reader also reads other sources for the same topic.

Cozy could extract keywords and do a simple web search, then present the user with other sources for the topic.

This is good

1. easy research
2. prevent cognitive bias
3. fight possible propaganda
4. Detect inaccurate content

I'm not sure if there's a standard way of determining the language of a code block we get from the extracted article.

would be nice to be able to select, and highlight text
would be extra awesome if we can save notes related on highlighted text

we will use IndexDb for this kind of things

• add versioning to cache
• if cached responses are for an older version, refetch and cache

Hide/show reading library ?

From astro support:

You can use the :global() selector for cases like this:

content :global(div p) {
  /* styles */
}

I have some building blocks toward this already

1. base class - https://ayco.io/n/web-component-base/
2. example using in Astro with a decorator - https://ayco.io/sh/astro-client-components

After we implement #20 we can work on this

In case user opens a cozy article, that is it's starting with https://cozy-reader.netlify.app

Favorited items, definitely via IndexDB

I'm not sure if the history (Cache) is technically searchable

Currently, I'm skipping the caching if the current page is home ('/')

• In this issue, add the script to index.astro to cache the homepage every time it is visited.
• Update the "Library" link in AddressBar.astro so that it does DOM swapping for the cached home page (see Library.astro for how this is done on the links there)

Move the app into it's own page, so it is accessible in route '/a' ... the way to do this is move the current index.astro page contents into a new a.astro page.

After that you can create the project landing page in a new index.astro page :)

Feel free to explore designs you think is aligned to the project: a modern-day reading assistant.

Would enable

• full text search
• tags/labels (organization)