Should stale profiles be removed from the Content Servers? (GOV) This proposal is now in status: PASSED. Voting Results: * Yes 72% 7,655,925 VP (65 votes) * No 27% 2,911,165 VP (14 votes) * Abstain 1% 37,370 VP (2 votes)

@BET they can be loaded as long as you are connected to that catalyst and once a change is done to the profile it will be redeployed to the network with a new timestamp.

So to clarify.. Some will store, some won't.. Will they still be loaded?

Cool, thanks, I'm fine with it then.

@HPrivakos after some research, the stale profiles deletion can depend on whether you have the Garbage Collection on or off in your catalyst node, this will provide the flexibility that you are looking for and you may choose not to delete the stale profiles stored on your catalyst node.

Any thoughts on a secondary server stack? Separating load time logic and storage? @paralax @HPrivakos

[quote="paralax, post:3, topic:21750"] The goal isn’t to erase our history but to use the resources smartly. [/quote] How about syncing profiles on the fly when needed then? There are other "smart" way to make the catalyst more performant than to delete millions of profiles. I still REALLY hope there will be an environment variable to disable it, else I might be forced to fork the catalyst. I resynced my catalyst twice or thrice max in the nearly 4 years I've been running one, having to wait a day for it to sync is ok in my opinion. Bitcoin nodes take a while to sync and people are ok with it.

Hello @BET, thanks for your comment, The poll delves into both the end user's perspective and the technical impact of the initiative. The goal isn't to erase our history but to use the resources smartly.

I don't know why this is written completely from a technical perspective and doesn't really elaborate on the pros and cons for the end-users.. For me it's a terrible idea to delete our history to save a little bit of storage space.. How many times are you needing to reboot the servers anyway?