Feditext

@Feditext@fedi.software
1.1K Followers
1 Following
684 Posts
iOS and iPadOS client for Mastodon, Glitch, GotoSocial, Firefish, Akkoma, and more! Maintained by Vyr @vyr@demon.social and Brian @bdube@gotgoat.com.

Please DM this account to join the TestFlight beta program, as we're not yet in the App Store. (Do not use the Firefish chat feature. Send a regular DM.)

Feditext is a community continuation of
@metabolist@mastodon.social's incredible work on Metatext, and supports features Metatext does not, such as rich text, post editing, notification grouping, following hashtags, exclusive lists, and emoji reactions. (Do not send bug reports or feature requests to Metabolist, as the original app has been retired.)

Feditext "ft" logos by Robert George:
@rrgeorge@raphus.social (CC BY 4.0)
GitHubhttps://github.com/feditext/feditext
bugs and feature requestshttps://github.com/feditext/feditext/issues
GitHub orghttps://github.com/feditext
backup accounthttps://mastodon.social/@Feditext
hey folks, Vyr here. since Firefish and fedi.software are no longer maintained, we're switching over to our backup account, @Feditext, with an automatic account migration. please follow us there from now on.

unfortunately, i came back from winter vacation with COVID, but hope to resume Feditext development as soon as i'm over it. major thanks to Brian for handling project matters while i was out. i'll be catching up on invites and issue categorization over the next few days.
I'm trying to work some more on notifications before the holiday break is over. In the end, I hope to have a backup endpoint and a queue to smooth out any interruptions. -b #Feditext
i think we're caught up with TestFlight requests now. thank you for your patience. if i missed your request, i apologize--please bump it. -b #Feditext
Notifications were down for a while. Some VPN nodes failed to come back up after a wind storm. My apologies for the downtime. -b

#Feditext
Push notifications were down for a few minutes, but they are processing again. -b

#Feditext
Feditext beta users: today's 1.7.2 (build 80) includes formatting fixes for the Siren HTML parser. there's still a known issue where text list numbers or bullets overlap with text styles (bold, code, links), but most Siren feedback has been positive, and we'll fully replace WebKit parsing with Siren in a future release.

#Feditext #Metatext
Feditext beta users: today's build 79 includes the new "Siren" HTML parser, which is 3-6× faster than the current WebKit parser for the text formatting used in Fediverse posts. this should result in smoother scrolling for many users.

Siren is experimental, even more so than Feditext betas in general, so by default, it's off. to opt into Siren, open Feditext's preferences, scroll all the way to the end, select Siren from the "HTML parser" dropdown (instead of WebKit), and press the "Apply new HTML parser" button below it.

notes:

- do not switch parsers while writing a post: you will lose the post.
- the HTML parser is an app-wide setting, and can't be configured on a per-account basis.
- if you have issues with Siren, you can revert to WebKit from the same menu.

known issues that you don't need to report:

- blockquote lower vertical margins may be too big, causing the end of a blockquote's background rectangle to appear under the next normal paragraph. (however, the indents are still correct, so non-quoted text will not be indented.) this is related to
https://github.com/feditext/feditext/issues/48 and https://github.com/feditext/feditext/issues/164 but is (currently) worse in Siren.

#Feditext #Metatext
Rich text display: vertical margins are off for blockquotes, lists, and headers · Issue #48 · feditext/feditext

Blockquotes and headers have too much trailing vertical margin, blockquotes don't have enough leading, and lists don't have enough trailing. This sounds like a job for NSParagraphStyle.paragraphSpa...

GitHub
Feditext beta users: today's build 78 fixes the paging issue with yesterday's build 77. big thanks to everyone who reported the issue.

if you had to downgrade from 77 to 76, please open the TestFlight app to install 78 and re-enable automatic updates for Feditext.

#Feditext #Metatext
Feditext beta users: please do not update from build 76. build 77 has a bug that prevents scrolling to old home timeline posts or notifications. thanks to @mirabilos for reporting. we're looking into it

we'll expire the build ASAP, but if you've already updated to 77, you can switch back to build 76 from TestFlight. switching back will keep all your local data and you won't be logged out.

#Feditext #Metatext
Feditext beta testers: today's build 77 contains internal changes to the HTTP client and the API clients built on it, and shouldn't have any user-visible effects. there are no other changes, because the purpose of this release is to test those changes before building further on them. please let us know on the bug tracker if you see any new kinds of HTTP error.

update: build 77 has problems loading old home timeline posts. please stay on 76 for now; see downthread for how to revert to it.

for those familiar with Apple development: we've rewritten the clients to use Swift concurrency (aka
async/await) instead of Combine, which is more readable and easier to reason about. this is the first step in replacing Combine in as many places as it makes sense, which we'll weave in with other work as we go.

prospective testers: we're working through a two-week message backlog, and will be sending invites out today.

we know it's been a bit since the last update. thanks for your patience.

#Feditext #Metatext