Maybe something like Munki, Salt, or similar, helps? https://www.munki.org/munki/ https://saltproject.io

Maybe Coursera, or other similar programs, or classes at a reputable local school. Caution: there are lots of shady schools. Here is an introductory (Scratch) class: https://pll.harvard.edu/course/cs50s-introduction-programming-scratch Then Harvard’s CS50 Python intro: https://cs50.harvard.edu/python/2022/ Further along, then maybe the Stanford Swift class: https://cs193p.sites.stanford.edu/ Apple presents Swift as an introductory language, and Apple and third-parties have lots of materials available to learn its capabilities. But you need to know some terms and concepts and a few algorithms. To find previous discussions about learning to develop apps around here, use this DuckDuckGo or Google search: site:discussions.apple.com learn Harvard Stanford python swift Getting going is probably an investment of two to four years of concerted study and class time, too. And then the learning just never ends.

1: accessing other websites and other network services can be leveraged by an adversary for command and control or for data exfiltration during a breach. (And some of the other apps and tools that can be involved with those other ports and services can themselves be vulnerable to exploits and a potential means of ingress.) 2: You’ll need to discuss that with Vercel support. Depending on the current hosting details, you may be headed for a dedicated host, which is prob preferable here anyway.

My (nuanced) answer: If you offer a quit in specific and appropriate circumstances, it may well pass app review. Otherwise, don’t. An example being as part of a completion dialog after performing a user-requested account deletion and data deletion procedure. (The only path left for the app in that state is starting an on-boarding.) Outside of specific and app-specific cases, I’d expect review problems.

Rent access to a Mac. Various hosting vendors exist.

Yes, the Apple Root Certificate Authority certificates expire. Apple Root CA-C2 and -G3 both expire in 2039. Details are here: List of available trusted root certificates in iOS 17, iPadOS 17, macOS 14, tvOS 17, and watchOS 10 Apple hasn’t updated the doc for the current 2024040500 certificates, so the above 2023071300 data is slightly stale.

Unenroll, and restore your pre-beta backup. There is no downgrade to iOS 17, which means restoring a pre-beta backup, or performing a factory reset, or waiting for iOS 18 later this year.

Here is how to: Unenroll Your Devices. There’s no downgrade, so if there’s no backup to restore from prior to installing the beta, you’ll be resetting and starting over, or will be waiting for iOS 18 later this year.

You can use ad hoc, or you can upload the app to TestFlight for testing. https://developer.apple.com/documentation/xcode/distributing-your-app-for-beta-testing-and-releases I’d usually suggest TestFlight. macOS apps can be notarized and distributed directly.

Short answer: find wherever the added SQLite was installed from whatever installed it, and its name, and add that as a library or SDK reference, and add the header. Long: I’d expect to either reference and link with the added SQLite in the library settings in the build, or to add the SQLite code itself (SQLite is very modular C). Here’s an example: SQLiteLib If you’re using Swift (you’ve not mentioned), I’d look at using a framework wrapper such as SQLite.swift. If you’re building using C or ObjC, you can pull the SQLite source code itself and the header directly into the project. sqlite3.h and sqlite3ext.h, IIRC. related SO thread

Lacking substantial context, so making some quite-possibly-wrong assumptions... Can you go after this password change from the server side, with what amounts for a forced password change setting? You can either accept and validate the password and force the password change on the server (probably preferable), or can accept any password (hazardous), and require a new password or (probably better) passkey be established. This server-side change might also require a little work on the client, depending on the details. And forced-password change mechanisms are baked into pretty much all enterprise directories, which means any installation involving a directory is going to have to contend with a server-requested password reset anyway. Backing up a step or two, this feature is right on the edge of a denial-of-service mechanism combined with a means for compromising existing accounts, too. If users can trigger this global reset, miscreants might well eventually explore its implementation details.

Find somewhere else to write your data. Here is an System Integrity Protection overview and some info about the read-only system volume, and here is an Apple video including info on the read-only system volume. Why are these areas becoming more difficult to access? You're effectively writing what is indistinguishable from malware. Writing outside of the user and app-related areas is undoubtedly only going to get more difficult, too. If you really do want to try this, maybe try this: https://developer.apple.com/forums/thread/649832 I don't have a macOS 14 Sonoma system available for this sort of hackery, so I'm not able to test those suggestions on Sonoma.

Theoretically? Sure. AppleScript is Turing complete, after all. In practice? Yikes, no, no, nope, nein, no. Natural language processing is no small matter. You'll here fundamentally need to identify exactly which words are nouns with some form of tagging. As has been used elsewhere as an example of the relative difficulty of this task, this sentence is semantically-valid English: "Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo buffalo". Even words you might think of as always being nouns—"butterfly", for instance—can be verbs. The rest of the problem here is housekeeping; of slogging through a database or some other storage for the identified nouns. The tagging? Yeah, not gonna try that in AppleScript. There's a book Speech and Language Processing by Daniel Jurafsky & James H. Martin, 2019, and the author Jurafsky has a draft of chapter 8 Part-of-Speech Tagging available online at Stanford. Alas, the URL isn't allowed here. AFAIK, macOS contains no APIs for tagging parts of speech.

Best discuss this and similar legal questions with your legal counsel, as the requirements, expectations, and options will vary by event details and by jurisdiction. This whether Private Relay, Tor, I2P, proxies, or any number of other means of obfuscation are used.

See if Viewing Sandbox Violation Reports gets you any closer. Also see what value is stored in errno, if sockfd has been returned containing -1. Something akin to: print("Error from socket(): \(String(describing: strerror(errno)))") I do dislike ChatGPT, having cleaned up source code "hallucinated" by that.