How can I verify this? I have replied to two posts on Mastodon; my replies show in the “Conversation” page on micro.blog, but they do not on the Mastodon conversation page.

(post deleted by author)

Just for awareness, trying to load micro.blog here and getting a 503 error. My actual blog loads fine though

As a comparison, I checked my own blog and I have a little over 2000 photos. I’m sure some people have more. You could use Micro.blog photo collections to organize photos (or even separate blogs like @jsonbecker suggested) but it would be a little clunky without a dedicated workflow that is just for this. Lots of clicking and dragging photos around. So I think the Micro.blog backend could handle this fine because it can hand off all the photos to the CDN, but getting all the photos _organized_ might be tricky. We have cross-posting to Flickr, but not the opposite to pull them in. In an ideal world, there would be an Aperture or Lightroom plug-in that could publish directly to Micro.blog.

I could imagine something like “design mode” or “dev mode” when you open up to make design tweaks that is a little pop up like “hey, are you about to make a bunch of changes? If you click this button, we won’t execute a fresh build when changing theme files until you hit this again or 1 hour passes without any theme changes” – but making a post would still execute a build.

Yeah, this is something I’d really like to improve. I’ve been making some tiny optimizations for publishing to get things faster, and improving how multiple changes are queued would go along well with that. Thanks y’all.

That does feel like how it works, but often the build starts and you still haven’t finished making small changes. Having an option to tell it to hold off, then run once you’ve completed might be more helpful and be more efficient on the backend system. Just a thought.

Thanks Jason, That’s pretty much what I’d concluded, but I wanted to see if I was missing a trick. Will look at other alternatives.

Updating to note that I haven’t seen this in the past couple of days, so it might be fixed.

The queue is effectively a batch– “hey, you’ve made a lot of changes too fast for me to catch up, so I’ll build it in a few minutes”– it doesn’t queue only the one change, it’ll build the blog in the state it’s at when the time comes up on the queue– I’m 99% sure the queue is “wait to run hugo build” but in the mean time all your files and changes are being saved, just not built and published.

Can it be done? Yes. Do I think it’s the ideal tool for the job? Probably not, IMO. I think the organizational tools that exist are not going to be sufficient for a project of that size. Micro.blog would be great for a site for one particular race (and maybe that’s how I’d do it? A blog per race maybe?). I might use it for a race or two to build up a Hugo setup that works well, then just setup my own Hugo site, but that comes with technology knowledge to do this. Very few things that I know of are built well to handle 10,000 photos on the web like that– most will work, but if not purpose built, won’t have the organization you’d need/want.

that’d be sweet for m.b. to be jxl ready. I think the tooling is finally maturing.

Apologies for the clickbait title, but I’d like to determine if micro.blog photos is servicable for the many photos I have and will remove from flickr. For context, several years ago I embarked on documenting all the local trail / ultratrail races and after 6 or 7 years, I ended up with 10K+ photos organised by event. I’d published them within hours of the race each on flickr, and I kept all the originals from Aperture and imported them to photos. I no longer pay for flickr and they keep threatening to boot me off (its been a couple of years) and I’d like to comply eventually. But i want to publish the photos, as they are still referenced by the runners / clubs. Essentually, I’d like to have an album per race that would contain anything from a few hundred photos to about a thousand or so (lots of runners / places). Each race is from a year, and has a title (example: La Mythik - Oct 2020). Firstly, is this too many photos for MB to handle? What would the best strategy to categorise these photos by event? Any other tips, size/ formats etc (they are all RAW in their original form bu twill export as necessary).

Sometimes you can’t avoid many little changes. It would be nice to have a batch update feature. I’m guessing that that would eleviate some of the queueing?

When I select “Add Threads” under “Sources”, I’m greeted with a very VERY large QR Code. I can use it on my phone to login to Threads, but nothing about linking accounts seems to happen. On a sidenote, the back button to go back to micro.blog becomes unavailable, so I have to type in the micro.blog url again.

I looked into this error behind the scenes and the Pixelfed server was returning the error: “400 Request Header Or Cookie Too Large” I’m going to fix Micro.blog to more gracefully handle this error. I don’t think I’ve ever seen that before. Does it still do that if you try again?

Sorry, I’m not seeing anything particularly wrong right now with your blog on first glance. I did a test publish and it was about 15 seconds. If you see in taking minutes again, send us a quick email to help@micro.blog and I’ll investigate further. Sorry about that! We’ll keep trying to optimize it.

Encountering this issue again, about 7 minutes hanging so far for a purely text post. Anything wrong with my blog specifically I need to change?

There is a new file format for images that is going to be rolled out. I have an example post here: https://mandarismoore.com/uploads/2026/play-lab.jxl Here is the wikipedia entry. en.wikipedia.org ### JPEG XL The JPEG XL Image Coding System (JPEG XL, sometimes shortened to JXL) is an image format that supports both lossy and lossless compression. It was developed by the Joint Photographic Experts Group (JPEG), Google and Cloudinary. It is a free and open standard defined by ISO/IEC 18181. The standard consists of four parts that cover the Core coding system, File format, Conformance testing, and Reference software, respectively. JPEG XL features a lossy compression mode called VarDCT built on block-...

Turned out this was a bug, now squashed by @manton: > Fixed not fully deleting uploaded files, only removing them from the CDN and not your own domain name.

Another tiny bug report…this has happened to me twice today. Start a post via the web UI, upload an image. Upload progress bar goes to the completed state. But then instead of a thumbnail of the image, I’m presented with a broken image graphic. This isn’t happening every time, so if I were still in the business I’d guess at a race condition. Luckily for me I’m not, and I’ll just wait for someone else to fix things. This is at most a minor annoyance, since the actual post works fine & includes the uploaded image.

You can use GitHub and sync your theme that way.

Manton tweaks the asset pipeline a fair bit. And aggressively wipes metadata, which all standard libraries I know of do a terrible job of letting you do that selectively versus with a canon. If I had to guess, changes in the video asset pipeline could have messed this up. Or you got a phone that takes HDR now or uses a non default color space that makes it noticeable. Or your process for converting to webp stores that data differently than it used to. All guesses.

I’m trying to set up the Pixelfed cross-posting (gram.social) but keep getting the error message below: > Error while processing the request. Please try again or email help@micro.blog. Check the news blog for updates

Is there a way to customize this? I have a family plan running a few instances and I’d like for each to have like a noreply@adobedigtest.com versus hatcher@hello.micro.blog which doesn’t seem like it has anything to do with the newsletter.