The way memories are deleted should queue things for possible deletion rather than deleting them FIRST, then check at the end of processing if the items queued for deletion have actually been removed from the embeddings JSON and only delete them if they are no longer referenced. This way, if multiple things reference the same segment, it doesn't get wiped out prematurely.
Also, when it comes to allowing the system to generate and store its own memories, if a memory ends up containing identical information to a note that is removed, it doesn't get wiped just because the note was removed - a memory still references it. That's very unlikely, but possible. I just think the current system is too aggressive about deletion.
The way memories are deleted should queue things for possible deletion rather than deleting them FIRST, then check at the end of processing if the items queued for deletion have actually been removed from the embeddings JSON and only delete them if they are no longer referenced. This way, if multiple things reference the same segment, it doesn't get wiped out prematurely.
Also, when it comes to allowing the system to generate and store its own memories, if a memory ends up containing identical information to a note that is removed, it doesn't get wiped just because the note was removed - a memory still references it. That's very unlikely, but possible. I just think the current system is too aggressive about deletion.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The way memories are deleted should queue things for possible deletion rather than deleting them FIRST, then check at the end of processing if the items queued for deletion have actually been removed from the embeddings JSON and only delete them if they are no longer referenced. This way, if multiple things reference the same segment, it doesn't get wiped out prematurely.
Also, when it comes to allowing the system to generate and store its own memories, if a memory ends up containing identical information to a note that is removed, it doesn't get wiped just because the note was removed - a memory still references it. That's very unlikely, but possible. I just think the current system is too aggressive about deletion.
A problem with this approach is deleting memories made outside of source files. I need some way to tag these so they don't get deleted.