Caching timeline, toots and media

Rubicon commented

2024-09-25 07:00:44 +00:00

Owner

This is a discussion about caching toots and media. It’s needed feature because caching significantly reduces the "empty" time as the app started.

Rubicon added the

feature

proposal

label 2024-09-25 07:00:44 +00:00

Rubicon commented

2024-09-25 07:32:59 +00:00

Author

Owner

What’s more, We already have a very simple toot cache for hero animation. The new cache system can ease the burden to set the cache.

Rubicon commented

2024-10-14 16:35:38 +00:00

Author

Owner

I think we may need separated:

timeline cache
toot cache and media cache

The toot and media cache can be done with the Web Cache API, as they can be seen as atomic data. The timeline cache is composed data so we may need indexed db to implement it correctly.

Additionally, the timeline cache may need to able to have hole - if we don’t actually fetch the whole missing part of the timeline.

Compatibility:

IndexedDB 2.0: all targets support
Web Cache API: all targets support

I think we may need separated: - timeline cache - toot cache and media cache The toot and media cache can be done with the Web Cache API, as they can be seen as atomic data. The timeline cache is composed data so we may need indexed db to implement it correctly. Additionally, the timeline cache may need to able to have hole - if we don’t actually fetch the whole missing part of the timeline. Compatibility: - IndexedDB 2.0: all targets support - Web Cache API: all targets support

Rubicon commented

2024-10-18 12:26:11 +00:00

Author

Owner

a RPC server is added into the service worker - we can use it to communicate with the service worker.

Rubicon added this to the (deleted) project 2024-10-18 14:52:18 +00:00

Rubicon removed this from the (deleted) project 2024-10-20 12:41:22 +00:00

Caching timeline, toots and media #14