-
I wonder what the best recommendation for such situations is. Maybe Cloudron should keep one backup per month till a year and then one backup per year or so? Or should there be more help and information about how to additional copy backups from the main backup location to something more longterm even?
-
I will close this issue (marking as solved) as unfortunately we can't do anything anymore to get the data back. For any later reader, if this issue is also hit, please stash the app logs for further debugging, maybe the issue is still visible there.
-
The same thing has happened to me as well. My entire meemo contents is gone, my backups show nothing. When I restore the oldest backup I have, the meemo seems to have completely reset itself (ie. all the instructional posts are there, but nothing else).
How to I check logs, and stash them (if they contain anything)?
-
Just an update FYI that this happened to me also just now.
Not a disaster as I was testing the app out.
But all notes gone when logging in again.Polite suggestion that maybe the app needs to be marked as unstable pending resolution.
Just so that someone doesn't commit a lot of information with no backup / copies of content. -
-
@timconsidine said in Meemo purged my notes:
Polite suggestion that maybe the app needs to be marked as unstable pending resolution.
FWIW, I have notes in my meemo for last 8 years and use it every day.
-
@girish said in Meemo purged my notes:
FWIW, I have notes in my meemo for last 8 years and use it every day.
In spite of that, I think @timconsidine's suggestion is a good one:
@timconsidine said in Meemo purged my notes:
Polite suggestion that maybe the app needs to be marked as unstable pending resolution.
Because 1) multiple people have inexplicably lost all their notes, 2) reported bugs have not had any response at all in over a month https://github.com/cloudron-io/meemo/issues/120 (causing people to think it is a dead project, as just expressed there 2 days ago)
-
@jdaviescoates I am happy to accept merge requests for fixes there, its just a regular opensource project from that point of view. I am usually prioritizing Cloudron related tasks and for my personal usage, meemo works as such
-
@nebulon said in Meemo purged my notes:
@jdaviescoates I am happy to accept merge requests for fixes there, its just a regular opensource project from that point of view.
Sure.
@nebulon said in Meemo purged my notes:
I am usually prioritizing Cloudron related tasks and for my personal usage, meemo works as such
I'm personally glad that you are doing that!
But, if I were you, I'd try to at least respond to issues raised on https://github.com/cloudron-io/meemo/issues/ even if it's just to say you don't have time to respond properly (because you're prioritising Cloudron) but that you're happy to accept merge requests for fixes etc.
I'm going off topic now, but as someone who reports quite a few bugs etc on various open source projects, it is somewhat disconcerting when one doesn't even get any acknowledgement/ response from the devs (see e.g. this small but annoying issue I reported about Nextcloud Calendar over 10 months ago that seemingly no one involved at Nextcloud Calendar has bothered to look at at all https://github.com/nextcloud/calendar/issues/4893 )
-
@nebulon you could perhaps also just remove the public feed/ sharing features completely given they don't currently work? that way no one would notice they aren't working
Although of course that'd take you time too, and even better would be to find the time to make them work. Rock, hard place.
-
@jdaviescoates said in Meemo purged my notes:
@nebulon you could perhaps also just remove the public feed/ sharing features completely given they don't currently work?
I would support that approach !
For me, public access is not desired and slightly contradictory to concept of private notes.
Like sharing a Joplin or Standard Notes entry.
Why would I want to ?It’s blurring the lines of private and team resource, and it goes into the slippery slope of managing more security.
Just make it private.I only found the public feature was failing because I was testing. I didn’t actually want it.
