jwcrux's comments

How is this different than the more robust https://github.com/gztchan/awesome-design?

Whoa that looks awesome. Nice work!

Hi everyone, author of the post here. Happy to answer any questions.

Troy does great work running HIBP.

It's an incredibly useful service - I highly recommend sending over a few dollars to help with infrastructure costs if you feel inclined to do so: https://haveibeenpwned.com/Donate

I'm a big fan of these posters! I even made something similar to show the format of the Tor consensus [0]

[0] http://jordan-wright.com/blog/images/blog/how_tor_works/cons...

Ah, I see - I'm speaking as someone from the US. I don't have the experience to speak to EU healthcare.

That doesn't mean that:

1) it's not a luxury 2) that medical providers will pass the savings on to consumers

This podcast mentions that only testing against non-viable embryos has been done. It's worth noting that just the other day, the results of the first testing against viable human embryos was released [0].

Also, I thought it was interesting when they talked about "who would turn down the ability to remove diseases for $x?" My answer would be people who simply don't have that kind of money.

This makes things complicated.

I'm not even close to an expert in this area, but I don't think it's too far a stretch to consider that having technology like this where you can theoretically pick and choose "add ons" for set prices would lead to class divides that are clearly visible when these add ons stop being just internal changes and start including exterior traits.

[0] https://www.newscientist.com/article/2123973-first-results-o...

Huh TIL. Good call!

You don't have to use scrapers, just use copies of the TLD zone files looking for cloudflare nameservers.

I prefer less opinionated where possible. "Worse" is really subjective, I just don't need bells a whistles for many of my projects, so the stdlib is just fine.

I prefer just using the standard library with a muxer like gorilla/mux.

> This topic could have been easily brought up after the holidays... but why wait? It's a topic to be discussed.

The way you're going about this entire conversation is simply too much. It sounds like you've reached out to multiple personal emails, created multiple issues, responded to those issues asking for updates, and brought the issue to social media in less than a day. During the holidays. That's overwhelming and doesn't put the devs on your side.

As others have mentioned, even if you're right, you really need to give the devs some time to think through the alternatives, consider your argument, come up with a solution, and implement it. This takes some time.

Removing information from a database may not seem hard to you, but you don't maintain the service. Sending a pull request is fine, but maintainers don't blindly merge anything. They have to review it, make sure it's the policy, quality of code, etc. that they want in the product, merge it, and deploy to prod after possibly testing everything.

Give it time (not measured in hours) and work with the developers.

Edit: This is exactly why maintainers don't blindly accept pull requests: https://github.com/gitpay/website/pull/4#pullrequestreview-1...

This is fantastic. One argument people will make (just like they did with Bootstrap) is that if every product used something like this, all the webpages would look the same.

To be honest, if all product webpages looked like this, I'd be quite alright with it, because this look great.

Well done!

The author specified that his source for finding the domains in the first place was the .com and .net zone files. This means that the domains were actively pointing to Google/DO/Rackspace's nameservers.

The author would therefore have complete control over the orphaned domains after the takeover.

disqus + google analytics?

That's a shame. I used that list fairly often for individual research purposes.

Oh hey, that's the exact laptop I drew.

Nice! I actually did something similar [1], just haven't gotten around to adding the Podesta emails.

[1] http://jordan-wright.com/blog/post/2016-10-12-mapping-the-cl...

It seems like a decent middle ground between high interaction honeypots and full on vm's would be leveraging something like containers.

I've considered doing this before but, you know, if free time grew on trees...

The benefit of using containers is that you can blow them away after every session, they have builtin networking so you can make entire honey nets, they're dirt cheap, and sharing the configs is a no brainer.