skysight-inc/HackerNews huggingface dataset:
Is anyone familiar with transcranial alternating current stimulation? As a synthesizer geek with a lot of, ah, neuro-introspective experience, modulation seems like a very natural avenue of exploration to me. I get intense pleasure sensations from simply listening to certain kinds of sounds (not necessarily in a musical context) and find it therapeutic to play and adjust droning noises at low frequencies, and have experimented with generating interfence patterns at brainwave frequencies as well as resonant frequencies of the body or harmonics thereof (eg the sort of sub-basses you can feel in your chest). I had actually been thinking about picking up a NeuroSky measuring headset because their SDK includes a tool for MIDI translation, but I'm also curious about tA/DCS.
I clicked the Create a list text on your homepage instinctively. That's how people use the web. It should be hyperlinked.

I like the idea of making lists because it speaks to my passion for process. I want to be able to bookmark lists as well as monetize and own my content. If I can run my own ads on the site, then I'm less scared of creating original content through that venue. Your terms of use sucks and is not favorable.
How were you expecting to make money?
Thanks - this has been in the back of my mind and is a reason I'm trying to be patient. A 2 line message saying what was happening would remove my frustration. Usually I get a corporate speak reply with a suggestion it is my fault though. What does the FDA code review do? If it isn't catching bugs that take the scanner offline for hours at a time, what is the point?
As Bruce Schneieir says, it is poor civic hygiene to even let the systems be built in the first place. Unfortunately we are well past that point.
I would say that many if not most of the issues in front-end webdev have been / are being fixed (web components, flexbox). Supporting non-evergreen browsers (ie. IE < 11) is what makes the task difficult in my opinion.
Spawning only a few babies as "we" do it is important to only spawn healthy babies. The first test is the "great swim" of the sperm. The second is the health of the mother in the next 9 month and the "last" one is surviving birth. This making only the fittest/suitable survive.

And that is why "routing" it something hard makes sense.
Swarm founder here. We have a very unusual organizational model that allows people to represent the Swarm without having an "official" status within the organization, which means that we are always at risk of some degree of misrepresentation. After this specific interview I issued a "Legal Action Plan" that specifies the particulars of our near and long-term legal strategy, such that no one makes faux pas like "we’re launching it entirely outside the system."

That said, a lot of these subtleties are lost on non-native English speakers, which at the moment is probably the majority of the Swarm.

The full letter can be read here:
https://docs.google.com/document/d/1b6krYF6rMECtTwmTjbcZWZ0l...
>>I'm very interested in technologies like GSS that ultimately don't try to change the behavior of the browser - just the behavior of the developers

To me, it's not fully clear exactly what parts of the process GSS is trying to change and what the full consequences of it would be. Even if I knew what it was _trying_ to change, I wouldn't necessarily make the assumption that the intended change would be the only change, or even the most salient change, that we as practitioners would actually have to live with. I have to look at something like this from every possible angle before I would trust any such claim, because, well... that's just what I do.

>>I personally would love for styling to get 5x faster. There's be no reason for me to charge any less for the work, so that'd basically be 5x more dollars for the styling portion of any given project

That would be great as long as it lasted, I'm sure. But, I expect that sooner or later, the secret will get out that websites just got faster and easier to develop, and your clients will start to expect to either pay less or get more for the same money. Even if your company doesn't charge by the hour, there's little doubt that some of your competitors are hourly. However it played out, economics is going to prevail, eventually.

I've been feeling some pain from CSS lately, which is definitely at least partly because there are newer tools and techniques available now that I still need to catch up on. My company has a guy who basically does nothing but handle the look of sites, and he ends up putting in some amount of time on practically every project we do. I have always thought of myself as a backend developer first and foremost, but CSS is hard to completely avoid.

>>and CSS is quite good at the non-layout side of styling

I don't know that I've heard it split into layout and non-layout before, but I'm assuming that non-layout is things like attaching colors and fonts to text, etc. CSS isn't bad for non-layout things, but, as far as I can tell, that is all of the easy stuff where there was no real engineering-type problem CSS had to solve, so, to screw that up, CSS would have needed to really work very, very hard at doing some inexplicably weird thing in order to have gotten that part wrong.
Ciphers: A Photographic Aerial Study
The fact that the money seems to be being spread around seems to be working well for the project.
Xikishell - interactive shell addon
I've come to the same opinion. Reading /r/bitcoin, people are losing their coins every week. And these are enthusiasts. The security just doesn't exist for mass adoption.

6.6% of all bitcoins have been stolen. When you consider around 60% of coins have never moved, that means a lot of the coins in circulation have been stolen.
Tearing doesn't necessarily mean your computer isn't keeping up with the game--you can get tearing with over 60 FPS as well. It just means the frames aren't in sync with your display.
The look and feel is cool and so is the map view but I think you should add more information about why those areas are so great besides just restaurants and hotels. Like a main attractions section since people don't just choose areas based on where they can eat and sleep
So far as I can tell, no traditional SQL systems have been tested. I'd lay a small bet that Postgres wouldn't lose data, although I don't even know if it has any kind of masterpool capability.
That's not quite correct. Our model includes a "Decentralized due diligence" aspect (https://bitcointalk.org/index.php?topic=664071.0;topicseen) that we believe greatly reduces fraud potential. Our full plan consists of a variety of fairly novel features, including crowdsourced project screening and fund-locking such raised funds are programmatically unlocked as founders achieve certain milestones.
This is something that I've thought about extensively. I'd be interested to hear your thoughts.

My thesis is thus: In the Information Age, data is subject to a kind of reverse economies of scale. That is to say, the more data you have, the more difficult it becomes to secure.

A website like MTGox is always going to fail. Period. Entropy is a thing, and there's no way to prevent 100% of security leaks. You can see the credit card economy leaking constantly as well.

What I imagine happening as time goes on is that businesses will start hiring someone to manage their public keys. Businesses already trust accountants with their finances. It's not a huge leap to imagine a specialized service industry catering to small business and dealing with private key management.

I feel as though trusting one person with only your company's data is going to be much, much more feasable from an economic perspective than trusting a large company with yours and 5000 other business's private keys.

This obviously won't work with the current "Payment Processing" infrastructure. It has drawbacks, certainly. But it seems like a world that can actually legitimately exist, in contrast to the MTGoxes and Moolahs of today.

I hope this makes sense. I'm not a infosec guy, so I'd love to hear criticisms of this paradigm/theory.
For scheduling problems, I have had way more luck with open source CP solvers like Choco than I have had with hyper-optimized commercial IP solvers like gurobi. Branch and Cut is just too indirect for constraint heavy IP models.
What did you spend $200K on? Just the design?

It seems like you have technical people on your team; so if you are not counting your time why is the number so high?

Even with design and team of two-three engineers consulting for a month or two that figure is extremely high.
A story on Anna Calvi, Vignelli and Legal Design
After having a look and reading your interview with marketingstartups[1], it is quite an interesting idea.

It strikes me as an evolved incarnation of Buzzfeed[2] in that the entirety of its content is user-generated, whereas this wasn't the case with Buzzfeed until recently, and even now, I believe user submissions are subject to moderation.

I don't think you should give up yet. I wouldn't. I would start by simplifying the design (sure, it looks nice, but it feels over-ornamented), defining stricter guidelines for posting (e.g. encourage "Top/Best X" type posts in lieu of general free-form lists, and figure out other ways to start driving traffic to it.

I wish you guys the very best and again, don't give up yet.

PS: Please get in touch if you'd like to talk more.

[1] http://marketingstartups.com/2012/12/18/interview-with-listn...
[2] http://buzzfeed.com
Could you explain what you mean by security primitive?
JOOQ + Java 8 Streams = No more ORM
But who would want to hack a lightbulb? http://www.gunpointgame.com/
> Most of the MongoDB hate comes from the PostgreSQL crowd.

Or anyone who doesn't like losing their customers' data.
Move to a foreign country without much cash for a summer or so. Hopefully your employer is accommodating; if not, find a good story or line-up a new job. It's an incredibly liberating experience. Puts a lot into perspective.
1. Yes, thanks to Armin's great work, this improves language support for parallelism. It doesn't improve support for concurrency patterns (like coroutines and channels). Python now has concurrent.futures, yield from, and the (overly complicated) asyncio library, which provide a toolkit for concurrent programming patterns, but it's not really beautiful nor a joy to use. That's part 2 of Armin's proposal, and he's asking for donations to fund it (see the link above).

2. Until recently PyPy was still regarded as an experimental side project, and had memory use limitations that prevented it from being a drop-in CPython replacement. CPython is a simpler codebase than PyPy and supports more targets and environments. PyPy does deal with native C code via cffi, but there is a lot of code that uses CPython-specific C bindings that will need to be updated to run on PyPy.

3. I think the Python world is doing great. The Python 2 to 3 and CPython to PyPy migrations are largely orthogonal, and will coalesce to "PyPy 3000 with STM" soon enough. Once that happens, I think that will serve as a really powerful foundation for future improvements. (Writing code that runs on both 2.7 and 3.3+ is not that hard, by the way.)
1. Well -- unless I misunderstand, they use STM to emulate a GIL (while actually letting stuff be done concurrently). Which means that it will still be a bit of a hodgepodge messy disaster.

2. I can't speak for Dropbox, but I worked in a shop that bet their future on Python -- and we spent a good bit of effort looking at PyPy ... it was a nightmare if anything went wrong -- a horrific impossible to debug mess.

3. Yep, I added Python to my "won't work on" list of languages (with Cobol, Progress and MUMPS).
If it's a small app, just use Maria or Postgres. IMO, the only time to even think about using one of these non-traditional stores is when you've scaled past what SQL systems can offer. And even then, I'd use the non-traditional store like I use a C extension in Python -- only for the parts that can't scale without it.
Thanks to CSS not having that from the start, it led to the situation we have today, where there are at least two different preprocessors to choose from: Sass and Less

Having two solutions is worse than having one solution, and we can credit CSS for creating this situation by not having its own.
Who are these "psychology people"? Automated coil placement exists, for example: http://www.rogue-resolutions.com/system/axilum-tms-robotics/ .
Flag of Bikini Atoll
Nah, he already tested Postgres: http://aphyr.com/posts/282-call-me-maybe-postgres
The best place to stay in Denver, CO is Downtown/17th Street Mall. It's actually the "16th Street Mall", although I do agree it is the best area.

I suggest adding (a) a brief explanation of why it is the best place to stay, and (b) more than one place. Denver (for example) is varied; depending on what you're looking for, you may also want to stay in LoDo, or Cherry Creek.
Show HN: Simple group contact sharing
You don't, really. Bugfixing by whole-program code inspection is incredibly inefficient and quickly because impractical with large codebases.

I've found its far better to hunt down bugs using a combination of debuggers, stacktraces, divide-and-conquer, log statements, assertions, and unit tests. I've gotten bugfix rates as high as 5 bugs/day in a fairly complex library (an HTML5 parser in C) using these techniques.
Made this app while I was learning AngularJS. It's quite useful for getting the contact information of everyone in a group (instead of having to pass around phones and risk missing numbers, etc).

Figured I would throw it out here instead of it sitting around on my hard drive! Comments and feedback welcome!
The content and audience are I suspect far more important than what your site does at this stage, and you should narrow the scope on both of those.

You have what looks like a serviceable site to produce lists (not really a complex challenge). I'm not sure why you think your site sucks? I'm sure you'll get some feedback on styling, content etc (it's not really to my taste, but hey, it's not terrible either), but if you are seeing slow growth, it's probably not because your site tech/design sucks, it's because no-one really deeply wants to make lists in the first place. The idea and marketing is the problem, not the execution.

So, who is the site for, what's the target market/demographic? Who are they making the lists for?

Perhaps instead of targeting everyone, you should narrow your focus, and start targeting a particular market. This sort of site needs either a very specific focus to which the list making and content are tailored - say shopping lists, or it needs a specific demographic.

If you want to make this a social site, perhaps target a demographic like Norwegian teens OR mums if you have experience there, but don't target the entire world from the start.

If you want to make money from shopping, maybe tailor this to just best of lists of products for particular niches and invest in content?

As it is I don't see how lists about These 7 Things Will Make Any Man Want to Fight for You and Best Tracks in Mario Kart 8 are going to keep anyone on your site. The content just isn't compelling at all (there are hundreds of existing content farms churning out stuff like this like buzzfeed etc) and it is far too scattershot.

PS Install some caching software prior to posting on HN :)
Some advanced techniques applying Markov chains to load testing. I submitted to HN but no-one was interested in it as a stand alone. Maybe people already interested in them here would like to see how to make them dance in practice.

http://edinburghhacklab.com/2014/03/taming-randomized-load-t...
Interesting article, would have been helpful when I was writing a paper on Google PageRank since it is a markov chain. I do think it would be valuable to talk about equilibrium distributions and how you can determine the tendency of the system
Never observed shitting the bed -- Zookeeper: http://aphyr.com/posts/291-call-me-maybe-zookeeper

"As with any experiment, we can only disconfirm hypotheses. This test demonstrates that in the presence of a partition and leader election, Zookeeper is able to maintain the linearizability invariant.

Recommendations

Use Zookeeper. It’s mature, well-designed, and battle-tested."

Doesn't Shit the bed when used correctly -- Riak: http://aphyr.com/posts/285-call-me-maybe-riak

"Is there no hope? Is there anything we can do to preserve my writes in Riak?

Yes. We can use CRDTs.

If we enable allow-mult in Riak, the vector clock algorithms will present both versions to the client. We can combine those objects together using a merge function.

...
CRDTs preserve 100% of our writes.
...
Moreover, CRDTs are an AP design: we can write safely and consistently even when the cluster is totally partitioned–for example, when no majority exists.
...

Strategies for working with Riak

Enable allow-mult. Use CRDTs."

There exist methods where by it wont shit the bed -- Cassandra: http://aphyr.com/posts/294-call-me-maybe-cassandra/

"CQL and CRDTs

Without vector clocks, Cassandra can’t safely change a cell–but writing immutable data is safe. Consequently, Cassandra has evolved around those constraints, allowing you to efficiently journal thousands of cells to a single row, and to retrieve them in sorted order. Instead of modifying a cell, you write each distinct change to its own UUID-keyed cell.

Cassandra’s query language, CQL, provides some collection-oriented data structures around this model: sets, lists, maps, and so forth. They’re CRDTs, though the semantics don’t align with what you’ll find in the INRIA paper–no G-sets, 2P-sets, OR-sets, etc. However, some operations are safe–for instance, adding elements to a CQL set:
All 2000 writes succeeded. :-D

That’s terrific! This is the same behavior we saw with G-sets in Riak. However, not all CQL collection operations are intuitively correct. In particular, I’d be wary of the index-based operations for lists, updating elements in a map, and any type of deletions. Deletes are implemented by writing special tombstone cells, which declare a range of other cells to be ignored. Because Cassandra doesn’t use techniques like OR-sets, you can potentially delete records that haven’t been seen yet–even delete writes from the future. Cassandra users jokingly refer to this behavior as “doomstones”.

The important thing to remember is that because there are no ordering constraints on writes, one’s merge function must still be associative and commutative. Just as we saw with Riak, AP systems require you to reason about order-free data structures. In fact, Cassandra and Riak are (almost) formally equivalent in their consistency semantics–the primary differences are in the granularity of updates, in garbage collection/history compaction, and in performance.

Bottom line: CQL collections are a great idea, and you should use them! Read the specs carefully to figure out whether CQL operations meet your needs, and if they don’t, you can always write your own CRDTs on top of wide rows yourself."
How one time password prevent me from work
I can't decide whether this is trying to be a lightweight meme site, a high quality luxury magazine product review site or some evil spin off of Facebook that my friends are just going to share ads with me.
But they are disconnected, one is running on the client, the other on the server. Regardless of any magical unified framework, there will be two processors talking asynchronously over network protocols. GWT does this kind of integration and it's far from a panacea.
Many have tried and failed. This undermines credibility.

I want to like Bitcoin but so much moves against it. Including the enthusiasts.
Backlink Çalışma İçeriği
http://www.hoofclub.ca/ufc-175-live-stream-watch-ufc-175-wei...
Geek business myths (2006)
I love that these guys think of 4 years as short term and 20 years as long term. Young companies often set up this dichotomy as a couple months vs. a couple years, which just isn't enough. Long term thinking is a big potential advantage startups have over public incumbents that have quarterly expectations, but it's usually not taken advantage of. Not just on founders obviously, whole startup ecosystem fuels this.
Kickstarter's "perks" model was not clear cut in the beginning. It became clear cut over time as the legal space was established. We are probably one step further than Kickstarter in that we offer things like programatic voting, but it's quite infeasible for us to offer "equity" at present and attempting to offer something like this is not even in our roadmap.
Nice idea but the design is a little dated. I don't know if that's intentional but people are fickle, and pretty / obvious always wins.
Indeed. A lot more people could be happy if they didn't believe in the lie that says you must be super rich to be happy. Lottery winners have already proven that a ton of money doesn't guarantee anything. Rich celebrities deal with depression.

Going from poverty to middle class is definitely an improvement, but there comes a point where more money doesn't help. Diminishing returns.
It is not for everybody, that's for sure. But if you want to run a giveaway of iOS promo codes on Twitter then you'll see that it is kind of a tedious task. You need to constantly check who retweeted your tweet, get a new promo code from the list, send a message to the person, delete the promo code from the list of available.. I was so bored doing that, I decided to build this service. :)
Also, you get extra exposure every time when your tweet is retweeted by one of your followers.
> Ruining the fun for everyone of us :(.

Enough of us have more fun reversing or breaking crypto applications :)
I think a manager for a product would give as much work and responsibility to one person as possible if they say they can do it, and sometimes even when they say they don't know if they can do it but they'll try. An experienced manager might know how realistic the workload is and downsides of having only one person on task x but every manager sees the upside, fewer people = less cost.
Wouldn't specialized computing devices ("hardware wallets") carefully designed with limited communication capabilities and requiring physical user confirmation for the transactions fix the most issues?
This iPad app helps keep the Air Force from crashing planes
How to Incorporate your Startup in USA?
On Cassandra, some CQL collection operations behaved well (adding elements to a set). Everything else Kyle tested there was demonstrated to lose data.

Kafka lost data all over the place under Jepson; though Kyle offered great respect to the team and expects them to deliver optionally configured safer semantics (at a performance cost) in future releases.

Riak was totally solid when using CRDTs and turning off the insane LWW default.
I like the idea but my first impression is that the front page is a tad overwhelming. I didn't actually read the top green pane until after looking at the images, which may say something about how users look at the content.

Perhaps interestingly, my first click was to Browse Top Lists, only to find that Porn Actresses, Page 3 Models and Hentai artists all feature in the top 5 and 4/9 trending lists have the same pink handbag image, even for the Best Web Apps list. You need an adult category which you can hide the NSFW lists in and then not display this to logged out users. As already noted, I think the content is your biggest problem; I may not be your target audience but regardless there's little there to be encouraged to comment on or find inspiration from for new lists.
It makes me uncomfortable as well.

But keep in mind that at that time, it may have well been the only programmer on the project, and that the manager was not likely qualified to read code.
The rest of the world would prefer the US to have its wars on its own soil though.