Maximouse wrote:

the2000 wrote:

You can also edit a Scratch project to contain inappropriate content and/or change it to be appropriate whenever you want. You can also use cloud variables to put dynamic, potentially inappropriate messages in your project. The solution is still reporting.

If this gets added you won't even be able to control if content in your own projects is appropriate for Scratch.

the2000 wrote:

Or you could just not link to sites with inappropriate content ._.

Maximouse wrote:

the2000 wrote:

Or you could just not link to sites with inappropriate content ._.

If users can post content on the site (which is almost always the case if it has an API) it can always be inappropriate.

celleron56 wrote:

Maximouse wrote:

the2000 wrote:

Or you could just not link to sites with inappropriate content ._.

If users can post content on the site (which is almost always the case if it has an API) it can always be inappropriate.

^ thats true if you want to have no inapropiate contend just dont let the user post theyr projects there always will be the risk of contend being inapropriate even without api's maibe the project could include a little sign saying that it uses api's but i would highl doubt that there will be many apis with inapropriate contend because reason 1. if this even gets addet and i know scratch scratch would just blacklist inapropriate apis and let users report the apis or whitelist apropiate apis and let users suggest new apis i see no reason for scratches WHOLE api to be blacklisted rather certain funktions from it like the loves and like count but others like message count would only display the message count of the scratcher thats viewing the project also any external server could just update cloud variables to match the loves count so if the loves and like count is blacklisted could just be a setting for induvidual scratchers plz correct me if i am wrong

Yeetoburro1 wrote:

IMO inappropriate content is not really a reason to reject a suggestion, because you can have inappropriate content with uploading images and uh, they still have that

ShyGamer16 wrote:

I like this idea. I think it would help to make web browsers for OS projects…but what exactly would this look like? What blocks would be included?

ShyGamer16

Happy_Face5678 wrote:

I also have ideas for what blocks to use:

I'd like an HTTP extension:

(GET data from [example.com/path/to/api]) // sends a GET request and reports data
POST () to [example.com/path/to/api] // sends a POST request
PUT () to [example.com/path/to/api] // sends a PUT request

Most API docs will say what HTTP request to send, to where, and what you'll receive.

I'd also like websockets:

set up socket with [12.34.56.78] on port [1234] // opens a socket
send [Hello] on socket // sends socket data

when socket data recieved //this should be an event
say (socket data) // say what has been received

close socket // closes the socket

This will make it easier to communicate with other stuff from scratch.

Both HTTP and WebSocket can be done easily in JS, so the ST won't need infrastructure on their side to make this.

ScolderCreations wrote:

Bumpity bump bump