no support
software bugs, third-party tools to modify projects, or minimal data corruption (metadata corruption due to network transfer, upload, or storage errors) could all «brick» a project file.

gdfsgdfsgdfg wrote:

gdfsgdfsgdfg wrote:

here are my solutions to “scratchers removing metadata”

make the filename different (so no-stealer would notice that instantly)
encrypt metadata (so it’s not easy to edit)
the project file won’t be opened without the metadata (to prevent issues with the offline editor, the metadata will only be added to shared projects)

of-course it gets detected by filter, so I have to edit-out the encryption methods

i’m surprised no one looked into this yet

here are my workarounds to “gdfsgdfsgdfg's solutions to ”scratchers removing metadata“”
×—the decryption key must exist in scratch's code, so—×
decompile the code from scratch's web editor (javascript is publically available)
reverse engineer the code (examine several projects to compare encrypted values/sb3 structure to find the algorithm)
brute force decryption (to keep projects loading quicky, encryption is simple)
intercept decrypted data (when scratch validates projects, monitor network traffic to view decrypted metadata, to then make fake metadata)
man-in-the-middle proxy (intercept the file to modify metadata before scratch servers process it)

Or a simple remix licensing type.

robloxnoob27 wrote:

here are my workarounds to “gdfsgdfsgdfg's solutions to ”scratchers removing metadata“”
×—the decryption key must exist in scratch's code, so—×
decompile the code from scratch's web editor (javascript is publically available)
reverse engineer the code (examine several projects to compare encrypted values/sb3 structure to find the algorithm)
brute force decryption (to keep projects loading quicky, encryption is simple)
intercept decrypted data (when scratch validates projects, monitor network traffic to view decrypted metadata, to then make fake metadata)
man-in-the-middle proxy (intercept the file to modify metadata before scratch servers process it)

naw thats wild
—
however
whos gonna do all of this for a simple remix

gdfsgdfsgdfg wrote:

robloxnoob27 wrote:

here are my workarounds to “gdfsgdfsgdfg's solutions to ”scratchers removing metadata“”
×—the decryption key must exist in scratch's code, so—×
decompile the code from scratch's web editor (javascript is publically available)
reverse engineer the code (examine several projects to compare encrypted values/sb3 structure to find the algorithm)
brute force decryption (to keep projects loading quicky, encryption is simple)
intercept decrypted data (when scratch validates projects, monitor network traffic to view decrypted metadata, to then make fake metadata)
man-in-the-middle proxy (intercept the file to modify metadata before scratch servers process it)

naw thats wild
—
however
whos gonna do all of this for a simple remix

Exactly! No simple thief is just going to go all this way for a few likes and follows. This system would at least stop not all, but some thieves, and any less stealing is good enough.

No support. This wholed remake the see the unshared projects part of turbowarp again.

CaptFrIEdshrimp wrote:

No support. This wholed remake the see the unshared projects part of turbowarp again.

And how?

CoolLock wrote:

CaptFrIEdshrimp wrote:

No support. This wholed remake the see the unshared projects part of turbowarp again.

And how?

project API?

CaptFrIEdshrimp wrote:

CoolLock wrote:

CaptFrIEdshrimp wrote:

No support. This wholed remake the see the unshared projects part of turbowarp again.

And how?

project API?

But this is to do with the .sb3 file
Don't worry, they already did the unshared projects thing again
And fixed it again
But not before I downloaded all the Map Scratch tests :P