bmann.ca
+1
-1
_journals/2024-01-04_2301.md
+1
-1
_journals/2024-01-04_2301.md
···-How many times have I ended up using this [Jekyll JSON Feed Template](https://github.com/georgemandis/jekyll-json-feeds)? Many times! The special treatment for link front matter has me thinking.Decided to not mess with feed format right now. It's working, let's use it for a bit, and see how various things look once they cross-post through Micro.blog to Mastodon. Where it's actually putting content on my under-used [@boris@toolsforthought.social](https://toolsforthought.social/@boris) account.
···+How many times have I ended up using this [[JSON Feed#Jekyll JSON Feed Templates]]? Many times! The special treatment for link front matter has me thinking.Decided to not mess with feed format right now. It's working, let's use it for a bit, and see how various things look once they cross-post through Micro.blog to Mastodon. Where it's actually putting content on my under-used [@boris@toolsforthought.social](https://toolsforthought.social/@boris) account.
+1
_notes/BMC.md
+1
_notes/BMC.md
···- [ ] Journal feed: consider linking back to the actual journal entry. ~~Hmm, or maybe appending a hashtag like `BMCJournal` for context~~
+19
_notes/JSON Feed.md
+19
_notes/JSON Feed.md
···
···+> We — Manton Reece and Brent Simmons — have noticed that JSON has become the developers’ choice for APIs, and that developers will often go out of their way to avoid XML. JSON is simpler to read and write, and it’s less prone to bugs.+> So we developed JSON Feed, a format similar to [RSS](http://cyber.harvard.edu/rss/rss.html) and [Atom](https://tools.ietf.org/html/rfc4287) but in JSON. It reflects the lessons learned from our years of work reading and publishing feeds.
+29
_notes/Micro.blog.md
+29
_notes/Micro.blog.md
···It supports aggregating multiple different RSS or JSON Feeds and either importing them into your blog, or just merging them into your Micro.blog feed.···
···It supports aggregating multiple different RSS or JSON Feeds and either importing them into your blog, or just merging them into your Micro.blog feed.···+The specification of [how cross-posting is configured](https://help.micro.blog/t/cross-posting-to-twitter-medium-mastodon-and-more/85):[^twitter]+> - Short posts without a title, and less than 280 characters, will be sent to Twitter unmodified.+> - Longer posts without a title, but longer than 280 characters, will be truncated with a link back to your microblog.+> - Posts with a title, regardless of length, will be sent to Twitter using the title and a link back to your microblog to read the full post.+> - Up to 4 photos embedded in a post are automatically downloaded and attached to your tweet. Photos should be larger than 200×200, to avoid accidentally cross-posting small buttons and tracking images that some blog systems include.+The newer write up of [how cross-posting works across networks](https://help.micro.blog/t/automatic-cross-posting-to-mastodon-and-other-services/860):+> - Short posts without a title, and less than 500 characters, will be sent to Mastodon unmodified.+> - Longer posts without a title, but longer than 500 characters, will be truncated with a link back to your microblog.+> - Posts with a title, regardless of length, will be sent to Mastodon using the title and a link back to your microblog to read the full post.+> - Up to 4 photos embedded in a post are automatically downloaded and attached to your post. Photos should be larger than 200×200, to avoid accidentally cross-posting small buttons and tracking images that some blog systems include.+> Similar rules apply for the other services, but with different character length restrictions.+**Note:** It appears that only JSON Feed content works reliably. I have an [ongoing thread where Bluesky rich text isn't syndicating](https://help.micro.blog/t/feed-and-cross-posting-issues/2427), and apparently RSS vs JSON Feed appears to be the culprit.