Lena Riess 📚💚🤍@Shkspr80 @ivory @MonaApp
I switch between from time to time. More #MonaApp than #Ivory. Mona is technically far ahead. But with so many features that's not always an advantage. Ivory is more good looking and compact but it's always been a bit behind.
@Shkspr80 @ivory
That is true. Most previews are correct. But in my timeline there are a few that are not. It should be possible to solve this problem.
Here an example of one of them.
Left on #Ivory, right on #MonaApp.
That is true. Most previews are correct. But in my timeline there are a few that are not. It should be possible to solve this problem.
Here an example of one of them.
Left on #Ivory, right on #MonaApp.
The Peter Pan of Nerdery™Been a while…
.. since I posted an AI video analogy of what the #MonaApp dev did to his paid customers
People who paid the one-time fee for #MonaApp then paid AGAIN for the damn thing be like..
Matthew Whitaker@MonaApp Anyone else using the Mona app running into this?
On the latest version (and this was also happening for me back on version 6), I’ll be typing—either with the standard iOS keyboard or Braille Screen Input—and the keyboard just randomly disappears. Then I have to go back, find the text field again, double tap, reposition my cursor… and sometimes it just drops the keyboard again. Rinse and repeat.
This makes it really tough to consistently write posts or replies, especially using VoiceOver.
Would love to see this fixed—Mona is great otherwise.
#Accessibility #VoiceOver #iOS #Blind #BrailleScreenInput #MonaApp #BugReport
てんせき a.k.a.みんないいこ。キャッシュをクリアしたら読めた。#monaapp
Jupiter Rowland@Mark Whybird Sounds like @Mona app basically behaves like the Mastodon pre-4.4 Web interface; in fact, I think I've read somewhere that it's still partly stuck on a Mastodon 3 level.
One issue with this is that the Mastodon pre-4.4 Web interface didn't automatically blur images in posts that have CWs. Instead, when you have images in a CW'd post, Mastodon flags the images sensitive. Mastodon's Web interface blurs images that are flagged sensitive, and I guess so does Mona.
However, most of the rest of the Fediverse doesn't support this Mastodon-specific, non-standard sensitive flag for images. In CW'd image posts from somewhere else than Mastodon, the images will generally not be flagged sensitive, Mastodon won't blur them, and Mona probably won't either.
For example, here on Hubzilla, I could make people click up to four times before they see an image. First, if they have NSFW installed, they have to click an automatically generated content warning. Next, they have to click a summary plus Mastodon-style content warning. Then they have to click a spoiler tag that reveals the blanked-out image. Lastly, they have to click the image to unblank it.
Mastodon/Mona users, on the other hand, will see the very same image below the very same post immediately, un-CW'd, unblurred.
This is why I won't go back to posting images here on Hubzilla and stick to (streams) for that: (streams) can set the Mastodon-specific sensitive flag by adding one or two particular hashtags to a post. At least I hope it still does that.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Mastodon #Hubzilla #Streams #(streams) #MonaApp
One issue with this is that the Mastodon pre-4.4 Web interface didn't automatically blur images in posts that have CWs. Instead, when you have images in a CW'd post, Mastodon flags the images sensitive. Mastodon's Web interface blurs images that are flagged sensitive, and I guess so does Mona.
However, most of the rest of the Fediverse doesn't support this Mastodon-specific, non-standard sensitive flag for images. In CW'd image posts from somewhere else than Mastodon, the images will generally not be flagged sensitive, Mastodon won't blur them, and Mona probably won't either.
For example, here on Hubzilla, I could make people click up to four times before they see an image. First, if they have NSFW installed, they have to click an automatically generated content warning. Next, they have to click a summary plus Mastodon-style content warning. Then they have to click a spoiler tag that reveals the blanked-out image. Lastly, they have to click the image to unblank it.
Mastodon/Mona users, on the other hand, will see the very same image below the very same post immediately, un-CW'd, unblurred.
This is why I won't go back to posting images here on Hubzilla and stick to (streams) for that: (streams) can set the Mastodon-specific sensitive flag by adding one or two particular hashtags to a post. At least I hope it still does that.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Mastodon #Hubzilla #Streams #(streams) #MonaApp
nSonic