Making WordPress.org

Opened 7 months ago

Closed 7 months ago

#7327 closed defect (bug) (invalid)

Link cards for Make blog posts shared on Bluesky show "429 Too Many Requests" as the preview

Reported by: 360zen's profile 360zen Owned by:
Milestone: Priority: normal
Component: Make (Get Involved) / P2 Keywords: close
Cc:

Description

When sharing blog posts from make.wordpress.org on bsky.app, the link cards show an error message ("429 Too Many Requests") instead of the post preview. The preview properly appears on X/Twitter, so it seems like this might be an issue with an allowlist or some other firewall/DNS type issue.

This appears to be happening for all of the make.wordpress.org links shared on https://bsky.app in the last 2 months.

Would love to see the Make blog posts looking good on that platform.

Attachments (2)

Screenshot 2023-10-26 at 10.09.09 AM.png (359.5 KB) - added by 360zen 7 months ago.
Preview errors on bsky.app
Screenshot 2023-10-26 at 10.11.35 AM.png (144.5 KB) - added by 360zen 7 months ago.
Preview looking fine on X/Twitter

Download all attachments as: .zip

Change History (6)

@360zen
7 months ago

Preview errors on bsky.app

@360zen
7 months ago

Preview looking fine on X/Twitter

#1 @Otto42
7 months ago

It takes a lot of effort to get a 429 from our side. It's possible, but the system is fairly liberal with allowing a lot of requests. It sounds like you need to bring this up to the bluesky administrators or code system. If they can get that kind of response out of our servers, then they are actually breaking most sites that get linked to on their system.

This ticket was mentioned in Slack in #meta by courtneyengle. View the logs.


7 months ago

#3 @Clorith
7 months ago

  • Keywords close added

I can verify that I can post to Bluesky with link cards, and they render as expected.

I suspect the platform may not have be caching things correctly, and that naturally led to a temporary rate limit :)

As things are working as expected, I'm going to suggest we close this issue.

#4 @360zen
7 months ago

  • Resolution set to invalid
  • Status changed from new to closed

I've re-tested this and you're right that new posts do appear to be working correctly. The old posts are still showing the 429 errors, but I guess that is some caching issue on their end.

Wanted to report here, in case they needed an explicit allowlist exception that they didn't have. No objection to closing it here.

Note: See TracTickets for help on using tickets.