@ivory macOS Version: IMO the black lines through the text isn't ideal to read. Also, the monk in me screams at the squished border-radius at the 3% example.
As for polling itself, love it. The word-wrap was really important.
@console That's a slightly unfortunate result of using the high contrast theme. We have a very limited and specific set of color variables to power the whole app and this is one of the edge cases. Can see if we can improve that slightly, but adjusting colors in one area affects them everywhere else in the app.
@ivory hm, that’s strange. I wasn't aware I had the high contrast theme enabled. I never need to do that in any app. I must have mis-clicked at some point. My apologies.
Just turned it off, wow: Everything is so much nicer to look at. Also the polls are easier to read! I think the high contrast doesn't help in this case.
@console Yea we will have to see if we can make slight adjustments to the high contrast colors, but as I mentioned it's tough because changing a color affects the same color everywhere in the app. 🙂
@abosio you are definitely in the minority. We received constant complaints about the single tap to vote. It worked better on Twitter, but there’s more options here. 🙂
@maxfenton you set that on your instance website settings and it will be reflected in Ivory. Might take half a day for ivory to check that setting though. If you want it to update right away, just go to your account settings within ivory and hit the “clear account cache” button.
@Chancerubbage We always set updates to roll out slowly over a week. That way if there's a huge bug we don't want everyone to get, we can stop the release, fix it, and then release again. But users who follow us probably want to get updates ASAP so we like to announce them here if you want to download right away. 🙂
@ivory I’m still hoping for filtering tools to reduce seeing duplicate posts. Eg if I’ve seen a post, and someone I follow boosts it, or worst of all if I boost it, I see it again (and again).
@JetForMe If you are boosting from another timeline, it's going to appear at the top of your home timeline no matter what. My original response was because I was under the impression you were boosting a post and it was appearing again at the top of the same timeline.
@JetForMe That's the confusing part. We've tested this hundreds of times and when you boost a post in your timeline, it doesn't appear on top for us. The post you boosted just gets a badge. Feel free to send us a recording of what you see.
@JetForMe alright check these 2 things. Make sure “hide duplicate boosts” is on in your ivory account settings. And then check your mastodon website settings to make sure this setting is on.
@JetForMe so we are thinking it might just be the way your particular instance is working. When you boost a post lower on your timeline on the website, is the behavior the same? What about if you do it from the official mastodon app?
@ivory As far as I can tell, no, my instance is not showing posts I boost (via the web UI) again in my timeline. I boosted a post, then refreshed the page to see if it would appear; it did not. It's a stock v4.2.3 install from source (not Docker).
@JetForMe next time you experience this with a post, check that post to see if it’s coming from a non-mastodon instance. Feel free to send us a link to that post as well. The only thing we can think of at this point is you happen to be boosting a post from a non-mastodon instance and sometimes they do things a bit differently.
@JetForMe ok. At this point it seems like you are the only user we are aware of with this issue. It’s definitely not ivory. But still no idea what is causing it.
@sayrer We know there have been some issues with the mentions and notifications tabs syncing between mac and iOS. We plan to dig deeper into that issue next.
@ivory looks like there’s a bug in the polls logic to calculate the bars. Note in this screenshot that I voted for the third option, but it shows 100% (of 2 votes) on the second option. Should be at least some percentage on the option I voted for.
@wrightfully Might just be some sort of server lag. But we are keeping an eye on it. Going back to the timeline and then to post detail again should refresh the data.
Add comment