Major Comment Latency Delay

Hello!

I created ScratchCat-AI but I am facing issues with latency between when a user posts a comment and when the bot responds. Usually it is 2 minutes, which is fine, but other times it can take 15+ minutes.

Is this Scratchattach's issue? My Code? Scratch? The User?

Thanks!

It's probably Scratch. Comments are kinda glitchy, and like to disappear on you.

Also, not sure if you're allowed to integrate AI into Scratch or perform social actions like commenting via a bot - just don't quote me on that

Understood. I will do some ToS and other various document scanning to see what I come up with.

…

On Sun, Apr 20, 2025, 22:36 minniesBaa ***@***.***> wrote: It's probably Scratch. Comments are kinda glitchy, and like to disappear on you. Also, not sure if you're allowed to integrate AI into Scratch or perform social actions like commenting via a bot - just don't quote me on that — Reply to this email directly, view it on GitHub <#386 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A43POXVN2CBX3PALAWCOGCT22RKS7AVCNFSM6AAAAAB3QGKM6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJXGUYTCOJQHA> . You are receiving this because you authored the thread.Message ID: ***@***.***> *minniesBaa* left a comment (TimMcCool/scratchattach#386) <#386 (comment)> It's probably Scratch. Comments are kinda glitchy, and like to disappear on you. Also, not sure if you're allowed to integrate AI into Scratch or perform social actions like commenting via a bot - just don't quote me on that — Reply to this email directly, view it on GitHub <#386 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A43POXVN2CBX3PALAWCOGCT22RKS7AVCNFSM6AAAAAB3QGKM6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJXGUYTCOJQHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

Scratch doesn't allow bot commenting, read scratch.mit.edu/robots.txt

Darn okay. I will figure something out.

…

On Tue, Apr 22, 2025, 03:37 kRxZykRxZy ***@***.***> wrote: Scratch doesn't allow bot commenting, read scratch.mit.edu/robots.txt — Reply to this email directly, view it on GitHub <#386 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A43POXWYNSZTQF5UVPJ36IL22XWR3AVCNFSM6AAAAAB3QGKM6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMRQGQYTSNZVGE> . You are receiving this because you authored the thread.Message ID: ***@***.***> *kRxZykRxZy* left a comment (TimMcCool/scratchattach#386) <#386 (comment)> Scratch doesn't allow bot commenting, read scratch.mit.edu/robots.txt — Reply to this email directly, view it on GitHub <#386 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A43POXWYNSZTQF5UVPJ36IL22XWR3AVCNFSM6AAAAAB3QGKM6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMRQGQYTSNZVGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

Reading that, I am slightly confused. Also, doesn't that mean that Scratchattach is not allowed?

Scratchattach's primary goal is scratch API interactions in general, not specifically comment bots.

@Fluffyscratch

Well, you can use the social actions features in many ways that isn't "bot commenting" - for example, if you had a script that you would run manually, and wasn't in a loop, that would probably be ok.

edit: @Fluffyscratch beat me to it

So looking at robots.txt I don't see anything disallowing. I also am not good with robots.txt files.

robots.txt files are for search engine crawlers, like Googlebot, to know where to avoid crawling. I don't see how it could be important to bot commenting.

@kRxZykRxZy said to read that and said that is where Scratch said no bots. Can I get a link to where scratch disallowed it? I looked in the Scratch ToS for words like "bot" "AI" "Intelligence" "auto" "automation" and got nothing.

…

On Tue, Apr 22, 2025, 10:28 minniesBaa ***@***.***> wrote: robots.txt files are for search engine crawlers, like Googlebot, to know where to avoid crawling. I don't see how it could be important to bot commenting. — Reply to this email directly, view it on GitHub <#386 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A43POXWYL3TJ4G2KSJDIZLD22ZG2BAVCNFSM6AAAAAB3QGKM6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMRRGUZDINRYGI> . You are receiving this because you authored the thread.Message ID: ***@***.***> *minniesBaa* left a comment (TimMcCool/scratchattach#386) <#386 (comment)> robots.txt files are for search engine crawlers, like Googlebot, to know where to avoid crawling. I don't see how it could be important to bot commenting. — Reply to this email directly, view it on GitHub <#386 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A43POXWYL3TJ4G2KSJDIZLD22ZG2BAVCNFSM6AAAAAB3QGKM6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMRRGUZDINRYGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

I'm not sure where that might be. Try posting on the Forums or asking via Contact Us.

…

On Tue, Apr 22, 2025, 7:38 AM MilesWK ***@***.***> wrote: @kRxZykRxZy said to read that and said that is where Scratch said no bots. Can I get a link to where scratch disallowed it? I looked in the Scratch ToS for words like "bot" "AI" "Intelligence" "auto" "automation" and got nothing. On Tue, Apr 22, 2025, 10:28 minniesBaa ***@***.***> wrote: > robots.txt files are for search engine crawlers, like Googlebot, to know > where to avoid crawling. I don't see how it could be important to bot > commenting. > > — > Reply to this email directly, view it on GitHub > < #386 (comment)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/A43POXWYL3TJ4G2KSJDIZLD22ZG2BAVCNFSM6AAAAAB3QGKM6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMRRGUZDINRYGI> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > *minniesBaa* left a comment (TimMcCool/scratchattach#386) > < #386 (comment)> > > robots.txt files are for search engine crawlers, like Googlebot, to know > where to avoid crawling. I don't see how it could be important to bot > commenting. > > — > Reply to this email directly, view it on GitHub > < #386 (comment)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/A43POXWYL3TJ4G2KSJDIZLD22ZG2BAVCNFSM6AAAAAB3QGKM6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMRRGUZDINRYGI> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > — Reply to this email directly, view it on GitHub <#386 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BBGW32TQGOHOZKPIRNCGHJL22ZH6XAVCNFSM6AAAAAB3QGKM6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMRRGU2TKMJVHE> . You are receiving this because you commented.Message ID: ***@***.***> *MilesWK* left a comment (TimMcCool/scratchattach#386) <#386 (comment)> @kRxZykRxZy said to read that and said that is where Scratch said no bots. Can I get a link to where scratch disallowed it? I looked in the Scratch ToS for words like "bot" "AI" "Intelligence" "auto" "automation" and got nothing. On Tue, Apr 22, 2025, 10:28 minniesBaa ***@***.***> wrote: > robots.txt files are for search engine crawlers, like Googlebot, to know > where to avoid crawling. I don't see how it could be important to bot > commenting. > > — > Reply to this email directly, view it on GitHub > < #386 (comment)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/A43POXWYL3TJ4G2KSJDIZLD22ZG2BAVCNFSM6AAAAAB3QGKM6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMRRGUZDINRYGI> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > *minniesBaa* left a comment (TimMcCool/scratchattach#386) > < #386 (comment)> > > robots.txt files are for search engine crawlers, like Googlebot, to know > where to avoid crawling. I don't see how it could be important to bot > commenting. > > — > Reply to this email directly, view it on GitHub > < #386 (comment)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/A43POXWYL3TJ4G2KSJDIZLD22ZG2BAVCNFSM6AAAAAB3QGKM6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMRRGUZDINRYGI> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > — Reply to this email directly, view it on GitHub <#386 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BBGW32TQGOHOZKPIRNCGHJL22ZH6XAVCNFSM6AAAAAB3QGKM6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMRRGU2TKMJVHE> . You are receiving this because you commented.Message ID: ***@***.***>

robots.txt files are for search engine crawlers, like Googlebot, to know where to avoid crawling. I don't see how it could be important to bot commenting.

That's what I through, thanks for your confirmation.

robots.txt files are for search engine crawlers, like Googlebot, to know where to avoid crawling. I don't see how it could be important to bot commenting.

Oh

So looking over Scratch's legal documents I don't see anything that would disallow bot commenting. So, unless anyone could find something that says otherwise, I think the bot will stay.

But if you do find something else that says otherwise please tell me.

We have great wifi, and I have the program pushing a message to the server
when a comment gets received, and it takes a long time before it receives
the message and prints the message.
…

You can't really fix this because scratch api doesn't have instant refreshing.

I think that is the issue. I had about 5 comments in the past hour, and it took 30 minutes for the bot to respond, but when it did, it sent the responses within a minute of each response, even though they were like 5-10 minutes apart. Seems like it does it in batches. It could also have to do with that I am self-hosting on a Raspberry Pi running the DietPi OS.

I think that is the issue. I had about 5 comments in the past hour, and it took 30 minutes for the bot to respond, but when it did, it sent the responses within a minute of each response, even though they were like 5-10 minutes apart. Seems like it does it in batches. It could also have to do with that I am self-hosting on a Raspberry Pi running the DietPi OS.

Run it on render, it's so much quicker, it's free.

But does it 24/7 host python?

…

On Mon, May 5, 2025 at 1:03 PM kRxZykRxZy ***@***.***> wrote: *kRxZykRxZy* left a comment (TimMcCool/scratchattach#386) <#386 (comment)> I think that is the issue. I had about 5 comments in the past hour, and it took 30 minutes for the bot to respond, but when it did, it sent the responses within a minute of each response, even though they were like 5-10 minutes apart. Seems like it does it in batches. It could also have to do with that I am self-hosting on a Raspberry Pi running the DietPi OS. Run it on render, it's so much quicker, it's free. — Reply to this email directly, view it on GitHub <#386 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A43POXXZDR5Z6ALIIYQCLZT246KUPAVCNFSM6AAAAAB3QGKM6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNJRGY2TONJVGU> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

But does it 24/7 host python?
…

I think it runs 24/7 for 25 days a month

Edit : uhhh read this specifically the warning

But does it 24/7 host python?
…

Yeah, you can host I think about two different services, node.js python next.js etc

But does it 24/7 host python?
…

I think it runs 24/7 for 25 days a month

Edit : uhhh read this specifically the warning

It runs 24/7 all month unless you hit the limits by hosting more than two services

I don't think the hosting is the problem. I am also hosting a Discord Bot on the same device and the response time is very fast.

…

On Tue, May 6, 2025, 02:46 kRxZykRxZy ***@***.***> wrote: *kRxZykRxZy* left a comment (TimMcCool/scratchattach#386) <#386 (comment)> But does it 24/7 host python? … <#m_-2767093148508149397_> I think it runs 24/7 for 25 days a month Edit : uhhh read this <https://en.scratch-wiki.info/wiki/How_to_Access_the_Scratch_API_Using_Python_3> specifically the warning It runs 24/7 all month unless you hit the limits by hosting more than two services — Reply to this email directly, view it on GitHub <#386 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A43POXTTR3BYFAL5KONTRVL25BLD3AVCNFSM6AAAAAB3QGKM6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNJTGQ2DQOBSGU> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

Would you maybe send your code? MilesWK ***@***.***> schrieb am Di., 6. Mai 2025, 14:38:

…

*MilesWK* left a comment (TimMcCool/scratchattach#386) <#386 (comment)> I don't think the hosting is the problem. I am also hosting a Discord Bot on the same device and the response time is very fast. On Tue, May 6, 2025, 02:46 kRxZykRxZy ***@***.***> wrote: > *kRxZykRxZy* left a comment (TimMcCool/scratchattach#386) > < #386 (comment)> > > But does it 24/7 host python? > … <#m_-2767093148508149397_> > > I think it runs 24/7 for 25 days a month > > Edit : uhhh read this > < https://en.scratch-wiki.info/wiki/How_to_Access_the_Scratch_API_Using_Python_3> > specifically the warning > > It runs 24/7 all month unless you hit the limits by hosting more than two > services > > — > Reply to this email directly, view it on GitHub > < #386 (comment)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/A43POXTTR3BYFAL5KONTRVL25BLD3AVCNFSM6AAAAAB3QGKM6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNJTGQ2DQOBSGU> > . > You are receiving this because you modified the open/close state.Message > ID: ***@***.***> > — Reply to this email directly, view it on GitHub <#386 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATCKMZRAZWOKKBIRHD4UIX325CUNHAVCNFSM6AAAAAB3QGKM6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNJUGQZDANZTGY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

Yep! I can do it soon.

…

On Tue, May 6, 2025, 09:27 TheCommCraft ***@***.***> wrote: *TheCommCraft* left a comment (TimMcCool/scratchattach#386) <#386 (comment)> Would you maybe send your code? MilesWK ***@***.***> schrieb am Di., 6. Mai 2025, 14:38: > *MilesWK* left a comment (TimMcCool/scratchattach#386) > < #386 (comment)> > I don&#39;t think the hosting is the problem. I am also hosting a Discord > Bot on the same device and the response time is very fast. > On Tue, May 6, 2025, 02:46 kRxZykRxZy ***@***.***&gt; wrote: &gt; > *kRxZykRxZy* left a comment (TimMcCool/scratchattach#386) &gt; &lt; > #386 (comment)&gt; > &gt; &gt; But does it 24/7 host python? &gt; … > &lt;#m_-2767093148508149397_&gt; &gt; &gt; I think it runs 24/7 > for 25 days a month &gt; &gt; Edit : uhhh read this &gt; &lt; > https://en.scratch-wiki.info/wiki/How_to_Access_the_Scratch_API_Using_Python_3&gt; > &gt; specifically the warning &gt; &gt; It runs 24/7 all > month unless you hit the limits by hosting more than two &gt; services > &gt; &gt; — &gt; Reply to this email directly, view it on > GitHub &gt; &lt; > #386 (comment)&gt;, > &gt; or unsubscribe &gt; &lt; > https://github.com/notifications/unsubscribe-auth/A43POXTTR3BYFAL5KONTRVL25BLD3AVCNFSM6AAAAAB3QGKM6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNJTGQ2DQOBSGU&gt; > &gt; . &gt; You are receiving this because you modified the > open/close state.Message &gt; ID: ***@***.***&gt; &gt; > > — > Reply to this email directly, view it on GitHub > < #386 (comment)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/ATCKMZRAZWOKKBIRHD4UIX325CUNHAVCNFSM6AAAAAB3QGKM6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNJUGQZDANZTGY> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> > — Reply to this email directly, view it on GitHub <#386 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A43POXTV2K7B3OWQM7P6JPL25C2FNAVCNFSM6AAAAAB3QGKM6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNJUGU4DIMRWGU> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

In case you didn't see this in my previous reply,
you might want to read the warning on this page

@minniesBaa

@minniesBaa So I am getting two different info. The terms of use linked at the bottom of all scratch pages doesn't say anything. Likewise, reading the wiki and the terms of use linked in the warning, I don't see what they are referencing. I also noticed that at the top of the document it says

Are we able to move this over to my discussion page, because I feel like a scratchattach closed issue might not be the place to discuss this, as it is off-topic.

Edit: Can we move the conversation here?

Navigation Menu

Repository navigation

Major Comment Latency Delay #386

4 remaining items

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Major Comment Latency Delay #386

Description

Activity

minniesBaa commented on Apr 21, 2025

MilesWK commented on Apr 21, 2025

kRxZykRxZy commented on Apr 22, 2025

MilesWK commented on Apr 22, 2025

MilesWK commented on Apr 22, 2025

Fluffyscratch commented on Apr 22, 2025

minniesBaa commented on Apr 22, 2025

MilesWK commented on Apr 22, 2025

minniesBaa commented on Apr 22, 2025

MilesWK commented on Apr 22, 2025

minniesBaa commented on Apr 22, 2025

Fluffyscratch commented on Apr 22, 2025

kRxZykRxZy commented on Apr 22, 2025

MilesWK commented on Apr 22, 2025

4 remaining items

kRxZykRxZy commented on May 5, 2025

MilesWK commented on May 5, 2025

kRxZykRxZy commented on May 5, 2025

MilesWK commented on May 5, 2025

minniesBaa commented on May 6, 2025

kRxZykRxZy commented on May 6, 2025

kRxZykRxZy commented on May 6, 2025

MilesWK commented on May 6, 2025

TheCommCraft commented on May 6, 2025

MilesWK commented on May 6, 2025

minniesBaa commented on May 6, 2025

MilesWK commented on May 7, 2025

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions