RT @codepo8@twitter.com "OMG terrible company $x says it only works on Chrome!", yell the people who exclusively use Chrome to surf the web and wonder why stats are so skewed.
:android: :chrome: Any takers for implementing the Web Share Target API in Mastodon?
It just landed in Chrome Canary on Android and it would take integration with the operating system to the next level, allowing users to easily share text from other applications in Mastodon.
@GNUDuffer Totally feel you. Donated via Patreon to a group of independent journalists that produced new and interesting content, but they totally didn't get how Patreon works. No updates, no engagement, no sneak peaks, no perks - they set it up as a donation box.
Would be interesting to see if the model Brave proposes catches on - would have preferred if they made it as an extension though, as I don't intent to switch browsers anytime soon.
"As LCD screens have advanced, designers have taken advantage of their increasing resolution by using lighter typeface, lower contrast, and thinner fonts.
But when you design in perfect settings, with big, contrast-rich monitors, you blind yourself to users.
To arbitrarily throw away contrast based on a fashion that “looks good on my perfect screen in my perfectly lit office” is abdicating designers’ responsibilities to the very people for whom they are designing."
Would love to see a follow up to the analysis The New York Times did in 2015 regarding the impact of ads on data usage. Doubt things improved - but then again when most of us refuse to pay and use ad-blockers, we kind of leave them with no choice.
@nolan@unarist@bea@ashkitten Looked some more into this and opened on issue for react-swipeable-view. TLDR the library is animating the right thing, but React just adds too much overhead when updating the DOM.
Took some time today to investigate why the swipe animations in Mastodon are janky in Firefox on Android. Of course the reason is too much JavaScript :mystery: