skysight-inc/HackerNews huggingface dataset:
Same trick as in the Will Smith film Enemy of the State (except Smith is trying to block government tracking)
This isn't reserved to Pakistan, the US, Islam or Google. [0]
Tbh if I had a choice between nudity being censored and bigotry being somewhat buried, I'd always go with the later. But for whatever reason a certain demographic, from a certain country, takes quite a lot of offense at the sight of something as silly as a female nipple.

[0] https://www.pastemagazine.com/articles/2016/09/censorship-is...
Linkedin https certificate expired
You have that backwards. Its primarily through gov favor (ILEC / CLEC / etc) - the structural factors are a by-product of their monopoly status not a cause.
>Having said that, a cryptocurrency that does its job... seems like a very valuable concept. Do any of them do that?

Why? What particular problems does it address that other currencies do not, and what would ultimately ensure its value or price stability?

Commodity currencies have value because they have non-currency uses. Gold is useful in electronics, manufacturing, biotech, and jewelry, and so on.

Fiat currencies are backed by tax authority, and control over territory... or in other words violence. We know fiat currencies are valuable because people have to use them to pay taxes, to use natural resources, etc.

Remind me why we should use a currency that someone merely imagines into existence. At least if I hand you an IOU scrawled on a piece of paper, I'm promising you something, and anyone who would find that valuable would be placing a bet on my trustworthiness, as dubious as it may seem to some. But bitcoin doesn't even offer that.
> What use is sorting a randomly generated value?

In general, order determinism. The elements in the table or list don't shuffle
on every refresh.
128 bits can be a waste of space, but I appreciate not wanting to publicly reveal the table size.

One of my biggest wishes from a database would be a function similar to auto increment, except that would pick randomly from the column's full integer range, guaranteed not to collide. I almost never need 128 bits -- 32 bits will let me handle 4 billion users.

It seems to me that a column index could be used to do that quickly -- essentially, if it's a binary tree, pick branches randomly but never pick a branch known to be full.
I haven't yet had time to properly investigate, but I have heard that wheat crops are sprayed liberally with glyphosate directly before harvest as a desiccant to make harvesting easier. (perhaps also increasing yield, I don't know) So the dose may be quite a bit higher than you'd generally expect.

Also note that glyphosate is Generally Recognized as Safe (GRAS) by the FDA, which means that it can be used in any quantity. With that designation, arguments about dosage carry less weight for me. If a regulatory agency were concerned with dosages in final food products, I'd feel a lot more comfortable.
You do understand how unsuitable zones are in a public cloud like AWS, right? Why are you even having this discussion.
Use both. PK = int, APIID = UUID

Using integers, auto incrementing or not, reduces the resource pressure on indexing when doing complex joins.

When you need to expose a key, expose the APIID.
Use lots of thermite to ensure any local data has been deleted ;)
Was This the First Dead Sea Scroll?
Without knowing their migration strategy it is hard to say.
A few things I notice that get borked often with migrations are not handling redirects & internal links properly, not updating sitemaps & canonical tags, and not checking Google Search Console & robots.txt
Much of the layoffs tend to happen in North America and Europe and the hiring is in China I understand at Autodesk. I do not have numbers to back that up though, but it is my understanding.
A lot of PHP folks nowadays try to distance themselves from the simplicity that made PHP popular. Avoid falling into AbstractInterfaceAdapterFactory trap and use it like it was conceived to be used; simple and procedural (https://toys.lerdorf.com/archives/38-The-no-framework-PHP-MV...). Otherwise, just use Java.
GPS jamming is a good way to have men in black show up at your doorstep. Source: a friend.
Who the heck uses a editor with tab completion to make changes to production database? As a DBA, I'm horrified...
There's the "Kaldi for Dummies" tutorial [1], which helped me to the point of creating a speech recognition program that could distinguish digits in recordings of my voice. I guess that's the documentation you're looking for.

My personal problem with Kaldi is that I don't have enough RAM in my cheap laptop to work with any of the big models. When it started swapping just doing the preprocessing for one of the pretrained models [2], I kind of abandoned that project until I bother to get new hardware.

For that reason, I can't tell how good the pretrained models really are.

[1] http://kaldi-asr.org/doc/kaldi_for_dummies.html
[2] http://kaldi-asr.org/models.html
This article conflates two different points, only one of which makes sense. First, the idea that the government can provide services at a lower cost because it doesn’t need to make a profit is laughable. Even Comcast’s profit margin is only about 10-15%. Eliminating the profit completely wouldn’t, by itself, make broadband affordable to poor people.

The second, implicit, point is that richer people should subsidize (via tax dollars) internet service for poorer people. That is, after all, how we handle other kinds of basic rights: Medicaid, Section 8 housing, SNAP. And that’s a fine idea! But it’s completely orthogonal to the first point.

In telecom, we conflate deployment and access. Under state and local regulations, anyone who wants to become an ISP also has to take on the government's burden of ensuring access to services. If you want to compete with Comcast in New York City, you can't build a "minimal viable ISP" in Chelsea. The government forces you to serve the Bronx too. That not only kills competition, it doesn't work. Just because you force a company to build fiber in the Bronx doesn't mean people can afford $70/month for it.

In other areas of the economy, we've learned to separate the two policies. The government doesn't run old-age homes--it pays private entities through Medicaid. It doesn't run an agricultural business--it provides SNAP payments. Governments are moving away from running public housing, and instead provide Section 8 vouchers.

What we do in telecom, in contrast, is like rent control. Rent control turns every apartment building into a mini-HUD, which is forced to accommodate lower-income people by overcharging other residents. Like rent control, it makes no sense.
Answer: Open suitcase. Insert 5 t-shirts, 2 trousers, 7 units of underwear of preference, 7 pairs of socks. Close suitcase. Repeat the same with laptop into backpack. Open door. Move out. Done.
I think we have a tendency today to under rate the abilities and knowledge of pre-modern people. There is a lot we can learn from earlier ages despite the fact that their scientific knowledge was not as advanced as ours.
Random distribution seems like it would be better for write performance - it means that inserting multiple new values and rebuilding the index can happen in parallel rather than having to coordinate the auto increments. It also naturally has the right properties for sharding as and when you get to the point of needing that.

On the read side it shouldn't make any difference, as there's no reason the rows you want to access at any given point should have any correlation to when those rows were created.
I don't see why it would be necessary to discount such claims. The claims are worthless. They're not worth considering at all, until they prove something (and right now they're running a substantial credibility deficit).

Ten years of zero net growth, and four years of declining profitability, should tell you everything you need to know about what's actually happening. They've spent most of their profits from the last decade on faking EPS growth with buybacks while their business was languishing. Now things are so bad, they're hatcheting their most valuable resource: their people.

I think they spent ~$188 million buying back their stock in the first quarter, while losing over $100m in operating income. They paid $85 per share for those shares. Around 80 times earnings, if earnings were still at the old 2013 levels.

It's financial suicide. They're driving Autodesk into a wall at high speeds, while destroying their balance sheet trying to keep the stock propped up with buybacks far beyond what they can actually afford based on present profitability and a reasonable outlook the next few years (which is why they're firing 13% of their staff).

Or put it another way. The cost of the share buyback announced last year could cover the cost of the 13% of workers that are getting fired, for at least two decades.

Autodesk long ago got into the IBM financial engineering business. The consequences of that are getting more unavoidable by the year.
Google holds the power to influence en masse. If not policed, Google has the power, if so it was to choose, to remove critical human knowledge from results. Perhaps the moonlanding never happened, or perhaps chemical weapons were faked. etc...

Their results can influence a great number of people, it can make or break a business, and it can (probably) cause or at least greatly contribute to a revolution in some countries.

You know, hence why countries like China want to control such power.
Having used both Laravel and Spring, I don't see Laravel being much worse at DI. Spring is just doing everything by Strings anyways, so if you're going to get failures they'll still be at runtime.
Problems are released midnight EST. First person with a solution globally gets 100 points, second person gets 99, etc. So you have to be one of the first solvers globally to get any points.
Ahh the pedway. A lovely idea, but every piece of it is in different shape. Some bits are nice (Illinois Center), but others are super dumpy (from Macy's to Millennium Station), and anything in between.

I hope this attention from the Architecture Biennial will result in some new interest and cash to freshen it up a bit. Because right now it's just raw and utilitarian, in that unsentimental way that Chicago infrastructure tends to be... :)
BTC addresses whose private keys are from SHA256 of another public address
That's a very interesting way of looking at it. I never thought about it that way before, but that's exactly what I'm talking about.

For example, I have a google home. Google home relies on an external server to work, but that's okay, since it's not really "replacing" anything, only adding a new "class" of device.

But it's not okay for a door lock to not take a standard key (or in my case, the door lock needed a number pad), just to get "smart" functionality.
I always try to use a semantic key first, if it makes sense. For example, I see this in my current database:

id utility

1 electric

2 gas

3 water

What is the point of the numeric ids versus simply making the name the primary key? I'd argue there is none, plus there significant drawbacks.

Every time we start with the utility name and need to get the row id, the database needs to search on a non-primary key. This is going to be commonly used in JOINs (and tables designed with superfluous ids lend themselves to many gratuitous joins.) Optimizing the primary keys based on the typical data used to search (actual key data from the user's standpoint) will make your DB blazing fast.

Also, using integers everywhere (or even worse, UUIDs) destroys the readability of queries. How many integer ids could be used in a query and still be understandable? The id `3` could mean almost anything, but the id `water` brings meaning to queries. The benefits to maintainability are significant.

Lazy DB designers seem to have a bad habit of adding auto-ids to everything regardless of value. I even see joiner tables (that should be using the composite primary key of multiple foreign keys) using unnecessary auto ids! This is sloppy work.

In short, I have found significant benefits to using semantic keys first (if appropriate - there are definitely reasons to use incremental integer or UUID keys in many tables) for these reasons:

1. Fewer columns without loss of meaning
2. Fewer joins needed
3. Faster searches
4. More human-readable
SSN will give them something to look up in the central registry; as a bank they'll have the authority to do requests for information.
> If a photo of your passport or whatnot is private information that must be kept secret, or else identity theft... well then it can't be sent to AirBnB en masse.

I think the main issue is that it’s not really you, but service providers who get to decide what’s an information that need to be kept secret.

For instance if most banks decide to exclusively use bits of your fingernails to verify you, your fingernails become something you need to keep secret, your personal position be damned.

And the more agencies that decide to use your fingernail bits, the more valuable they get.

For Airbnb, if the practice propagates enough, your photo with your passport in it will become the new way to fake you.
What I'm getting at is that Bitcoin is essentially being traded as a security, where it's basically just how much electricity mining pools have wasted. Despite being designed as a currency, it sees very little use as such and mostly just gets moved around between people trying to get rich.

>your statement as it stands is worded to be condescending

That is intentional. I find Bitcoin is stupid and wasteful by design.
Uncovering the Intuition Behind Capsule Networks
I will use PHP 7.2 on projects I maintain.

However, starting a web project with Kotlin in 2017 has a minimally larger set-up cost (have to understand gradle or kobalt) than PHP, but is definitely a better option. Check out http4k or ktor and squash (orm)
> So what exactly is your solution?

Enforce antitrust laws.
It depends upon how you define regulations. The free market is capable of regulating itself as long as there are societal rules against stealing and fraud, rules to enforce contracts, etc.
Good thing most people know how to make a hash.
These days, I believe the monitor is becoming the KVM. High-end Dell laptops have multiple inputs as well as USB slots for peripherals, and even a handful of USB type B to send back downstream.

Mine doesn't, unfortunately, so for my two computers plugged into my Dell monitor, I have the keyboard and mouse plugged into a cheap USB switch, while simply cycling through the inputs on the monitor.

It's two clicks instead of one with a traditional KVM, but I don't have $150 to blow on a KVM that has something better than a VGA slot...
I can't help think the actual software end of this is over-engineered.
That's the worst of both worlds. Writes are slower than ever since you have to update both indices on every insert. If you normalize your database you have to do a bunch of extra joins for every API response. If you denormalize it you have twice as many columns and either complex foreign key constraints (slowing down writes even further) or the possibility of getting your data into an inconsistent state.
How do you handle syncing in orgzly? My current approach is "remember to hit the sync button", but apparently I suck at that. :) At least it's easy to fix sync conflicts in Emacs using ediff.
Would it be useful to compress 128-bit UUIDs to fit them into narrower columns and reduce IO? I don't fully grasp the issues this would entail.

Looks like there's an old patent related to this:

https://www.google.com/patents/US5913217
Assess Angular, but no mention of React?
Preparing for optimal live streaming video content delivery
HN really isn't a good example of modern software or good UX tbf.
I was going to say burn it down, and make it look like an electrical thing...
Does it support inline images?

I'm using Quiver for Mac, but really a cross platform solution would be more appropriate.

I tend to take notes/drawings on paper then take pictures of the useful stuff and put it into Quiver so I can see it in context
After reading lots of negative comments about pricing, I think that many people don't get it - AWS Fargate is not a replacement of EC2 nor ECS. It's a sort of lambda with containers and lots of features (HA, autoscaling, etc.) implemented + pay-per second - which is absolutely great! This way you could run short and long running jobs which are container-based (a django-admin job that performs migrations? dunno... just saying...), and also your "normal" services without taking care of scaling up/down, HA, etc.

It's not for everyone, it's not a "one solution fits all", it's very specific and what it does, it does it great (only tested, of course we have to see long-term...), because you don't need anymore to manage a cluster, which is really expensive especially because you don't want to shutdown your machines when you go home and restart them when you come back to the office (for example, in case you don't have a smart autoscaling in place).

Thanks AWS for providing this service!
There is a different reason that auto incrementing ids are bad: they don't scale.

When you need to shard your table, the autoincrementing is is a bottleneck across all shards as you need to hold a lock on it when incrementing. In fact, that's exactly how it's implemented explicitly in POSTGRES.

And if you want something that's way MORE distributed such as CockroachDB or (RIP) Riak then forget about it.

But you don't necessarily need UUIDs. You can use for example https://www.npmjs.com/package/shortid

What we do is generate a random 7 character string (alphanumeric lowercase) and then check if it exists in the db and - if not - insert it, using a transaction. Otherwise repeat until one works.
I refuse to install any more Electron apps on my desktop.
> it’d have made an operating profit of 0.2% last year.

Factor in no need to advertise services, no duplication of effort (and greater scale), no sales department, no executive bonuses at all levels, no contracts, no legal department, no billing, no metering and so on.

It's not the profit that makes a difference.
I can retire already (pretty much at around 40, but I do really love my job, so every year I am postponing for 1 more year :-)
Datally, Google's mobile data management app
Is a societal rule against, say, polluting waterways also not a regulation?

How exactly do you draw this line and why is that line more natural than others? Is the idea of a division between "societal rule that isn't a regulation" and "societal rule that is a regulation" even coherent?
Counterpoint is that buyers aren't either.

I think the underlying issue is that people don't see a huge amount of value in a little bit of automation and balk at the prices, so the market consists mostly of buyers that really want to be able to do various automations.
Open Door Policy: The Laziest and Most Incomplete Answer to Company Culture
> societal rules against stealing and fraud

That's what we call regulation.
Basing user ids (as facebook did) on an autoincrementing number exposed when a user joined the site.

Mark Zuckerberg is famously 4 and you can find a lot of famous silicon valley types in the first million user ids :)
> The need to standardize things like std::filesystem was my point.

Which circles back to my statement about "The C mentality of some devs dragged into C++ world.".

Many useful C++ libraries were not standardized in the early days beyond STL, because many thought C++ should be like C where libraries are whatever the OS provides and nothing else.

Which is clearly visible in the decision to have ANSI C and POSIX APIs as two separate standards, although most C compilers try to provide some kind of additional POSIX compatibility, specially visible in non-POSIX OSes.

Thankfully, the ANSI C++ committee realized the mistake and now we are getting a useful set of libraries into the standard.

As for compilation flags, even for C it is only true if all compilers on the platform follow the same ABI.

And you still need to provide all variants anyway (debug, single and multithreaded, hard and soft float, pre-defined pre-processor macros, ...).

C ABI only appears to be simple in OSes that happen to be written in C.

Grated that is the case nowadays with most being UNIX clones, besides Windows and mainframes, but it wasn't always like that.

I remember the pain of trying to mix multiple C compilers back in the 90's.
I think this one is a bit more telling:

https://trends.google.com/trends/explore?date=all&geo=NG&q=b...

(it's for Nigeria)

And the global map for since 2004:

https://trends.google.com/trends/explore?date=all&q=bitcoin

With the search term being most popular in Nigeria.
Essentially the house should function regardless if the Internet is connected or some random server is reachable.
It's not a "private company" thought is it? Not only is it "Publicly Held", but it's also a "Corporation" which historically meant it has certain rules it has to operate by. Not withstanding, of course, that such rules have been relaxed a lot in the last 40 years to appease big businesses, like Google.
Good. If I have to pay capital gains on normal stocks I don’t see why crypto traders shouldn’t have to also.
Erlang Garbage Collector – update
Some discussion about day 2 in yesterday's thread about day one: https://news.ycombinator.com/item?id=15811229

To cross-pollinate further, I found yesterdays presentation about Esperanto particularly fascinating (or to be fair, close my own interests, not that it's objectively better or worse than something else). So let me speculate a bit.

It'll be at least a year or so before they have something out in the market. Given that NVidia Volta claims 7 TFlops/s DP, lets say Esperanto is targeting 16 TFlops/s in order to have a competitive product at launch. Further, lets guess a target clock of 2 GHz. To reach that performance they would thus need 16e12/2e9/2 = 4000 DP FP execution units (the extra divisor of 2 due to FMA being counted as 2 flops). So that would match pretty well with their 4096 minion cores having 1 DP FP unit each. Now, they also say the minion cores have the RISC-V vector extension rather than being scalar cores. And the V extension says that the minimum vector length is 4. Implying that executing an vector arithmetic instruction takes up at least 4 (consecutive) issue slots, a bit like old-school pipelined vector supercomputers (think: Cray 1). Meaning that the primary purpose of the vectors is not to get wider execution width, but to amortize instruction execution overhead (fetch, decode, etc.) and to drive memory level parallelism, like in old-school vector supercomputers.

Further, it is mentioned that each minion core has several hw threads. For the sake of argument, lets make that 4. Now, lets look at the aggregate size of the vector register files. So each VRF has 32 registers. Since they claim to be targeting HPC as well, and not only ML/AI, lets assume that means they support double precision FP. Meaning that the maximum vector element size is 64 bits (8 bytes). And as mentioned before, the maximum vector length must be at least 4. Thus, at a minimum, each VRF is 32 * 4 * 8 = 1kB. So the total size of the register file with 4096 minions and 4 hw threads/minion is at least 4096 * 4 * 1kB = 16 MB. Or if the vector length is 8, 32 MB. Or 8 hw threads/minion, also 32 MB. Or vector length 8, 8 hw threads => 64 MB. Which already starts to be a pretty huge number, even on 7 nm. So I wouldn't be surprised if the vector units bypass the caches and go directly to memory? Oh, and you'll need absolutely gargantuan memory BW to feed this thing.

And how is this thing supposed to be programmed? Vectorizing compilers, obviously, but what then? OpenMP? Message passing between the 16 fat cores, and each fat core running the main thread, farming out to OpenMP threads running on 4096/16=256 minion cores?

Anyone care to confirm, deny, or at least poke holes in the argument above?