view the rest of the comments
Pop!_OS (Linux)
Pop!_OS is an operating system developed by System76 for STEM and creative professionals who use their computer as a tool to discover and create. Unleash your potential on secure, reliable open source software. Based on your exceptional curiosity, we sense you have a lot of it.
Whether this is your first experience with Linux, or your latest adventure, all are welcome to discuss and ask questions about Pop!_OS and COSMIC. Keep the discussions friendly though, and remember to assume good intentions whenever you reply. We're all here because we have a shared love for Linux and open source software.
Support us by buying System76 hardware for you or your company! Or by donating on the Pop!_OS website through the "Support Pop" button. Pop!_OS and COSMIC are fully funded by System76 hardware sales. All systems are assembled in the USA. With your support, we'll work to push the Linux desktop forward with COSMIC.
Links
Guides
Hardware
Recommended
- !system76@lemmy.world
- !linux@lemmy.ml
- !opensource@lemmy.ml
- !linux@programming.dev
- !linux_gaming@lemmy.world
- !linux_gaming@lemmy.ml
- !selfhosted@lemmy.world
- !rust@programming.dev
- programming.dev
- fosstodon.org (Mastodon)
- !redox@lemmy.world
Community Rules
Follow the Code of Conduct
All posts on pop_os must adhere to the Pop!_OS community Code of Conduct. https://github.com/pop-os/code-of-conduct
Be helpful
Posts to pop_os must be helpful. When responding to a user asking for help, do not provide tongue-in-cheek responses like "RTM" or links to LMGTFY. Linking to direct sources that answer the asker's question is fine, but it's advised to provide some explanation as to how you got to that source.
Critique should be constructive
We within the Pop!_OS community welcome helpful criticism or ideas on ways to improve. However, basic "It's bad" or other simple negative comments don't help anyone fix anything. When voicing a complaint about something, try to point out ways the complaint could be improved or worked around, so that we can make a better product for it.
This rule applies to both Pop!_OS and its projects as well as other products available from third-parties.
Don't post malicious "advice"
It can be funny to joke about malicious commands, however this is not the venue for it. Do not advise users to run commands which will lock up their systems, steal their data, or erase their drive. Examples of this include (but are not limited to) fork bombs, rm, etc.
Posts violating this rule will be removed, even if the post is clearly in jest. Repeated offences may lead to a ban. You may understand that the command isn't serious, but a new user might not.
No personal attacks
Posts making a personal attack on any user will not be tolerated.
No hate speech
Hate speech of any kind will not be tolerated. Any violations will be removed, and are grounds for a ban.
If that comment is true and you don't have the database anymore then there's no hope.
If you were writing comments to understand which file is which then consider a directory scheme for sorting your files and add readme.md files in a narrow category of files to describe them. I do something like: All coding projects go into home/code, each project has a readme. Etc.
If you were just logging for history purposes ie good memories in photos I'd suggest just making a markdown gallery. Or something similar.
Yes, I was mainly using it for photos and videos. I wrote a lot of text in old photos from when I was a very young child or baby in order to record as many memories I still have in relation to them as possible, so these comments mean a lot.
Unfortunately I'm afraid they're lost (I think). UPD: see kolorafa's comment
There's some alternatives if you're willing to continue with that:
Aves Gallery on android (is on fdroid) can embed comments into image long term metadata. But I have not tested it after transfer.
Creating a directory Gallery with markdown files and a subdir for all images and then writing comments inside those markdown files with a link to the local image. Very simple to do with Obsidian or similar markdown-powered software.
Out of the top of my head I can think of two structures for that:
/Year/month/day/ dirs, hoursminutesecond.png and hourminutesecond.txt with the comment per photo.
/Gallery/images/datetime.png and /Gallery/yearmonth_gallery.md with comments and links to multiple images for that month.
And probably more that I'm not aware of myself.
Only lost if the files got moved to another filesystem as it turned out they are actually stored inside file metadata.
Great, then they might be recoverable.