620 karma · joined March 31, 2011
Should have EU relied less on US and actually spend those agreed upon 2%+ of GDP like Poland, Finland and others have and be self reliant? Yes. Very much so.
Perun has an interesting video about it EU reliance of US military support: https://www.youtube.com/watch?v=BFoJGHZEqAk
It’s cheaper and pretty much the same features without the bugs of Superhuman.
I've build webhook systems myself in the past and there are so so many issues that you don't think about at first that are difficult to solve correctly like staggering retries, routing, logging is a big one! Really happy that there is now a great service for this. Nice work!
Right now I use my watch for alarms (for sleep), pager duty alerts and fitness/sleep/health related stuff.
Is it really profitable to have this information flow controller? Don't they just want to sell ads?
Look, I know it's not that simple. But why not do this?
I just wish people implemented their webhook systems well (a popular standard would be nice as well) - REST is fine, it mostly works and it's pretty standard.
I would love something like Reviewable - it uses github as the "DB" and provides a nicer interface for doing code reviews.
Kernels, compilers, language runtimes, databases? Sure, build them to last. Web pages that will not be used in 2 weeks? Don't waste your time with "build to last".
The problem is that some of us think that our software should be build to last - but in reality it's just some mediocre thing that needs to get in front of the clients as fast as possible and some bugs are "OK" to live with.
Is there any strong evidence that gravity is following quantum mechanics? Maybe a real theoretical physicist can explain.
> (b) A business that makes an automatic renewal offer or continuous service offer shall provide a toll-free telephone number, electronic mail address, a postal address if the seller directly bills the consumer, or it shall provide another cost-effective, timely, and easy-to-use mechanism for cancellation that shall be described in the acknowledgment specified in paragraph (3) of subdivision (a).
I'm not a lawyer of course.
The issue is that when a parallel scan starts, it's not limited to the `work_mem` which you would expect per connection. Instead, every parallel worker gets it's own `work_mem` limit. On a very busy db you can quickly end up with lots of OOM errors. What you end up doing is either disable all parallel scans or reduce `work_mem` which sometimes results in slower query performance for non-parallel queries. Suffice it to say, I wasn't smart enough to tune them and just disabled the parallel scans. Another way to do it is set a higher `work_mem` for expensive queries while having a generally low `work_mem`, but that's just hard to get right and you end up with even more bookkeeping.
This behavior might have changed. If anyone knows more about this would be glad to hear what you've done.
Meaning that new customers can't connect with facebook anymore to access their own data using OAuth! We don't need permissions about your friends, your photos, or whatever. Just accessing their own messages and posts (which is what our customers want to see in our app and pay for).
I know they are shell-shocked after #deletefacebook stuff, but this overreaction is ridiculous.
So glad it's not our only channel of communication through. Times like this you appreciate email - crazy huh?