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.
Our apologies, there were HTTPS errors for quite a while there due to an expired certificate. This has now been resolved.
While the https:// support is new, we will always keep the non-secure http://www.unna.org/ URLs for direct access from Newtons and retro hardware. It's always a good backup in case of HTTPS issues too.
_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.
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.
@tantramar @gumnos I wholly agree that most of these are shared problems, but I have to — respectfully — disagree on points 1. & 4.
1. 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
2. I encounter this frequently, especially on mobile devices where switching apps may cull browser tasks
@tantramar @gumnos I'll counter that using a form has many downsides (naturally, many still shared by email):
1. Still a target for spammers, often requiring JS captchas and such
2. No guarantee the destination is checked or left to collect spam
3. Doesn't provide the user with actual contact info
4. Higher liklihood of message data loss (user must remember to copy form content before submitting because an error often results in loss of the message content)
5. Privacy concerns
This is a good initial response to my new video where I show "FireJam", my new C application that makes old compact macs a synth, including its in-house Sound Driver and also external MIDI hooks, both IN and OUT.
Keep the suggestions for improvements coming, I got..... (1/2)
https://youtu.be/gliJVwzRifA
An interesting article¹ by Spencer Mortensen on obfuscating email addresses on web-pages, detailing how well each technique has worked.
While all the more advanced techniques had much higher blocking-success, I dislike how they rely on CSS or JavaScript which breaks in most of the simple text-mode browsers. For inline-text email addresses, the comment method
me@examp<!-- comment -->le.com
seemed to hit the sweet-spot of working in all browsers, yet effectively eliminating 98% of spamming attempts.
However, that doesn't appear to work in a mailto: link,
<a href="me@examp<!-- comment -->le.com">Contact me</a>
so it might make more sense to use the Entities method in that case:
<a href="mailto:me@example.com">Contact me</a>
@csilverman @splorp @proedie @likesoldmacs @falken The hardest parts of really creating a new market is decisiveness. Especially in one so personal as to be carried on one's person all of the time and to store & retrieve intimate details. Then try pushing the envelope with new technologies and interfaces that aren't yet proven.
It was much easier for Palm to then create a stripped down and affordable (if significantly less powerful & resilient) PDA, once it had been fully realized.
Morgan Aldridge
UNNA
1Bit
Tim Chase