Upon the next release, smart watch support will be removed. It may still work, but accessibility features for watches will be gone.

The new UX/UI of MyScratchPage (coming in v0.4) includes increased usability on mobile.

If a user doesn't have an aviate status use the ocular status.
If a user doesn't have an ocular status use the aviate status.
If a user has both, use Aviate?

god286 wrote:

If a user doesn't have an aviate status use the ocular status.
If a user doesn't have an ocular status use the aviate status.
If a user has both, use Aviate?

All the statuses are implemented.

MagicCrayon9342 wrote:

god286 wrote:

If a user doesn't have an aviate status use the ocular status.
If a user doesn't have an ocular status use the aviate status.
If a user has both, use Aviate?

All the statuses are implemented.

Looks like Aviate is really tiny in comparison to the huge ocular status. Maybe we should wait for the conversation for a single standard to finish.

v0.4 has now been released!

When fixing merge errors, it very much broke the new MyScratchPage source. I might redo it soon.

Due to issues, MyScratchPage will be reverted to v0.3.1
Just temporarily as I remake MyScratchPage in vue or svelte.

Vue is amazing! I'm using it now!

New! and Improved! UI coming soon!

Wanna know what else is coming soon?
today's sponsor
Logins! Custom pages and statuses! APIs! everything!!

Pro-tip: Use border-radius.

Rounded corners should be used to reduce the contrast between two boxes.
But it’s just my opinion, personally I always use border-radius when I make websites. I like my content to be organized.

It’s sad that I can't access to .io websites, but I download a zip of this repo sometimes to look at it.

happex wrote:

Pro-tip: Use border-radius.

Rounded corners should be used to reduce the contrast between two boxes.
But it’s just my opinion, personally I always use border-radius when I make websites. I like my content to be organized.

It’s sad that I can't access to .io websites, but I download a zip of this repo sometimes to look at it.

The URL is https://jdev.eu.org/MyScratchPage
also, this does not use vanilla CSS it uses tailwind. It's a classed based CSS framework

New UI and….
errors in fetching user data are now handled better

users will also be notified, upon first use of the site since the update. That some users, on their ocular profile, choose to instead of displaying their ocular status through the api, have their aviate status shown instead.

Why does it say “Not seeing the right status..? Maybe the user decided to have their Aviate status shown through the ocular API.” Aviate has no Ocular integration yet, and might never be implemented.

NFlex23 wrote:

Why does it say “Not seeing the right status..? Maybe the user decided to have their Aviate status shown through the ocular API.” Aviate has no Ocular integration yet, and might never be implemented.

your ocular status and aviate statuses appeared same so I made a mistake.

MagicCrayon9342 wrote:

(#116)
At the moment, MyScratchPage is purely a mirror of other Scratch services displayed in a singular website. But once the hefty Scratch Auth integration is handled, there can be more than just information from other sites. When authentication is up and running, users will be able to create their own MyScratchPage page with seperate information. Of course, I kinda need a server which I don't have, might make an api endpoint I have no idea. However authentication is priority at the moment.

First you'll need a database to store sessions and user data. I recommend Supabase since it has a generous free tier and is really easy to use. Second, you will need an authentication system. Scratch Auth is currently the best choice since it's easy to use and has one-click sign in. Once you authenticate a user, store a UUID key with their username as the value in a session on Supabase, and store that UUID in the browser cookies so that the user doesn't have to log in every single time they come to your site. Thirdly, make a system for verifying the user's session ID (UUID) cookie before going to a protected page, like their dashboard, to make sure the user is logged in. You can view Aviate's source code if you're having trouble with any of the steps.

NFlex23 wrote:

MagicCrayon9342 wrote:

(#116)
At the moment, MyScratchPage is purely a mirror of other Scratch services displayed in a singular website. But once the hefty Scratch Auth integration is handled, there can be more than just information from other sites. When authentication is up and running, users will be able to create their own MyScratchPage page with seperate information. Of course, I kinda need a server which I don't have, might make an api endpoint I have no idea. However authentication is priority at the moment.

First you'll need a database to store sessions and user data. I recommend Supabase since it has a generous free tier and is really easy to use. Second, you will need an authentication system. Scratch Auth is currently the best choice since it's easy to use and has one-click sign in. Once you authenticate a user, store a UUID key with their username as the value in a session on Supabase, and store that UUID in the browser cookies so that the user doesn't have to log in every single time they come to your site. Thirdly, make a system for verifying the user's session ID (UUID) cookie before going to a protected page, like their dashboard, to make sure the user is logged in. You can view Aviate's source code if you're having trouble with any of the steps.

I'm probably going to have trouble with all those steps as right now I didn't understand a thing you just said

By default, MyScratchPage will favor Aviate over an Ocular status. However, if an Aviate status is not detected it will fall back to an Ocular status.

MagicCrayon9342 wrote:

I'm probably going to have trouble with all those steps as right now I didn't understand a thing you just said

Here's the recipe!

Ingredients:
Database (recommended type Supabase)
Auth system (recommended type Scratch Auth, easy to add)

Instructions:

1. Add the Database into your Application. You can use supabase-js for Supabase. Ensure that you are using environment variables for this - you can use the dotenv package to load .env file into process.env
2. Learn how to use the Auth system, this is in the Scratch Auth documentation, and implement it so that you can go to Scratch Auth and authenticate the user.
3.

NFlex23 wrote:

Once you authenticate a user, store a [random] UUID key with their username as the value in a session on Supabase, and store that UUID in the browser cookies so that the user doesn't have to log in every single time they come to your site. Thirdly, make a system for verifying the user's session ID (UUID) cookie before going to a protected page, like their dashboard, to make sure the user is logged in. You can view Aviate's source code if you're having trouble with any of the steps.

You can read the Aviate source code to see how to do this. Or if you want to use JWTs (probably more confusing than Aviate's way) there is webdev03/scratchinfo on github but it uses a custom auth system.