2FA should be working on the latest build (:
Should be working in the latest build. Give it a shot and let me know!
Sure! I’ll add it in the next release (:
2FA is working in the build I'm about to upload. Waiting for the build to finish up 🥱 Edit: Xcode is not letting me post the build to TestFlight for some reason. Gonna update and hope that fixes it.
Good catch on the first one, 2FA is working in the build I'm about to push (along with some other things)
That reminds me the lemmy app I'm making doesn't show post body on link/image posts. Thanks for that lol. But yeah that's dumb it's literally a git server so idk what they mean by that
Yeah I haven’t implemented that yet. Now that public beta is out this will be my top priority. Thought I had more time 🤣
Where do you see “Git free”?
Player isn’t loading for me. Just gives a play icon with a line through it
I love forgejo. Only thing it’s missing for me is the ability to have a private repo with a public issue tracker. Gitlab has it but GitLab is really heavy, takes a pretty beefy server to self host
Theme switcher is up & running! Any requests?
I’ve finally got the theme switching logic sorted out and a preliminary UI done up. Getting ready to send this out to testers, but before that are there any requests for color schemes?
There will eventually be a theme creator and a community repo where people can share their custom themes. Need to build the backend for that. It will come along with push notifications. if it isn’t there already, hopefully I can get a PR raised and merged to add webhook support to Lemmy so all mobile apps can add push notification support(:
Thanks for the feedback! I can’t wait for you all to see what I’ve been working on. Haven’t been this excited about a project in a long time (:
It’s iOS 17 only. You need to be enrolled in the developer beta there are a ton of guides online if you’re interested, and I talk more about it in the other thread (:
Something weird is definitely going on. I can see my subscribed communities on the web interface, but for some reason the API is returning an empty list. Something must have changed with the API in this release. I also notice a lot of my communities show 0 posts, even the one I created which I know has posts on it. And that’s in the web interface.
Edit: it looks like when fetching subscribed communities, the query param is type, where it used to be type_. 🥲 the sorting is also different. If your sorting is set to active and there aren’t any active posts, the list will just be empty. Change to new or old and the posts will appear again.
Unfortunately that appears to be the case. I am certainly considering releasing a version that can run on older iOS versions, but I worry it would be an inferior experience. At the end of the day, I’m building this app in my free time and don’t foresee it ever becoming a significant source of income for me and my family. If I ever do decide to charge for the app it would be for auxiliary features like push notifications and would only cost as much as I need to keep the servers running to avoid operating at a loss. Anything extra I receive would be given back to the community in several forms. I plan on operating my own Lemmy instance so the extra funds would go towards that and anything leftover would be donated to Lemmy. The amount of extra time and effort required to build an app like Olympus is drastically reduced when utilizing the new frameworks available in iOS 17. On top of that it makes for a much more polished and responsive experience for users. If Olympus does ever one day have a significant userbase and I can justify the amount of effort required to support the older platforms I would undoubtedly do it in a heartbeat. I hate the feeling of alienating a large portion of my userbase but for the reasons I’ve given I ultimately decided that it’s better this way in the long run. Luckily there are a ton of other awesome Lemmy apps in active development for iOS!
Known Bugs and Upcoming Features
Hey all,
Wanted to make a post where we can keep track of the known issues and features that are WIP. Leave a comment below and/or create an issue on the issue tracker
Known Issues
- No animation when collapsing comments (they just vanish, working on it)
- No way to view saved posts
- Sometimes when you interact with a post (vote, reply, save), if you navigate to a new screen and come back shortly after the UI won't reflect your interaction (this is an issue on some instances and is a known bug with Lemmy. The change doesn’t come in from the API response. I'm working on a way to circumvent this without showing incorrect information)
- Some comments are missing whitespace
Features Currently Being Worked On
- Join posts with the same URL across iinstances
- Indicate when a post is on multiple instances in the feed view
- Separate comments by instance in the comments view
- Allow filter by instance in the com
That is correct. Until iOS 17 is released to everyone you will need to join the iOS 17 Beta to use Olympus.
This is because the new iOS version comes with a lot of powerful new features for developers and if I started building it without those features I would need to scrap a lot of my work and start over to take advantage of them.
Welcome to the Olympus for Lemmy Community!
I'm creating this community as a place for discussion around the upcoming Olympus for Lemmy iOS app. The TestFlight build is awaiting approval and should be available in the next 24 hours. In the meantime, here's a bit about the app and what to expect.
Motivation
I think a lot of us have an alien shaped hole in our chest that needs filling. I, like many of you, was not satisfied with the quality of many of the apps available for browsing lemmy. I got spoiled with Apollo and couldn't stand to settle, so I set out to build a similar experience for the Fediverse. While I've taken a lot of inspiration from Apollo, Olympus is by no means meant to be a direct clone.
Goal
I want to create a browsing experience that can be customized in every conceivable way. From visual personalization to content filtering, you will be able to change as much as is feasible about the app. A lot of the groundwork for this customization has been laid, but the settings are not yet user-accessible. In other