Opuscating code

[cookieclickerer33]

The second one
it’s a teamwork thing
I’m testing out a system where you need 4 different people to view a project and each person gets their own part of the code, then it’s all assembled into one code and that gets decoded

The code for doing that is done ( I even made a reimplementation the the “user id” block for this ) but making the code for separating the string into 4 parts is where I’m drawing a blank

[cookieclickerer33]

I need to split it by every X letter
But idk how to do that

[cookieclickerer33]

Exactly where tho, its a huge topic

[pajamaclaws21]

Jens talks about it:

@jens

The anti-social part ... is making it hard for others to follow your ideas [and] putting effort and creativity into excluding others, making them feel inferior and inept. Yes, recently we've put more effort into making Snap scenes and projects more customizable, and we've often talked about how this is giving me great headaches. But at least those settings are visible, explorable and malleable through the GUI, and no script can lock you out of that. Guaranteeing a reliable and predictable user experience for everybody from novice to expert, from kid to teachers is a foundation for democratizing computing education for all, not just for those who all too eagerly get excited over seemingly "advanced" concepts that more often than not turn out to be elitist mirages ("ringifying result values").

EDIT: Maybe it's not explicitly disallowed, but more looked down on -- a lot.

[cookieclickerer33]

Yes it’s too risky
I think I’ll just keep it as a remake of the user id block

[loucheman]

dont mess with this:

Accessing the SnapCloud In a Snap! project will get you permanently banned

Folks, please do not attempt to access the SnapCloud in your Snap projects. We've taken some measure to prevent that, and some of you seem to regard this as some kind of technical challenge or contest to set up your own proxy server or to otherwise obfuscate your queries. The reason we don't want you to do that is to protect this community so that Snap! is allowed to be used in schools. By keeping us busy with looking after your more or less inventive ways to break our rules you are causing me w…

[cookieclickerer33]

That has nothing to do with this, apart from having the word in it

[joecooldoo]

@pajamaclaws21

EDIT: Yeah, I think that isn't allowed.

+1

It isnt

[turtle-coder]

I seriously am clueless to whatever you all are saying. Can anyone explain this to me maybe?

[joecooldoo]

@cookieclickerer33 wants a way to hide something ("Opuscating" ^[sic]) in their code to make it harder for someone to read it. Unfortunately, I think this isn't allowed.

[turtle-coder]

So by doing something complicated, he's attempting to make it hard to remix.Right?

[joecooldoo]

That or making it hard to find a secret

[starbox614]

@pajamaclaws21

@cookieclickerer33

make the project self destruct if it’s edited

I don't think that's allowed, sadly.

I mean, I made a challange involving self-destructing projects, but all of them could be disarmed.

[joecooldoo]

That project was for a fun kind of thing. They want to make their code un-readable, which isn't allowed. It seems their going to do it anyway, so I wouldn't be surprised if they got a warning or got banned for doing this.

[starbox614]

huh. I've sometimes given blocks misleading labels to distract from secrets in games, but I guess that isn't really making the code unreadable.

[pajamaclaws21]

IIRC, it is allowed but like annoying/frowned upon to purposefully make your code unreadable-- while the bit that is not allowed is making your project unable to be remixed/edited through methods like a self-destructing project.

[starbox614]

any self destructing project can be disarmed using XML editing or JS code.

example

running this code in the console will disable the WHEN EDITED hat block:

StageMorph.prototype.fireUserEditEvent = ()=>{};

[pajamaclaws21]

I think that is beside the point, though.

[cookieclickerer33]

I literally said I’m not doing it