Discuss Scratch

littlebene
Scratcher
52 posts

A better policy about extensions

PackersRuleGoPack wrote:

Lol that doesn't work.
Well from a legal standpoint it does….
290Scratcher
Scratcher
1000+ posts

A better policy about extensions

I agree.

If you're going to block an extension that you shouldn't block, why block it?
JGames101
Scratcher
100+ posts

A better policy about extensions

I agree completely with this.
I think all of these regulations are sane, and make much more sense than the current one.
littlebene
Scratcher
52 posts

A better policy about extensions

PackersRuleGoPack wrote:

I am currently making one, although I won't be able to mention it on Scratch so, it's pretty much useless.
One question: Is Email or YouTube allowed to be posted on Scratch? If so we can use those methods to opt particular users into a program: Maybe something like Forumotion.com
Econinja
Scratcher
1000+ posts

A better policy about extensions

GDcool500 wrote:

hi
i r8 8/8 /s
st remove this post pl0x
===

littlebene wrote:

One question: Is Email or YouTube allowed to be posted on Scratch? If so we can use those methods to opt particular users into a program: Maybe something like Forumotion.com
Email is banned.
YouTube is a grey-ish area. If it's like a link to a video it'll be fine. If it's a link to your channel with personal identifying information, nope.
===
Is it me, or is the ST attempting to remove the ATers by banning userscripts (which were once the core of AT)?
littlebene
Scratcher
52 posts

A better policy about extensions

Econinja wrote:

i r8 8/8 /s
+1
DeleteThisAcount
Scratcher
1000+ posts

A better policy about extensions

100 % agree

how I read the message I got
TrueFBK
Scratcher
71 posts

A better policy about extensions

Agreed.
pinkieofthepies
Scratcher
500+ posts

A better policy about extensions

I have to agree, I wake up this morning and see the alert I got for having an certain extension that tells people of an online status *cough cough* linked in my about me. All I could really say was “well, darn.”
JGames101
Scratcher
100+ posts

A better policy about extensions

pinkieofthepies wrote:

I have to agree, I wake up this morning and see the alert I got for having an certain extension that tells people of an online status *cough cough* linked in my about me. All I could really say was “well, darn.”
I got an alert for my posts about an extension I made. It's sad, because it was such a natural way to branch out from Scratch into HTML/JS and Extensions and stuff. I was going to make a second extension, and that one would have had even more learning about extensions with passing messages from background/popup scripts to the content scripts, and I'll learn that other ways, but it was the best way to do it, to naturally branch out from scratch to extensions.
AmazingMech2418
Scratcher
1000+ posts

A better policy about extensions

JGames101 wrote:

pinkieofthepies wrote:

I have to agree, I wake up this morning and see the alert I got for having an certain extension that tells people of an online status *cough cough* linked in my about me. All I could really say was “well, darn.”
I got an alert for my posts about an extension I made. It's sad, because it was such a natural way to branch out from Scratch into HTML/JS and Extensions and stuff. I was going to make a second extension, and that one would have had even more learning about extensions with passing messages from background/popup scripts to the content scripts, and I'll learn that other ways, but it was the best way to do it, to naturally branch out from scratch to extensions.
You can use Scratch extensions still! You also just can't advertise extensions. I also have a question. Are bookmark-based codes allowed? I made one intended for Scratch that brings back the discuss button. Just wondering if it's allowed. So far, it adds the discuss button and makes a JS console for computers that have the console blocked and soon, it will have many Scratch extensions and custom features.
catnap_403
Scratcher
8 posts

A better policy about extensions

I agree with WL!
WolfCat67
Scratcher
1000+ posts

A better policy about extensions

I agree. The policy needs to be revised; if extensions being advertised on the site to improve Scratch made by Scratchers are considered too dangerous by the Scratch Team, then they could simply blacklist the extension name itself. If an extension deemed to be safe (such as the all-too popular [oh wait I can't say its name anymore]) by the Scratch Team, then it should be allowed. Simply not allowing ANY extensions to be advertised is completely overkill. If the code is open-source and is safe, there's no reason to block it.
Slugasaurus
Scratcher
34 posts

A better policy about extensions

Support! How ’bout, like the list of approved websites, approved Scratch extensions? It takes a lot of work to create a shortcut like iO’s, and makes extensions for Scratch harder to find. They can still have a ban, just not a 100% ban.
–––––––––––––––––––––––––––––
P.S. Are we still allowed to say “You should get ScratchMoji!” or something like that? It’s not even linking to it. Scratch is not the ST’s to do whatever they want with it –– it’s everyone’s website. We should get a say, too. We can all have a say!

What’s gonna happen to the Scratch Extensions forum?!

Last edited by Slugasaurus (Dec. 7, 2017 20:19:46)

jromagnoli
Scratcher
1000+ posts

A better policy about extensions

AmazingMech2418 wrote:

JGames101 wrote:

pinkieofthepies wrote:

I have to agree, I wake up this morning and see the alert I got for having an certain extension that tells people of an online status *cough cough* linked in my about me. All I could really say was “well, darn.”
I got an alert for my posts about an extension I made. It's sad, because it was such a natural way to branch out from Scratch into HTML/JS and Extensions and stuff. I was going to make a second extension, and that one would have had even more learning about extensions with passing messages from background/popup scripts to the content scripts, and I'll learn that other ways, but it was the best way to do it, to naturally branch out from scratch to extensions.
You can use Scratch extensions still! You also just can't advertise extensions. I also have a question. Are bookmark-based codes allowed? I made one intended for Scratch that brings back the discuss button. Just wondering if it's allowed. So far, it adds the discuss button and makes a JS console for computers that have the console blocked and soon, it will have many Scratch extensions and custom features.
Yes, but because you can't tell anyone, no-one can get it.
kenny2scratch
Scratcher
500+ posts

A better policy about extensions

World_Languages wrote:

This makes me wonder why there is a forum topic dedicated to tell people which websites are okay or not for Scratch. There are way less extensions people would like to mention than websites.
Is that topic even managed anymore…?

My opinion:
Partial Support. Though this is the first topic I've seen that proposes a good change, it has its pros and cons.

Pros:
  • Makes very clear what extensions can or cannot be advertised.
  • The process is easy enough for most people to understand.
Cons:
The first one here is the most important:
  • This is very difficult to moderate. The Scratch Team would have to deal with even more reports - no matter if the reports were frivolous, or falsified, or simply misguided, or even valid.
  • Besides that, moderating extensions with a backend is extremely unreliable - the backend could change with no one the wiser. The only way to solve that is to have an ST member with access to the extension's backend, but that requires even more moderator work.

So because of this, I only partially support this proposal.
iforgotmyrandomname
Scratcher
47 posts

A better policy about extensions

I agree for the reasons in the original post.
AmazingMech2418
Scratcher
1000+ posts

A better policy about extensions

jromagnoli wrote:

AmazingMech2418 wrote:

JGames101 wrote:

pinkieofthepies wrote:

I have to agree, I wake up this morning and see the alert I got for having an certain extension that tells people of an online status *cough cough* linked in my about me. All I could really say was “well, darn.”
I got an alert for my posts about an extension I made. It's sad, because it was such a natural way to branch out from Scratch into HTML/JS and Extensions and stuff. I was going to make a second extension, and that one would have had even more learning about extensions with passing messages from background/popup scripts to the content scripts, and I'll learn that other ways, but it was the best way to do it, to naturally branch out from scratch to extensions.
You can use Scratch extensions still! You also just can't advertise extensions. I also have a question. Are bookmark-based codes allowed? I made one intended for Scratch that brings back the discuss button. Just wondering if it's allowed. So far, it adds the discuss button and makes a JS console for computers that have the console blocked and soon, it will have many Scratch extensions and custom features.
Yes, but because you can't tell anyone, no-one can get it.
So I can't advertise it? I really wanted to allow scratchers to program on mobile devices…
asivi
Scratcher
1000+ posts

A better policy about extensions

World_Languages wrote:



A proposition

  • Nothing with autoupdate would be allowed, at least at first. Userscripts can easily be set to not autoupdate, and are much easier to moderate.
  • Userscripts that are being advertised that collect information need to fill out a form that explains how it works and what information it collects, and send this to the ST. The creator of the userscript also must mandate that users read this before it collects any information (preferably in layman's terms), as well as sending this to the ST.
  • Userscripts without a backend can be advertised freely, as long as they are open source, and the information above is sent to the ST in some way. If they are visibly malicious, Scratchers can report them, and all you need to do is alert them and ban said or extension in it’s noncompliant state. Scripts cannot be invisibly malicious because of the lack of outward requests.
  • Userscripts with a backend or any requests to other sources require acceptance by the ST or an appointed trusted user in order to be advertised, and a reason must be stated in a form for each data point collected. Obviously, not following this can warrant whatever you want (although I don’t think having your head in the sand is punishable here).
  • Userscripts can’t require permissions that they don’t use or aren’t actually necessary in the current release. This is so that the user also knows why they’re granting something when they do it.

That's it. What do you think?

I suppor that what you propose.
littlebene
Scratcher
52 posts

A better policy about extensions

Ooh, Just got an idea: If you would like to spread the word about extensions you could use one that was already made to do so! All that would be needed was an update….

Powered by DjangoBB