skysight-inc/HackerNews huggingface dataset:
JWT makes access control super easy/efficient in some cases because you can setup middleware functions to block/allow specific connections/requests just by looking at access rights stored in the JWT token (no need to do database lookups in many cases).

I disagree about using cookies instead of localStorage. Cookies with the HttpOnly flag enabled (as suggested in the article) don't work well in some environments such as hybrid HTML5/native apps (using WebViews) because of cross-origin restrictions - For an app which runs inside a WebView, the cookie will not be sent to the server if your script files are served from the mobile devices' file system - So your server will never get the JWT token in this case. With localStorage (or a Cookie WITHOUT HttpOnly), you can manually read the JWT using JavaScript and send it through - I know this opens you up to XSS attacks but it's a small price to pay.

Most frontend developers accept the fact that if you have malicious third-party code running inside your app's frontend, that's pretty bad news in any case. The fact that the malicious code can access a user's JWT token isn't the worst thing that could happen - At that point, the malicious frontend code could theoretically do anything it wants with your account by hijacking your UI.

The simple solution to mitigate XSS attacks is to serve all your frontend scripts from your own trusted CDNs - When it comes to vulnerabilities, there is always a tradeoff between CSRF and XSS - Personally, I find XSS threats much easier to manage than CSRF (it's a smaller attack surface).

Also, you CAN invalidate JWT tokens - You can change the auth key from the server-side (thereby invalidating the signature of previously issued tokens). Or you can send JWTs with really short expiries (e.g. every 10 minutes) and then renew them on an interval (e.g. every 9 minutes) so that the JWT doesn't expire while the user is still active.

There are a lot of different ways to use JWTs safely. It is not right for someone to say that a technology is bad unless they are aware of all the possible use cases for it.
Not so much for "traditional" desktop apps. This sort of performance isn't going to do anything for your spreadsheets or word docs. It might pave the way for some really interesting video games though!
Because it is not a standard. It is still in progress and deemed unsafe by Apple. (See their mail to the PR mailing list)
Nailed it.

Any app or service that isn't cross platform has no real future.
ALGORITHM INTFACT: A MATURE VERSION
> people in the 19th century: they had to go with Newton because they couldn't measure anything beyond Newton

As far as I know in 19th century there were already the measurements and the calculations resulting from them that didn't match Newton's model.

https://en.wikipedia.org/wiki/Urbain_Le_Verrier#Precession_o...

By the way, Le Verrier also discovered Neptune just by studying the measured movements of the known planets.
I installed a different environment and hid all the apps I never use. I can get to them but they're absent from my day to day. I went through a number of iphones and loved the simplicity that iOS provided. Then I got an Android and put a lot of work into my UI via settings menus and drag and drop, which resulted in something far more minimal than what iOS was (at the cost of setting it up).
I would love this, every time I'm reading off my Kindle I wish that it could go online so I could read blog posts and some websites. I don't like the eye strain I get after being on the computer for far too long.
I don't see why they couldn't have gone to any of the dozens of other municipalities in the region.
That's too bad, while I'm happy with Signal, I understand where people using LibreSignal are coming from and it'd be a shame to be unable to talk to them (or install yet another freaking app for it).

It's hard to imagine there are enough LibreSignal users to make a notable impact on the OWS infrastructure in terms of expenses. Though over time, that could change, especially if other forks joined the party, and of course the fallout of shutting them out would only grow over time.

Given OWS's worries about federation and shared standards standing in the way of progress, they might want to avoid third party access simply because it might stop them from changing the server interface. Thirds party clients would be at the mercy of their developers when OWS makes an incompatible change. Caveat emptor, I would say, but again, the problem would only grow.

My personal situation is that the only people I talk to via Signal are nerds; the kind of people who jump ship when a sexier alternative comes up -- like we did when TextSecure/Signal offered good e2e crypto. But that's stopped being a unique feature since WhatsApp also uses the Signal Protocol, which simultaneously made it feel much less pressing to convince non-nerds to switch from WA to Signal.
I've been in the same position. Was first to join a couple of founders, built the first few iterations of the application, small group, great fun, lots of challenges, lots of code. As funding came, team grew I became the CTO officially. But then the fun stopped. Technical decisions which were meant to be mine were dropped on me by one of the founders despite my objections (most if not all proved to be mistakes). In the end I stepped down and we invented a new role where I'd be in charge of innovation. That worked well. The CTO who replaced me run away himself after a short while and after that we were CTO-less.

Thing is there are many forms to the CTO role and different people see that role in different eyes.
To me the CTO is a technical leadership position. You are meant to decide the technical strategy of the business. Decisions from which servers to use, to what language to how things are done, architecture from the top down, etc. Someone mentioned about the VP of Eng. role which I can't agree more - That role is there to support you with the crap. That person needs to be more manager than tech. He is there to make sure your time is dedicated to the core of your position. Not everybody saw this roles as I did which is why I was happy to stand down than try to fight it. I was there from day 0 to acquisition about 7 years later.
A recommended read
As long as Swift continues to have strong reliance on Apple, Swift on server-side will run the risk of being a second-class citizen. It's unlikely to have a well-established ecosystem of external developers either because Swift currently attracts primarily iOS developers. So, till Apple makes some moves to show that it considers server-side a first-class citizen, or you see a very obvious external developer ecosystem building for server-side Swift, I'd recommend not using it there.
mmap() tricks you into thinking you can directly access the disk. What really happens when you access the mapped data is that the CPU generates a page fault, the OS takes control, copies the data from disk to physical memory and maps the page in your address space. So essentially it is a convient way to do read().

The mmap() model is good. The current page fault mechanism, not so much.
So people in Mongolia will use English words for addresses? The whole "easy to remember" is completely lost when it's a foreign language.

Imagine if America switched to three Chinese characters for an "easy to remember" address system.

In China numbers are often used inside of roman character email addresses, or domains, because roman characters are only convenient for westerners, much less English words.

See 1688.com (alibaba.com), or use of QQ numbers for email addresses.
Read/write are certainly a bit slow, but this may well be acceptable for most applications. High performance apps can use mmap, which can be extended to directly map the nonvolatile memory in question.
Thanks, as always I guess it comes down to what you're familiar with. To me the home screen requirement feels restrictive and cluttered, but to an iOS user perhaps the two screen concept feels needlessly inconsistent.
Does that mean I can set Gmail app to be the default email client if I remove Mail?
Adobe has to get their shit right.
I'm not saying Microsoft's approach is bad, just pointing out that there's a much higher chance of rapid adoption for this new filesystem.
CSP isn't a silver bullet.
It costs a fortune to map a file on every OS I've tried, it makes little sense unless you're consuming a lot of data from few files rather than little data from many files
I've ran the initial FreeBSD patchsets for ZFS support on a dual-p3 with 1.5g ram, so 1g for a recent version should be more than doable. ZFS on FreeBSD has become a lot better with low-memory situations.

There are two additional things to consider.

ZFS uses RAM mostly for aggressive caching to cover over both spinning disks and the iops tradeoff vdevs make over traditional raid arrays. Thus low memory is not such a big deal if you have a pool with a single SSD or NVMe device.

The other point to consider is that on at least any non-Solaris derived platforms, the VFS layer does not speak ARC. So data is copied from an ARC object into a VFS object, taking up space in both. If you are able to adopt your platform to use the ARC as direct VFS cache, you can save RAM that way as well.
The Berkeley one is a bit slower and it has a statistics/probability refresher. I found it much easier to follow at 1.5x speed. I'd recommend the Udacity one if your stats/probability knowledge is fresh or if you're re-learning the topics.
Me too my friend, me too.

E-ink usage has been underwhelming/disappointing. When the technology was first announced I thought it would take the world by storm, but all we wound up with was eBook Readers and little else.

I really hope that color is the missing piece of the pie, and we'll wind up with color e-ink photo frames, LCDs in adverts displaced by color e-ink, and even secondary screens which are e-ink based.

It is such a cool technology, almost zero energy use between updates, that has been ignored and under-used. It legitimately makes me sad.

I guess nobody wanted to be that "dated" manufacturer who used a black & white screen on something in 2016, no matter what the benefits.
I think the first programming I did was Turtle Logo, or Apple Logo or whatever it was called.

Traditionally it's been Pascal and Basic, but I think those aren't used much anymore. I learned Commodore Basic first then Pascal in High School and CS1 in college.
I think the parent meant the other way around too.

However, the transition between the case insensitive and case sensitive filesystems isn't going to happen overnight. People will be copying files around both ways for quite some time, so the insensitive -> sensitive case is still going to be a concern.
That expressly ignores what I set up as my criteria, so I'm unsure why you presented this.

Even if that does cause a crash, which is entirely dependent on the language, I think there's a clear delineation of whether something can be expected to crash or not based on the opt-in assumptions of the language you choose. If your language is not type-safe, you've already accepted that as a constraint ("types may not help you"). Should we expect addition to be implemented in some way that causes problems within the constraints you've already accepted? I think not.

Here's two specific examples of dynamic languages, one weakly typed (Perl), one strongly typed (Python), and how they are internally consistent.

# perl -E 'say 1 + "2" + "four" + 8'
11

# python -c 'say 1 + "2" + "four" + 8'
File "<string>", line 1
say 1 + "2" + "four" + 8
^
SyntaxError: invalid syntax

Each makes it clear what you can expect up-front. If python could occasionally crash from addition of two integers, or Perl would occasionally interpret an all alpha string as non-empty in numeric context, all for the name of being slightly faster, I would consider that the wrong thing to do as well. (Note: There are rules for how mixed alphanumeric strings are interpreted in Perl, but they are well defined).
that's mostly true, except US/Canada we put the zip/postal code at the end which is more specific than the city/state/province. But your gist remains true.
Non-standard CAE and mech / nuclear eng consultant. Side project - helping local kids set up a small data science shop at www.databot.it
> Reminds me of Stanford's iOS dev resources from 4-5 years ago.

Believe it or not, they still release a course every year (or semester, not sure). The latest one covers iOS 9 using Swift. You can find them all on iTunes U.
To what3words' credit, when I typed reporter.smoker.received into the map tool, it did suggest the correct location in its list of similar locations. https://imgur.com/G2ChrxA.png
Is Siri really not used for anything? As an Android user I find myself using "Ok Google" daily now for all kinds of things.
The difference is that you only take the page fault once per page (or less than once if you do some prefetching in the kernel), while you have to do a system call for every read().
I wasn't talking as narrowly as the RIAA. I meant even USB ports are disappearing in favor of wireless charging and bluetooth.

If there's a USB port, most people will just plug in and back up to their computer. But if they do it over wireless, they'd just rather use Google / Apple's services, which means they get your data.
I have a 64GB iPhone SE. What I really wanted was a 128GB SE, but sadly such a thing does not exist.
Can't you maintain session state in a Redis daemon and invalidate it there? Or are you talking about stateless JWT?
>Bluetooth.

-more expensive, again bluetooth stack is the size of IPv4 stack

-lossy audio, or again more expensive headphones full of patented crap

->100ms latency
Depending on how Desktop sync works, I'm thinking we'll all be very familiar with the "Upgrade Storage" alert.
JWTs do have plenty of valid uses.

I definitely agree with this point, though:

>If you are concerned about somebody intercepting your [anything], you should just be using TLS instead

It's weird to see a lot of devs try to reinvent the wheel and do some kind of half-assed transport encryption when they could just use TLS.
In case parent doesn't return:

fine with current hardware, based on
>...done computer vision/machine learning with a much less powerful MBPRetina...
All the VPs who came through engineering that I found did so after having been early employees at one of the top tech companies. I buy that. But if you are going to climb the ladder now, I doubt you can do it through engineering at Google
Steve was fantastic at saying no. He said no to the app store multiple times. He said no to almost everything that ended up being Apple staples. I'm not sure it's fair to give him so much credit.
Interesting. I'm no subject expert so I can't critique this, but it sounds better than other online voting systems I've heard. I like the checks and balances in place too.

Now I only skimmed this article, but I feel like most people who argue against online voting use arguments about how insecure it is that already apply to what's happening right now (voting software is a black box, can be hacked, etc etc, this also describes current voting machines). The only difference is there isn't a single voting db or site somewhere for people to manipulate a large number of votes (which like you said is protected as long as people can verify the open software / data).

Yes paper does have indelible properties but paper doesn't scale well, and having a paper counting machine introduces the same black box that people use as argument against current voting machines. Yes security is an issue, but scalability is also an issue.
The above comment is, sadly, quite relevant and should not have been downvoted. Especially if one is aware of certain rather disturbing events which have happened in that city recently. Only significant counterpart to make is that the recent uptick in neofascist activity is probably more a reflection of (rather than a feeder cause into) the city's long-term economic malaise.

Nonetheless, at some point a self-reinforcing dynamic tends to emerge, and I can imagine that if I was thinking or investing in or moving to a city like Leipzig, I would -- especially if I were not of the default local demographic -- definitely take the recent violence into close consideration.
Microsoft Inherits Linkedin's Talent Density
Why?

The big screen all but ensures there will always be plenty of space.
What is sensible is first based on the language definition, not your opinion. If the language defines it explicitly and has well defined rules, there's nothing non-sensible about it. Consider the following, which fall well within the definition of how Perl handles implicit conversion of strings to numeric types, and is well known to Perl programmers:

# perl -E 'say "1zero"+0 '
1
# perl -E 'say "zero1"+0 '
0
Forced updates are not acceptable. Whose computer is it, anyway? I don't care how useful you think it would be, if you try to force me to update I'm simply not going to use your software. No. My computer, my choice.
10 Ways To Program Your FPGA
I just look at the state of internet "security" and that tells me all I need to know.
ComponentBase – reusable React component library
> I think there's a clear delineation of whether something can be expected to crash or not based on the opt-in assumptions of the language you choose.

I can say exactly the same thing about StringBuffer vs StringBuilder, with the obvious substitution for the word "language".

The point of kodablah's post is that, if your stance is that safety should always be chosen over other practical concerns, then a natural conclusion is that you should by default be opposed to dynamic languages, as they trade type safety for programmer comfort (for lack of a better term).

EDIT: I also want to point out that "crashing" vs throwing an error is not a distinction worth making for this conversation. If your program stops executing for any reason that could be prevented by a type-checking system, then it seems reasonable to call a type-checking system a safety feature.
Mystery meat doesn't really apply here, as keyboards are not supposed to be obvious -- they are supposed to be "learn once and then remember forever".

You don't want to be looking "where's the key with the Alt sign" or whatever key you want to find every time you need to hit it.

Ideally a keyboard could even be totally black -- and fancy touch-typing key-switching keyboards are.
Only to be discovered later that NSA is spying on your votes too.
Read this BEFORE you start CLOUD MIGRATION project
Yes, and the used names have changed at least once in the past.
Do you know if it's possible to expose an MDX or similar interface to MonetDB for a BI purpose?

I see many references to being able to define your own language, so I wonder if this has been done. I don't see anything explicit when looking through the site.

I ask because many popular visualization and reporting tools can natively generate MDX queries.
Mongolia is separate from China, however I brought up this same point since their language isn't English (it's Mongolian).
Move the pointer to central SF (and Trulia will assume you have instant access to the freeway). 30 minutes with no traffic. Not 15.

But anyway, I was talking about the entrance.

30 minutes would barely get you from central SF to the airport ramp with a mostly empty 101.

But that's not the problem. Getting parked and a shuttle in will be at least 45 minutes, if you get a shuttle faster than normal.

Taking BART to SFO entrance: check the schedules. You'll be surprised how much of the day it doesn't run at all.
Yes. I was a heavy user of ZFS on Mac OS X back then. Was on the developer mailing list for that implentation, submitting bugs and talking to Apple developers working like mad to ship it.

Then Steve Jobs' buddy Larry bought Sun, and licensing of ZFS became basically impossible to sort out on time. So they dropped it.

Was that 2007 or 2009?
They should just replace the long press with it. The problem is it's only on the 6S models, and the difference between 3d touch and a long press is a delicate balance.

Replace the long press, and the experience degrades nicely on older hardware.
Would it be wishful thinking to hope Microsoft would follow suit by open sourcing ReFS?
Di-photon decay suggests it is a boson or force vector with no charge and integer spin. Perhaps it is a super resonance of the Higgs or some unkown force.
3DS Export to STL ASCII and Spliting Mesh of Existing 3D File Are Enhanced in .NET
Aspose team is pleased to announce the release of Aspose.3D for .NET 1.6.1. In this new version, the way of converting 3DS files to STL ASCII has been improved. The common 3D software packages can now easily import the resulting STL ASCII files. Previously, the opening of STL ASCII files in 3D Builder was displaying a loading error in most of the use cases. Similarly, the import of FBX and splitting the Mesh features have also been improved internally. We still have more to do in improving appearance of meshes. In reference to this, our product team is working hard to bring more features and enhancements in the upcoming versions. Based on the client’s feedback, we noticed, the FBX import was crashing due to the complex internal structure of meshes. It was specific to the FBX sample. The FBX importer now handles this more gracefully. We recommend our clients upgrade to this newer version from their old version to get this enhancement.
Especially English meaningless combinations for 3 words. If you don't know English it might as well be a set of numbers, except you'd also have to memorize the 26 letter alphabet.
I very optimistic about what AR can bring. To me, the biggest roadblock for AR as well with VR, is user interacting with the digital world constrained by the physical one (a problem that's been recognized since the beginning).

Even in AR you do not have haptic feedback, this to me is a critical component for a system to be truly adoptable outside of niche domains such as surgery, industrial processing etc.

I am sure many people are think of this. I have seen some research work out of the Media Lab at MIT trying to address this problem with deformable tables, likewise a Japanese group was doing air pressure haptics.

Could anyone working in this space comment on some state of the art stuff? And provide links? Thanks in advance.
It's impossible to know how long they have been working on it. As I recall, Swift had been in development for 3+ years before it saw the light of day.
thanks for mansplaining rootless and encryption (/s).

Encryption is not authentication, so it does not prevent unnoticed modification.

And secure boot only really depends on authentication and not on encryption, so you are conflating two different concepts.

No you cant just trust the data, replay attacks over time and space are still an issue.
Thank you, this is fantastic. Fixes something about iOS that has bugged me for a long time.
KLM lets you pay extra for sitting next to an emergency exit, which gives you a nice legroom increase.
Haven't taken Udacity's offering. I took CS188 on when it was offered on edx and loved it! I hope the bring the course back!
How about having them not ever adjusting the ringer?

You can always adjust the ringer (something people rarely do -- for quite times there's the "silent" mode anyway) from the UI, and always use the volume buttons for the system's (music, video etc) audio volume.
"Developer State of the Union", Jesus... you talk about a closed platform.

I've never been able to stand these ecosystems where you need to attend state of the unions to know what will be deprecated and how the "establishment" has decided you would run your business (tools, etc...).

I know there's good money to be made there but Apple is just too much for me.
Yeah, I wasn't really sure what I was watching there... this is Apple?