Change remixable versions to private if only used by the owner
There are times when people go to publish, but get mixed up about what will be published and if it would be published remixable or not because of interdependencies, things like this... And they immediately realise that things have been uploaded as remixable that they didn't want to be remixable.
The only time the credit chain would be broken by undoing this would be if someone else besides the owner already used it in a creation in which it must be remixable--for example, importing an element into another element or scene. Or having a locally saved element/scene containing it, or as a remix of it.
In almost all situations where this arises, this isn't the case. No one has noticed it's even been published yet. And may not for months, or may not at all--depending on how buried it is in the genealogies and if it's unlisted, etc.
So the owner might be fine, and their work they don't want to be used/remixed might never be used in that way that they don't want it to be used. But they'll never feel safe about it--even if it's never used at all.
Allowing this would really help put a lot of people at ease with things they've published accidentally in this way. Please add it.
-
Yeah this is a must have it constantly happens to me lol
-
Forcing our creations to be public forever just stinks. I feel this, Tap.
I imagine changing this requires coordination with the legal team at Mm, since there is a hefty policy we consent to before publishing something. But I'm just speculating of course.
If nothing else, clarity about why this isn't possible would be nice -- as it is, publishing feels more like punishing, particularly if someone needs to change their mind. Why deny us that?
At the risk of hyperbole, it kind of feels like Dreams is stealing our work via a publishing system that arguably herds us into this public arena.
Let us change our minds and not feel as though we've given up our rights. If there are inevitable consequences (like public remnants even after unpublishing), I would find accepting that preferable to being SOL, as it were, and stuck with assets that we no longer entirely own.
My 2 cents
-
Someone else mentioned they view the "public is forever" notice as some sort of legal notice. But I think it's just a warning because that's how it currently works; I've never viewed it as something they legally have to do, or that it legally has to be designed this way. I feel like if it worked differently, the notice would say different things, myself.
Definitely agree on the parts already in use staying in-use. Far better that than stuck forever and never feeling safe to publish--and therefore develop in Dreams in the first place. I know of multiple posts about publishing issues over on Reddit where they have left Dreams entirely because it's far too stressful and nightmarish trying to cope with the way things work, worrying they've done it wrong, just waiting for everything to be ruined by a misclick...
-
Having publishing publicly as the default option when saving elements is not ideal. Makes it much easier to inadvertently make this mistake.
-
DrSecksy Interesting... what do you mean by it being "default"? When I use it, there are different options I can click on at will. But I use the gyro controls--maybe that's the difference?
Por favor, entrar para comentar.