@paul i am certain this is like the bottom of most bottom priority, but ivory seems to not be able to talk to a pleroma server beyond fetching very basic user info (display name/profile photo), i haven't checked how much its api deviates from mainline mastodon's, but i was under the impression that it wasn't a ton, lmk if i can send anything for a bug report via email

@nsfmc it’s probably not something we’ll be looking at until after a 1.0 ships. I’m sure I’ll take a look at some point but like you said bottom of the list.

@paul right on, the testflight looks gorgeous for now on my mastodon.social acct btw. 🤘🏽 i wonder actually if it’s possible that my instance being hosted on a domain separate from my account’s webfinger domain might be the issue. i’ll check my server logs later tonight and report back.

@paul @nsfmc I'm also wanting to using Ivory with Pleroma. The main difference I'm aware of is that Pleroma uses uuids for account ids instead of numbers. The Mastodon docs say the type for id is "String (cast from an integer, but not guaranteed to be a number)". It couldn't be something as simple as a stray conversion to an integer could it? I'm happy to wait until after 1.0 and for the dust to settle, I'm just excited about Ivory as a TweetBot fan!

@thefloweringash @nsfmc@turbotime.turboteam.xyz there are no stray conversions, there’s 10+ years of code and optimizations that expect it to be a number. Can it be fixed? Sure, but I’m not pulling at that Jenga block before everything else is nice and stable.