Continuing to work through some lingering Micro.blog issues with the Ruby 3 upgrade. As I spot errors, Iโm fixing them. Donโt hesitate to report issues via email or @help.
Continuing to work through some lingering Micro.blog issues with the Ruby 3 upgrade. As I spot errors, Iโm fixing them. Donโt hesitate to report issues via email or @help.
@manton my last two photo challenge posts are missing their photos. They do have photos on my WordPress site.
@dejus We noticed that too. The WordPress CDN is refusing connections from Micro.blog. Not sure why that started happening, but I'm going to implement a work-around.
@manton I doubt it's Ruby related since it's been happening for a couple months, but my Bookmarks feed stops working unless I resubscribe. Is the RSS feed changing?
@manton And still getting this error in my logs for the Newsletter:
Newsletter: Error running template, Error parsing JSON: parsing time ""2024-03-11 16:12:35 +0000"" as ""2006-01-02T15:04:05Z07:00"": cannot parse " 16:12:35 +0000"" as "T"
@manton looking at my timeline on the Micro.blog website, my last post with a picture appearing was 2024-04-16 at 13:25. Minutes later at 13:37 was another post without its picture. So that gives you a pretty small window of when it started.
@manton seeing the Newsletter error as well, even though I have no newsletter to publish.
@manton also missing my two last photo challenge posts. Both published via Micro.blog as scheduled posts.
@ericgregorich @jarrod I fixed the newsletter issue this morning, so should be good going forward. Unfortunately we don't have a way to re-send failed newsletters. I'm going to add a "Send Again" button or something to send them manually when needed.
@manton no problem. My 2 subscribers will be fine without my boring updates this week. ๐
@jarrod showed up this morning, just delayed. The notifications seemed to come through after I logged into Mb on the web, not sure why.
@bryan I'm rolling out a couple improvements to Bluesky support: fixing not getting some @-mentions, and better checking if you aren't signed in on the web or official native apps (so what you described does make sense).