> Weird to add them to the list when they don't build a browser any more
It seems like their browser engine is still being supported for use in "Universal Windows Platform" apps, or at least that's what Wikipedia says.
21 karma · joined July 30, 2021
It seems like their browser engine is still being supported for use in "Universal Windows Platform" apps, or at least that's what Wikipedia says.
Linux users can experience this now by using sed on macOS
I fall under this. I'll be upgrading from an 11 Pro this time around mainly because I've let my battery go bad.
We can do most things from the simulator and when we need bluetooth or CoreLocation we can always run the app as a Mac app and use the computers chips.
The job title is a nice excuse to get the latest and greatest but it's not strictly necessary.
I think the key word in OPs comment is "effectively".
The tools for building cross platform Swift exist and work in various levels but they aren't at the point where you would want to choose Swift over existing cross platform tools.
I had to add the start on first thread flag to prevent errors and start a launch. I do get stuck after `Starting UI Subsystem` gets logged but I havent put any real effort into trying to debug that yet.
Very in my opinion, but I'm coming from a bike packers perspective.
Start the route tubeless and run it until it fails. When that happens throw a spare tube (that you should be carrying anyways) in it. If that goes flat, patch it.
Converting back to tubes is easy: take the value stem out -> put in tube. Yes, it's messier but it's not like you're showering regularly anyways.
> Being able to locally resupply with a compatible sealant is the main impediment
I would think that tubeless setup + plugs with spare tubes + a patch kit would get you far enough for this to not be a major issue. Carrying a small bottle of sealant would help. Worst case, you run tubes the rest of the trip.
Note: These are just my thoughts as a (formerly) sponsored bike packer.
Git adds some author information to each commit [1]. You can set those values project by project, and you can also set them globally.
To set a name and email to default to on all repos, you'd do this:
`git config --global user.name "Topsoil"` `git config --global user.email "topsoil@example.com"`
To set different committer info for a repo, you'd run the same commands without the `--global` flag while in the root directory of the project.
When this person got re-interested in their project, they decided to squash all the commits into one new commit, but forgot to change their name and email on the repo and as a result exposed their real identity when they published the code on GitHub.
I had to look up what f-list was, and it seems to be some kind of furry role-playing community? (i didn't do any research other than briefly looking at the first page of google) so i understand why this person DCMA'd themself.
The attack mentioned in the Wired article[1] relies on iMessage asking the sandboxless Springboard[2][3] to deserialize a maliciously crafted field, included in the incoming iMessage, to escape the sandbox. This specific vulnerability doesn't appear to apply to other apps.
[1] https://googleprojectzero.blogspot.com/2019/08/the-fully-rem... [2] https://en.wikipedia.org/wiki/SpringBoard [3] https://iphonedev.wiki/index.php/SpringBoard
Normally if I want to use a permission, say location, I need to provide a value for given permission in my app's `info.plist` file, and if I don't and the app tries to grab the current location, it crashes with logs yelling at me to provide a description for the location privacy key.
With local network permissions it's different.
I've never had to do any local networking in my career as an iOS dev so downloaded Apple's peer to peer example app (https://developer.apple.com/documentation/network/building_a...) and removed the `Privacy - Local Network Usage Description` key/value pair from the `info.plist` file and ran the app on my device.
I fully expected a crash with a description telling me to add this key but iOS just filled in the missing description with a default value and asked away. I wonder why that permission is treated differently from the rest?