skysight-inc/HackerNews huggingface dataset:
I was obliged to move from San Francisco to Columbia, South Carolina for work and I desperately miss SF. I miss the energy levels, the buzz on the street and present at practically every event I went to.

To give just one example, I tried signing up for improv comedy lessons --- and I found that my teachers were among the best in the world, and that they had a range of lessons available ranging from beginner to master. In Columbia, there were beginner lessons only, and then the instructor flaked on us -- so now there is nothing.

From my perspective (30s, single), paying SF rent was the best investment I ever met. In SC I do indeed own my home --- but I find myself saving half my salary, not because I am either unusually well off or frugal, but rather because there is nothing I terribly want to spend money on.
1) This sounds like rationalisation. Clearly there's advantages to being 10x at something valuable.

2) The premise of the 10xers not being around in 50-100 years could be correct. It depends on the amount of money invested in anti-ageing technology.

Coming down on one side or another, in a binary fashion: I think your comment is false.
Exactly-once is possible in practice if you effectively bring the client under the umbrella of your transactions. E.g. you can (ab)use MySQL and other RDBMs to do something like:

1. Have a table where each row is a "job" or "message" and has a status which when enqueued is status = "unclaimed". You can also have a `last_changed` column.

2. Have workers consuming that table that GET_LOCK() a row and set status = "processing" and hold the lock for the duration of the processing.

3. When they're finished with the task they update status = "finished" and unlock the row (or equivalently, disconnect).

This requires much tighter coupling between the queue and the queue consumer (each client must maintain a lock / connection for the duration of processing items).

But it means that:

* Nothing will ever pick up the item more than once due to the GET_LOCK().

* If the consumer dies the item is either just unlocked, or the status is "processing". You can as a matter of policy re-pick up "processing" with a `last_changed` in the distant past, alert on those items and manually inspect them.

* If the consumer processes the item successfully it'll set the status to "finished" and nothing will process the item again.

Now obviously this requires a lot more overhead & maintenance than what you have in mind, in particular it makes some of the failure cases be "the item is delayed due to a consumer dying and won't be processed until a human looks at whether it was actually finished".

But this is the sort of pattern that you might use e.g. if you have a queue for sending out invoices. At work we use MySQL + https://metacpan.org/pod/Data::Consumer::MySQL to do this.
Mailpile beta rejected
It doesn't have to pass through anything but if the '/addNSAbackdoor.sh' script just adds a routine to the code that adds the Public Key of an NSA owned key-pair before the encryption process, then the NSA can pick it up from any Internet-tap they have and decrypt it.
Here is a good explanation of Material Design principles:
http://materialdesignblog.com/the-ultimate-guide-to-googles-...
410 Gone – Thoughts on Mark “diveintomark” Pilgrim's and _why's Infosuicides
I filed this bug (along with http://crbug.com/458362), and there's a bit of context that may be missed. First, this is to protect weak devices and services on private networks or localhost, that really can't be safely exposed to attacks pivoting from the web. It will block only sub-resource loads and navigation from the web to private networks. Navigating directly (via bookmarks or omnibox) or in the other direction (from private to web) is still fine. Essentially, this is applying similar rules to what's already in place for file URLs.

We also appreciate the concerns for legacy apps, local servers, etc. That's why we plan on supporting blocking UI overrides, opt-in by the page on localhost/private (maybe via CORS headers), and permanent exceptions via the command-line and enterprise policy. So, there might need to be some small tweaks, but all the use cases I've seen described in this thread should still work in a portable manner after these changes are made.

Also, to my knowledge no one is actively working on these changes yet. Hence why the details in the bugs are still a bit nebulous. Although that is likely to change pretty soon.
Using gpg is not so awesome. Obnam uses gpg. Since Obnam invokes gpg in batch mode, if you want to have a passphrase, you have to use gpg-agent, which at least for me took more effort than I found reasonable to set up on a GUIless server.

Furthermore, all the crypto config depends on gpg defaults or your gpg.conf. Whether this is good or bad depends on whether you are OK with gpg's defaults that are chosen for a non-Obnam use case and whether you like tweaking gpg config.

While figuring this out, I started wishing that Obnam used libsodium instead of gpg to avoid configuration and especially gpg-agent. (libsodium didn't exist when Obnam was created.)
Meta Tag Tips for SEO that you may not have heard
I'm not sure. Can you say for a fact that my texts aren't being intercepted or even saved by the phone company?
It's fairly trivial to build an in-memory broker with zmq, though, but you should rather consider zmq as building blocks for a message queue, or sockets on steroids.

It fills a need for certain applications, and it is very good at what it does.
SAP Lumira: Electric Cars Comparison
Right. Some landlords/management companies don't accept guarantor companies.
That's not entirely true, since what you describe isn't a CP system. The client is a part of the system!

It is possible to have the client be part of the consensus algorithm and guarantee exactly once delivery, but the latency gets quite high.
I mentioned this above, but we plan to let the localhost/private page support an explicit opt-in, maybe via CORS headers. Those details may not be captured in the bugs yet because currently no one is actively working on this.
I'd be interested in a longer blog post on your observations, particularly the one about rhythm.
> Whether you choose the luxury option, the commodity option, or something in between, you are buying future garbage.

I think this is one of the biggest differences between today and when our parents grew up.

When something was made back then and when someone bought it, it was bought with the expectation that this should last. And it did. It probably still works and could probably be used by you if you wanted to use it. Basically decades (or in some case centuries) of durability.

Contrast that with today. If you buy something this year, servicing it next year will be unprofitable compared to throwing it away and buying a new one.

Take a wild guess at which is the eco-sustainable one.

I wonder if or when the pendulum will swing back and we will try to strive for durability, and just how bad things needs to get before we understand that we need to go there.
If it makes you nervous, switch to a hosted solution[1]. There will apparently be a hosted "Travis Pro" at some point in the future as well.

1. http://www.quora.com/What-are-the-alternatives-to-Travis-CI
It's great to block access to http routers on localhost, which I think was the original point of the bug.

But it's essential that access to secure websocket on localhost not be blocked in the process (which appears to be the case is it stands).

That's the reason for posting here in the first place.
> Test what you write as quickly as you can.

Until you run into that one problem where you can't test between the small steps, because you need the whole thing to be up (to some degree) and working for any test to work.

Operating system kernels would be an example of that: The best test for a *nix OS kernel is, if it can run a shell. You need all the essential syscalls to do something sensible and if any of the required parts doesn't work the whole thing fails.

Another example would be refactoring a complex library into something more manageable. If you keep working in small, testable steps you can move only along the gradient, bordered by "can execute" and "doesn't execute". So you'll be able to reach only a local extremum. Now if you're in the fog and don't know where to go, that's fine. And for most development this is exactly how it happens. But sometimes you can see that summit on the other side of that rift and you know you have to take a leap to get over there.

I spent the past 3 weeks doing exactly that, refactoring a code base. I knew exactly where I wanted to go, but eventually it meant working for about a week on code without being able to compile, not even think of testing it, because everything was moving around and getting reorganized. However now I'm enjoying the fruits of that week; a much cleaner codebase, easier to work with and I even managed to eliminate some Voodoo code nobody knew why it was there, except that it made things work and things broke if you touched it.

> - Hold it in your head! Or you won't have a clue what all your code, together, is doing.

Or, sometimes it's important to get it out of your head, take a week or two off and look at it again with a fresh mind and from a different angle. Often problems seem only hard because you're approaching them from that one angle and you're so stuck with wanting to get it done, that you don't see the better way.

Instead you should write code in a way that it's easy to get back into it.

> - To get started, ask yourself, what is the simplest thing that could possibly work?

And then wonder: What would it take to make this simple thing break. Make things as simple as necessary but not simpler.
This is indeed interesting and something I thought about recently on the train. I dabble in fiction writing and was thinking about trying a kickstarter of sorts at the end of the year. One of the key things I wanted to offer was making the writing process as transparent as possible. My initial thought didn't go much beyound..."well github repo would be a start". This seems like just the thing I could use. Bookmarked and added to my Trello card for the project :)
On OSX I just installed it in a virtualenv with python3:

brew install python3 # will install python3 but not make it default
mkdir xonsh && cd xonsh
virtualenv -p /usr/local/bin/python3 venv
source venv/bin/activate
pip install xonsh
xonsh
Using /dev/urandom instead of /dev/random help, too. http://listmaster.pepperfish.net/pipermail/obnam-support-obn...
Huxley – Rail API Proxy
Websockets already have the Origin header as mentioned in the bug by Tyoshino: https://code.google.com/p/chromium/issues/detail?id=378566#c...

Edit:

From my other comments, there is the additional implicit opt-in shown by WSS itself on localhost requiring (1) a public DNS record and (2) a valid SSL certificate for that FQDN.

I doubt that there are WSS servers on localhost out there setup with a public DNS record and validating SSL certificate which are not also expecting public traffic.
Well, there is something; assuming that you refer to an Ubuntu Desktop backup engine with a simple interface, there is Deja Dup.

The problem is though, that the last time I've checked, it was excessively simple- it didn't support individual files selection.
Show HN: Fast and simple way to get EV SSL certificates
As I already stated, we plan on having an explicit opt-in for these cases. However, what you're describing is an implicit opt-in (external DNS pointing to localhost, etc.), which can be trivially abused by third-parties in exactly the kind of attacks we're trying to prevent.
THE APPLE RING CONCEPT: Multifunctional Rolling Ring with 4 Low-Voltage NFC Tags
Hi HN,

Creator of Certsimple here. I made CertSimple while applying for and waiting 3 weeks for GoDaddy to issue an EV certificate earlier this year. I looked around for existing companes that could verify and issue certificates without the complex steps. Every company I looked at had a hugely detailed registration process or didn't sell EV certificates - the ones that actually check your identity (like github, mozilla, stripe, and npm sites).

The main difference with Certsimple is the amount of work you have to do to get a certificate.The whole process of applying of a cert with CertSimple is now less than a minute.

This is because:

- We build the entire CSR command, including the subject for both Linux/Unix and Windows. There are no questions and answers. Just paste onto your server (using openssl or libressl on Unix and certreq on Windows) and paste the results.
- We set correct the defaults for 2015 browsers (Chrome 41+ is now showing warnings for SHA1 certificates)
- We automatically set the required encryption strength for an EV cert (2048 bits)
- We check the CSR as soon as you paste it
- We're quite specific about the information we ask for, don't repeatedly ask for the same thing, and a few other bits and pieces.

You won't really notice any of this, though: you'll just find it's really easy.

The best way to experience this is to try it - it only takes a few seconds we don't ask for payment until the process is complete.

10% of the profit from our certificates goes to The OpenBSD Foundation, GnuPG, the EFF or Open Rights Group (you pick your preferred source at the end of the order).

Mike
I have a few years experience with TSM and always found it to be pretty fast and very reliable. Like most IBM software, it looks overly complicated and obtuse at first glance, but once you overcome a few "standard" obstacles(1), you realize there's some pretty serious engineering under there and it's actually quite likable. It's not cheap though...

(1) IBM software seems so be designed by smart people for really hard scenarios, but it all gets buried under tons of enterprisey crap and UIs designed by monkeys...

1. Drop the excruciatingly slow and clunky web console and learn to use the CLI (really, it's horrible);

2. Resist the urge to throw your arms up in disgust because the syntax and concepts seem foreign (it probably won't look so foreign to mainframe people, and it isn't actually bad, just different);

3. ??

4. Realize the CLI and storage concepts are actually very powerful.
Surely you could easily migrate this to GitHub?
I am not using CI today but I will definitely use a hosted solution if the build server needs secret keys.
> I'm sure they could trim the fat

Indeed, the article mentions they were paying for office space in both Manhattan and San Francisco.
Kitware Releases CMake 3.2 to Advance Software Development
Show HN: How We're Using Git Flow
I was about to post this, thank you for doing so.

Seriously? What could they be thinking? The entire premise of 2-factor - in most cases, something you know and something you have - is that if someone steals/guesses/social hacks my secret, they don't have my keyfob (or phone); if someone steals my keyfob or phone, they don't have my secret knowledge. The probability of losing both is much lower than either.

But using just one factor, and one that goes across insecure networks, and is visible on my phone even on the lock screen? And I cannot use it if I have mobile issues? Really??
Zoning also suppresses growth in the supply of housing, but so does rent control. People don't build apartment buildings out of altruism.
There's also protonmail.ch tutanota.de and several others in early stages.
WSS already has explicit opt-in in the Origin header.
My interpretation of that part of the article was "refactor early and reimplement often"

That grabs in the concept of switching between planning and experimenting modes with the end result of not getting stuck.

I may be biased in having learned this stuff a long time ago so when I get stuck its from getting hopelessly backed into a corner at which point the best solution is pretty much start over differently, and first semester programmers might get trapped a little more easily, like they don't even know common ancient anti-patterns so they don't even know where to start looking when debugging.

Reading between the lines it almost sounded like the A level programmers wrote their tests first (which is usually easy) then wrote code to pass the tests (usually not too awful) then they were done, whereas the lower grade level programmers wrote the code first, then tried to debug (and debugging is always harder than test writing or coding)
$50 off from what?
Awesome CheckiO Python one-liners compilation (PART 2)
Is there a reason xonsh doesn't honor the PS1 variable from bash to keep your terminal prefix? Or is there a way to customize xonsh's?

Example:

10:54:01 foo@bar:~/scripts/xonsh$ xonsh
foo@bar ~/scripts/xonsh $ # no time prefix
NSCAL – new pseudo-language to code and analyse novels
Check out a random subreddit *redirect*
Why the Coldest Storage at Google Is Nearline
The "NIMBY crowd" also must stop blocking new development. SF desperately needs new housing development at a scale unprecedented in its recent history.

In the meantime, all rent control does is create an arms race between property owners and tenants, one the tenants will all gradually lose. It also eliminates incentives to renovate or even more productively use existing housing stock.
Humans killed at least 2.8M whales in the 20th century
Pacific gray whales are migrating to Atlantic ocean due to warming temperatures
It sounds like they discovered that some people already knew how to program.
I agree with you that we should agree to a set of rules without knowing our circumstances.

But the rest of your argument doesn't make sense. You've never met an SF real estate owner with a certain opinion, so you know something about most of them? There are at least 10,000 SF real estate owners. Have you talked to more than 0.1% of them? And even if you had, how would that help with your original claim that you can identify whether commenters in this thread were SF real estate owners or not?
High levels of vitamin D is suspected of increasing mortality rates
Does any economist disagree that free market is more efficient than a price regulated market, i.e. provide more people with more bousing? Its not just about the liquidity at the demand side, at the supply side, rent control makes it harder for market to create more supply to meet the demand.

From a human right perspective, I am not sure I agree that a person have the right to live at the same place forever as long as he maintain the same income just because he used to live there. Maybe a couple of years but it shouldn't be forever.
As a note, Scrum started outside of software development. It was created to deal with brand new problem domains with many unknowns.
Logdown: a console utility for the browser and server, with markdown support
Secure Pirate Bay 'unblocked' by Most UK ISPs
The category size bias
Rhythm, Resonance, and Recursion.
unfortunately am a bit older, though still in good health and don't smoke.
Was looking for professional organizations like the IEEE which might offer group rates.
Warning spammers or deliberate ToS violators is now a matter of decency? The company admitted they knew they were in the wrong and that Twitter would eventually shut it down. I'm not sure how it's remotely a matter of decency when it comes to intentionally malicious actors.

On reflection, it's almost certainly because the app was getting some press and Twitter wanted to make it clear what the situation was. Versus allowing the offender to pretend it was another issue or spin it against Twitter (though they seem to be trying!)
Sarcasm? How does that sound fair for the owner. Not being able to rent out your apartment for 5(!) years is ridiculous.
Nice project, but while the design has a appealing simplicity, the details on the site are poor. What kind of certificate do I get (wildcard possible, how many domain names, ...)? How will the business and domain owner be verified? And most important: what is the price tag?

You state you only ask for payment at the end and it's $50 off for HN, but what is the regular price? It's nowhere on the site, which is quite intransparent.

Minor bug: after entering a server name I cannot edit, delete or reorder the entries anymore.

Major bug on submitting the form: {"err":"missing required field: preferredDonation"}
This makes it look like you have not even tested the released version.
They can be easily intercepted by anyone near your phone with TI Calypso based phone, like Openmoko Neo Freerunner or old Motorola phones. Of course there are also dedicated pieces of hardware for that.
So, when the process is complete... how much will you bill me?
Ask HN: Review my startup, www.getmustapp.com
Ask HN: Review my startup, www.getmustapp.com
Getting the Bitcoin Price from an API with Jquery
Protected from me patenting it and then suing small companies that use it.
I think the emphasis is more about the way people think about solving programming problems than the way they think about the problem itself. An analogy is that two people may differ in their mental models at the level of syntactic sugar rather than Turing completeness.
I'm using zfs-auto-snapshot[1] and zfs send/recv to backup my work desktop machine to a remote server. The naive approach of just doing 'zfs send -R -I snap1 snap2 | ssh remote zfs recv -dF pool'[2] has a number of drawbacks:

* Assumes remote is available 100% of the time. Recovery from downtime at the remote probably requires some manual intervention to get things back in sync.

* If the remote is in a different physical location with limited bandwidth between the hosts, compressing the stream on the fly isn't going to be particularly efficient with bandwidth.

I've built some scripts to help[3], dumping the necessary incremental streams into a local directory and then compressing them with lrzip[4]. This decouples the host and remote systems and the zfs streams compress really well: a 33Mb incremental stream I have here compresses to 4.4Mb with lrzip. Once you have a directory of compressed streams you can push them wherever you want (a remote server where you convert them back into zfs snapshots, giving you a live filesystem; S3 buckets etc.) You also are able to restore using standard operating system tools.

I'd assume btrfs is comparable, but haven't tried it myself.

[1]: https://github.com/zfsonlinux/zfs-auto-snapshot

[2]: see https://github.com/adaugherity/zfs-backup for example

[3]: currently in my local fork of zfstools at https://github.com/mhw/zfstools/blob/master/bin/zfs-save-sna...

[4]: http://ck.kolivas.org/apps/lrzip/README
Edit: I've now added pricing to the front page of the site, in the currency (USD/EUR/GBP) matching your IP location. I've also added certificate length too.

Hi there and thanks for the feedback!

You can enter as many server names as you like.

Wildcards aren't possible with EV certs - both of these are mentioned on the 'Server names' box. The feedback is appreciated though so I may make this information more prominent if I hear this repeatedly.

I'm currently looking into the bug you found - it hasn't shown up in testing. What browser/OS are you using?
> when what they operate is a website

They do more than just operate a website. They are in the hardware market as well. You can accept credit cards from your phone and it will run through Etsy, which is handy for sellers rep on Etsy. I'm not sure what else they do, but it's not just running a website.
Auto līzings-kredīts līdz 25000 eiro
People Who Use Firefox or Chrome Are Better Employees
That's not the way the origin header works. The origin header in websockets is provided from the client to the server, and the server must take overt measures to protect itself or scope origins that are allowed. Given that we're worried about unsafe servers, the origin header won't protect against the attacks we're seeing. What we need is a mechanism for the server to authorize the client explicitly, so that we can disallow the resource implicitly when authorization is not present.