skysight-inc/HackerNews huggingface dataset:
Exactly! And the gold weapon would be able to see all employees' corporate and private emails, along with their search queries. Uh oh.
Thought: _hmm there's a business opportunity of lemonade stand scale here_.

Sure enough: https://www.amazon.com/WhatKeys-Keyboard-Shortcut-Stickers-W...

$8 would have been instant click. I program for a living on a Mac and still can't remember the damn 'option' symbol in shortcuts.

$20...? Hmmm. Not so much. Where's that silver sharpie...
Interestingly with SSD storage devices, control of the hardware can help a lot more as it can become possible to categorize, fully explore and if needed, ensure a particular behavior of commands like TRIM. Other filesystems have the unenviable task of running on any random piece of storage you throw at it, including things where the firmware straight up lies, or the hardware delays non-volatility past the point the filesystem assumes (potentially producing data loss in a crash) or similar types of problems.

Anyway. Overall, I think it's safe to say hardware control doesn't make most of filesystem development much simpler or easier. But there's a few interesting places it arguably does!
in the UK from here - https://www.overclockers.co.uk/evga-geforce-gtx-1070-founder...
Ideally that's what I'd like to see as well, but in practice, downvotes are used overwhelmingly to express disagreement here, with little regards for the quality of the actual post. I'd love to see something in the official guidelines to discourage this toxic behavior.
Letsencrypt.org vous livre sa base de données emails gratuitement
Ill chime in with my $0.02

* Inability to invalidate stateless JWT tokens can be more or less be remedied with a short expiration time of the token and a token refresh flow. If a token is only valid for 5 minutes, and you can only refresh the token during that 5 minute window, it greatly reduces the attack vector. If that risk is too high, you should easily implement state with the same Redis setup that author mentions

* a classic CSRF example where youre logged into your app in one tab and you open a malicious link in another tab is not a threat if you, like the author suggests, use cookies for storage, but not for authentication. If you pass a token around in an "Authentication" header and have the server IGNORE the cookie which will inadvertently be sent, the request made in another tab via a malicious website is not going to be authenticated.

There are definite Usability and security pros to using Session cookies for storage:

* Unlike Session Storage, the cookies are visible by your application if you have two instances of it running in different tabs/windows.

* Unlike Local Storage, session cookies get wiped out when the user closes their browser
But all laptops do.
for the Marvel fans, longing.rusted.furnace is a mountain road north of Verona, Italy. The system doesn't use numbers, so thats as far as you can go if you want to write some sort of Winter Soldier fanfiction based on this.
I had to prepare a developer improvement program recently. After doing a lot of research, I thought plural-sight was an invaluable resource. I don't get anything in return for promoting them. I think it is time and money well spent.
I really can't stand the whole 'Marie Kondo' bs. Ask your grandparents about quality and you can skip the nonsense. Buy what you need, save before you spend, buy quality and repair your stuff rather than throwing it away. It's just common sense.

This stuff only works on people that are easily pushed by marketing and advertising to fulfill needs they didn't have in the first place and end up with houses full of things they can easily get rid of. Fortunately for Miss Kondo the same people are also easily sold a book that they didn't really need. Who thought an 'organizing consultant' was something we would one day take serious.
Why getting a $250,000 investment made getting to market harder
In the case of Homebrew, it'll install things to 'usr/local/Cellar', and symlink them from /usr/local, leaving the OS X tools in place in /usr/bin
I'm rooting for the crapware camp to find new theories on how to make things slow.
>So how do you account for Mark Zuckerberg, Elon Musk, Larry Page, and so on?

Is this a game of "which of those three does not belong"?

If so, too easy...
One of the benefits of being vertically integrated.
Great, now I can get rid of that page 2 folder called 'Junk'.

Well maybe not. Game Center and Health seem to be too core to be removed.

Edit: I wonder what happens if you ask Siri for directions, but remove the Maps app. I have my doubts that it'll fall back to Google Maps.
Last long distance flight I did we took economy premium, considering the amount of luggage we had, it was actually cheaper, and the leg room was very reasonable.
Or a way to make system calls faster, some sort of vdso with the ability to switch privilege level.
Honest question: how is a man who thinks he is a woman different from an anorexic who thinks he is fat?
Unless said employer is LinkedIn (or now MS). I wonder what sort of information they'll be leveraging without telling their employees.
Your first point is mostly dead on. I see a number of people stating that you cannot revoke a token, and it's simply not true.

The approach I use is to replace the shared session store (which is large, grows linearly with your user base, and hard to sync across clusters if you need that) with a shared revocation list.

The revocation list is small, easy to check, only contains IDs and a TTL, much less cumbersome to replicate... And is functionally equivalent.

If you have already gone the route of using a token for your session, it's really easy to implement and scales much better than a massive in memory store.
Not to mention that small regional airports can often be significantly closer to your destination. General aviation for the masses would be a game-changer.
This. Exactly my take too. Manufacturers are not as tuned in to user feedback as most might think. Many think they know better. No one worth any chops in UX though sees the removal of the audio jack as good. I've read and heard all the arguments in favor of removing the 3.5mm audio jack. Everyone ignores the fundamentals of good UX principles though. Too many companies have a very narrow UX scope though.
Hrrm, now you're in a situation where you're using part of the unverified payload to look up part of the secret before validating the signature and hence the payload. This is a neat idea but it introduces a whole class of potential vulnerabilities. (This is similar to the argument against the algorithm being selected from the unverified payload before being used to validate the signature per the JWT specification.)
just.like.home is in between a power plant and a chemical plant in England: https://map.what3words.com/just.like.home
Very nice, very beautiful but I find this of limited use.

Firstly I have to look at every job page individually. So I'd rather look at remoteok.io for that. I guess this is good for speculative applications, but is it a good use of my time trolling through 100's of companies sending out speculative applications?

Secondly I am not in the US or on US time zone so there would be little relevant to me anyway.
That's fair. Though I've yet to actually need that time, so I feel arriving at the airport with less than an hour to go is a realistically acceptable thing I could do.
SSD's haven't displaced drives for bulk data center storage because it's all about $/GB and although SSD's are getting cheaper, spinning disks got cheaper in the same way. Intel is not going to compete on price, but on performance. So rest assured that spinning disks will be with us for a while.
You ALWAYS will sign your tokens with a well known secret, you could eventually even add some salt from a database to it.

Exactly. Each JWT I generate has a salt inside which I store in the DB, and ideally the salt has accompanying data such as the datetime the JWT was generated, the IP address that generated it, etc. Now you can provide an interface that lists "sessions" and allows the invalidation of logged in sessions by deleting the salt from the DB, rendering the JWT invalid.
Work is not fun for most people. As well, fun level certainly does not drive pay ha ha.
Can't speak to 3D touch as I'm on an older phone but I use Siri all the time, mostly for timers and dialing.
Optimize for taste, not for fast growth, please. I don't want to pay for lettuce with taste of straw.
I imagine most stores with a large mobile audience have their conversions heavily lean iOS, just based on app spending.
Even 18kHz is too high. Adolescents can only sometimes hear as high as 17kHz, and adults can often only hear as high as 14kHz.
> except for the iPhone keyboard cursor thing.

That's enough for me to never want to miss 3D touch again.

>I use it all the time (at least once a day)

I use it almost daily too, you get used to that things so quickly. The thing that annoys me with Siri is that it is slow. I want to say: "Hey Siri, how is the weather today?" and not "Hey Siri" wait, wait, wait, bling, bling, wait, wait, wait, "How is the weather today?".
Oh, I used the example of my GF responding to messages/viewing notifications to essentially bring out my privacy concerns. Not that I don't trust my partner :)
I must have disabled this feature when I installed iOS 9 and being unnecessarily surprised at this now.
I am genuinely curious how its possible to keep track of 'insider trading'. There is always information asymmetry and people will make decisions on that info, thats the entire premise of the market.
Greenhouses in NL use natural gas to heat and they are getting a serious discount compared to homes and offices, compared to what they are paying for gas heat any conversion from electricity to heat is a loss to them.
They threatened to sue Mike Spagat but that’s not shutting him up
NYTimes now A/B testing headlines
The same could happen if the API was paid. In this instance, it's conceivable to setup your own NLP/bot engine with OSS alternatives to do more or less the same. But starting with wit would be much faster and allow you to focus on getting the product market fit right
I completely agree. Seems like the underlying technology wouldn't be that difficult to reimplement independently, or am I mistaken? Surely a few CS interns in Mongolia would be up for slapping together a vital national infrastructure project on the government's dime, eh?
Game Center is now removed.

>The GameKit framework (GameKit.framework) includes the following changes and enhancements:

>- The Game Center app has been removed. If your game implements GameKit features, it must also implement the interface behavior necessary for the user to see these features.

https://developer.apple.com/library/prerelease/content/relea...
Discover Aurelia, the JavaScript Framework
2 years ago we had the polar vortex where the groundwater froze and when it cracked sounded like someone kicking tour front door open.

I doubt there was a polar vortex in the bay area.
Wouldn't the simple solution be to just replace the 3.5mm analog jack with a 1.5mm analog jack? As long as I have proper analog out I don't mind using an adapter for my old headphones.
actually I often see stating that you should rely on a 3rd party authentication library since its mostly well known and well tested.
While I would agree here I know that mostly the library will be your weak point since you have no idea how its implemented or whenever a new version comes around if it maybe has a security issue or if you keep your version if your vulnerable to something.

Actually most people should take their authentication mechanism as something really really important and not just rely on something.
It's really important that your authentication/authorization stuff works and is hardened, not just for you, also for your users.
I know that auth could be really hard, especially when the language of your choice contains some bugs, but its a nogo to just use something when it is that important. I don't mean that you can't use a library, but if you do please double check the code twice on each version.
Is this a bluetooth problem or shitty product problem?

Eg. my car has no problem being the 'headphone' for several different devices.
It did say intelligent error checking. People have proven themselves to be idiots.
Thank you Moxie!

Although we personally trusted and would've moved forward with Moxie's informal permission to distribute SignalProtocol within ChatSecure on the App Store, our funder required us to get the legal details squared away or we'd lose our funding. This announcement is an amazing gift for us, and for other GPL compatible Mac/iOS apps.

This announcement also more broadly benefits the copyleft community. There has been a decline in GPL apps on Apple platforms, particularly because of this conflict between the GPL and Apple's App Stores. It makes it clumsy to accept pull requests because you need a CLA to allow relicensing for distribution. There's a also lot of FUD from anti-Apple copyleft zealots. Having a good template for other developers who wish to stick to strong copyleft without worrying about App Store issues is a great contribution to the Apple-friendly copyleft community.
Just yesterday, I did my first Linux installation with ZFS as the root/boot filesystem (Ubuntu 16.04). This is after using it as the default filesystem on my FreeBSD systems for several years, and being very happy with it.

I've used Btrfs many times since the start, and been burned by dataloss-causing bugs each and every time, so I'm quite cautious about using or recommending it. I still have concerns about its stability and production-readiness. If in doubt, I'd stick with ext4.
This is NOT journalism.
I'd imagine that homonyms are avoided by careful selection of the reference word lists.
It's a little depressing Moxie believes federated protocols can't compete with unfederated/proprietary ones. I don't like the idea of all future innovation taking place in the Slacks and WhatsApps rather than the IRCs and SMTPs.

Are there any recent counter examples of successful federated protocols?

It would be an interesting thought experiment to design a protocol that started with the basic features of IRC and incrementally layered on new features in backwards compatible / gracefully degrading ways until you arrived at Slack. Of course it would be a lot easier with the benefit of hindsight than if you started in the 1980s.
This is a tradeoff made with dynamically-typed languages. Open up your dev console and try some JS for other examples: `[] + []` or `[] + {}` or `{} + []` or `{} + {}`.

There are several ways to solve it all with tradeoffs. Types can solve it with tradeoffs. Checking the types in the function can solve it with tradeoffs. Stating in the docs what arguments may be passed is another way to solve it.
Data Engineer consultant - Working with Spark, Hadoop, HBase, Kafka, HIVE, scikit-learn, Yarn, LOTS of crappy legacy Java. Python

Startup 1: Media monitoring - Cassandra, Kafka, RabbitMQ, scikit-learn, nodejs, AngularJS, Python, Cython, Postgres, Spark, Hadoop

Startup 2: Forex Trading - Keras, TensorFlow, Kafka, Spark, RabbitMQ, nodejs, postgres, Pandas, celery, scikit-learn, iOS App, Flink
What does the revocation list look like? "Reject all tokens for user X issued before timestamp Y?" Or do you assign UUIDs to your tokens?
Bulk data is the key there, for many other use cases servers are already using SSDs and once the economies of scale will cause another order of magnitude decrease in cost I think spinning disks will be much more expensive in $/GB than SSDs. Chips are cheap, robust, quite dense and should have a much longer operating life than anything mechanical. The writing is on the platters.
It's still a good heuristic. When presented with a question as headline, I immediately answer it with "no". If I still want to read the article when the question has been answered, that might mean I'm genuinely interested in the topic.
> Unless you've used cookies with the HttpOnly flag XSS trivially escalates to session stealing

Then again you could just use CSP and mitigate almost 100% of those XSS cases. Yes, even most of the stored ones. And with JWT + JavaScript you don't have to worry about all the oddities in the way cookies work, which is a huge plus.
It's the transparent compression I'm using btrfs for. Only that, ZFS and NTFS support it, so not much choices for that scenario.
Seems like AT&T are increasing the caps and adding the option to have an "unlimited" version:
http://arstechnica.com/business/2016/03/att-boosts-data-caps...
Slovenian Police Informant Hacks 100s of Individuals
How often does it need to be recharged? Will it last a whole day at the beach?
Many people use headphone stands, or some kind of hook under their desk. That hook could be where the charging occurs.

Also, many people are talking about using ambient wifi transmissions as a power source.
I wonder, did they really rewrite or refactor. Did they chuck out every single last line of code at once, or transitioned it slowly? Do they no legacy code left at all?
It seems to me that your choice to open source the code without also saying "sure, we'll just give away everything else however people who want to use the open source want us to" is resulting in people falling into the Copenhagen Interpretation of Ethics trap ( https://blog.jaibot.com/the-copenhagen-interpretation-of-eth... ). Shortest quote that summarises the article's point: "There wouldn’t be any scathing editorials if BBH Labs had just chosen to do nothing – but they did something helpful-but-not-maximally-helpful, and thus are open to judgment."

Looking at the LibreSignal thread, you appear to be replying with the sort of snippy tone that I tend to end up using when I'm explaining the same damn thing for the Nth time to an audience that probably isn't going to listen. The only thing I've found that works for me to avoid ending up doing that is to summarise the explanation into (for IRC channels specifically) a factoid entry in an infobot or (for longer things and other distribution means) a blog post.

Or, alternatively, (1) people are being entitled as fuck because, well, people are people, (2) you might wish to consider writing up a blog post explaining the reasons for all of said opinions and then just post a link to it, since this will probably achieve just as much as trying to argue and will be far less bloody annoying for you, (3) IMO you're not guilty of anything and "carry on doing exactly how you're already doing" is not a choice I personally can see any good reason to fault you for.

(random free opinions of this HN commenter worth exactly what you paid, of course ;)
> [This is] not unprecedented; Google and Facebook have similar structures...[t]he Ford family used this kind of structure..."

Alphabet's B shares hold 64% of its voting power [1]. Zuckerberg controls 57% of Facebook's votes [2]. And Ford's Class B shares hold 40% of the voting power [3]. Selling the public 10% of your company while retaining 99% of the vote is a huge red flag.

[1] http://www.investopedia.com/articles/markets/052215/goog-or-...

[2] http://venturebeat.com/2012/02/01/zuck-power-play/

[3] http://venturebeat.com/2012/02/01/zuck-power-play/
On what devices? The problem with these kind of features (e.g.: huawei's knuckle touch) is that unless you have a large enough device support, the developers can not rely on it. 3D Touch will have a massive support in a few iPhone generations.
I asked this question below, but how do you use the payload to select the correct salt from the database in order to verify the signature before verifying the signature and confirming that the payload is valid?
Not being a recruiter myself, I couldn't say whether the paid features are worth it, either. However, I never accept invites from people I don't know, especially when they lack context (i.e., an introductory message to go with the invite). The odds I'll at least skim an InMail message are higher, even if my responses are almost 100% of the time "Thanks, but I'm not interested right now."

That said, I log into my LinkedIn account maybe a half-dozen times a year, so I doubt my usage is typical. Take the above with a grain of salt.
> I've never been asked to fill out a survey about the features I like/dislike about my phone.

I've never been asked which political candidate I prefer, but I see polls on the news every night.
in French, they probably put the most unused words they could find in the dictionnary. As an example, you have 'maussaderie', 'taniser', 'houblonner', 'époussette' or 'numismate'. I'm sure a good proportion of native speakers would have to use a dictionnary to find the meaning.
Houyhnhnms vs. Martians: A critique of Urbit
If you could make the phone smaller from shrinking components, don't. Instead keep it the same size and fill the extra space with a bigger battery.

Or, if you could remove battery because of lowered power consumption of components (and then make the phone smaller) just Keep the battery the same size.
I've found 3D touch to be useful. Looking forward to the increased support.
Checksumming makes no sense on modern hardware. Hard Drives and SSDs use CRCs already.

When a sector goes bad on a hard drive, the firmware will mess about retrying and altering the analog amplifiers to try to get the signal back. If it gets the data back, it might "recover" by moving the data to spare sectors. Without a CRC, the firmware would have no way of differentiating between a sector read correctly and one that is read erroneously.
Older Apple keyboards didn't have them either. I'm using one right now.
I was HPE Discover and while HP Labs had a pretty big presence, "the machine"(what a name, huh?) was less present. In previous years, it was more center-stage. I am obviously overreaching, but that isn't a good sign.
Long Term Obligations for IoT Companies
Steam on Mac does, or at least did last time I tried to use it on a case-sensitive partition. It's not that steam inherently needs case-insensitivity, it's that some of the main app mixes the case of files in the app from what is on disk. So without case-insensitive FS it cannot find some files. Stupid problem really.
I'd love to see your medicine cabinet and sock/underwear drawer.
Yeah, I guess it is. I only use redis for a simple cache and for worker queues. For authentication I use JWT. I store the user permissions inside the token, purely to be used by the client side (for showing/hiding interface elements). Permissions in the backend are over the database. So I tried to minimize the revoke-problem.
SteamOS is Linux, based on Ubuntu. So I assume it is ext4, ext3, or xfs.

Btrfs is not stable enough IMO for something like SteamOS.
My own view differs from the "benefits management platform" thinking. I don't think they want to do insurance or retirement benefits. I think they want you to use their productivity tools more frequently.

To me this is all about white collar productivity tools and integrations. LNKD is the keystone that manages a users journey as users ebb and flow through using (and not using) MSFT tools and products (Word, Excel, Sharepoint, Outlook, et. al.). The journey here is starting a job, starting projects, managing and coordinating projects, completing projects, and looking for new jobs. MSFT has tools in all aspects of the lifecycle except for the time between jobs.

Therefore MSFT offering gets stronger because they can keep that relationship with you even if you leave your employer and LNKD relationship gets stronger because they gain the relationship when you're still content at your current employer. The possibilities here are really interesting from a MSFT perspective.

Here's MSFT's deck on the summary [1].

[1] https://ncmedia.azureedge.net/ncmedia/2016/06/msft_announce_...