skysight-inc/HackerNews huggingface dataset:
> You are welcome to keep thinking...

I get it. You don't believe the problems are real. Or you don't believe that the drugs are effective at treating them. So I'm lying. And other people are lying. We're all lying to you, part of the vast conspiracy of children who never actually went through something that you didn't go through. Congratulations, you found us out! Or maybe you don't actually know everything.

> You are welcome to keep thinking you are doing yourself a therepeutic solid

I'll do you one better. My mother's strong advocacy for my mental wellbeing saved my life and ultimately made me an understanding and compassionate person who listens when someone tells them about real childhood trauma from being literally unable to read until the medicine magically fixed what was wrong.

> I feel bad that you think amphetamines are some class of "lifestyle" drug

I feel bad that you don't understand that different people have different needs to be able to function, and that sometimes things go wrong in ways that are fixable. I feel bad that you don't understand that people are very often willing to accept harmful side effects because those are less bad than the alternative.

> one of the most simple drugs around

Simple, eh? Let me tell you a story about a little drug called Lithium Carbonate. We can compare.
This is good news for me.

My company was considering Slack - the only reason it was agreed was due to the IRC gateway.

So it looks like slack is out of the question now.
Rails code can get that deep, the difference being MRI doesn't have an inlining jit...
Fourier-based techniques (FBT) and sample slicing (SC) may be similar if doing "raw" transformations, but FBT can potentially be cleaner, or at least easier to clean up. If you use raw "bit-maps" for FBT, yes it will be choppy like SC, but one can use regression or regression-like curve-fitting to give FBT smooth time/frequency curves to synthesize against, sounding more natural. There are down-sides to using regression, but for typical voice and music, those won't matter much.

One rough area for curve-fitting is white-noise-esque sounds (WNES) like the letter "s" or "h" and tambourines. The processor can perhaps detect if WNES exceed a threshold, and use other techniques such as SC instead.

It's roughly comparable to JPEG versus GIF images. JPEG is better (more faithful) at gradual shades while GIF is better at edges. A better compression algorithm perhaps would use each where it does best per given image. However, at the cost of algorithm complexity and compression/decompression processing time.
With this I can run Debian Sid/unstable on Windows 10 Version 1709. After editing the sources.list and upgrading all packages, apt starts to complain about missing seccomp support but this can be worked around this way: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1732030/c...

I haven't noticed any other issues with the newer packages.
Honestly, I don't think you can point to any actual business reason for a native client. Slack makes majority of their revenue from large organisations buying thousands of seats in one go and a native desktop client is sadly not a huge selling point for the sales team.

At the end of the day Slack has to optimize for growth and there's a huge list of features that will bring more ROI than native clients which will require trebling the size of the code base.
Does restricting access to the mic from idle programs also conveniently prevent any competition to Google Assistant?

That's kind of unsettling because it seems Google is doing a lot of data collection through their home speakers.

An anecdote:

I got a little creeped out at assistant / home and disabled all the tracking. Almost immediately my Android phone started harassing me to turn permissions back on through my phone. And Google Home refused to do anything with tracking off. It responded to all wake prompts with "you need to change settings".
The ~600 person distributed company I work for doesn't use phone or email and obviously doesn't do anything face to face. We relied on IRC for years before switching to Slack so yes, all of our real-time communication is via Slack. We have internal blogs for threaded important async discussion though, but Slack is where our high bandwidth talk done.
Yes, it's even included in the Riot UI.

Note that unlike IRC, where bots or users must be on the same server rooms are completely independent of any single homeserver. There's nothing that says a room belongs to a certain homeserver. So the bridges set up by matrix.org will work with any room, unless you explicitly turn off federation.
https://www.wxwidgets.org/about/
http://www.netzfrequenz.info

All power grids are connected, so there is just one frequency.
A "Google Assistant" competitor.
There's an explanation here:

https://stackoverflow.com/questions/47220595/why-the-6-in-re...

It's an arbitrary value, but 6 fits best into 8 bits.
If somebody wants to definitively answer this, there's no reason you couldn't just say random advertising related words in front of your phone (1 per day) and check how many come up in your search. There are basic statistical methods to establish if the results can be explained by chance.

This would have the upside of not requiring any reverse-engineering.
Let's not forget designers, illustrators, accounting, onsite-building security, benefits people, account managers, mid level managers, execs, advisors...
At a glance, no. PAS is our distribution of CFAR, what you might think of as "classic" Cloud Foundry.

Our k8s distro is PKS, which is the closer one here.

Disclosure: I work for Pivotal.
But technological advances are fairly static. If you lead in some kind of technology, that tech won't suddenly cut you out, or cut you off. Plus, government does tinker with its internal economy, protections etc.

Another question is why goods are cheapet; cheap labour is often associated with poorer working conditions, and fewer consumer protections, relying on the "market" to deal with legal issues (e.g unsafe products) diesnt really cut it.

Financial markets cherry pick their domains, heavily structured representations thereof - and they ate still known for being irrational and prone to panics etc. The point is "the wisdom of crowds" doesn't work against strategic trade attacks.

Your answer to my question is based on your own metaphor of "steel produced in Iowa". There is no steel produced there, only a dependency on foreign steel. If an external country needs X that they would trade for steel, they still need X if they won't trade the steel; but maybe the US can use it's own steel.
It's good to know that there are decent people out there, but as an American who isn't white, I don't why anyone would go through the trouble of living in the Midwest if they had the choice. If anyone wants to move to the US, I always tell them to avoid the midwest and Texas like the plague. There's no point in being in an area where a significant number of people hate you because of your skin color.
and still is now that the fees are low again and spam attacks pushed off
I like it, I might add that to the description. But what sets a Heathkit apart from a regular kit? Sometimes I describe it as "a place for virtual kits". (Also, didn't Heathkit make a little bit of a comeback? http://heathkit.com)

It would indeed be great to have more types of designs. We've had an influx of animal shaped PCBs recently (partly my own fault [1]) so I am on the search for some rectangular green, serious ones to offset that. I feel like it's slowly getting to a point where it's worthwhile adding categories.

[1]: https://blog.monostable.co.uk/posts/etching-oscillators-in-z...
Looks like a well thought out tool. Though to get me or my team to adopt it I'd need at least a sprint or two of a free trial. I hope it gains adoption. It probably says more about me than the business strategy, but I don't think I've ever bought a tool that I couldn't try or play with first for free.

What I'm not sure it does, and would hope it does, is provide a WYSIWYG way of CSS layout. I.E. under the hood it's using css3 to layout, but in a way I don't have to think about it, and could output it after I get the design the way I want.
Loc – Count lines of code quickly
Came here to say this.

I was on slack in 2015, took a break and came back in 2017. Nothing changed - no new features, and yet it was less reliable than I remembered.

They aren't even up to date on emoji. I just can't find symbols I expect to be there. Talk about low effort. And yet they had time to redesign the ones they did have (and the new ones are fugly).
Sure we do. It’s much more efficient to have some engineer pulling down crazy money to buy existing housing stock or move in with 6 roommates as compared to ripping down and replacing buildings. It just sucks for everyone when there are thousands of those engineers sucking the oxygen out of the city. You could say the same things about the $2000/mo trailer parks in South Dakota when gas booms.

I live 4,000 miles away. My humanity doesn’t require that I have an apartment on 5th Avenue. Instead, I own a home where high quality housing runs around $100/ft.

Fundamentally, the reason you don’t live in Cleveland or Buffalo is that aerospace and other industries left and moved to California 80 years ago, largely because it was cheap to buy an Orange grove. Capital and the investment culture of tech is why SFO is the way it is. Until that changes and Google Omaha starts impacting demand, you are stuck.

Markets are about control. Not fairness, not what is right. If you don’t control the votes, and don’t control the land, you don’t have a stake.
What is a temperamental UI? It must have something with UX to do I am sure but can’t find anything on the first page of Google about it aside from one page that mention avoiding UIs to be temperamental but firstly that was all that was said it seems and secondly the forum is was posted on was, ironically, completely broken on mobile such that the text could not be seen. The page had a mobile navigation bar and the zoom set to mobil unchangeable but the content is wide like on a regular monitor and cannot be scrolled into view and additionally there is a sidebar so only the first few letters are visible of each line of text. It was about the worst thing I have ever seen on mobile. Obviously they have wrapped a forum solution in their own templates and their templates are responsive but the forum content is not. So I guess the people that run that site don’t browse their own forum in a mobile browser. Anyway I digress.
Probably because a call is the most reliable way of getting the alert. There are many places in my apartment in which I can't get enough reception to browse a webpage but still can receive and place calls.
These numbers sound large, but are probably too low by a factor of 10.
PS: Here is the link https://www.lean.org/FuseTalk/Forum/messageview.cfm?catid=49...
You can do one more thing that may be extreme, depending on where you live now. You can move to a country covered by GDPR.

If you're in the US, you can also be a privacy activist, which we need more of.
Snapchat and Nextdoor are great examples. The former runs most infra on Google App Engine, and the latter runs primarily on AWS.
Researcher: New forensic analysis indicates bones were Amelia Earhart's
Don't you think it's more likely that they just aren't noticing the ad before it is relevant? I mean, how often do you really notice an ad anyway?

That being said, perhaps the ads are doing their job and planting the idea for that particular product. You then bring it up in conversation or mention it out loud. Then, when you return to facebook later, you see the same ad again and due to it's recent mention, it jumps out at you.

Both seem more plausible.
I'm sure this being Android you'll be able to whitelist apps to allow background data collection. You'll just need to find the right setting.
When they were stiill using drop down boxes to select the days and months.
So he re-built Gradle, or Buck, or Bazel, or any number of roughly similar it-runs-a-dag build tools? Not sure I buy that his problem was real. Gradle's the only one I'm meaningfully familiar with and making custom commands over a dag is a breeze.
There are a few. They're pretty good, too
Eric Ries on How to Make Gatekeepers a Source of Power and Speed
VHacks – A hackathon at the Vatican
Gatekeepers sit at the root cause of many significant problems in our institutions and companies (including startups).

Eric shows how to redefine the context around their work to make the entire organization more adaptive.

This is the most significant thing he's ever written.

If you sell to enterprise customers, this is a playbook on how to win deals faster and reduce the cost of Customer Success.

If you care about changing society's public institutions for the better, this is where your bright ideas will live or die.
I don't really see how that's superior to anything. It adds complexity to a system that's already hard to understand to large slices of the voters, and provides nearly no actual advantage to either the old paper ballot or the new electronic system.

A potentially better approach would be to have the systems themselves publicly auditable and somehow have the live ballot devices verifiable.
Thanks for sharing Kitspace on HN, your site looks promising. At first I thought it may be hard to gain traction over the established players (such as Tindie), but after looking into how the site works it looks like it has the potential to lower the cost for acquiring the hardware, as well as reduce the customer support burden for open hardware creators. Nice work!

Any short term plans to expand the site further?

I had thought that selling solder stencils perhaps might be a good optional extra for larger boards, but I guess they could prove a little expensive. Cheapest I've found with a quick search was this site:

https://www.oshstencils.com/
If you need an F500-friendly kubernetes platform, Pivotal has PKS. Red Hat has OpenShift. I imagine either of us would be happy to listen to what's worrying you.

Disclosure: as you might have guessed, I work for Pivotal.
Cool project! This reminds me of an idea that you're awfully close to: optimized small-volume part kitting. I can order boards from OSHPark and stencils from OSHStencils, but figuring out which distributor has parts in stock for the lowest price and in the preferred packaging still takes an inordinate amount of time. The Octopart BOM tool is the closest thing I know of, but it will only let you fill a cart at a single distributor. Going in one step from BOM to ordered parts from multiple optimal distributors would save a lot of time.
This looks much worse than it actually is. You could implement it in a much flatter way.

function HandleRequest(request : Request) : Response
{
LogRequest(request)

CheckAuthentication(request)
CheckAuthorization(request)

var response = DispatchAndHandleRequest(request)

LogResponse(response)

return response
}

This way you would have no deep stack traces and all would be fine. But only until you need to do some additional work somewhere right in the middle, say patch malformed requests between authorization and dispatch. With the above implementation you would be somewhat screwed, the best you could do would be reimplementing HandleRequest() with your additional step in the middle.

But with implementations like those show in the article you just have a list of steps with a common interface, each step does its work and then the next step gets called. If you need to do something new somewhere in the middle, you just add a new step to the list of steps in the right place and you are done, possibly simply by putting the class name of the new step in a configuration file.

var steps =
{
new LogRequestStep(),
new CheckAuthenticationStep(),
new CheckAuthorizationStep(),

// This stupid XYZ client always sends broken requests.
new PatchMalformedRequestFromXyzStep(),

new DispatchAndHandleRequestStep(),
new LogResponseStep()
}

function HandleRequest(request : Request) : Response
{
var context = new Context(request)

foreach (var step in steps)
{
step.Execute(context)
}

return context.Response
}

This would still avoid deep stack traces because we are iterating over all the steps but note that with this implementation we would not really be able to abort processing the request somewhere in the middle, say if the authorization check failed, but we could fix this by adding a flag to the context and check it inside the loop after a step executed. But a more serious limitation is that every step only gets one chance to act, note for example that we have two separate steps for logging the request and the response.

Imagine we wanted to log the request duration, then we would need a step getting the current time at the beginning and another one getting the current time after the request was handled at the end. And the first step would have to somehow communicate the processing start time to the second one, possibly by storing it in the context. A much more elegant solution is to organize the list of steps as a linked list with all steps looking like this.

function Execute(request : Request) : Response
{
PreprocessRequest(request)

var response = GetNextStep().Execute(request)

PostprocessResponse(response)

return response
}

This creates those deep stack traces but it also creates a huge amount of flexibility and extensibility. It surly looks crazy if you do not need it, but when you need it, it is really easy with this model.
I don't think that documentation truly exists. You can read the Gtk+ documentation and the Cairo documentation, but that really only tells you what the APIs do in the grand scheme, not why they were added, what problems they solve, or the gist of how to get best perf. Most of the time when you're writing new widgets you only care about drawing lines, placing icons and laying out text, for which Gtk+ has fast higher level mechanisms and you should use those (see gtk_render_line(), gtk_render_icon(), gtk_render_layout() and their friends). When in doubt, use the newer widgets and functions (the ones with the latest "Since:" annotations), since they have usually replaced older functions with worse performance or behavior. If you're lucky, those new functions will even document why you shouldn't use the old function anymore...

The general theme of working with Gtk+ is "do as the library does", as it's mostly been written and maintained by people who know these things through decades of experience and that code can help guide you towards avoiding bad behaviors (like the famously bad StackOverflow-style toy example code that creates an image surface, renders some clock or gears vector image to it imperatively, and then setting that image surface as your widget cairo context's source and rendering the whole image to your widget and wondering why you can only get 10 fps vs using gdk_window_create_similar_surface() to make your offscreen rendering target, splitting your drawing up into the "clock face background" and the "clock hands foreground" pieces, and only re-rendering the hands as they move or even prerendering all of the different hand positions to another offscreen buffer and blitting the pieces as necessary and suddenly realizing you can get hundreds of FPS easily.)

Sadly all of this means source diving a lot of the time. And it can be hard, especially in cases where you want to stray off the beaten path and do a completely new widget design - you will want to find and make friends with great GNOME people as they can really mentor you through these more complicated widgets until you get your legs under you.

The toolkit as a whole is moving towards a model more like that of modern browsers, where widgets are conceptually smaller and simpler and composite widgets and layouts are more of what you actually have to maintain. (A good example of the latter is looking how complicated the current code in GtkSpinButton was, compared to how conceptually it could be a much simpler composite widget that only handles the key/button events between a pair of buttons and a text entry).

This shift in design is a boon for many application developers, but it can mean really struggling if you want to write or maintain complex applications with components such as drawing canvases (e.g. the GIMP) and layered cross-process rendering (I used to work on VMware Workstation...)

You can help! Document your findings as you learn, write patches against these libraries and their documentation, get it reviewed and committed. The Gtk+ folks are not scary to work with, just very opinionated.
Sounds like she is just more context aware. I skim past ads and never notice them. Some people might take note if the ad is something they had recently discussed.
I think Google provides the longest upgrade period among all Android phones (Which clearly is not enough). But the good thing about Nexus/Pixel is that the bootloader is unlocked (if you buy Pixel from the Google store not Verizon). An unlocked bootloader enables you to flash cutom ROMs on your phone.
For snappiness, most of new phones with Android 8.1 are fast enough.
But again, if there is a big community for that phone in XDA (like with Nexus phones), and the bootloader is unlocked, you will be able to flash new versions of Android for a long time.
The Guardian is reliant on advertising as much as subscriptions (though there is then the income from its trust investments and other assets, which are dwindling and at risk).

The BBC is reliant on the support of the UK government, who essentially control it's future.

Serious analysis of the editorial lines of The Guardian and the BBC show pretty consistent pro-corporate pro-establishment bias.
Basically, there are people using power on the grid without paying anyone to generate a corresponding quantity.

This means that less power is going into the grid than is being taken out of it, an amount that has accumulated since January to a bit over 100GWh. This missing 100GWh of energy has been collectively sapped from the inertia of the all spinning synchronous machines connected to the grid - mostly generators, but also motors - as a result of which they are spinning slower than they should be. Slowing spinning synchronous generators means a lower grid frequency.
Break time in big sport events also leave there fingerprints in the grid frequency. Everybody start to make a coffee, go to toilet (light), etc.
The JSON support in Postgres is in my experience much more consistent than that of e.g. MongoDB, and I understand performance is better too. Postgres really is awesome :)
Table top gaming. Board gamers are particularly keen to be around people while being totally engrossed in not talking to others. And there are some really good games that have proliferated in the last 2 decades.

You may have to find a way to work past some asocial/antisocial behavior. But they certainly won't judge you not wanting to experience 'the nightlife'.
Yik Yak comes to mind; the product died but they got acquired by Square for the engineering talent. I can see VC's seeing a solid team of engineers as an asset that's potentially more valuable than the actual product.
Road to Hana is a great outdoors option. Lots to see along the stops, waterfalls, natural landmarks.
This is easy to understand. The autonomous cars I've encountered drive terribly. They signal too early, leading other drivers to believe they are turning into a business instead of at an intersection. They drive slowly in the wrong lanes. They don't adapt to surrounding conditions. They have no situational awareness.

Of course, the company will blame the humans, but the cars are not designed to broadcast visual cues that human drivers do.