Just a reminder (as there seems to be quite the influx of support email 🙄 ) that Mercury does not and will never support instances like Gab or its various incarnations and spinoffs.
There's a complete list of unsupported instances on the help page here: https://onmercury.app/help
There is a known issue where people who started using Mercury at version 1.6 don't stay logged in. There is a fix on its way that should be out shortly!
Anyone effected might also need to de-authorise previous versions of Mercury from their account so as to not receive multiple notifications — https://your_instance_domain_here/oauth/authorized_applications
@jwildeboer hey there! Sorry, I just saw this and you may have worked this out by now. But it seems that's the "view detail" button that lead you there. The reply button is the left-pointing arrow 🙂 if tapping that takes you to the detail page, then let me know as that's indeed an error 😬
@weirdwriter oh wow! I literally just saw it come in. That's very generous of you! Thank you very much! I'm so glad that you enjoy using the app 😊
@devinprater @weirdwriter last time I checked it's not possible to grab the limit from the instance. I did check around 6 minus ago though, so that may have changed. I also looked at adding this to the API so that other apps can use it too, but got distracted and never finished submitting the code. For what it's worth though, the composer in Mercury won't disable the send button if a toot goes over the 500 character limit to compensate for the fact that not all instances use the default value.
@weirdwriter all the VoiceOver stuff you've been helping with has been released to the AppStore version of the app 👏🥳
@weirdwriter well, the funny thing is that the button was supposed to be at the top right all along, but I broke it while testing out some recent changes 🤦🏽. It'll be back in the next release
@weirdwriter hey! Yep, I can add this too 😊 I'll have it be spoken after "boosted" if a status has been boosted.
@weirdwriter oh cool! Yeah that is a good idea :) thanks again for all your feedback here too, I appreciate you taking the time to do that.
@weirdwriter yep! I have been trying this approach out over the last few days and it seems good to me and I can't wait to send out a TestFlight.
I am thinking the list of actions will be something like boost, reply, favourite, details, author, links, hashtags.
There is also a "more menu" action that allows you to block a user or a domain as well as mute and report so I want to work that in to the actions list too, but I feel it may get too long. Is there a reasonable limit of actions a thing should have?
@weirdwriter oh sorry, I have added some now. Feel free to request a tag in the issue report and I'll tag it appropriately too
@weirdwriter hmmm good question, I am using a github project to track issues — https://github.com/dNitza/mercury-issues/issues , but you can also email them to mercury at dnitza dot com or just a public or direct message here is also fine. I'll be adding them to the tracker on GitHub anyway so there is some public visibility over what's currently been reported :)
@weirdwriter this is currently a limitation brought about by my lack of knowledge about the web push API and how to get the notification type from the push payload. It's something that is on my list to address :)
@weirdwriter ah this is perfect! Thank you :) And yes, I'll set it up with those 2 gesture / action combos and add the rest around that.
@weirdwriter Hey Robert! Thank you for giving Mercury a go, I really appreciate it.
I have been trying for ages to work out how to best add the ability to interact with toots and had never stumbled on Voiceover's custom router actions. I think that's exactly what I was looking for, and yes, I would love to set them up to enable interaction with toots. Thanks for the tip! I'll be giving it a go shortly and will hopefully have something out in the next update.
@marcozehe Also, if you have the time, could you elaborate on what makes the layout work for you? I have had some feedback that the menu screen before the timeline view feels clunky and am exploring ways to reduce the friction there, but I don't want to sacrifice any accessibility affordances in doing so.
A Mastodon client for iOS made by @nitza
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!