Used an extension to mask the useragent to Chrome 118 and it didn't like me. I think I'll pop open the network tab to see what's happening in the automation, might be worth it.
Used an extension to mask the useragent to Chrome 118 and it didn't like me. I think I'll pop open the network tab to see what's happening in the automation, might be worth it.
https://discord.com/channels/676906881020854302/773195410688049164/1187182893257207849
So I popped open the developer tools for Chrome and ran the automation, which said it posted successfully, and there were otherwise no errors, but the post does not appear in the community. I did the same in Brave, and saw something slightly different in the posting.
It appears that whatever the automation is using to post, it isn't trying to post to the Locals community, but to somewhere else. I closed the window early, but it was something like share_type, which for automation was share, but when I posted, it was group. My manual post also had group_id, which I believe corresponds to the community in question. I'm going to see if I can find where those posts are actually going, because the posts are being accepted, but they don't show up in the group.
So I popped open the developer tools for Chrome and ran the automation, which said it posted successfully, and there were otherwise no errors, but the post does not appear in the community. I did the same in Brave, and saw something slightly different in the posting.
It appears that whatever the automation is using to post, it isn't trying to post to the Locals community, but to somewhere else. I closed the window early, but it was something like `share_type`, which for automation was `share`, but when I posted, it was `group`. My manual post also had `group_id`, which I believe corresponds to the community in question. I'm going to see if I can find where those posts are actually going, because the posts are being accepted, but they don't show up in the group.
I've confirmed this in my own Locals profile as well. It must be that this type of URL (https://<community>.locals.com/share/post) was working at one point in time, but it no longer works. Automation will need to be updated to use the form at the top of the main community page (https://<community>.locals.com/).
I've confirmed this in my own Locals profile as well. It must be that this type of URL (`https://<community>.locals.com/share/post`) was working at one point in time, but it no longer works. Automation will need to be updated to use the form at the top of the main community page (`https://<community>.locals.com/`).
Instead, what happens with the /share/post URL is that I get redirect and there's a "Retrieve Draft" message at the top of my screen. I don't recall seeing that in the automation browser, and using a separate browser changes several variables... but anyway! Those are my findings.
Instead, what happens with the `/share/post` URL is that I get redirect and there's a "Retrieve Draft" message at the top of my screen. I don't recall seeing that in the automation browser, and using a separate browser changes several variables... but anyway! Those are my findings.
I will add more info later, but whenever SMP tries to post to Locals, it'll appear to succeed, but there will be no post in the feed.
Let me know if changing the user agent does anything
Used an extension to mask the useragent to Chrome 118 and it didn't like me. I think I'll pop open the network tab to see what's happening in the automation, might be worth it.
https://discord.com/channels/676906881020854302/773195410688049164/1187182893257207849
So I popped open the developer tools for Chrome and ran the automation, which said it posted successfully, and there were otherwise no errors, but the post does not appear in the community. I did the same in Brave, and saw something slightly different in the posting.
It appears that whatever the automation is using to post, it isn't trying to post to the Locals community, but to somewhere else. I closed the window early, but it was something like
share_type
, which for automation wasshare
, but when I posted, it wasgroup
. My manual post also hadgroup_id
, which I believe corresponds to the community in question. I'm going to see if I can find where those posts are actually going, because the posts are being accepted, but they don't show up in the group.I've confirmed this in my own Locals profile as well. It must be that this type of URL (
https://<community>.locals.com/share/post
) was working at one point in time, but it no longer works. Automation will need to be updated to use the form at the top of the main community page (https://<community>.locals.com/
).Instead, what happens with the
/share/post
URL is that I get redirect and there's a "Retrieve Draft" message at the top of my screen. I don't recall seeing that in the automation browser, and using a separate browser changes several variables... but anyway! Those are my findings.