~wiwie, do you use Cloudflare in front of your Microblog instance? I found out that disabling Cloudflare’s proxy (the orange cloud icon in DNS listing) fixes the problem.

I discovered this trying to fix another issue with hosted domains at Fastmail. According to their support, Cloudflare flattening CNAME is the culprit. Problem is: at least in my (free) account, there’s no way to disable flattening CNAME.

I ran into exactly the same problem. I made the same "tweak" on my instance, that would show the articles on "/". Thanks for reporting this! Changing it back indeed solved my problem of not being able to follow anyone.

Hey, I was just trying to link to some locally hosted images in one of my posts and saw that none of them was working.

In this case the problem was, that I host some images I linked to in my posts on the same server at another subdomain. This tripped the is_valid_url check / SSRF protection.

My temporary workaround is, to set "debug = true" in my profile.toml.

For my use case having this feature would be really important as well.

I'm evaluating to run my blog (non micro) with microblog.pub and not being able to edit posts is almost a showstopper.

To me it would already really helpful to be able to edit only the markdown part, such that the website shows the corrected posts. And for the activitypub part, as long as there is no update support implemented, maybe it would be possible to decouple the activitypub publishing from the markdown editing, eg via a separat button that says "publish" next to an article. So that one can fine tune the markdown a bit before publishing to activitypub.

I'm interested in this as well. Adding the language on a post would enable to provide that meta information to the fediverse, eg for automatic filtering or translating.

But it would also enable features on the UI, eg to show posts of a specific language.

Apart from this, but that would probably be a separate issue, I'm also interested in multilingual posts.

I'm in the same boat.

I'm trying to migrate my blog, and for that adding my existing posts with the correct dates is important.

As long as I don't have any followers on my instance it would be possible with the current code to tinker with the database and change the dates in three places. That allows to have the correct date shown on the UI and have the outbox expose the posts with the original dates. But it's more than inconvenient.