reallysoftuser wrote:

No support, the API is not the primary focus of the scratch team.

Ok then we should remove anything that is not the primary focus of the scratch team.
say bye bye to this forum then.

reallysoftuser wrote:

Also, this should be in Advanced Topics.

No, it shouldn't. It's a suggestion.

The problem with things like FluffyScratch is that they are complex, and use things like comments and cloud logs. An official system would be faster, simpler, and might put less stress on the servers.

bump

Bump.
(This'd be amazing for Ocular)

Mockups for the asking-permission page:




The user icon is from Material Symbols; the cloud and eye icons are emojis.

(note: the permissions in yellow don't have to be added, but I made a mockup for them in case they do. things like permissions for posting comments/projects probably wouldn't exist.)

There are a few issues:

- At least 99% of Scratchers would never come across a situation where they would need to use this feature and it doesn't really do anything for Scratch at this time. Why make a feature for < 1% of Scratchers that doesn't benefit Scratch? It makes sense for accounts for services from bigger companies like Google or Apple, but Scratch doesn't need to be a sign-in method. None of the sites that use Google or Apple to sign in would consider using Scratch to do the same.
- Often, websites that you sign into have communication features, which the Scratch Team usually disallow linking to unless they can verify that they're safe.

Scratcher-made solutions are fine, as long as they and everyone using them follow the Community Guidelines.

Support

MyScratchedAccount wrote:

(#46)
Support

Why do you support? And be constructive.

MyScratchedAccount wrote:

Support

How do you have 1000+ posts yet little experience when discussing features?

What (kind of) apps would use this?

wer65hertg wrote:

What (kind of) apps would use this?

Any apps which request personal information securely, like your unshared projects (not like your name and location lol)

ajskateboarder wrote:

Any apps which request personal information securely, like your unshared projects (not like your name and location lol)

What would they do with this?

wer65hertg wrote:

ajskateboarder wrote:

Any apps which request personal information securely, like your unshared projects (not like your name and location lol)

What would they do with this?

IDK, it could let users analyze information within the projects and generate insights/statistics?
Whatever cool ideas developers have

ajskateboarder wrote:

IDK, it could let users analyze information within the projects and generate insights/statistics?
Whatever cool ideas developers have

It is important to know exactly who and what will use this data and power. For one, the users and the Scratch Team need to understand that this isn't just a big security risk, and two, that developers need to know what powers and data they can get. If both points aren't met, then this feature won't be added.

wer65hertg wrote:

(#49)
What (kind of) apps would use this?

For one, any Scratch-related site that has Scratcher interaction (things like ocular reactions).

wer65hertg wrote:

ajskateboarder wrote:

IDK, it could let users analyze information within the projects and generate insights/statistics?
Whatever cool ideas developers have

For one, the users and the Scratch Team need to understand that this isn't just a big security risk

Absolutely. It would be so sad to see people think that OAuth, an open authentication protocol for secure access, has security issues

Bump! Why did I see a lot of new topics recently?

wer65hertg wrote:

ajskateboarder wrote:

IDK, it could let users analyze information within the projects and generate insights/statistics?
Whatever cool ideas developers have

It is important to know exactly who and what will use this data and power. For one, the users and the Scratch Team need to understand that this isn't just a big security risk, and two, that developers need to know what powers and data they can get. If both points aren't met, then this feature won't be added.

schools
Extracurricular stuff
idk

Bump
I just want to use the API directly, not through some weird wrapper

Bump.

Support. This would be really useful, as current solutions like ScratchAuth or the Wiki's OAuth are kinda complicated to set up.

This would be nice, so you can log on with Scratch on external services, and potentially log on to Scratch from external services safely! (In a way that the access can be revoked, that is.)

I have a couple suggestions for logging on to Scratch from external services:

1. There should be a timer before you grant access to your Scratch account, so little kids actually read the message first.
   
2. There should be a force rollback feature, so you can roll back any unwanted changes.