Field notes
A saved link is not an archive
A bookmark, an embed and a saved file solve different problems. Know which one you have before you rely on it.
You save a useful video. A month later, you need one detail from it. The title is still in your library, but the original post has disappeared. Did saving fail?
It depends on what you saved. A link remembers an address. An embed asks the source to play something. An archived file keeps a separate copy. Treating these as interchangeable makes a library harder to trust.
Three things worth telling apart
A bookmark gives you a way back to the source. It is useful even when a service cannot retrieve the page or download its media. It does not promise that the source will stay available.
An embed lets you watch a source's player inside another page. Playback can depend on the source's availability, account requirements or embedding rules. Seeing a working player does not prove that a separate video file exists.
An archived file is a copy stored outside the original post. It can protect a useful reference from some source changes. It still depends on the storage account, permissions and file being available. No one storage option removes every dependency.
Match the effort to the reference
Not every interesting link needs an archive. Keep the original URL when you mainly want to revisit a topic. For a reference that a project depends on, check whether you have the content you will actually need later.
In Kepero, saving the link and downloading available public media are separate actions. Source restrictions or an unsupported format can prevent a download while leaving the saved link intact. A retrieval error describes what Kepero could obtain; it does not by itself prove that a post is private.
Before relying on an archived video, open the saved copy, play it and try a seek. A thumbnail or title is not a playback check. For an album, check the individual files rather than assuming that the first frame represents the whole set.
Keep the reason, as well as the source
An archive preserves bytes. Your context preserves why they mattered. A short personal note can record the question a source answers, a point you disagree with or the part you want to use in your own work.
That note does not need to repeat the source. Try a sentence such as: “Useful counterexample for the opening of the presentation.” It gives you something to search for when you remember the project but not the original title.
Decide what another person needs
When you share your work, the reader may need a link, a quoted observation or an explicitly included media file. Choose that deliberately. Sharing a public view should not require sharing your whole research trail.
Kepero's personal notes and transcripts stay out of public material and collection views. A Post has its own published snapshot, so review the text and media you choose to include. The sharing guide explains those boundaries.
The useful question is not simply “Is it saved?” It is “What can I return to, and what does that still depend on?” For the practical steps, start with saving and organizing a library.