skysight-inc/HackerNews huggingface dataset:
The market is so small that one or few bigger holders/investors can move with it significantly.
Mongo with a strongly typed language also encourages someone to put some definition around the dataset. That someone is just the developer creating the PO*O (Plain Old [C#/Java, etc] object).

In C# for instance using the standard Mongo driver, you're dealing with strongly typed collections and the compiler is keeping you from mistakingly going outside of the "schema".

I don't know how good the other .Net drivers are for other Nosql databases.
Yep, it might have bottomed out.

Or maybe it’s a dead cat bounce. It’s amusing either way.
The diabolical genius of the baby advice industry
Yet a lot of, say, Hawaiian words are written like that and nobody cares. Seems like Nazarbaev wants to keep the language ASCII instead of adding diacritics which would make it hard to type.
Sorry for going off-topic, but is there any good community I can join if I am interested only in understanding the technical side of blokchain and blockchain development, its potential use cases and pitfalls.
Shanghai has a maglev shuttle between Longyang Road and the airport, the 30km trip takes ~8mn. Going by car or on line 2 takes ~45mn.
It probably means the keyboards people in Kazakhstan already have. Which I assume is a Cyrillic keyboard, which can also do Latin script but does not have keys for umlauts and such.
Do you have some example searches?

I believe you, just never seen it myself. Perhaps I switched some obscure setting on years ago.
Automation is the other solution. For example in Helsinki-Vantaa, there are far more automated passport check gates than there are traditional immigration desks: https://www.flickr.com/photos/bergie/3176184017

Even at SFO I've gotten to fill the immigration questionnaire a few times with a self-service machine, greatly reducing the time spent on the process.
I don't think Americans should be demonized... Having met a lot of you, I know you're not all crazy. So yeah, I'm obviously being a little provocative :)

But I do something wonder if you just don't want the problems solved? The solutions seems obvious, and yet you keep getting side tracked, like blaming the prankster.

Other than police training and changes in behavior, what real solutions do you see?
Attention-grabbing headlines and bad research has conditioned me to not update my beliefs based on anything that I only briefly stumble upon like this. There might have been a time when reading an article like this would blow my mind, and make me excitedly share it with others who had a similar belief, but now my first impulse is to just feel sceptical.
They might be there for a reason, but that reason doesn't necessarily benefit the individual who is being harmed by them. E.g. KYC/AML.
atleast bitcoin will end
It would be a fun challenge, note that for instance the first part of the script is dependency check, the whole is basically `import a,b,c,d` in meaning.

It's true that calling programs shortens tremendously, but every time you have to glue things together you're back to grep/sed and all the fragile bash idioms.

Of course you could have standalone programs to do that, in the end it would be as having a non bash programming language in disguise
Novice crypto question... I read a comment here about 1 month ago someone predicted a correction of BTC value to mind january because some coins would "expire" then. I'm trying to find the comment now to learn more. Anyone have any insight what I'm talking about?
...poison? Aren't there actual recording(s) of the sounds? [1]

I guess this doesn't rule out them having bee poisoned on top of it, but it sure does raise eyebrows. Are they hypothesizing sounds were used to cover up the poison or something?

And given that even the article acknowledges some had concussions (here's another source I saw it in [2]) I'm not sure why the poison hypothesis is being entertained?

[1] https://www.youtube.com/watch?v=ghdLfQsztBo

[2] https://www.theguardian.com/world/2017/sep/14/mystery-of-son...
You are right that there have been people speculating about it for a long time, going back more than a hundred years. Some of the earliest reports are from the time of the Indian Plague Commission, and there have been some snippets of evidence since then.

One of the groups that is doing most of the research on body lice as vectors of plague is the group of Didier Raoult. Michelle Ziegler made a nice summary of that work here:

https://contagions.wordpress.com/2016/11/17/the-case-for-lou...
Or it could be, gasp, perhaps bitcoin was overvalued? No, anything but that.
"In other news, GOOG jumped by 7% today upon speculation that Google would soon introduce a banking product offering instant transfers between accounts. The speculation arises from a technical blog post, which describes Google's vision for how a banking website ought to look like, and stood out because no American banking product actually works in such a fashion today. Google's new banking product would compete with banks like Monzo, which also attempt to disrupt the legacy systems that power most contemporary banking infrastructure."
>> Setting people up to fail is a thing. How can so many people apparently not see that?

Are you OK with your kids and your spouse and your parents being murdered by police because... some random POS made a phone call, and "set them to fail"?
I see, but sticking to HS256 should solve this without much headache.
This is crypto logic. In 'real' stocks this will be called a collapse for today or at least an extremely wild ride.

I wonder how much technical analysis can be done to predict this.

Just HODL!
> it really does seem like the universe conspires to minimize some quantity.

But there's only one min/max isn't there? Otherwise all values may be permitted, and we'd have entropy.

The vast body of physics may concern behavior simple enough to be expressed, but much of reality behaves in complex ways?
One thing to be aware of with OAuth 2.0 is Refresh Tokens. If the spec is followed, the Refresh Tokens are long-lived and never expire (the spec makes a suggestion that you revoke used tokens, but it's not required), so if they are leaked you are in for a bad time.

There's an RFC that goes into some of the security considerations of OAuth 2.0, that should be required reading if you implement it (even from a pre-built library): https://tools.ietf.org/html/rfc6819
Well to be fair, half the money came from Melinda.
1. As secret, use encrypted(some internal device id, pregenerated-key)

2. Generate pregenerated-key upon first login (maybe based on email or tel no?). Just like, e.g., Signal does it

3. On your servers, check if pregenerated-key and/or email is used more than once at the same time, if so invalidate it and direct user to 2.
Ideally you use some kind of time-limited API tokens, and find a way to automatically distributed new API tokens, before the old ones expire.

That way, the breach of a single device doesn't immediately give the attacker unlimited access to the API.

You should also monitor for unusual activity, and blacklist API keys and devices with such activity.
Could it be a possibility to generate a keypair on the machine and then attempt to register itself to your webserver supplying client-name, IP and public-key. Then you would be able to see and OK any attempts to connect. Once you've OK'ed it, it would be able to authenticate and communicate normally as an authenticated device.
I think Chrome history might be limited in time. Something like 3
I know, INR works instead of ₹. But goddammit I don't wanna type those extra 2 letters!
A few names come to mind:

Josef Koudelka, Henri Cartier Bresson, Greg Girard, Masahisa Fukase, Sergio Larrain, Jean Dieuzaide, Hiroshi Sugimoto, Brett Weston, Kourtney Roy, Franco Fontana.

Searching those names on Google is already a journey by itself.
Bitcoin Tumbles as Digital Coins Resume Their Slide
Bitcoin:
% 1h	% 24h
+0.13% +3.21%

#	Name	Symbol	Market Cap	Price	Circulating Supply	Volume (24h)	% 1h	% 24h	% 7d
1
Bitcoin	BTC	$237,388,220,556	$14,126.10	16,804,937	$12,931,700,000	0.13%
> The end result was a system that, for each update, required six background jobs to be launched, which each launched their own cascading jobs that patched up the data. And our records all had to be peppered with version fields and updated-by-job fields and version-of-foreign-key fields that these fixup jobs had to test against to make sure they're not operating against stale data or running over each other, such that this crap actually outweighs the actual data in the records.

That sounds bad. The way you're supposed to do it is have the initial data be immutable and compute the downstream data separately, but into its own places.

> So for my money, give me a strongly consistent system by default. I don't even particularly understand the argument given above. With a strongly consistent system, you can still choose to do things like join in the client if there's a reason for it. But going the opposite way and forcing consistency to be unassumed everywhere produces the mess we're dwelling in now.

I'd say transactions should never be the default, because a database transaction that isn't a semantic transaction is worse than useless. If the application programmer hasn't thought about transactionality and synchronization, it's much better for that to show up as not having any transactions - you can fix that, by adding transactions where you need them - than to have transactions that don't mean anything, and the data ending up inconsistent even though no transactions ever overlapped.
Depending on your usecase, a quick setup would be to use https://auth0.com/ They have a lot of documentation and samples to get started.

We have implemented it for authentication with a Asp.Net Core webservice, with a REST based API. Authorization is also possible, either by working with the JWT token scopes, or using the Auth0 app_metadata.
There's certainly been speculation that Cemu was helping along by documentation/SDKs that should have under NDA (from the pace of development etc.), so I wouldn't be that shocked if they were keeping it closed until that is engineered out.
In this specific case, holding the caller responsible. When someone goes out of their way to hide the origin of the call using special equipment, that is not the same as some dumb 10 year old being handed the phone and dared to dial 911 and make something up.

The fact that the US has a general problem with police shootings is absolutely not a reason to let the caller off the hook. If anything, it is a reason to argue that he reasonably knew this could result in someone's death, so the charge should be more serious than manslaughter.
> all the best practices that we by all means should be following, but aren't because of a senior engineer stuck in the 1990's and is seemingly not only paralyzed by analysis (and bikeshedding), but seems to subscribe to the notion as a way of living, and management who defers to him at every turn despite all evidence of how it holds us back (not to mention directly contributing to outages)

Huh, that's exactly how I feel about the "must use a RDBMS for all data" senior architects I've worked with.
Is it? I remember being told this about pot, as a 12 year old.

I think most drugs have a wide range of users. Some have more or less problem users of various kinds, notably addicts. But all also have large numbers or normative users, even heroin.

In the 80s, the most noticeable gays were transexuals, eccentrics, prostitutes or people busted in embarrassing situations. People who couldn't/wouldn't be low key. This led to the impression that gays are mostly fringey people. Same for prostitution. No one knows about the individuals with a phone number and a regular life. Same for all vice. Normative people manage to keep it under the radar. You see street users, not the 32 year old coffee machine shop owner.

I don't think there's any drug that will addict many users after one or two times. Obviously, many do lead to addiction in large numbers, so are still risky.
Facial recognition software is coming to industries like fast food
Yeah, the tools I had were picky. The size of the OS partition was very specific - it had to fit on to a multiple of a CF card I think. There was some kind of hard limit of about 32MB or something like that. I know I had it all running on an old Compaq PC at one point, but the bootloader would only boot if it was the only OS on the drive, so that was a bit of a pain in practice. I probably still have the OS images somewhere.

I also know that the OS was a bit quirky in so much as some of the R5 API's were missing, or closer to the R4.0 ones at least. The File System was definitely flaky.

I started to write this app to do PalmOS style handwriting input for the DT-300, but I ended up selling it on to finance some other project before I finished it. https://github.com/memsom/ratcowsoftopensource/tree/master/B...
These two (Bill and Melinda) seem so dodgy to me. Something is off about this whole good-samaritan-donator story.
5 SEO Aspects You Should Always Check Before Launching a Website
I'm in Europe. It's not ridiculous. It's ridiculous the police officer isn't being charged. But the idiot who caused the incident is also liable.
If there is nothing special about it, I'd recommend JWT, for the simple reason that you have less load on your DB (and more on your CPU but that is usually not the bottleneck)
It's a bloodbath today. Global coin market capitalisation is down to $570B down from $830B 9 days ago (-32%)
Not a bad first impulse :-). It often pays in science to wait a few years/follow-up studies before fully accepting something. What is thought to be true in plague is especially fluid now with ancient DNA studies on human remains coming out regularly, each with its own narrative on how to explain the phylogenetic tree.

That said, there are some long-standing questions in plague research, one of which is why the first and second plague pandemic were that much more lethal than the third plague pandemic. Prior to the aDNA work, people speculated that medieval plague was a different pathogen altogether, but that hypothesis has been put to rest now. An alternative theory has been that plague could spread through human ectoparasites, and we found a novel way to test that theory. That resulted in this paper.
There are slack channels and of course the GitHub repos.
No, of course not. And that isn't a rebuttal of my point that the caller absolutely needs to be held responsible for his actions in this debacle.
They were, but, in the last few minutes the last hour numbers have all gone green. They were definitely all red when I checked this half an hour ago.

I think the whole thing is a scam and that it is incredible the willingness of people to be scammed. Yes I see merit in a decent online currency that works like cash but securely, however, these crypto things are speculative tulip stocks in a book-keeper's window and the people that have bought into it are very much in a cult of their own devising. It is comical. When fools rush in.
The "BTC Dominance" chart from Coinmarketcap sheds light to this: https://coinmarketcap.com/charts/#dominance-percentage

It actually shows that Bitcoin has lost a lot of value against altcoins since the early December top.
Can't store password on device (it's a device we don't control)

Can you expand on this? Because storing a device-specific password (or api key, which is essentially the same) would be my first suggestion.

If it's because you can't configure the device, then my suggestion would be to create a process that embeds the device key into the software before deploying to each particular device.
For applications using a HMAC token with some sort of timestamp which can be checked for replay attacks. AWS has a good guide: https://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthenti....

For users, I'd add a OAuth layer to the application layer and still have this application using a HMAC like above. You want to try keep things 'stateless' when it comes to your API's.
I never used a BB, but I did have a bunch of "dumb" cell phones, and I miss them. Making calls on them was easy: Flip open, press Talk, dial, Success! Now it's: Turn the phone on (which takes approximately 60 seconds on my Samsung because it can't see keystrokes until it finishes trying to connect to wifi), hit Home button, wait 3 seconds for that to work, hit Phone icon, wait 2 seconds, hit keyboard button, wait 1 second, dial phone waiting 500 ms between each key, press Call icon, wait 20 seconds for call to go through, hit speakerphone button (because as often as not the cheek sensor fails to work and my cheek disconnects the call), Success!

As the saying goes, smart phones are just pocket computers with shitty phones attached.
> But why should the caller not be similarly liable?

He should, he will, and I never meant to imply that he shouldn't. But the cop should to, yet probably won't. That's a very wrong message to send to the other officers who struggle with accurate situation assessment and cold-headedness. Not to mention trigger-happy sociopaths.

> The fake situation called in was so serious

It's part of proper police work to assess the actual seriousness of the situation before escalating violence. Hostage-taking is a crime that actually exists, and police must be prepared to face it adequately. But SWATing is also a crime that actually exists, and police must also be prepared to face it adequately.

In most other countries, there is a much stronger doctrine of trying to avoid violence escalation, and way fewer people are killed by police: guilty suspects, innocent suspects and collateral damages alike. One could be tempted to see a causality.

> at least a manslaughter charge for both would be more than reasonable.

Totally agree. And depending on whether the cop felt like "he's about to gun me!" or "I'm unsure, but if I shoot I can get away with it", it's either manslaughter or murder. We'll probably never know beyond reasonable doubt, so it can't go beyond manslaughter in practice.
Well aware of the economic term that's not the problem.

The claim was that gold have intrinsic value and bitcoin doesn't. But to the extent of discussing intrinsic value in economical terms then bitcoin does too.

In other words you can't both have your cake and eat it.

Either both bitcoin and gold has intrinsic value in economical terms or none of them have in philosophical terms.

The value of them are both based on the trust that the market will accept that value which currently for bitcoin is fluctuating very rapidly and for gold more slowly.
Then perhaps I'm biased. Where I was raised (eastern orthodox), preaching in favour of contraception and abortion
as divine mandate was/is seen as crazy. I certainly don't have numbers to compare.
> Highly-structured systems like a traditional RDBMS are very good for resiliency because they require someone to put some definition and formality around the dataset to get basic functionality, and they are generally extremely careful about ensuring the things that come in and out of them are safe and accurate.

That's not what happens in practice. Just because an RDBMS has transactions doesn't mean a programmer who isn't trying is going to use them correctly. And when you do enforce constraints at the DB level, you end up duplicating all your logic in two different languages, one of which isn't very nice for programming in. E.g. I've never found database timezone handling to be anything other than harmful. The application is just better at enforcing this kind of constraints; a well-designed application could make use of transactionality, but putting the transactionality in the datastore won't make the application better at it if the dev wasn't thinking about it - and if the dev is thinking about it, they can usually do better at the application level.
It has a lot to do with how police react. It is done to elicit aggressive response to punish victim for whatever. It was not done for fun here.
> Can't store password on device (it's a device we don't control). No user, so authentication has to be all autommated.

Am I missing something, or have you painted a contradiction?

* You want the device to hold some secret

* You want the device to be able to prove that it holds the secret

* You don't trust the device to hold a secret

If I'm understanding this correctly, then you've left the realm of cryptography and entered the realm of obfuscation.

Edit

This isn't necessarily a losing battle, but it changes the way we need to think about the problem.

Games consoles and DRM'ed video media (Blu-Ray and HDCP) do something similar in not trusting the end-user: they want to hold the key to the kingdom whilst ensuring the user never sees it. They've done this with varying levels of success.
My only explanation to this would be that they would choose whatever was close and easier to get to. Don't forget that travelling was way different back then.

I've heard stories of fleeing to Mani, Sicily and Egypt.

I guess each family, or person was choosing the easiest place to get to by his own means.

Now why they stayed there and didn't e.g move up to Genova, I have no idea. Maybe some people did, some others didn't.

On your second point, I feel like organised crime in the US is and I'd say in the world to an extend is made up by groups that tend to be foreign to that Country. If you take it by todays standards and leave out the Italians in Organised crime that have the means both political and economical to do what they do, you have other groups like the Albenians that tend to influence things using pure muscle even nowadays. Here in Europe the Albenian mafia seems to have a very powerful crew, most of its power doesn't come by political factors nor economical, but by manpower and muscle (e.g members of the albenian mafia won't care if they will be jailed, they are just going to act). Same applies to some other groups e.g form Afghanistan that run drugs etc. My opinion on that is that they tend to be tougher due to having participated in wars. Imagine an Afghan boy that lived through his whole family teared apart and seen death in a war, smuggling his way in London and instead of Europe helping him get on his feet, there is a group of his own people that offer him a few bucks in order to go do something illegal. Btw this has nothing to do with Afghans, its just an example, I have nothing against them.
Gold has utility in electronics. It has nothing to do with it's value.

Bitcoin have utility as a store of value.
If they're available for $50 after it means the market price has gone up, if they can sell them at $50 why can't you? Securities/Tokens are a two way street not your typical discount aisle.
I believe a similar problem affects TDD, and in general any methodology that assumed that longer processes are modularisable into smaller problems.

Ask someone to TDD a Sudoku, where the simple rules have inter-dependency. You can write three tests:

1) each column contains numbers 1-9

2) each row contains numbers 1-9

3) each box/subgrid contains numbers 1-9

But the solution must pass all simultaneously. The usual "write test, pass test" loop entails writing two lots of useless code if you try passing one/two alone - "write test, pass test, throw away what you just wrote cause the real crux is interdependence"...
Masalasoft Released MyOffice – Microsoft Office Edition Version 2.2
Seems to me the answer is indeed that simple: use OAuth2 and be done.
IMO BTC's value could sensibly fluctuate around $10k. The hype/trend and the media frenzy caused the spike of $20k.

Let it rest for a while and I believe it will have more races up-and-down the 10k-22k range so people can enjoy their gambling ;)
If the Refresh Tokens are leaked, you revoke them and the user has to re-authenticate.

It's crucial that clients are able to respond to their refresh tokens being revoked.

The good thing is that it is a standard workflow, contrary to API key being revoked, which is generally not handled (most people hard-code API key in their client).