p8952

Louis C.K. wonders how different the world would be if murder was legal, or at least a misdemeanor, in his HBO special "Oh My God": https://www.youtube.com/watch?v=iHnsajl-kB8

Surly the issue here is a complete lack of communication? Why did the development team start of 9.x without first consulting Ops about what versions are supported?

Allowing developers to install and "self-support" a non-supported database version is an _awful_ idea. When shit hits the fan it will be Ops/DBAs who are left to pick up the pieces.

It's probably a bad idea to start (another) discussion on this topic, but...

While the original (Debian Fork) made some ridiculous claims, this is not a fair comparison to make. As a neutral party I don't think I've seen anyone make the argument that SysVinit is any good, just that some other options may be better, and they should at least be an option.

When you compare systemd with something like OpenRC the obvious choice is less clear: http://pastebin.com/DfAL75Kd

Your Discuss button seems to be overflowing: http://i.imgur.com/8s9O3DA.png

Oh awesome, I didn't see that anywhere. I appreciate that mine is a strange edge case so thanks for all your help.

Hey joshfng. Thanks for the info, but it's more the BIOS settings I'm interested in.

For example DigitalOcean's Ubuntu 12.04 x64 images work fine with Vagrant/VirtualBox, and their CPUs support VT-x. However since they do not enable VT-x in their BIOS you can only run x86 guests.

If you could let me know the output of these commands in your images before I drop $10 to try it out it would be much appreciated:

$ cat /proc/cpuinfo| grep 'vmx' # Checks for VT-x support on the CPU.

$ rdmsr 0x3a # Checks if VT-x is enabled in the BIOS.

I'm interested in knowing how GitHost are hosting GitLab CI. I'm currently using GLCI to run integration tests in Vagrant VMs, which unfortunately means most "cloud" hosting is out.

joshfng (Assuming you are from GitHost). Do you know if your environment would support this?

That's a very good idea, coupled with what other people have suggested (Increase the time on the fly for devices/IPs making repeated or spammy looking requests) I could see this working.

This is the key point I think. From my desktop (Intel Xeon CPU E5-1620) the example takes 12 seconds to run, on my phone (ARM Cortex-A7 MPCore) it's taking about 120 seconds to run.

If you don't want to annoy your visitors you're going to need to have the max runtime on any device at around 25 seconds.

Now you can't scale this per device, because you can't rule out devices spoofing what they are. So this means you're looking at barely a few seconds to break it on any sort of desktop hardware, and even less on any dedicated server.

Spammers are probably waiting longer than that to just load the page they want to spam, so it wont slow them down. For this to work you need to solve this issue, and I hope you can, but I don't see how.

As I pointed out on Twitte(1), this looks like it might be illegal in the UK.

Things such as ethnic background, political opinions, and religious beliefs are classified as sensitive personal data(2)

Such data can only be recorded in specific circumstances and only with explicit consent(3). Such quizzes, from my point of view at least, do not make it clear that you are consenting to the data being collected.

(1) https://twitter.com/p8952_

(2) https://www.gov.uk/data-protection/the-data-protection-act

(3) http://ico.org.uk/for_organisations/data_protection/the_guid...

Seems to require a SSN, so I assume it's only good in the US?

Rolling your own? This is as simple as it gets: http://128bitstudios.com/2011/11/21/authentication-with-sina...

If you want to make it even easier, use OmniAuth: http://recipes.sinatrarb.com/p/middleware/twitter_authentica...

You should be sending a token and/or reset link which will allow the user to choose a new password.

This is much better than just sending a new password because:

* It can have a TTL.

* The user has to change it, they can't just keep using the plaintext one forever.

* You can perform some kind of verification, was the request for a new password sent from the same country/IP/device as the person generating a new password.

>She asked my husband if he spelled his name (Kevin) "the way you expect to spell it". I got a button that said "with Keven" and didn't have the heart to tell her what was wrong with it.

Poor girl. As someone cursed with the inability to spell non-phonetically I'd hate to have to ever write anything without the help of spell check.

It's such a silly thing when you think about it but people will write you off as a moron without a second thought.

I forgot that the first line of the GPL reads "YOU MAY NOT SELL THIS FOR PROFIT". It's a shame there are no billion dollar companies based around the GPL... /s

In my personal opinion this is what DevOps is, in fact "OpsDev" might even be a better word for it in most cases.

It's about carrying out what are traditionally "Operations" tasks (Provisioning, Configuration, Orchestration, Monitoring, ect) using tools and workflows with are traditionally used by Developers (Version Control, Automated Testing, ect)

In large companies this work is often carried out by operations people who have expanded their skill set to include things previously limited to developer roles. In startups this work is often carried out by developers, as in the original rant, who are tasked with maintaining infrastructure as well as developing.

I can't comment on the protocol, but tinc is very easy to set up. You just need to generate pub/priv keys and then add your routes in /etc/tinc/vpn/tinc-up. We're running it in production with ~30 nodes worldwide and using puppet to dynamically add/remove nodes on the fly.

What is great is it's able to re-route around any peering issues suffered by local ISPs. Say you have three nodes in the US, UK, JP and your JP ISP loses routing to your US ISP. If both can still route to the UK then tinc will automatically keep traffic flowing.

Knight Capital Group went bankrupt, it wasn't due to HFT, but was caused by bad electronic trading.

http://pythonsweetness.tumblr.com/post/64740079543/how-to-lo...

Net Neutrality can be supported and enforced without government intervention though.

Check out Zabbix or Icinga

Or for Python3: python -m http.server .

Or Ruby: ruby -run -e httpd .

I see you are using Puma for your rack server, how do you find it performs compared to Unicorn?

Displaying the names of unconfirmed entries is also probably not the best idea: http://coingen.io/status.html

I think you're trying too hard to jump onto the "ProductX FOR HACKERS!" (Or Developers) market. Such people simple are not interested in paying $18 a month for a blogging system when you could get multiple VPS for that price which can host not only your (Open source and truly hackable) blogging engine but also every other project you have.

If you were selling this to another market it would probably look a lot better.

No source code, full of "analytics" trackers, only allows you to upload/edit themes via a proprietary 3rd party application, no revision control on blog posts, and the promo video is just some guy quickly clicking buttons on a MacBook while busy and brightly coloured backgrounds dance around.

Not to mention costs $18 per month, so I assume your content gets nuked when you stop paying.

No thanks, it looks like you're marketing to the wrong audience.

Nice!

A couple more things I noticed after a short play around:

* It's not obvious how to (or maybe even not possible) to find a list of your published guides.

* It's not obvious how to (or maybe even not possible) to delete your published guides.

* You have to publish your guides right away, I doubt anyone wants to read my first draft.

* Your source code editor does not accept tabs which means everything has to be copied and pasted in. Have you though about using something like ace? https://github.com/blog/905-edit-like-an-ace / https://github.com/ajaxorg/ace

Can guides be viewed offline? Perhaps allowing users to export them as PDFs?

I'd hate to put in weeks of work only to find my work lost when I need it due to network issues, the site closing, ect.

I would not say this was 'paranoid' behaviour, but rather standard operations procedure. Leaving access to email accounts after someone has been let go is just asking for a nasty email sent to all contacts.

Look at the tension in one of the pictures[1], it looks like if you rolled over with keys in your pocket you'd rip right through it.

Not to mention the price tag of $1,350.00, I'd be shocked if they'd sold any.

[1] https://cdn.shopify.com/s/files/1/0213/4326/t/1/assets/carou...

The EFF's view on exploit sales and forced disclosure is questionable at best.

https://lists.immunityinc.com/pipermail/dailydave/2012-Augus...