my opinion is that if you’re going to have a feature request, you need to make it specific. i don’t think you can have a very productive conversation on a request that is not well-defined or is shifting.
for example, i could make a feature request that would be something to the effect of “make the observation page faster”, but without a specific idea or set of ideas about how to do it, i’m not sure how that kind of request would lead to much action.
now if you want to brainstorm ideas for reducing space, then i’m not opposed to that, but i think that should be done as a general discussion first rather than immediately as a feature request.
i think this is technically a very different proposal than “reducing space”. if i’m interpreting what you’re saying here correctly, this would effectively change up the entire identification data model to include a history within any given identification. i suppose that’s doable, but it seems like that kind of thing would be super super complex, with lots of tentacles reaching out to many parts of the way the system works.