こんにちは。今後、GPT-4を使ったアプリケーションやサービスがたくさん登場してくると思います。その中には、たとえばSNSを利用したbotもたくさん出てくるでしょう（現在でもすでにありますけれど）。そこで質問なんですが、SNSでおしゃべりしている相手が、人間なのか、GPT-4などの技術を使ったAIなのかを識別するにはどのような会話をしてみればいいでしょうか。一般的なAIでは難しいかもしれないので、GPT-4に限ってもいいです。あなたの考えを聞かせてください。
GPT-4のような高度なAIと人間を識別するのは、時に難しいことがあります。しかし、いくつかの方法を試してみることで、相手が人間かAIかを見極めることができるかもしれません。
Disclaimer: This piece is written anonymously. The names of a few particular companies are mentioned, but as common examples only.
This is a short write-up on things that I wish I'd known and considered before joining a private company (aka startup, aka unicorn in some cases). I'm not trying to make the case that you should never join a private company, but the power imbalance between founder and employee is extreme, and that potential candidates would
以下転載:
| # The trick is to link the DeviceSupport folder from the beta to the stable version. | |
| # sudo needed if you run the Mac App Store version. Always download the dmg instead... you'll thank me later :) | |
| # Support iOS 15 devices (Xcode 13.0) with Xcode 12.5: | |
| sudo ln -s /Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport/15.0 /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport | |
| # Then restart Xcode and reconnect your devices. You will need to do that for every beta of future iOS versions | |
| # (A similar approach works for older versions too, just change the version number after DeviceSupport) |
| extension CVPixelBuffer { | |
| func deepcopy() -> CVPixelBuffer? { | |
| let width = CVPixelBufferGetWidth(self) | |
| let height = CVPixelBufferGetHeight(self) | |
| let format = CVPixelBufferGetPixelFormatType(self) | |
| var pixelBufferCopyOptional:CVPixelBuffer? | |
| CVPixelBufferCreate(nil, width, height, format, nil, &pixelBufferCopyOptional) | |
| if let pixelBufferCopy = pixelBufferCopyOptional { | |
| CVPixelBufferLockBaseAddress(self, kCVPixelBufferLock_ReadOnly) | |
| CVPixelBufferLockBaseAddress(pixelBufferCopy, 0) |
| <!-- | |
| This disables app transport security and allows non-HTTPS requests. | |
| Note: it is not recommended to use non-HTTPS requests for sensitive data. A better | |
| approach is to fix the non-secure resources. However, this patch will work in a pinch. | |
| To apply the fix in your Ionic/Cordova app, edit the file located here: | |
| platforms/ios/MyApp/MyApp-Info.plist | |
| And add this XML right before the end of the file inside of the last </dict> entry: |
| # Set variables in .bashrc file | |
| # don't forget to change your path correctly! | |
| export GOPATH=$HOME/golang | |
| export GOROOT=/usr/local/opt/go/libexec | |
| export PATH=$PATH:$GOPATH/bin | |
| export PATH=$PATH:$GOROOT/bin |
| func createGIF(with images: [UIImage], loopCount: Int = 0, frameDelay: Double, callback: (data: NSData?, error: NSError?) -> ()) { | |
| let fileProperties = [kCGImagePropertyGIFDictionary as String: [kCGImagePropertyGIFLoopCount as String: loopCount]] | |
| let frameProperties = [kCGImagePropertyGIFDictionary as String: [kCGImagePropertyGIFDelayTime as String: frameDelay]] | |
| let documentsDirectory = NSTemporaryDirectory() | |
| let url = NSURL(fileURLWithPath: documentsDirectory)?.URLByAppendingPathComponent("animated.gif") | |
| if let url = url { | |
| let destination = CGImageDestinationCreateWithURL(url, kUTTypeGIF, UInt(images.count), nil) | |
| CGImageDestinationSetProperties(destination, fileProperties) |
| class MyCell: UITableViewCell { | |
| override init(style: UITableViewCellStyle, reuseIdentifier: String?) { | |
| super.init(style: style, reuseIdentifier: reuseIdentifier) | |
| configureView() | |
| } | |
| required init(coder aDecoder: NSCoder) { | |
| super.init(coder: aDecoder) | |
| configureView() |
