HN user
stinky feet
Same unexpected worlds colliding for me while drinking coffee from a Lost Art Press mug this morning and seeing this article's author on HN.
The mug is as close as I get to woodworking on most days, unfortunately.
We had the same problem. Our VM's are now back up. Log in to accounts is still spotty.
Are you saying Cliff's claims are too...
one-sided?
I'm a trustee on the board of a very small village in Illinois. There was a vote to allow the gaming before I got on the board, and only one vote since then to approve a new license for an establishment. I argued the income-vs-sleaze ratio was lousy, but was out-voted. I wish I'd had this article and its facts to back up my more emotional reasoning for not liking it.
Video gambling is indeed a blight, even if it is profitable, but this article only makes it more depressing to see just how worthless (or actively punitive) it is to all but the companies that apparently wrote the original legislation.
That's what I thought too - I mean this is interesting, but dang -- BT was the bee's knees.
I think you're missing the point, but maybe I'm missing yours.
Perhaps I could use some mentorship from you. =)
Without context, working for free requires careful thought. But in the context of this conversation "free" means without monetary compensation, but you're still receiving the benefit of the mentorship (and thus not free).
TLDR; No one's advocating working for free. The Warren Buffett approach is "trade money for time with a good mentor."
Ah - cool. That makes sense!
I don't see Gitlab explicitly listed as a supported service, but wonder if that would be supported or require google or gitlab to make the integration happen. (This is on a GL EE instance we manage).
And what about public-facing web apps developed in-house? Can we add SAML integrations that would work with this for employee access?
These are probably basic questions, but I couldn't seem to find the details on the site.
I think you meant "redacted" vs "retracted". But yeah, there are a lot of stories out there of people assuming a black bar over black text is high security.
Will second the #2 recommendation above - I have a fair amount of sidewalk in front of my house and the front of my office that I bought the snow pushers for. They're fast and move a lot of snow with minimal heavy breathing. 4 years and zero heart attacks. =)
Whatever mechanism makes it likely you'll keep posting is the right one. Thanks a bunch for highlighting some thoughtful approaches to basic design decisions that often get overlooked. The effort is appreciated.
Apropos of nothing, but I just migrated a site to metalsmith, and I've really enjoyed the results and ease of building out any functionality that was lacking in the framework (though most needs were met already).
I'm also looking to escape Flickr, and still have yet to find a good self-hosted solution.
Mitch's low twitter output could come from a variety of factors. I'm banking on either a) heavy touring schedule or b) his death in 2005.
It took seeing how dismissive people are of a great, free resource to realize I needed to donate just to spite such silly entitled commentary.
Thanks for providing the motivation, random entitled community member! =)
Now I just need to figure out what to get with the new, custom icon reward...
As with the others, backed it on KS, and I don't feel like you owe me anything more than what you've provided. Keep the money, and do something to keep your dream moving forward.
We dislike managing PG too, so we've been migrating to https://www.compose.io/postgresql/ It's not for every situation, but they have replication and failover and downloadable daily backups with the option for SSH-only access. Been using them for about 6 months on some smaller DB projects, and haven't had any hiccups.
We went through various configurations/deployments of ES in-house, and eventually outsourced the job. The fickle nature of cluster restarts/upgrades were frustrating along with the unassigned & lost indexes that would often result. Then there were cluster partitions that wouldn't heal without a lot of manual intervention.
The tradeoff in value wasn't worth the time it was requiring, so we outsourced to compose.io -- they've been a good fit price & stability-wise, and feel pretty close to a blackbox for the benefit. If you need a large cluster however, you'll pay handsomely with any of the SaaS providers when last I looked at it. For large quantity work we've moved to AWS Redshift.
I've felt a similar pull away from django on a number of apps. Just looking through the Channel docs [0] however, many of the reasons I get frustrated with Django (primarily the lack of a solid websocket/SSE story) are being addressed. Frankly, I'm addicted to Django's built in auth & admin UI, and I'm thrilled I won't have to bolt on a kludged solution if I want to get some realtime behavior. My frankenstein chat system of Node & Django can be put out of its misery... someday.
Healthchecks.io looks really interesting, both because it's an open source django project and because I was disappointed with Dead Man's Snitch. DMS forces me to live within their timing for running checks -- If you have something that has to occur @ 3am every morning, you won't know it failed until midnight UTC later that day, or when a customer calls to complain.
Healthchecks handles this a lot more sensibly. I might throw it on a linode and give it a shot. Thanks for releasing it.
Nice sandbox for quick tests. Can we add backbone and knockout.js? Or a simple method to add scripts on demand? Although it's easy to over-engineer things -- Simple is probably a good thing. =)
Been re-reading Rhodes' book the last few weeks and it's spectacular, not to mention some great turns of phrase. I really wish someone would make a multi-part tv documentary based off his book. Just fascinating stuff.
I'll second the vote for Haraka. Good support via IRC, and a very strong, accessible plugin architecture. I like the basic mechanism Mailin is providing (convert e-mail to a semi-structured doc) - I just don't know their smtp wrapper's reliability. It's tempting to just build a Haraka plugin to provide a similar output (and feed it to Elasticsearch for logging/searching later on).
Reading through the source it looks like it spawns a child_process per-message to for checking both SPF and DKIM via a python script... That feels inefficient, but I don't know if there's a better node-based solution.
We're using vagrant and ansible to manage local dev instances with the same ansible scripts responsible for provisioning/deployment to our production boxes. My thought being the less I manage with vagrant, and the more I codify stuff in ansible, the more predictable things are when I go to provision/deploy in production.
I'm thrilled with how vagrant helps the process locally, but at the same time want to do as little as possible in vagrant because it's not applicable/involved when I provision/manage a box @ Linode or Digital Ocean.
Am I under-utilizing vagrant? Or missing a greater benefit by limiting its role?
"It's no wonder security researchers turn to black hat methods" -- this seems such a binary and pointless reduction of the options available. Yes, Prezi could have turned this into a PR and security win, and failed to capitalize; but the assumption that now the only option for a security researcher is to turn to the dark side is... pretty ridiculous.
Those who "turn to blackhat methods" do so because they want to make money and don't place a premium on the potential moral/legal/ethical issues at play in how they're doing it. They make a choice, irrespective of the shortsightedness on display by Prezi here. Don't conflate the two behaviors.
Anyone know if there's any more substantive info about what their tech stack looks like? I wouldn't expect all the details, but something more than "we did it, and it's not SAP, and it's totally web-scale" would be pretty interesting to read.
I'm guessing that like the Nest thermostat they have an external web site (nest.com) you can register the device with, and then perform config via that site.
I wonder if anyone's sniffed their Nest's traffic to see if it's encrypted?
I'm a fairly happy Linode customer and have been for 3 or so years. (Yes, security/transparency could be better). We've got a nodebalancer and ~10 nodes. What longview lacks for me is a mechanism for notification & alerts. The value of monitoring is only half the equation. Step two is something that either has sensible defaults or easily adjusted settings and notification when limits are exceeded or below acceptable limits. I don't want to have to constantly watch longview to see a problem.
Anyone know if it provides this, or if there are better monitoring tools or services that do?
The status report mentions a DoS attach is specific to Sunday (yesterday as of this writing), but the manager is still not resolving for us. https://twitter.com/StatusLinode doesn't appear to mention anything more recent than yesterday either.