It may be, may not be. Either way, I'm not opening on my work mac. Do you have a release for Linux, since it's written in rust?
Also, I think if you make it a .app with a developer license from apple, the creepy message goes away.
174 karma · joined January 8, 2016
It may be, may not be. Either way, I'm not opening on my work mac. Do you have a release for Linux, since it's written in rust?
Also, I think if you make it a .app with a developer license from apple, the creepy message goes away.
Why not just use another site, that you know, isn't Google? Like they suggested, you can search Reddit, or you can search Tumbler, or you can find a Facebook group, or where we found this article: Hacker news.
I miss the yesteryear when people didn't expect Google to somehow be the answer to everything on the web. Here's an idea: your fan sights can co-exist as well as Google.
And the irony is, the authors own blog home page uses a dark pattern to try and convince you to subscribe to their newsletter! Talk about ruining the web for commercial purposes!
ens.domains is a privately owned and managed DNS provider. It's litterally the exact opposite of what web3 claims to be. Having a "constitution" is just re-wording "Terms of Service". I love how it sells hard covers versions of it's Terms of Service for fiat at Blurb.com. And no, Blurb does not accept cryptocurrency payments even, lol.
Signal.org existed well before they added crypto, and quite frankly, yes I did just about completely stop using it - and so did many others. The introduction of cryptocurrency in that app litterally chased away users rather than improve adoption.
Gawd, could go on forever here.
LOL. Um, IDK, some people might disagree. Some people - like those innocent childrens' parents - might think it's like 99% of the problem.
You are correct about the documentation. I find the tragedy of open source documentation is that the people who need it most - the novices - are the ones whom could write it best - if they only knew if what they were saying was accurate. And then by the time you become an old-timer, and know thy ways, you just want to wipe your hands and walk away, because your tired....and still not sure if all your knowledge is accurate.
But anyway, once it's all figured out, it runs very reliably.
- you will need a copy of each platform running in order to build the binary - it's X-times++ as much work to package for X number of platforms. - The code you chose might not compile well on all platforms without code changes. - Dependency conflicts can be a pain.
oh boy, i could go on.
And I don't want to tie my github to this thing, i have all sorts of github accounts for legitimate reasons.
I would be glad pay a lifetime licence fee (maybe with a 30 day money back guarantee?) to check it out, but no way am i going to do a subscription model for my terminal.
But sure, we can all dream.
People are terrified of cancer and that's all they think about with smoking, but actually far more people die from heart and stroke related illness after smoking than from cancer. I don't know the exact number, but it's a multitude.
The price has little to do with the R&D and manufacturing cost, it really has to do with how small the market is. Once you have a customer that is willing to pay $1,000 for this novelty, they will likely also pay $10k for the novelty.
Also....I seriously doubt artificially extending daylight hours is good for anyones health.
Also, I'm not sure this is an actual breach. I think they accidentally published the data themselves, that's the vibe I'm getting from reading between the lines. It's like the code maybe missed checking a flag that would exclude private records from showing.
We are just 10,000 hacks away from bitcoin being gone forever! A boy can dream.
Which is to say, this isn't how they actually got cought, it's just how the nail will go in the coffin (and thankfully for those impacted, some funds recovered).
FWIW, if you ever find yourself in this position of owning a large amount of stolen crypto, I believe the best way to wash it would be to "robin hood it out" to a bunch of random wallets. You just happen to own 10-20% of the wallets, but the feds now have to try and track thousands of different people over years to try and identify the true thief, and there will always be plausible deniability.
Or sometimes I just keep it in my car as a an emergency phone / for pandora / for maps. It almost never goes to waste that way.
They will turn around that statement on a dime and not a single investor will blink with "...but you said to the regulators...". No risk in making such a silly statement.
They probably will get a change of leadership though. Often they chose the best-man-for-the-merger, and when it doesn't work out, they then actually search for the best-person-for-the-job.
Yeah, don't use consul as redis, they are not the same.
It's not. .1% of 36524 = 87.6 hours of downtime - that's over 3 days of complete downtime every year!
For a more complete list of their SLA's for every service: https://aws.amazon.com/legal/service-level-agreements/?aws-s...
They only refund 100% when they fall below 95% of availability! 95-99= 30%. I believe the real target is above 99.9% though, as that results in 0 refund to the customer. What that means is, 3 days of downtime is acceptable!
Alternatively, you can return to your own datacenter and find out first hand that it's not particularly as easy to deliver that as you may think. You too will have power outages, network provider disruptions, and the occasional "oh shit, did someone just kick that power cord out?" or complete disk array meltdowns.
Anywho, they have a lot more room in their published SLA's than you think.
Edit: as someone correctly pointed out i did a typo in my math. it is only ~9 hours of aloted downtime. Keeping in mind that this is per service though - meaning each service can have a different 9 hours of downtime before they need to pay out 10% of that one service. I still stand by my statement thier SLA's have a lot of wiggle room that people should take more seriously.
Multi-Region is a different story.
It's a good thing these guys were late to the cloud. I shutter how lousy my life would be as a sysadmin if I was forced on-prem because of how untrustworthy the reputation of cloud computing would have been.