Feditext beta users: we're aware of the performance regression under the release version of iOS 17 and are tracking it in https://github.com/feditext/feditext/issues/253. we don't know the cause yet. if you're a heavy Fedi user and don't have a pressing need for iOS 17 features, it might be a good idea to stay on iOS 16 for a few more days.
hey, folks! progress update: i've been coding and testing a possible fix for the iOS 17 hangs and stuttering, and hope to release a new build with that fix sometime next week.
see issue #253 for more details, but the short version is that the iOS API we were using to turn HTML in posts and bios into displayable styled text is now unusably slow, and i'm replacing it with a Feditext-specific text formatter. this might also give us some speedups on iOS 15 and 16, although the difference won't be as dramatic there.
i know there are some people waiting for beta invites as well; we'll get those out soon.
Feditext beta users: tonight's build 76 includes a partial fix for the iOS 17 performance regression. this fix removes a keychain access on a hot path, and is not related to the HTML handling change mentioned above, so you shouldn't see any visual changes.
as always, to update: open the TestFlight app, pull to refresh, and tap the Update button next to the Feditext icon and name.
Feditext beta users: today's build 75 includes the first of several performance fixes resulting from our perf investigation. there's a lot still to do; we'll be alternating perf fixes and bug fixes for the next few beta builds, so non-perf problems don't sit for too long.
Your favorite iPhone Mastodon client (wish I could list more than 4 options in a poll, feel free to reply if your favorite isn't listed, e.g. the official Mastodon client):
#Question on #posting (I use the #Mastodon site on desktop, #Feditext on my phone): if I #post something with a #hashtag in it, but put the post behind a #CW, is the hashtag then hidden? If not, would people following it need to click through the CW?
we've had a few questions about an Android version lately. for the record: there will never be an Android version.
Feditext is Apple tech from the ground up (Swift, SwiftUI, UIKit, and other iOS platform APIs) so porting it would be more work than writing a new client from scratch, and we'll leave Android to the Android professionals.
Feditext users: Mastodon 4.2 is finally in beta! Feditext already supports some 4.2 features, the most useful of which is Hometown-style exclusive lists: you can hide members of lists from your home timeline by tapping the gear icon in the upper right of a list view. this lets you create lists of accounts that you may follow for a certain topic but don't need in your home timeline all the time, such as hobbies, local news, or Fediverse development announcements.
we'll be adding support for other 4.2 features in later releases; watch issue #175 and issues created from it for updates.
Feditext beta users: we're aware of the hitches in scrolling your timelines, and are tracking them in https://github.com/feditext/feditext/issues/122, which is the next big bug on the to-do list. thanks for all your reports, and for your patience: perf issues can take some time to figure out, especially if they're not due to obvious regressions.
@HaruEb@Ciela@supakaity@ada At this stage it's likely that any native app would come from the #Firefish devs, but if there was a lot of interest in that I know the #Feditext dev has said she'd look at implementing some of the native API to support antennas but that's sometime down the track.
Feditext beta users, today's TestFlight build 69 includes various fixes and workarounds for Firefish and Hajkey.
we will be working with server devs to get some of those fixed on the server side (for Hajkey's case, in Iceshrimp), so that future clients won't have to special-case anything.
known not to work in this release:
Hajkey's suggested accounts to follow: displays an error message
intermittent foreign key constraint error when browsing Firefish or Hajkey timelines: you don't need to report this one, we're already investigating
Feditext beta users: our current error report system involves copying and pasting JSON to GitHub, rather than a collection API, to give you the option of removing any personal info from them before submitting.
we do generally need to know the file, line, and function of the error, what kind of server you're talking to, what the server and Feditext versions are, and what API was being called, if applicable, or we're not going to be able to do much with it. we may also need to know your OS version and device type, since some app behavior is different between iPhones and iPads and between iOS 15 and 16 (and probably 17).
we don't capture HTTP request or response bodies in the error data, so the actual contents of your post shouldn't show up in them, and please feel free to replace instance names, post IDs, hashtags, etc. with XXX or whatever if they're sensitive. (just don't change the data structure.) we do not need to know what porn you're looking at or which government you're planning to overthrow, although we wish you good luck with either.
Firefish users: there's a known issue (#10543) with unimplemented MFM rendering which prevents links, hashtags, some mentions, and any rich text formatting from being displayed correctly.
this affects all Mastodon API clients, not just Feditext. you don't need to report this one to either us or Firefish.
Feditext + Firefish users: Kainoa says the missing MFM to HTML renderer is on their list, so hopefully the text issues will get fixed in the near future.
fixes for other Firefish-specific bugs on Feditext's side are in progress.