It is our policy not to make features-for-donations transactions, as we feel that would compromise the spirit of the project and set a dangerous precedent that could lead to development becoming beholden to the wealthiest donors. We really appreciate your enthusiasm and your generosity, though--we're going to be busy for a little while getting 2.0 up and running, but we can tentatively scope widgets for 2.1!
Yes! We aren't happy with the current state of our media viewer. 2.0 is a backend-focused rewrite, so probably won't have a new media viewer on launch, but it's without a doubt high on our list of important features.
Hard to say. Our iOS compatibility policy guarantees compatibility until iOS18 reaches 75% market share; after that, I can't make any promises. We take the decision to drop compatibility very seriously, and try to only do so when the features offered by the newer iOS are valuable enough that we would be compromising the potential quality of the app by ignoring them.
Yes. We're still working out some UX concerns stemming from the fact that it's very slow to search posts and comments compared to communities, but it's in the plans.
We're reluctant to give concrete time estimates since our development time is constrained by our day jobs and other responsibilities, but we hope to have 2.0 in early TestFlight on a schedule roughly in line with our release cadence (~2mo).
We don't plan to release any new features to the 1.x codebase after 1.3, but we will continue to fix major bugs and maintain compatibility against changes to the Lemmy API while we bring 2.0 up.
We maintain a client-side list of instances supported by lemmy-status.org. Looks like we just forgot to add toast.ooo--should be fixed in the next build.
We plan to completely overhaul our markdown handling for the next major release, which will include both properly handling Lemmy's dialect quirks and integrating markdown editing tools into the composer.
App Store Connect reports there are a couple hundred empty spots, but we've had issues in the past with it reporting empty spots on the dev side but not letting more users join.
That's unfortunately not currently supported by the Lemmy backend. There is an issue open for it, though it doesn't appear particularly active right now.
We have some major changes in development that might make this feasible to implement client-side--I've put up an issue for it, but can't make any promises pending a more thorough technical investigation.
There are both technical and design reasons for the change.
Technically, it lets us rip out a lot of logic that handled the differences involved in loading and displaying your own profile vs someone else's; from a design perspective, this makes your profile page a much more logical grouping: "content you created" instead of "content you created and also content you saved." Feeds is already the root category for "content other users created," with each item (All/Local/Subscribed/Community) displaying a filtered subset of that content, a grouping into which Saved fits much more naturally.
You can pick which of these to use via Settings -> Open Links In Browser (on will use system browser, off will use in-app browser). Right now we don't support opening in a third, non-system-default browser.
Saved was the odd man out in the profile page--everything else there is your own authored content
Saved is a feed containing a subset of content generated by other users. Every other such feed was under Feeds; now all such feeds are under Feeds
This way, what you see on your profile page is the same as what other users see on your profile page
By extension, the code is much nicer this way because we don't need to do as much conditional rendering and processing in the user page--we can use the same component with very little modification to display your own profile or somebody else's
This also lets us add the Saved feed to the app shortcuts menu without making that horribly inconsistent--the four shortcuts are the four header items in the Feeds tab
It is our policy not to make features-for-donations transactions, as we feel that would compromise the spirit of the project and set a dangerous precedent that could lead to development becoming beholden to the wealthiest donors. We really appreciate your enthusiasm and your generosity, though--we're going to be busy for a little while getting 2.0 up and running, but we can tentatively scope widgets for 2.1!