BGMead wrote:

No passwords, it’s against the CGs. Here’s how it’ll work:

• User goes to site login page
  
• Enter their Scratch username
  
• If they’re in the DB, they’re asked to enter their AutoUOC password.
  
• If not in the DB, they’re asked to respond to the comment with the code.
  
• After they respond, they are asked to enter a password that they don’t use for Scratch.
  

We can also use comment verification for password reset if needed.

Pufferfish_Test wrote:

Oh right, I understand now. It all makes sense! Thanks.
Also, should I make the mongodb database (I have an account) or do you want to? I'll make one anyway for testing purposes, but… actually, it doesn't matter. We can just change the connection url if we need to.
Also, what's actually going in the db? So, obviously, usernames and passwords, but it would be nice if we could have a list of what info we need for the shops and UOCs.
Right, I'll go off and start working on that.

• Username
  
• Password
  
• Scratch ID
  
• Date Registered (to AutoUOC)
  
• An array of thread IDs which (a) they own and (b) AutoUOC operates in.
  
• An array of thread IDs which (a) they co-own* and (b) AutoUOC operates in.
  

• Thread ID
  
• Owner Username
  
• Array of co-owners usernames*
  
• UOC post ID
  
• Shop name
  
• Terms/conditions codeword ('' for none)
  

• Post ID
  
• Shop name
  
• Array of objects representing what and where different elements are located (unclaimed orders, claimed orders, overview, etc)
  
• Array of unclaimed orders
  
• Array of claimed orders
  
• Array of completed orders
  

-PizzaKing- wrote:

BGMead wrote:

No passwords, it’s against the CGs. Here’s how it’ll work:

• User goes to site login page
  
• Enter their Scratch username
  
• If they’re in the DB, they’re asked to enter their AutoUOC password.
  
• If not in the DB, they’re asked to respond to the comment with the code.
  
• After they respond, they are asked to enter a password that they don’t use for Scratch.
  

We can also use comment verification for password reset if needed.

Sounds VERY confusing……..

Sorry, you have to wait 60 seconds between posts.

BGMead wrote:

Pufferfish_Test wrote:

Oh right, I understand now. It all makes sense! Thanks.
Also, should I make the mongodb database (I have an account) or do you want to? I'll make one anyway for testing purposes, but… actually, it doesn't matter. We can just change the connection url if we need to.
Also, what's actually going in the db? So, obviously, usernames and passwords, but it would be nice if we could have a list of what info we need for the shops and UOCs.
Right, I'll go off and start working on that.

Here's a list:

Accounts

• Username
  
• Password
  
• Scratch ID
  
• Date Registered (to AutoUOC)
  
• An array of thread IDs which (a) they own and (b) AutoUOC operates in.
  
• An array of thread IDs which (a) they co-own* and (b) AutoUOC operates in.
  

Shops

• Thread ID
  
• Owner Username
  
• Array of co-owners usernames*
  
• UOC post ID
  
• Shop name
  
• Terms/conditions codeword ('' for none)
  

UOCs

• Post ID
  
• Shop name
  
• Array of objects representing what and where different elements are located (unclaimed orders, claimed orders, overview, etc)
  
• Array of unclaimed orders
  
• Array of claimed orders
  
• Array of completed orders
  

*Co-Owners are scratchers that can be added by the owner to a shop. They have permission to edit the UOC.

Pufferfish_Test wrote:

Ok, thanks!
Edit: By the way, this is going to use cookies so they don'g log out every time the page refreshes. They'll also be used to detemine whether someone's in the process of signing up or not. They'll just be session cookies, so I won't make a pop-up, but if you feel we should have one, I can.

BGMead wrote:

Hey! Imma be gone for three-ish days on a trip. During that time I won't be able to develop the bot too much. I'll be checking up on GitHub though to make sure everything is still okay.

Pufferfish & Nammy should have write access to all the repos, so you can make changes without my approval. If not, let me know and I'll update it.

See ya soon!

• posts that are orders
  
• posts that are staff taking orders
  
• posts that are staff completing orders
  

BGMead wrote:

BGMead wrote:

Hey! Imma be gone for three-ish days on a trip. During that time I won't be able to develop the bot too much. I'll be checking up on GitHub though to make sure everything is still okay.

Pufferfish & Nammy should have write access to all the repos, so you can make changes without my approval. If not, let me know and I'll update it.

See ya soon!

Also, it would be cool if someone could try to get as many posts as we can in the following topics:

• posts that are orders
  
• posts that are staff taking orders
  
• posts that are staff completing orders
  

I want to mess around with using AI to detect order status, but we need a dataset. All we need is the post IDs. If anyone could help, let me know!

GrahamSH wrote:

BGMead wrote:

BGMead wrote:

Hey! Imma be gone for three-ish days on a trip. During that time I won't be able to develop the bot too much. I'll be checking up on GitHub though to make sure everything is still okay.

Pufferfish & Nammy should have write access to all the repos, so you can make changes without my approval. If not, let me know and I'll update it.

See ya soon!

Also, it would be cool if someone could try to get as many posts as we can in the following topics:

• posts that are orders
  
• posts that are staff taking orders
  
• posts that are staff completing orders
  

I want to mess around with using AI to detect order status, but we need a dataset. All we need is the post IDs. If anyone could help, let me know!

I could do that. Can they be prexisting ones?

BGMead wrote:

GrahamSH wrote:

BGMead wrote:

BGMead wrote:

Hey! Imma be gone for three-ish days on a trip. During that time I won't be able to develop the bot too much. I'll be checking up on GitHub though to make sure everything is still okay.

Pufferfish & Nammy should have write access to all the repos, so you can make changes without my approval. If not, let me know and I'll update it.

See ya soon!

Also, it would be cool if someone could try to get as many posts as we can in the following topics:

• posts that are orders
  
• posts that are staff taking orders
  
• posts that are staff completing orders
  

I want to mess around with using AI to detect order status, but we need a dataset. All we need is the post IDs. If anyone could help, let me know!

I could do that. Can they be prexisting ones?

Yeah, that's perfectly fine! We'll need as many as you can grab. Putting the IDs in a text document or pastebin should work for now.

EDIT: Just make sure it's sorted as noted by the categories above

GrahamSH wrote:

Got it! I'll start tomorrow.

ajsya wrote:

I'll grab some orders from The Frost Shop in the morning.

Executec wrote:

blankslate.io is great for text sharing

BGMead wrote:

Hello! I'm a member of the AutoUOC project and I've decided to stop by to ask for your assistance!

We were wondering if you could assist us in development by providing us with some of your orders (completed, taken, and uncompleted) as we need them to help train our AI used to power AutoUOC. We're giving all shops who participate access to AutoUOC Beta when it releases!

Confused? AutoUOC is a Scratch bot that can automatically update an unclaimed orders center (UOC for short). While still in development, we plan to release it soon to the shops here on Scratch!

You can learn more about what we need and how to contribute at this post. Thanks for your help!

- BGMead, Lead developer of AutoUOC

when green flag clicked
set [It actually kinda is v] to [advertising]