215 karma · joined June 10, 2015
Their development and QA process is either disorganized to the extreme, or non-existent.
...and I got rejected by HR, because I didn't have 8 years of working experience at 23.
Still the funniest job hunting story I have.
https://learn.microsoft.com/en-us/legal/cognitive-services/o...
Fun trick: convert ProRes RAW to cDNG. You now have 59.94 raw DNGs per second to choose a photo from.
So yes.
```
I do understand what you want, but we're not going to make that change at this time.
This probably isn't the answer you wanted, but I'm afraid we can't be any more help with this issue. I'm marking this ticket solved. Please open a new ticket if you need anything else.
```
https://www.androidpolice.com/google-shutting-down-assistant...
We use it and don't plan on switching for a few reasons, but I would not recommend it to most folks.
I still have my XPS 13 Developer Edition, but dealing with quirks caused more lost time than I saved with i3wm. Dell has questionable UEFI firmware, and GPU drivers (aside from Intel) were a constant source of kernel panics every few weeks if I ever bumped my eGPU cable.
For incoming emails, Cloudflare Email Workers are $0 per email and SendGrid is also $0 per email. We only pay for the cost of the Worker with this setup.
2. Would not pay for click tracking. Might use it if it’s free.
3. We probably won’t use MailChannels again yet since we want to use AMP emails and ticket #221628 was handled pretty poorly. (We made our own MailChannels-like API for AWS SES after the frustrating experience.)
https://github.com/aimoda/cloudflare-worker-to-aws-lambda-fu...
We don't have this in any public example yet, but here's our simple trick with Workers on how to bypass needing to pay for Amazon API Gateway or CloudFront but still get routed to the nearest AWS location:
1. Add add Lambda Function URLs as records in a latency based record on Route 53. (Lambda Function URLs do not support custom domains, so you cannot use this record directly.)
2. Have the Worker do a fetch to `https://cloudflare-dns.com/dns-query` on the Route 53 CNAME to discover what lowest latency Lambda Function URL hostname is.
3. The Worker can then fetch the Lambda Function URL using the discovered hostname.
cf.worker.upstream_zone ne "" and not cf.worker.upstream_zone in {"aimoda.workers.dev" "ai.moda"}
I'm not entirely sure if this change does anything, since it appears that employers can still put in a non-compete agreement (which is void, but still works as an intimidation tactic).
The only thing here that I can see the benefit of, is that the news coverage of non-competes being void, will make more employees aware that they're void.
Even a high tax state like California would have a five figure amount less owed in taxes than Ontario at certain income levels.
It’s unfortunately really hard to Google for, since results keep returning on how to get mitmproxy to export SSLKEYLOG, not ingesting it.
Did you open source it by any chance? =)
The permissions are set to world writable, so you're giving every app the right to modify your system.
I'm still not sure why Allwinner resorted to this silliness instead of using su like a sane developer. If anyone could loop me in that would be appreciated.
Thomas Kaiser appears to have been the first person to discover it on April 29th, 2016. http://irclog.whitequark.org/linux-sunxi/2016-04-29#16314390 (Thanks to HD Moore for linking me.)
From what I can tell, it went unnoticed for slightly under a year.