Jorge Caballero

Some version of this warning has been in Mastodon UI since January 2, 2018: "This post won't be listed under any hashtag as it is not public. Only public posts...

Would love to see progress on this issue. There's an [open PR](https://github.com/unjs/nitro/pull/796) that, while imperfect, is better than the status quo.

I can confirm that IceCubes app remains incompatible. The problem seems to stem from an incomplete implementation of the `GET /api/v2/instance` endpoint (as previously mentioned by @riaf). The app hangs...

I reached out to the Tapbots team to ask how they determine whether the server is Mastodon-compatible. Awaiting their response.

Heard back from the Tapbots team. They said they require post/statuses/toots to have numerical IDs. Wildebeest uses UUIDs. Separately, while digging into the issue, I noticed that Wildebeest uses the...

@xtuc No worries. The asynchronous communication across several issues & PRs makes it a bit challenging to collaborate on a project of this complexity. I'm aware of the #Wildebeest Discourse...

Hi @7glaucio - I was just about to submit an issue/request for this exact feature. Thank you so much for submitting a PR. It looks like some of the PR...

FWIW, Eugen just merged this commit to Mastodon main that will increase the rate limit significantly for app tokens and user tokens: https://github.com/mastodon/mastodon/commit/c6ef56fd5e8f2648a256ae1479ddc28d0164c602

> Have you tried to delete your KV namespaces starting with `wildebeest` and rerun? Hi there - I've tried this, and it doesn't fix the problem. What I've been able...

During the latest attempt I was able to get as far as this error message (see image): `error creating ruleset Wildebeest: exceeded maximum number of zone rulesets for phase 'http_request_firewall_managed'`...