Cross-posting is not working in two category feeds

Cross-posting
1

Sorry. I’ve seen many other topic regarding this issue but none of them gave me a solution.

I have two category feeds and none are cross-posting properly. This two feeds are:

  • https://umerez.eu/categories/blog-legal/feed.xml. I’ll call it Legal feed. For cross-posting purposes, I have it linked to Twitter, Linkedin and Mastodon.
  • umerez.eu/categories/blog-personal/feed.xml. Personal feed. Linked to Mastodon.

Both feeds work properly in my RSS readers (Reeder and DEVONthink), but do not cross-post.

I have another general feed https://umerez.eu/feed.xml where cross-posting is disabled.

In the logs, the Personal feed does not show any issues. It says Feed: Downloading feed then Feed: Not modified, even if I did publish a new post in that category. It shows in my blog and in the micro.blog timeline, but it does not cross-post to Mastodon.

The Legal feed does show errors in the logs. There’s one recurring error every time it tries to download the feed:

2023-01-04 09:07:21: Feed: Skipped processing large RSS feed 1368461

That error does not prevent the feed from working properly in the other RSS readers.

And there’s a longer error, that showed up after I published a new post in the Legal category:

2023-01-04 09:06:01: Publish: ERROR 2023/01/04 08:05:59 Failed to get JSON resource "https://publish.twitter.com/oembed?dnt=false&url=https%3A%2F%2Ftwitter.com%2Fuser%2Fstatus%2Fid+number+%2819+digits%29": Failed to retrieve remote file: Not Found, body: "<!DOCTYPE html>\n<html lang=\"en\" class=\"dog\">\n <head>\n <meta http-equiv=\"Content-Type\" content=\"text/html; charset=utf-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n <title>Twitter / ?</title>\n <meta name=\"version\" content=\"1\">\n <link href=\"https://abs.twimg.com/favicons/favicon.ico\" rel=\"shortcut icon\" type=\"image/x-icon\">\n <link rel=\"stylesheet\" href=\"https://abs.twimg.com/errors/fullscreen_errors-39d97faf8c7cf33e502c3c015176efd9.css\">\n </head>\n <body dir=\"auto\">\n <div class=\"top\">\n <svg xmlns=\"http://www.w3.org/2000/svg\" viewBox=\"0 0 1519 200\">\n <defs/>\n <path d=\"M708 103l9-5 13 1 2-2 5 1h8l1-1 42-5h7l7 3v1l12-2a9368 9368 0 0129-6l2-5 12 1 6-2 3 1 2 1v-2l13-2v1l4 2 7-1h1l17-3 1 2 4-1 18-7 3-1 4-1h9l13-1 1-4 3-2 13 1v2l22-2 10-3h6l10 5 16-5 15-3 2-1 8-4 6-2 12-1 7-2 8 5 7 1 22-9h7l5-1v-1l25-3 1 2 5 2v1h11l2 1 8-4h3l-1 1h11l10-6 6 3 9-1 4-1 1 1 1-2 6-1 1-1 10-2h2l7-5v1h4l3-1c11 0 23 2 34-3 2-2 7 0 10 0l12 1 4 1 9 2 12-1 11-3 11 1h4l10-6 17 1 2 1c9 2 19-3 22-11l1-1 9 1 15-5c3-1 9 4 9-5 5 0 5 3 5 7l2 3 4-1 4-2 9-4 3-3h3l8-4 6-3 26 2 7-4h18l7 1c10 3 13-6 17-12l8 4 3-1 14-3 15-2a38 38 0 01-5-1l-8-4 7-8 8-4-10-136-922 71 16 205z\"/>\n <path d=\"M-36 193l9-5 13 1 2-2 5 1h8l1-1 42-5h7l7 3v1l12-2a9328 9328 0 0129-6l2-5 12 1 6-2 3 1 2 1v-2l13-2v1l4 2 7-1h1l17-3 1 2 4-1 18-7 3-1 4-1h9l13-1 1-4 3-2 13 1v2l22-2 10-3h6l10 5 16-5 15-3 2-1 8-4 6-2 12-1 7-2 8 5 7 1 22-9h7l5-1v-1l25-3 1 2 5 2v1h11l2 1 8-4h3l-1 1h9a6 6 0 002 0l10-6 6 3 9-1 4-1a6 6 0 001 1l1-2 6-1 1-1 10-2h2l7-5v1h4l3-1c11 0 23 2 34-3 2-2 7 0 10 0l12 1 4 1 9 2 12-1 11-3 11 1h4l10-6 17 1 2 1c9 2 19-3 22-11l1-1 9 1 15-5c3-1 9 4 9-5 5 0 5 3 5 7l2 3 4-1 4-2 9-4 3-3h3l8-4 6-3 26 2 7-4h18l7 1c10 3 13-6 17-12l8 4 3-1 14-3 15-2a37 37 0 01-5-1l-8-4 7-8 8-4-10-136-922 71 16 205z\"/>\n </svg>\n </div>\n <div class=\"container\">\n <div class=\"content\">\n <a href=\"https://twitter.com\" title=\"Twitter logo\"><svg class=\"bird\" viewBox=\"0 0 24 24\"><g><path d=\"M23.643 4.937c-.835.37-1.732.62-2.675.733.962-.576 1.7-1.49 2.048-2.578-.9.534-1.897.922-2.958 1.13-.85-.904-2.06-1.47-3.4-1.47-2.572 0-4.658 2.086-4.658 4.66 0 .364.042.718.12 1.06-3.873-.195-7.304-2.05-9.602-4.868-.4.69-.63 1.49-.63 2.342 0 1.616.823 3.043 2.072 3.878-.764-.025-1.482-.234-2.11-.583v.06c0 2.257 1.605 4.14 3.737 4.568-.392.106-.803.162-1.227.162-.3 0-.593-.028-.877-.082.593 1.85 2.313 3.198 4.352 3.234-1.595 1.25-3.604 1.995-5.786 1.995-.376 0-.747-.022-1.112-.065 2.062 1.323 4.51 2.093 7.14 2.093 8.57 0 13.255-7.098 13.255-13.254 0-.2-.005-.402-.014-.602.91-.658 1.7-1.477 2.323-2.41z\"></path></g></svg></a>\n <h1 id=\"header\">Nothing to see here</h1>\n <p id=\"description\">Looks like this page doesn’t exist. Here’s a picture of a poodle sitting in a chair for your trouble.</p>\n\n <a id=\"button_search\" href=\"/\" class=\"button\">Looking for this?</a>\n\n </div>\n <img id=\"image\" src=\"https://abs.twimg.com/errors/ErrorState_NotFound.png\" alt=\"A primped poodle with a bow in its hair sitting in a chair like a human.\">\n <div class=\"footer\">\n <ul>\n <li><a href=\"https://twitter.com/\" id=\"footer_home\">Home</a></li>\n <li><a href=\"https://status.twitterstat.us/\" id=\"footer_status\">Status</a></li>\n <li><a href=\"https://twitter.com/tos\" id=\"footer_tos\">Terms of Service</a></li>\n <li><a href=\"https://twitter.com/privacy\" id=\"footer_privacy\">Privacy Policy</a></li>\n <li><a href=\"https://support.twitter.com/articles/20170514\" id=\"footer_cookie\">Cookie Policy</a></li>\n <li><a href=\"https://legal.twitter.com/imprint\" id=\"footer_imprint\">Imprint</a></li>\n <li><a href=\"https://business.twitter.com/en/help/troubleshooting/how-twitter-ads-work.html\" id=\"footer_ads\">Ads info</a></li>\n <li dir=\"ltr\">© Twitter <span id=\"copyright-year\">    </span></li>\n </ul>\n </div>\n </div>\n </body>\n <script src=\"https://abs.twimg.com/errors/404-8651f633fd193e0b546010676a4fac06.js\"></script>\n</html>\n"

Any ideas? Any help would be appreciated. Thanks in advance.

Esteban

2

Micro.blog has size limits for RSS feeds and your legal feed exceeds that limit. It’s too big, so Micro.blog skips it.

The other error is a little harder to debug from the outside. It’s clear that Micro.blog tries communicating with the Twitter API and fails to do so. Do you embed tweets in some of your posts, maybe with a shortcode like {{< tweet user="FooBarBaz" id="1453110110599868411" >}}?

3

Thanks a lot, @sod.

As for the length of the legal feed, I have two quite long articles, do you think dividing them in smaller posts will solve that error? I will try.

Anyhow, that length problem seems to prevent the legal feed from cross-posting via micro.blog. The feed itself works fine in Reeder and DEVONthink, updating the feed as expected.

And for the Twitter error. Yes, I use shortcodes, two natives in Hugo (Twitter and YouTube) and one for Mastodon that involved creating a new template and inserting the necessary code in it (following a tutorial in the Hugo forums). They have all worked fine for a few weeks. And the thing is that I have disabled the cross posting to Twitter and it still gives the error.

I really don’t know what to do. Should I delete the posts that have shortcodes in them?

4

It’s a file size limit, 800 kB, so splitting posts won’t do anything, I’m afraid. The feed have to contain less content (fewer bytes). I think the problem will go away if you choose to paginate the category pages by going to the Design page and checking the box next to Paginate category pages.

The feed size limit is an arbitrary one @manton has decided on for Micro.blog. Other feed readers, like Reeder and DEVONthink, might have other size limits or no limits at all.

Regarding the Twitter error: what the shortcodes does is looking up information about the tweet when building your website. You probably have a shortcode somewhere including a tweet that no longer exists, which throws an error from the Twitter server. If you can identify this post and remove the shortcode, the error should go away.

I know that other Micro.blog and Hugo users have stopped using the Twitter shortcode for exactly this reasons. Tweets disappearing is common enough, and they don’t want their sites to break every time that happens.

5

OK, so the Twitter error is fixed. I had three posts with Twitter shortcodes, one of them pointed to a deleted tweet. Just in case, I deleted all of them.

And the feed size is still problematic. I did as you said, went to Design and saw that I already had Paginate category pages checked. So I will turn to @manton and @help and see if they can give me a hand.

Thanks a lot for all your help, @sod.