25 years later I still cherish this cup
Remote
Thomas Tempelmann
@tempelorg@iosdev.space
mastodon 4.7.3Indie developer since early 80s.
Mainly Mac, some iOS, rarely Windows. Specializing in file systems. Available for contract work.
230 Followers
85 Following
18 Posts
Joined November 25, 2022
Replying to
@ole@chaos.social Same here! I've added a "Release notes" menu entry to the Help menu of my apps that just open the release notes in the browser to alleviate that.
Pretty confident it's a toaster.
Replying to
And the apprentice never learning from its mistakes?
Replying to
@peternlewis@mastodon.social I made the same consideration. But it started already a few months ago, when suddenly, the app would not remember where I left it last - often the app now takes me back to the login or to the home page when I left it in the middle of watching a movie. And then you have to navigate to it awkwardly again. And then this latest incarnation where you can't even skip fwd/back any more with the usual shortcuts any more. Terrible.
Replying to
@octothorpe@mastodon.online That is when a text parser tries to store "rich text" in a not-so-efficient way in an html format. Better not ask how PDF is done, or you'll keep losing faith in modern computing.
Replying to
@RakowskiBartosz@hachyderm.io @thisismissem@hachyderm.io @WPalant@infosec.exchange Well, no. You can't demand the right to look into the internals of your partners - they have a right to privacy as well. You are instead "protected" by the law that requires the partner to protect your privacy interests, or by contracts. What that law is missing, however, is a way to universally verify that they do it correctly, e.g. by independent auditors. Which isn't often feasible, though. It's all a compromise, and it sucks.
@alldritt That link doesn't work for me, though.
This works: https://github.com/alldritt/aequery
Replying to
@twostraws Clarification please: Is this for iOS app only or does it work just as well for marketing macOS apps?
Replying to
Are you using TestFlight as a developer?
How do you deal with the following situation:
You've run a successful beta cycle on TestFlight and have now released the final product in the (Mac) App Store. But your TestFlight users are still on the beta track, and their app eventually gets disabled after 90 days. They get confused because they're not getting any idea that they have to drop the TF app and instead re-install the app from the Store.
Can that be avoided or resolved more elegantly?
Can someone enlighten me about Xcode support for pre-10.13 macOS deployment?
The release notes for Xcode 14 says that deployments targets < 10.13 wouldn't be possible any more, and I found that it would reset my min target to 10.13 then.
But now, when I open my 10.11 targeting project (Find Any File) in Xcode 26, it allows me to build for 10.11 again.
What did I miss? Did Apple reverts its decision not to supoprt pre-10.13 after a few Xcode 14 releases again?
Replying to
@rmondello@hachyderm.io I wonder: If I am still using systems that do not support passkeys, such as older macOS systems, should I allow websites to switch me to using passkeys? I have the impression that this will break my old style logins with those sites.
Replying to
@teilweise@layer8.space I did try to upload the released version to TF afterwards as well, but Apple's system won't let me. I would have to make a new version just to be able to keep the current one alive there.
Replying to
@gabrielesvelto@mas.to I always thought that the entire Intel CPU architecture was doomed with its over-complicated instruction set. I preferred Motorala designs. Do you have insights on how PowerPC and ARM (Mac) CPUs fare in in this regard? I suspect they use microcode as well, but it may be less complex? But then again, that may allow them to optimize in other areas more, which in turn raises the complexity just as well. (Oh, seeing you replied already, i.e. that your ARM base is much smaller)
Replying to
@obrhoff@mastodon.social @nicklockwood@mastodon.social I met someone a few years ago that used to work in Apple's App Store review team, which I only learned from a co-worker because the person was not even allowed to disclose that to people. When I accidentally mentioned it to someone else, I got shushed. And that was in Germany, where we have, I'd think, more worker friendly laws than in the U.S.