skysight-inc/HackerNews huggingface dataset:
> next time you decide to post some bullshit like this don't do it under a throwaway account, pussy

Personal attacks are not allowed on Hacker News, regardless of how wrong you think someone is.
The Symfony Demo Application on Roids (Elasticsearch, OAuth, RabbitMQ, Redis..)
If you don't mind committing to Anaconda Python distributions, then you should simply use conda.

You can still pip-install things within a conda environment, and conda can manage more dependencies than just Python dependencies (a common use case is managing R dependencies for a Python statistical workflow).

You can do

conda list -e > requirements.txt

then

conda create -n newenv --file requirements.txt

to create a Python environment from the frozen requirements.

I believe that conda makes it easier to selectively update, but even if you don't enjoy those features of conda, the same two-file trick as in this post will work for conda as well, since you can use `conda update --file ...`. Conda's "dry-run" features are more useful than pip's as well.

The perfect feature for conda to add is the ability to specify alternative Python distributions, either by a path to the executable, or by allowing alternative Python distributions to be hosted on Binstar.

I can understand why Continuum wants conda to heavily influence everyone to use only Anaconda, but I think the goodwill of making conda work for any Python distribution would bring more to them than keeping it focused solely on Anaconda. (For example, I know some production environments that still use Python 2.6 and are prevented from updating to 2.7 -- and even if they did update, they'd need to keep around some managed environments for 2.6 for testing and legacy verification work).
This puts the acquisition of BostonDynamics in a new light. They weren't the peaceful people snatching them for civilian use. They were a shill for the military; hiding them inside of something less violent seeming to keep the heat away.
Hyperledger Project
How hard is it to set your CI to run off a separate branch? Or to run CI for all branches which are checked into a repo (a common option I've seen implemented)
Great, so now instead of a password to remember, I have to remember a link? How is that substantially different from carrying around emails with passwords in them? Or with dynamic links, I now have to go through a separate application with an extra click-link-to-login-then-close-tab-and-find-original-tab motion?

Instead of logging in by opening a password safe, I now have to log in by opening email... and have a new source of email clutter... and can't share an account with other people... and disposable emails for signing up to less reputable services becomes less of an option.

And what happens when you move email addresses? Or there's a problem with email (delays are common)? A password safe that relies on an asynchronous messaging protocol? Yuck.
Economists working at tech companies
I have a number of friends who work in the restaurant industry including some very close friends who are opening a restaurant and their families have numerous restaurants throughout the Bay Area. I'm quite familiar with this pain point. Some questions:

1. Who are you targeting this to - small businesses or large managed groups?

2. How will you compete with time trackers as they get integrated with POS? Does yours integrate?

3. How are you going to handle training? In my experience, people in the restaurant business do not know technology and any type of software requires extensive training.

4. Do shift managers find value over using their own existing methods?

The pricing seems ok but it's a tough market. Small businesses with hourly workers do not have a ton of money, while larger groups already have solutions in place. Just my 2 cents.
Just for the reference: I'm building similar systems professionally (and have done that with most mainstream programming languages on the market), and I was probably the first one who explored async IO and eventloops in Rust (https://github.com/Matthias247/revbio - but I'm not really proud of it) - so I think I'm at least halfway qualified to talk about this.

And unfortunatly by experimenting with these things I really got the fealing that these problems don't expose the best side of Rust. Wrapping lots of types into stuff like Rc<RefCell<T>> wasn't the greatest experience, and the problem that this didn't work with trait objects back then did not increase that either (might have changed).

Message passing is a low level primitive, and it's probably a decent solution for communication between threads. However there is also a need asynchronous communication inside a thread (the eventloop thing), for which they are not really useful. Futures/Promises/Observables are great for both use cases (and imho even greater in a singlethreaded environment). These are definitly harder to implement in Rust - and if you don't believe me just check out how many good implementations are currently available in Rust vs. other languages.

How does the eventloop design in Servo look like? Wasn't that some integration with Spidermonkey?

I agree that in Rust you will spend less time on writing tests and debugging - but this applies also for a lot of other statically typed languages which bring in a better ecosystem for that task.
For starters, any utilities based on sourcing won't work, such as nvm/rbenv/etc.

That's technically true for zsh in cases, but it's far easier to port or add compatibility for zsh than fish.
The Year 2038 problem
Kayne pirating software and showing everyone where to get it for free instead of acting like it was worth paying for is hardly an endorsement.
Tiny static and fastcgi reverse proxy with no configurations required
Comcast gets big tax break that was designed for Google Fiber
Works on a Fall 2011 Macbook Pro, too. Didn't know it has an accelerometer embedded.
Why I didn't shave and not take a Salary
Servo and Summer of Code
I tend to think of ABP a bit like the Advertising Standards Agency in the UK. They essentially enforce a minimum standard upon advertisers, whilst collecting administrative fees in exchange.

Long-term this is actually better for advertising agencies and websites supported by ads, as it'll help stop people just blocking ads completely. But people rarely think long-term anymore...
Well... I loved the video. It actually doesn't have to show what it's actually for... you just have to make people interested enough so they will give it a try and then make sure that they learn about all the great new stuff as they use it.
But again, you are going to hear all type of comments, positive or negative, just try to not take all of them for granted. Keep doing your stuff based on your guts and metrics. Good luck.
My thoughts were very similar to yours. In 1992, when I started out in embedded on a Philips 8051 and debugging it was via an ICE and had direct visibility and control of the 8051.

The ICE would be connected to a bonded out version of the 8051 and I was almost able to capture every single clock cycle of 8051's execution. When I hit a failure, I would just replay the trace and see what went wrong.

It looks like the folks on the big machines have caught up :-)
This is clearly a Worse is Better solution. Where the "worse" is the complicated and often not user-visible process involved in getting the login email to them in a timely manner.

That said, I implemented it a while ago, since there's no widely deployed distributed alternative, and as seen with OpenID, attempts to create one will be frustrated by entrenched interests and technical debt.

I still think that Mozilla could have gotten around that problem with Persona if they had built it right into the browser. Pity.
Rotten Apple or Overreaching FBI Intrusion?
These tokens should not be able to be reused, even if found in browser history. Additionally, the HTTP flow is to 301 redirect to the user's homepage or dashboard and browsers tend not to bother storing URLs that result in 301 redirects.
Journey to the Center of Microservices
depends which government you are talking about ;)
Sure. For each role, you can set how many hours a person works in a workday (e.g. California limits 8 hours before overtime), and how many consecutive days they may work (e.g. California limits to 6 consecutive workdays in a workweek before overtime - we technically go beyond this and limit to 6 consecutive days independent of the window). For a worker, you may set how many hours per workweek they may work (e.g. 30-40 hours).

We define a workday as midnight to midnight, and you control the workweek start day when you create the trial.

Other nice-to-have features include that we try to give consecutive days off (like a weekend) when possible and we allow you to control the minimum amount of time between shifts to prevent "clopens" (e.g. when a worker closes at midnight then gets assigned the opening shift at 7am).

If you have more detailed questions, I'm happy to answer them via email too (philip at staffjoy)
Unprecedented Apple-FBI fight: Telecom cooperated with government for a century
One Day After Indictment, Former Chesapeake Energy CEO Dies in Car Crash
never lost it ... why are hoomans still so naive?
Intelligent Networks: A New Co-Processor Emerges
Thank you for the work you do Eric. The light you shine on the dark parts of markets is incredible.
Better link: https://web.archive.org/web/20110326050206/http://www.firing...
I agree. Only used conda on a few projects just recently, so not too battle tested, but I've found it much easier to use, especially with "difficult" libraries.
Links would be one-time-use tokens, just as with existing password reset links. Security footprint is essentially the same as today.
The “Frosting” on Your Citrix Environment: Blue Medora and VROps
Pretty sure he lives in Wellington and so must work remotely.
Hmm. I'm curious about this - it seems that since this is torrent-based, archivability should be trivial - as long as on person still possess the data, regardless of what the author does, it should be possible for other users to reach that data.

The issues you speak of (with a page going dark) are strictly due to things like DNS changes, right? So other users can still visit webpages by connecting directly to the torrent some other way - right?
It helped, thanks!
This could be done in a legitimate way. Suppose there were an AdFixPlus plugin with the mission of cleaning up advertising on the Internet by making sure every website conforms to an acceptable advertising policy that forbids intrusive ads. Users install it for free and advertisers pay for it.

It seems like that should be fine so long as both the users and the advertisers know what's going on, and there are alternative plugins with different policies out there.

Websites can forbid to serve users who turn off too many ads and users can refuse to visit websites that serve too many ads. But both sides would gain if some compromise can be reached. So it seems like a competitive market should evolve towards something that looks quite like this, with a middleman of some sort setting some reasonable rules, rather than one side deciding by fiat how it's going to be.

Of course ad networks and publishers do some of this already. They have policies about not accepting all ads. The constant negotiation about which ads are okay to show is part of the reason why Internet advertising is so complicated. But they are less focused on what the user wants since the user can't choose between ad networks; only the advertiser and publisher can.
That's fair, but my takeaway from this article was that screen readers were this whole other kind of thing that was so much more difficult to use. I could see that being true for someone who never used computers, or for someone used to using them a certain way and having to transition. And I worry that people will read it and come away with the impression that, since screen readers are hard, accessibility is harder and just isn't something they have time/money/expertise for. In actuality, much of accessibility is just using things as they were intended to be used, and attaching textual labels to visual-only elements. If web developers just used <button/> and <a/> instead of <div/>s for interactive elements, there's 90% of accessibility right there. You may be amazed at how hard of a sell just that much is. If the practice of attaching click/keyboard handlers to a <div/> were to be wiped from the face of the earth today and forever, I'd instantly love the web a lot more. :)

So yes, I generally agree that conversational interfaces are a good direction, and I'd like to incorporate them into the app I'm currently building. I just worry that the tone of this article makes the current state of the art sound terrible, when it's less the state of the art and more the implementation details of that state that makes things difficult.
From the other tabs, it looks like Kayne isn't smart enough to use an adblocker when he visits Pirate Bay.
Oh no, I totally understand - typing this on a happy hacker keyboard ;).

I'm just somewhat of a cynic, since my workflow tends to fall on its face when I'm on a server that uses special snowflake rc files. Furthering that cynicism.. these days I'm just using plain /bin/sh for any shell scripts just because of the amazing level of bloat that exists within bash.
Vaguely related, I hacked together a little tool called Olaf[1] for people who like to pip freeze but also like to have multiple distinct requirements files like requirements-dev.txt – Needs a little work still but I've been using it on projects quite happily.

[1] https://pypi.python.org/pypi/olaf
Sounds like a very cool concept. Few things I noticed:

- (not a native speaker) but the english-text in the video seems weird: „much tools“, „very hassle“.

- the landing page is too bloated in my eyes (colors, text), really hard to get a quick grasp of what it is about

Good luck!!

EDIT: - text-color on the signup form is black with a black background. Not sure if intended? Nearly impossible to read what I type. (FF 44.0.2)
People downvoting me–you have a media company which has demonstrable statist bias, crafting a headline that downplays the Military-Corporate Complex aspect of a story that couldn't possibly be any more of a smoking gun.

The chairman of Google–a company which enjoys more Presidential access than any other single company–chairing a board at the Pentagon.

Hence: the fix is in, something which should shock no one by this point.
We at Transit App have about 15000 routes, which were managed by one or two people or so until relatively recently. Manual mapping, an extra task, would not be feasible.

You also have to consider that just having good shapes for routes (which is often in the data anyway) doesn't mean you automagically get good transit maps. You have to decide when lines are travelling together, which Google apparently does by considering the stops that lines travel on. You can see lines stay together as long as they travel the same stops, and immediately branch at a stop when they branch, even though the physical branch happens later.
> That is an outright lie and the mere fact that this was published as truth shows the BBC is just a propoganda arm of the UK.

First off there's absolutely no propaganda benefit in that supposed lie.

Secondly they're trying to dumb down the history of public key cryptography, and what they mean by "once controlled by the state" is that James H. Ellis & Clifford Cocks discovered and implemented it in secret for the GCHQ in 1970-73. With Malcolm J. Williamson implementing the Diffie–Hellman key exchange in 1974.

In 1976 Whitfield Diffie and Martin Hellman released Diffie–Hellman key exchange to the non-classified world.

So what they said is right, if you specifically know they're talking about public key cryptography and know the history of it. It could have been better written.
I wonder how many public computers are configured to end sessions when the browser is closed? Actually, can you even configure that anymore?
You might want to add a 'motd' with a little welcome message and a simple 'help' listing the commands and a one liner for each of them (Autocomplete for some reason didn't work for me - Chrome 48, Mac).
This really wasn't my intent. I sincerely apologize for communicating otherwise.

I identify as blind or low-viz and wouldn't want to take away from others who also identify as such or as disabled.

That line was meant to be a response to the fears that it seemed like my family and friends had about my diagnosis. Fears, that I wouldn't be able to remain independent or be successful. You know how loved ones generally fear the worst possible scenario. Anyway, wording it this was was terrible, and I'm sorry. I'll see if I can make an edit and rephrase things.
https://www.consol.io/encryption/

> At this time, Consol supports encryption only of certain content types, viz. notes, code blocks, and images, for users who have subscribed to the E2EE component. The other content types available in Consol are not yet encryptable.

> Notably, Consol E2EE does not yet support encryption of the titles of any content types. For example, if you create a Consol note and encrypt it, the text you add to the note’s body will be encrypted but its title will not be encrypted. For now, you should operate accordingly. We plan to improve this in the future.

> You acknowledge that if you encrypt an item after you create and add content to it, there may be a period of time in which your item’s body content is not encrypted while being stored in our database. To ensure the greatest security currently available in Consol’s system, you should, where possible, encrypt an item in its pageview before you begin adding content to it. It is better practice in Consol to encrypt an item first and only then begin work by adding content.

> This means that for certain content types that require creation and upload before the pageview is visible, such as uploadable or linkable images, Consol does not yet provide a way to encrypt such body data beforehand. You acknowledge and consent to the attendant risk that you must manually designate certain content for encryption after it has been uploaded.

I don't appreciate having to dig through your FAQ to find the holes and caveats. There is literally no technical reason for this.

If you are going to make security promises like this you need to:

1) Actually have them implemented.

2) Have them secure by default.
Google is building a 100kW radio transmitter at a spaceport and no one knows why
Thanks for your feedback. The current flow allows me to see who's interested in the product, but may not be interested in paying. If the price was front and center from the get-go, I wouldn't have ever known of numerous users who showed interest.
I always found it odd, especially because he lives in NZ which is a very secular country. For instance no serious politicians will ever admit to their religiosity or lack thereof. Therefore it's a very unfashionable thing to announce in the context of where he lives.

Although an Atheist I kind of have to admire the fact that he believes so much as to put it out there and have it define him, especially when it is so unfashionable here.

I also find it interesting when clearly rational and intelligent people have faith. It's kind of something that you would expect from people who lack in education, as it is a crutch. But I guess that's why it's called faith, it defies logic at least by my way of thinking.

Not meaning to offend anyone with the above, so sorry if I did.
its pretty amazing how few people seem to have base domain knowledge of core market infrastructure considering how many people work in that area and that it isn't particularly tricky. It certainly colours the opinions of everyone here jumping to entirely silly conclusions.
> First, HFT firms aren't especially lucrative compared to other finance specialties, so one answer to that question is "nowhere".

Total bullshit. If there was so little money to be made why is every exchange catering to high frequency traders? Why was the building across from the NYSE hollowed out to become a data center? Why are custom fiber optic cables being layed down specifically for it?

> If you're a retail trader, automated electronic traders make money off you by outbidding the markets to quote good prices to you for your dumb market orders, and then pocketing the spread --- in other words, they make money the same way market makers have always made money; they just make less of it at an instant, but at a far larger scale.

This seems to be typical of HFT apologists. They start to use terms that are defined in other terms that they've essentially made up, much like trying to get to the first principles of a religion. There are no 'market makers', there are people selling with a miminum price and people buying with a maximum price. They aren't outbidding the markets, they are front running by seeing an order, buying it, and then selling it to the original buyer. Everything else is there to obscure the truth. I've seen so many of these posts here and none of them has ever approached any sort of justification or validity.
It's more "Less is Better"; today for a password login system you need to have and secure:

1. Password database
2. Password UX
3. Forgot Your Password UX
4. Forgot Your Password one-time-use token via email/SMS

This drops 1 and 2, leaving 3 and 4 as the remaining security footprint.

(I also think that Persona was heading in the right direction and wish it had received better traction.)
> For my profession as an executive it would've been more valuable to get a Bachelor of Laws instead.

How would knowledge of law, as opposed to having all-rounded knowledge of business administration and a network of people with similar backgrounds, help as an executive?
Not OP but we use Jenkins for our CI which has a plugin[1] which fails builds if a threshold is not met.

[1] https://wiki.jenkins-ci.org/display/JENKINS/Checkstyle+Plugi...
> - (not a native speaker) but the english-text in the video seems weird: „much tools“, „very hassle“

This is a play on doge speak[0]

[0]: http://the-toast.net/2014/02/06/linguist-explains-grammar-do...
Incognito Mode, In Private Mode, whatever you want to call it. Browsers now give you a spiffy, hard to miss logo when in such a mode these days now too.
You have to pass pip the --process-dependency-links flag at install time (which is pretty shitty if users are expecting to be able to install from PyPi normally) and it will ignore your dependency links if it thinks there is a better package available at PyPi (e.g. some other package with the same name has a higher version or the GitHub repo has some critical bug fixes but still has the same version as the PyPi package). Sometimes you can fool it into working, but it's just been such an unpredictable mess that I've given up on dependency_links for software that's distributed to third-parties.
Thanks Robert for signing up for StackOverflow just to answer my question http://stackoverflow.com/q/34488237
Bruce,

I appreciate the above piece. You're right; ad-blocking is a must. What with malware vectoring, tracking, bandwidth robbing, and other issues, I block all ads, tracking, Web beacons for the sake of my own sanity and safety whilst online. I'm always mildly shocked at friend's places if I need to use a computer or am asked to "fix" something. Their PCs are awash with the flotsam and jetsam of the WWW, sometimes so badly only a re-install will correct it.

I'm toying with the idea of creating a non-browser-based piece of software that blocks all this junk whilst not letting on to the websites it's been blocked. Something similar was done under Linux/*nix boxes whereby we simply created a symlink to /dev/null for Flash Player to avoid the LSOs (Super cookies). We could watch Flash content, but nothing was ever written to disk. I need to look into doing something like this using a method like the current ad blocking subscriptions.