skysight-inc/HackerNews huggingface dataset:
It's a special case of a more general (Israeli) bullshit detection technique. They'll ask something unexpected, but reasonable enough that an honest person would be able to say the answer immediately. The idea is that you bait a person presenting false information into revealing that they are lying. Security will ask a sequence of inane questions that a truthful person should be able to answer immediately. If a person being questioned grows shifty, nervous-looking, starts sweating, stops making eye-contact, or shows any other sign of illegitimacy, then the questioning will continue until (il)legitimacy is established. It is not a flawless method (see end of comment) but it usually works. It is virtually impossible to nail every single aspect of a BS story. If you're 100% legitimate, then you'll probably have no problems recalling things like your grandfather's name or the synagogue you were Bar-Mitzvah'd at. I'm a pale South African Jew - I was asked that.

Example:

Security: Are you a member of a Hebrew congregation?

Person: Yes, such and such a synagogue

Security: Who is the Rabbi there?

A legit person might say "Oh it's Rabbi so-and-so", but if a person hesitates, and has to think, and blurts out an answer like "Rabbi Cohen" then it is less likely they are being forthcoming.

In some sense, this is a very rough mental-Bayesian process of probability updating. A person arrives at the border / El-Al check-in. Security assigns some prior probability p_0 that a person should be allowed access, and via a string of questions, amongst other techniques, a posterior probability p_n that that person should be on that flight / in Israel is established.
Don't endorse? That's first and foremost words -- the website, "TimeToDieJake" and the picture of the guillotine chopping of his penise, that's more real.

Their plausible deniability doesn't translate into "confirmed false flags". It can't be confirmed either way, I'd say, since we can't read minds. "endorse" just means "not publically support", which in turn just means "we're not that insane". But you're right, it's AFAIK not entirely right to speak of aggressive twitter accountS, but I for one didn't buy their "we're not related" about TimeToDieJake for one second. Can't prove it, but it'll take you hard proof to convince me otherwise.

I agree you can't blame people directly for all of anyone out there does now, I'm sure plenty of people enjoy stirring the pot. But you can blame adults at least partially for the storm they unleashed and the way in which they did it, and how unable they are to even see, much less acknowledge that. Stirring up hatred against someone and then saying you don't endorse hateful messages against them might be useful in a court, but beyond that? To me, generating hatred against Appelbaum was the whole and the sole point of the exercise. I mean, while we're at accepting "this seems plausible" as good enough, then that's a somewhat reasonable assumption I'd say.

For me so far the claims of Appelbaum being a super psycho are hearsay, some of it plausible, sure, and nobody coming out for real against it - but I also see manipulation, using others to destroy someone, not wanting to lay it out in the open, and so on. Those are also red flags. And that's not because Appelbaum is playing his narcissist mind games on me, and makes me blame his doings on the victims, that's simply the stuff I see.

I see a whole lot of disagreeing with downvotes instead of people using their words, too, and that is also a signal. For people who claim to be against abuse, some people are mighty abusive.
The ALE agents are almost always using grey-scale pixels in the first place (to save on processing and NN space requirements), so flipping the color makes no difference.
I think the advice on shying away from db normalization is a terrible idea for beginners. If anything, they should try to stick to creating db tables in 3rd normal form until they learn when and where to bend those rules.
It's not standard and it's not pleasant to most ears, but I think over the last 20 (!) years of development the Trolltech guys have tried to make sure they could advance Qt and make a living doing it. I respect that a lot.

OSS was a completely different animal back when this thing started. And it was forward thinking to avoid the whole problem with people demanding free support and bugfixes for open-source code.
To be fair, I think this mistake in the US judicial system should be fixed separately.
Sometimes when this story comes up what is NOT made clear is that the church complaint is not that he debunked the miracle
but that he said they where purposefully profiting off something they knew was false.

One could argue they did and it is a distinction without a difference. It is slightly different though than the spin in headlines of this story which makes it sound more outrageous. The headlines often say the legal threat is to do only with him debunking a miracle.
OTOH, there were, as recently as a few months ago, ads in Toronto's subway system exhorting people to go to the doctor if they found blood in their urine. And this is in Canada, where there's no financial barrier to going to see your doctor for "maybe it's nothing"-style ailments. I fear you might be overestimating the average person.
Since there is some UUID hate here, some missing pros to using them:

- No round trip for generating keys, data can be sent in with an existing or new uuid without having to hit the autonumber/keymaster, removes a single point of failure for a small fee on each row. Storage is cheap so 16-byte uuid is not a deal-breaker, the benefit is speed and horizontal scalability. Optimized read-only tables and/or caching can be made where this has any impact at all.

- Some databases like Oracle you need a sequence to even do autoumbering, huge pain

- Autonumbering is a pain when having to replicate across environments or when you start getting multiple databases and clusters

- Numeric ids for important data is not exposed, prevents easily incrementing for next/previous (other ways to do this but this is one)

- Many databases have a UUID field or field optimized for unique ids/guids/uuids now

- If you were a piece of data wouldn't you want to be unique? All your data are unique snowflakes with UUIDs. On a serious note, this can help to identify data across all types and not just in the same table.
What World of Warcraft Class Best Matches Your Tech Job?
Completely agreed. When I tried my hand at gardening, weeding was the hardest part .. we ended up neglecting our garden for a few weeks and the weeds pretty much took over. And this is despite having laid down a layer of black plastic and mulch.
Everyone has a right to a defense attorney, just not a free one. Are you suggesting that the government (which is to say, taxpayers) fund the legal defense of everyone who gets sued in America? Including, say, OJ Simpson's civil suit?
Yes, but my statement was more of a technical one regarding how such a system might work.

I am speaking about the method used to determine how much is in an account and what can be withdrawn, because they can't check your balance without a pin number, and if their system is issuing multiple repeated authorizations, what protections banks have in place that might block these sorts of transactions to prevent theft.
Ah, yes multiple downvotes without explanation, that always convinces me.
It sure would. If I had to be executed and could choose my method, I would choose this.

I don't know why it's not universally used. I suppose it's some combination of tradition and a belief that executed criminals should suffer.
It helps to have a broad view so you can plan and design accordingly. Back end developers should understand how people use the system, even if they're not going to own the designs. Similarly, to be great programmers, front end developers need an understanding of what goes on underneath the hood, even if it's not their day job. (I understand it's all part of the learning curve) The extreme of this is Joel's [0] exhortation that every programmer should learn C. It's a different context, but the same principle.

[0] http://www.joelonsoftware.com/articles/CollegeAdvice.html
> judge determines what is a reasonable amount for the legal fees

That just gives financial unsupervised power to the judge, without any clear definition of involved terms. Which doesn't really sound like a good idea.
> A number between 1 and 10 on Tuesday is only slightly different. You can say it is not arbitrary, whatever.

It's not arbitrary, because the constraints at least in Postgres are themselves constrained to validating a single row in a single table. Your app code can be truly arbitrary, you could trigger a device that posts a carrier pigeon to someone many miles away and waits for it to return with a result. That's arbitrary.

> Just in case you forgot the original claim, it was that if you use a SQL database, the constraints are in your database, but if you use mongo, the constraints are in your code.

Sorry, that's not what I was claiming. I was stating, correctly, that constraints relating to the data belong in the database. Constraints belonging to the business logic that powers your app belong in your app. You can be 100% sure that a constraint in your database will be respected, whereas the same can't be said of your apps code.

If you are given a specification that says "no username can be longer than 12 characters", that's what you add to your database constraints. A specification that says "No emails from temporary email providers are allowed" belong in your app code. Clear separation of concerns, that mongodb has no clue about. 'Just validate everything in your code, and if you get junk data in your database then I fucking hope your code can handle it'. Please.

> Therefore, saying that it is a great win that a SQL database can do some basic constraints checking

It can do pretty complex constraints. On the data. The more complex, completely arbitrary constraints belong in your app code.

> is a ridiculous argument because it hardly contributes any benefit due to the fact that even more complex constraints are in the code.

What. That makes no sense. So having 100% certainty that no column value in your database will violate any of the constraints you place on it 'hardly contributes any benefits' because... you have other, unrelated, business constraints in your app? What logic is this?
OS X has great support for Bluetooth, and Bluetooth mice and keyboards do not typically have the "skipping" issue you are describing.
> I'm also curious why numerous developers have not demanded an Insurance Protection Product / Plan that would take a premium in return for subrogation (defense) if a frivolous Patent Suit is filed. I'm rather certain the market exists and while it may be for larger businesses or players, developers forming a Mutual Company and writing on some big name AM Best A paper (or even going to Lloyds) could be helpful.

It would be very cool if company such as NewEgg could offer this - they already have the in-house counsel/expertise; and since the number of people trolled is very small, I'm sure even a small premium would be enough to cover it (provided you have enough customers).
One way to generate UUIDs in a more index-friendly way, at least in Postgres, is to use uuid-ossp's uuid_generate_v1mc() function. They end up sequential, so maybe not the best if you need total unpredictability, but the lower order bits should be reasonably random.

h/t to Wayne E. Seguin for his article http://www.starkandwayne.com/blog/uuid-primary-keys-in-postg...

Docs here: https://www.postgresql.org/docs/9.4/static/uuid-ossp.html
You are correct. The only serious frameworks nowadays are Qt or Electron if you're targeting the cross-platform desktop. There's also wxwidgets, although its python 3 bindings are still being built.

Personally, I'm keeping my eye open on libui (https://github.com/andlabs/libui/) as it is already possible to do some basic things with it. However, it is pretty much in alpha state and I'm slowly writing the Python bindings for it at https://github.com/joaoventura/pylibui/. The thing that I like in the libui is that it is a thin wrapper around platform specific frameworks. Therefore, the library is very small (some 340 KB) and it's as native as the underlying platform calls are..

Regarding Electron, I am writing an application on it, but it is too god damn heavy in terms of memory, disk space and boot time, and web front-end development is absolute chaos these days. Although I'm currently writing my app on it, it is mostly an MVP as I want to make pylibui/libui usable enough to switch to a pure desktop cross-platform library asap..
Also I understand them but the rates seem a bit rubbish. I just got a quote for a 55 year old and they offered 3.7% (this is in the UK). For comparison you could buy rental property and get a yield like 6% plus capital appreciation. With property, you suddenly want a lump sum, you can sell or mortgage. With the annuity you are out of luck. Also the rent goes up with inflation, this annuity I think not.
Since when have you guys been leveraging VPP? How do you find it? I tried to write some code for it, and I found it kinda difficult in comparison to Click / Snabb, but I realize that they're two totally different systems.
Yes, undoubtedly that was the idea. But "Vulnerable person exploited" is really less of a story than "police rob citizens". You could add "at gunpoint" to bait it.
Interesting read. I was speaking with some colleagues just yesterday about a potential pet project to identify which of our customers have eCommerce websites.

The concept would involve processing millions of companies names found on the "Bill TO" field of sales records. Then using these records to populate a ElasticSearch index for use with Graph Query API to help further normalize/dedup the company names that share similar string semantics. The next stage of the process would be to scan the normalized, dedupped, list of company names and attempt to locate the company website URL by crawling the first page of Google search results. This would need to be metered because I assume Google would block me if I performed rapid attempts. After gathering a list of company URLs the plan would then shift gears into attempting to identify if any of the companies websites contain the typical components that make up an eCommerce website. Think searching the HTML for all variations of "add to cart", "shopping cart", "my account", etc.
If you can avoid exposing those ID's then 64 bits should do fine with no problems.

But it turns out JavaScript can only handle ~54 bit integers, so if you try to randomize your IDs to prevent people scanning your data, you'll be in for a rough patch making sure you always treat IDs as strings. At least with UUID you pretty much have to treat it as a string.

You also avoid being the next developer in a long line who thinks they know what 'unique' 'random' mean but can't actually be trusted with that much responsibility (it's okay, most of us can't. I once stopped someone in the 11th hour from shipping a mutually authenticated SSL application that could only generate 256 unique AES session keys, due to a seeding bug. That was scary)
Time to lookup ERAD Inc. online. Fun times ahead!
I'm not sure where exactly this assertion stands - Judge Davis retires last year, and in 2011 when Lodsys was represented by his son's firm, their cases were always assigned to the other district judge (Gilsap I believe?) due to the conflict of interest.

It's sensational and scummy sounding, so it really fits the narrative of the evil patent trolls (a narrative I wholeheartedly support), I don't see any reason to believe it's true.
Sonatype has a manual review process as well before allowing new projects to deploy to Maven Central. [1][2]

One step to mitigate things like this as well would be to have some sort of "crowd-sourcing" command in the package manager program... like "npm flag coffe-script" or something like that to alert repository maintainers of possible issues.

[1]: http://central.sonatype.org/pages/ossrh-guide.html
[2]: http://central.sonatype.org/articles/2014/Feb/27/why-the-wai...
The App Boom Is Over
Facebook has ~2 billion users, and if they use 64 bit primary keys, theres no way they will reach that number (2^63) - 1
Years ago I built an image server that served up millions of tiny images (1k or so) and found mysql did a pretty good job for that, avoiding the file system overhead which would overwise be awful.
Data as Infrastructure for Smart Cities
Timestamp + server id can be uniquely guaranteed per server without coordination, so yes, it works fine :P Also, modern computers have monotonic clocks available and can use things like PTP.
Ugg...that's a super evil version of the classic "razor blade" business model.
The common pattern I've seen is to send the 64 bit integer back as a string. So it would be a "numeric string"
Heading Back from WWX (Thoughts on Haxe)
couldn't you register a typo namespace?
Not saying that this is wrong, just that it's no wonder if they think this to be FUD if one isn't familiar with the rule.

As for the reasoning, a customer developing their product for years in-house and switching to commercial just before releasing would definitely place Qt financing in a shaky ground when compared to traditional commercial frameworks.
I'm already spinning up a comprehensive FOIA request with MuckRock.com. Feel free to reply to my comment if anyone would like to collaborate.
They're literally suggesting an "array" in a VARCHAR field (by which I assume they mean comma separated or similar). That's a dangerous habit to get into for a beginner, and how you wind up with so many over stuffed columns.

In the article's specific scenario I'd recommend they just create the darn tables rather than doing his hacky solution.
One of the best things about the ASF is that technical governance stops at the Project Management Committee (PMC) level. There is no steering committee sitting in judgment of your project or telling you what to do. The Board's writ extends to community oversight, but not technical oversight.

The ASF believes that emphasizing community tends to produce excellent software on average. Gating projects or otherwise interfering based on somebody's arbitrary judgment of quality would be be foreign, and would in fact impede the freedom of projects to develop according to the best judgment of the individuals actually doing the work.
The scope of the mutual non-disparagement clause seems excessively broad. Why would a computer security researcher sign away his right to criticize the products, services, vendors and affiliates of the leading anonymous communication tool?
Broadband CEOs Admit Usage Caps Nothing More Than Uncompetitive Markets Tolls
Oddly enough, you can opt out of the Social Security - some employees of government agencies don't have to contribute and some religions are also exempt.

Personally, I feel that anybody should be able to permanently opt-out if desired.
Of course not. But I could totally see Trolltech getting critical bugfix requests from people "promising" to pay the commercial license once they launch.

I would totally understand the response eventually turning into "yeah, we'll fix your bug, but put your money where your mouth is", which is where they are today.
Ah. I get your point.

Tell me what percentage of attackers on the net have full access to the network traffic and can do full MITM attack?

If the goal is layered defense and minimizing exposure, worst case scenario is not good counterargument.
San Francisco just backed Airbnb into a corner
They've long confiscated cars and cash. They're just upping their game.
It blows my mind this is even technically possible. Surely the target needs to enter a pin or something in order for the bank to authorise the transaction.

That said seizing cash whether physical notes or electronic must be subject to due process and a court order.
i think if my bank offered advice, i'd strongly consider doing the exact opposite of whatever they suggested. i'd rank it up there w/ listening to jiffy lube's recommendation to refill the blinker fluid.
Is Linux the best choice for a router, or would one of the BSDs work better? Obviously the author chose Linux because he was most familiar with it, and that's an excellent reason, but I'm curious what the choice would be if you were starting with a clean slate.
Upvoting you and GP wasn't enough; I screen captured the exchange for my personal archives. If I ever write my great American novel, I'll try to give credit.
Swiss reject universal basic income in public referendum
Messenger bots can hear you typing too
Uh... things that seem to work fine in Mongo under light load tend to fall over during heavy load. Things like this problem. Like key reordering: https://jeremywsherman.com/blog/2013/04/23/key-reordering-ru...

Yes, with enough extremely careful coding knowing exactly all the internals of the database, you can probably avoid these giant gotchas. But that's a hell of a lot of work for a DB that's supposed to be easy.

And then you're still dealing with a database without ACID guarantees. No transactions, very little atomicity.... and good luck if your server crashes... we've had multiple customers have their DB corrupted that way.

MongoDB is only good for storing data you don't really care about... in which case, why are you bothering to store it at all?

What most people end up storing in Mongo: strongly schema'ed, relational data that is critical to their application. This is exactly what mongo is not for.
Custom Chef Knives Review
> News 9 obtained a copy of the contract with the state. It shows the state is paying ERAD Group Inc. [...] 7.7 percent of all the cash the highway patrol seizes.

I think that might even be worse then the police being able to sieze all of you money.
Original author here, what I'm proposing is an ARRAY[VARCHAR]. Postgres has a native array type, different from manually mangling an array.
Agreed. And the reason here for using UUIDs is not accurate. UUIDs are for having multiple systems (or components) create IDs and having a reasonable expectation for uniqueness, hence the Universal Unique part.

It grinds my gears when people sneer at integers when they perform optimally or nearly optimally on the majority of use cases.
Thanks! You should see the updated checkbox if refresh the page.
NPM's scale is the exception, rather than the rule.
Or just refer to packages by 2 names.

Maintainer/PackageName

It solves so many problems, this included.
EAV isn't all bad, there are use-cases for it. If you have a highly dynamic data (user configurable) then EAV might be a good way to STORE that data.

Is it ugly, it sure is. Moving read out to a cache layer, and search out a purpose built system, the DB becomes a persistence engine. You have solved the other issue you don't mention with EAV, and thats performance.

Edit (my ability to post should be forbidden till I have had coffee, cleaned up for clarity)
Thank you! Glad you're enjoying it.
“Promises: All the Wrong Ways” exploring promise anti-patterns
Ha - I like it. I want to replicate this so that when our sales team closes a deal then can press a button and queue the noise! :-)

Looks like a good Friday afternoon hack.
If you're in this position, you have scale informing product requirements already and can denormalize up front. But this is uncommon for read/write transactional workloads and an especially uncommon scenario for a beginner to find themself in.
it'd be like Pharma companies refusing to manufacture lethal injection
Is it learning the specific level layout or can it adapt when the screens are different and order swapped?
In other news, the reveal itself was pretty interesting, so thank you for the link, even though that wasn't the intended purpose, I had no idea about it :)
No, people want large, busybody departments. It makes them feel safe. They don't want to increase their taxes, though, especially in conservative states such as Oklahoma.
hahaha nice +1 would read again
Which PHP framework is right for you?