[GH-ISSUE #435] [Feature request] Add "Random Bookmarks View" to rediscover forgotten links #278

Open
opened 2026-03-02 11:48:24 +03:00 by kerem · 4 comments
Owner

Originally created by @alexkutsan on GitHub (Sep 27, 2024).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/435

Originally assigned to: @xuatz on GitHub.

In large bookmark collections, many valuable links become forgotten as they get buried under newer additions. To help users rediscover these overlooked bookmarks, I propose adding a "Random Bookmarks View" feature.

Proposed Solution:

  • Random Bookmarks View: Introduce a new view that displays bookmarks in a random order.
  • Persistent Randomness: Use a constant seed for the randomization so that the order remains the same across page refreshes. The seed could automatically change daily or be manually reset via a "Shuffle" button.

Benefits:

  • Rediscovery: Encourages users to revisit and engage with older bookmarks they might have forgotten.
  • Enhanced Engagement: Adds an element of surprise and exploration, making the bookmark manager more interactive.
  • Personalization: Gives users control over how they view and interact with their bookmark collection.

This feature is akin to how platforms like Google Photos highlight past memories, prompting users to revisit content from a year ago or more. Implementing a similar concept in. Hoader can enhance user experience by bringing forgotten but potentially valuable bookmarks back into view.

Originally created by @alexkutsan on GitHub (Sep 27, 2024). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/435 Originally assigned to: @xuatz on GitHub. In large bookmark collections, many valuable links become forgotten as they get buried under newer additions. To help users rediscover these overlooked bookmarks, I propose adding a "Random Bookmarks View" feature. Proposed Solution: - Random Bookmarks View: Introduce a new view that displays bookmarks in a random order. - Persistent Randomness: Use a constant seed for the randomization so that the order remains the same across page refreshes. The seed could automatically change daily or be manually reset via a "Shuffle" button. Benefits: - Rediscovery: Encourages users to revisit and engage with older bookmarks they might have forgotten. - Enhanced Engagement: Adds an element of surprise and exploration, making the bookmark manager more interactive. - Personalization: Gives users control over how they view and interact with their bookmark collection. This feature is akin to how platforms like Google Photos highlight past memories, prompting users to revisit content from a year ago or more. Implementing a similar concept in. Hoader can enhance user experience by bringing forgotten but potentially valuable bookmarks back into view.
Author
Owner

@MohamedBassem commented on GitHub (Sep 27, 2024):

I love the idea. And it shouldn't be too hard to implement. I'll add it to my backlog :)

<!-- gh-comment-id:2378914251 --> @MohamedBassem commented on GitHub (Sep 27, 2024): I love the idea. And it shouldn't be too hard to implement. I'll add it to my backlog :)
Author
Owner

@jakob1379 commented on GitHub (Jan 14, 2025):

I like the part of rediscovery, that would definitely help rooting out the weeds of history!

You can do it easily with the cli tool already as well by doing

npx @hoarderapp/cli bookmarks list --json | \
jq -r '.[].id' | \
shuf -n 1 | \
xargs npx @hoarderapp/cli lists add-bookmark \
  --list <id-of-random-list> --bookmark
<!-- gh-comment-id:2589783742 --> @jakob1379 commented on GitHub (Jan 14, 2025): I like the part of rediscovery, that would definitely help rooting out the weeds of history! You can do it easily with the cli tool already as well by doing ```bash npx @hoarderapp/cli bookmarks list --json | \ jq -r '.[].id' | \ shuf -n 1 | \ xargs npx @hoarderapp/cli lists add-bookmark \ --list <id-of-random-list> --bookmark ```
Author
Owner

@xuatz commented on GitHub (May 18, 2025):

This sounds interesting, I also have a vision of a feature something like this, so I'll give it a shot to implement something to satisfy this issue @alexkutsan

<!-- gh-comment-id:2888837047 --> @xuatz commented on GitHub (May 18, 2025): This sounds interesting, I also have a vision of a feature something like this, so I'll give it a shot to implement something to satisfy this issue @alexkutsan
Author
Owner

@jakob1379 commented on GitHub (Aug 22, 2025):

This sounds interesting, I also have a vision of a feature something like this, so I'll give it a shot to implement something to satisfy this issue @alexkutsan

if we could just get the number of entries one could simple ask for a random id in the range

<!-- gh-comment-id:3214692420 --> @jakob1379 commented on GitHub (Aug 22, 2025): > This sounds interesting, I also have a vision of a feature something like this, so I'll give it a shot to implement something to satisfy this issue [@alexkutsan](https://github.com/alexkutsan) if we could just get the number of entries one could simple ask for a random id in the range
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/karakeep#278
No description provided.