You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Uro, we're unable to modify existing uploaded assets or otherwise understand them.
Describe the proposed option and how it helps to overcome the problem or limitation
Able to see:
date originally uploaded
date updated.
store version info so old / incompatible assets can be identified
Disable incompatible assets based on date.
'Public' but 'unlisted'.
A concept of ownership separate from uploader to allow users to delegate usage rights of certain to certain specific users or (if we introduce it later) user groups.
Describe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams
Please help design.
Positive Consequences
We are able to clean up older artifacts.
Stop clients from loading incompatible assets.
Negative Consequences
Need a per object blob database entry.
An asset will will fail to load and they will appear as big glowing exclamation mark
Option graveyard
Do nothing.
If this enhancement will not be used often, can it be worked around with a few lines of script?
Not a few lines of script and needs to be on the backend.
Is there a reason why this should be core and done by us?
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
The text was updated successfully, but these errors were encountered:
Describe the status of the issue.
List the deciders of the issue.
V-Sekai,fire,saracen,lyuma
Describe the tags of the issue.
V-Sekai,content,uro
Context and Problem Statement
In Uro, we're unable to modify existing uploaded assets or otherwise understand them.
Describe the proposed option and how it helps to overcome the problem or limitation
Able to see:
Disable incompatible assets based on date.
'Public' but 'unlisted'.
A concept of ownership separate from uploader to allow users to delegate usage rights of certain to certain specific users or (if we introduce it later) user groups.
Describe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams
Please help design.
Positive Consequences
We are able to clean up older artifacts.
Stop clients from loading incompatible assets.
Negative Consequences
Need a per object blob database entry.
An asset will will fail to load and they will appear as big glowing exclamation mark
Option graveyard
Do nothing.
If this enhancement will not be used often, can it be worked around with a few lines of script?
Not a few lines of script and needs to be on the backend.
Is there a reason why this should be core and done by us?
Uro is ran by us.
References
License of the contribution
Copyright (c) 2022 V-Sekai contributors.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
The text was updated successfully, but these errors were encountered: