Generally on Apple platforms the move here would be putting the shared binary into a dynamic .framework rather then trying to eliminate the shared dependency. Is this a limitation of authoring it in Go that it has to be entirely static?
1,618 karma · joined May 3, 2011
zacwest@^^domain^^
I extensively use the API for pastebin and URL shortener. It's very much a selling point for me -- love being able to control things on the command line with a few simple scripts.
Great package of tiny little web apps for a good dollar amount and a great author.
Call me a pessimist but it seems really unlikely that AI will cause problems so much as continually increasing automation. It makes such terrible choices around qualitative decisions and increasing existing AI to a general solution pretty much always fails.
> Tech companies: Do you want to help put your users behind bars by handing over the data you hold about them in response to legal demands by law enforcement? Do you not really care if they go to prison, but do care about the bad PR you’ll get if the public finds out about it? Then start planning now for what you’re going to do when – not if – those demands start coming in. Data minimization and end-to-end-encryption are more important than ever. And start worrying about internal access controls and insider threats, too: don’t assume that none of your employees would ever dream of quietly digging through users’ data looking for people they could dox to the police in anti-abortion jurisdictions. Protecting your users is already so hard, and it’s going to get a lot harder. Update your threat models.
> Deleted Artist
> Sorry, Strays by Ghost Mice is no longer available. Please contact Ghost Mice for more information.
One company gave me a free version of their paid offering because my email address was me@them.my.domain, which triggered their "is an employee?" check. (I reported it to a friend who worked there, but they didn't prioritize fixing it. Lasted a while.)
Uber tried to make me change my email address because:
> As much as we appreciate your enthusiasm, and value you as a loyal rider, I do need to ask if you could, please, update your email to something that doesn't use "Uber" in it, as that's technically a trademark violation.
> I apologize for any inconvenience that may cause and thank you for your cooperation. If I can help further with making that change to your email, please let me know.
They backed down, but it was pretty amusing to get this email in response to a totally unrelated one.
There's no analytics nor reporting in the app. I've been slowly removing[0] things that talk to servers other than your Home Assistant server, but your private information's never left the device. Right now the app will talk to 2 additional sources, both of which you can disable in the Privacy settings:
1. alerts.home-assistant.io, which will alert for security issues but is strictly a JSON file it loads [1]
2. Firebase Cloud Messaging, for push notifications (since we can't talk to APNS directly in HA)
FCM is a dependency I'm actively trying to kill off in favor of an implementation that is both end-to-end encrypted and talks directly to Apple's Push Notification Service. Apple would not allow a solution where HA talks directly to APNS as they do not want that many active connections, and it would require disclosing private keys for the App Store account.
Unless Robbie wanted to give me his personal Apple ID password, moving the app to the Nabu Casa App Store account was the only way for me to do anything with the app.
[0] https://github.com/home-assistant/iOS/pull/2010 [1] https://github.com/home-assistant/iOS/blob/861a40a50aa201ff4...
Apple have created and embraced an entire language (Swift) around the idea that things like memory safety are important, but you cannot just rewrite an entire operating system overnight into a new language.
I do not believe SPM is mature enough to be the entire platform, and worst yet if you experience any problems it is entirely impossible to customize the behavior. I think it's going to be another year or 2 before dropping CocoaPods entirely is a fair choice for libraries -- SPM works for the most basic use cases, but not all.
Does seem like they have noticed enough to start escalating it though: https://twitter.com/sonic/status/1336013450909257730?s=21
I also believe that, right now, they're just rubber stamping all app reviews. They cannot handle this volume.
1. Download, extract, and run the new version of Xcode.
Note: you cannot upload builds for production App Store with pre-GM builds. You _must_ use the GM or production Xcode.
It's a 12 GB download, and extracting takes 20 minutes. Factor in about an hour here. Especially around when it's posted you can expect a very slow download.
2. Build, execute and validate the app at least _launches_.
Maybe another 30 minutes.
3. Create and upload an archived build to Apple.
Maybe another 30 minutes.
4. Wait for the uploaded build to finish processing.
This takes somewhere between 1-3 hours.
5. Submit the finished-processing build.
Manual inspection of metadata, screenshot uploading, etc. Let's call it 20 minutes.
6. Wait for approval from Apple.
Who knows how long.
7. Release.
So this is somewhere around 4-5 hours at _minimum_ of work to get the build uploaded.
When you're told at 11am that users will have it in their hands the next day, even if you are incredibly prepared, there's simply very little time to actually do the above in a safe way. And if you're not on Pacific Time, you're going to miss this window entirely.
Not to mention Apple uploaded a GM build of Xcode around noon, and then silently replaced it with an updated version sometime later without explaining what the difference was. Fun stuff.
Also: the GM build has regressions.