mastodon
4.7.0-beta.1
Design, development, discourse. He/him.
Here to learn and share what I've learned, but -- knowing me -- probably man(1)-splaining. Please tell me when that's the case.
Design, development, discourse. He/him. Here to learn and share what I've learned, but -- knowing me -- probably man(1)-splaining. Please tell me when that's the case.
_Finally_ upgraded my 12.9in #Apple #iPadPro (4th gen) to #iPadOS 26.x a couple days ago.
Glad I waited! I'm not seeing any of the major UI bugs reported in the early days, at least in the apps I use. I am using #WindowedApps and the #MenuBar implementaton is _very_ odd, but it's better than not having it (for me.) I do like the pointer being arrow-shaped, since I mostly use the trackpad and/or controller these days.
I certainly suggest Settings > Display & Brightness > Liquid Glass = Tinted.
Design, development, discourse. He/him. Here to learn and share what I've learned, but -- knowing me -- probably man(1)-splaining. Please tell me when that's the case.
Something very #SesameStreet meets #AppleCommercial, but still 100% #SpikeJonze about this:
It's really lovely. Just the kind of thing I feel like I needed right now.
Design, development, discourse. He/him. Here to learn and share what I've learned, but -- knowing me -- probably man(1)-splaining. Please tell me when that's the case.
Design, development, discourse. He/him. Here to learn and share what I've learned, but -- knowing me -- probably man(1)-splaining. Please tell me when that's the case.
@tantramar @gumnos I wholly agree that most of these are shared problems, but I have to — respectfully — disagree on points 1. & 4.
JavaScript and captcha requirements are often a problem for website users (maybe just running older/lower-end hardware, limited/inconsistent Internet access, or accessibility issues due to disabilities) and the spam is still a problem for the receiving user
I encounter this frequently, especially on mobile devices where switching apps may cull browser tasks
Design, development, discourse. He/him. Here to learn and share what I've learned, but -- knowing me -- probably man(1)-splaining. Please tell me when that's the case.
@tantramar @gumnos I'll counter that using a form has many downsides (naturally, many still shared by email):
Design, development, discourse. He/him. Here to learn and share what I've learned, but -- knowing me -- probably man(1)-splaining. Please tell me when that's the case.
Design, development, discourse. He/him. Here to learn and share what I've learned, but -- knowing me -- probably man(1)-splaining. Please tell me when that's the case.
Design, development, discourse. He/him. Here to learn and share what I've learned, but -- knowing me -- probably man(1)-splaining. Please tell me when that's the case.
Design, development, discourse. He/him. Here to learn and share what I've learned, but -- knowing me -- probably man(1)-splaining. Please tell me when that's the case.
Apparently, I don't post much here on Mastodon when my mental health is poor.
Design, development, discourse. He/him. Here to learn and share what I've learned, but -- knowing me -- probably man(1)-splaining. Please tell me when that's the case.
Design, development, discourse. He/him. Here to learn and share what I've learned, but -- knowing me -- probably man(1)-splaining. Please tell me when that's the case.
Design, development, discourse. He/him. Here to learn and share what I've learned, but -- knowing me -- probably man(1)-splaining. Please tell me when that's the case.
Design, development, discourse. He/him. Here to learn and share what I've learned, but -- knowing me -- probably man(1)-splaining. Please tell me when that's the case.
@flameshot@fosstodon.org I will admit, I'm not actively using Flameshot, but have considered it in the past. (Still using maim/slop/``Gromit-MPX` under X in the ancient WM I maintain.)
Design, development, discourse. He/him. Here to learn and share what I've learned, but -- knowing me -- probably man(1)-splaining. Please tell me when that's the case.
Design, development, discourse. He/him. Here to learn and share what I've learned, but -- knowing me -- probably man(1)-splaining. Please tell me when that's the case.
Design, development, discourse. He/him. Here to learn and share what I've learned, but -- knowing me -- probably man(1)-splaining. Please tell me when that's the case.
Design, development, discourse. He/him. Here to learn and share what I've learned, but -- knowing me -- probably man(1)-splaining. Please tell me when that's the case.
Design, development, discourse. He/him. Here to learn and share what I've learned, but -- knowing me -- probably man(1)-splaining. Please tell me when that's the case.
Design, development, discourse. He/him. Here to learn and share what I've learned, but -- knowing me -- probably man(1)-splaining. Please tell me when that's the case.
Design, development, discourse. He/him. Here to learn and share what I've learned, but -- knowing me -- probably man(1)-splaining. Please tell me when that's the case.
Design, development, discourse. He/him. Here to learn and share what I've learned, but -- knowing me -- probably man(1)-splaining. Please tell me when that's the case.
Design, development, discourse. He/him. Here to learn and share what I've learned, but -- knowing me -- probably man(1)-splaining. Please tell me when that's the case.
Design, development, discourse. He/him. Here to learn and share what I've learned, but -- knowing me -- probably man(1)-splaining. Please tell me when that's the case.
Design, development, discourse. He/him. Here to learn and share what I've learned, but -- knowing me -- probably man(1)-splaining. Please tell me when that's the case.
Design, development, discourse. He/him. Here to learn and share what I've learned, but -- knowing me -- probably man(1)-splaining. Please tell me when that's the case.