skysight-inc/HackerNews huggingface dataset:
Well, this cert is OV (IV?) so it's always going to be at least semi-manual because we know the structures to truly automate OV issuance are flaky at best. The fact a DigiCert person looked at this application is unsurprising.

The problem starts when that person gets to do crazy things like pick a Public Suffix as the thing being validated and gets worse when the "proof of control" is only barely related to the thing claimed. I await more from DigiCert on what was supposed to be going on here and how they'll improve.

I don't buy the theory that DNS is worse than WHOIS. Even the WHOIS proponents generally try to fudge this by trying to compare RDAP, because the security considerations for WHOIS come down to "cross your fingers".

In theory RDAP becomes mandatory (for the gTLDs) later this year. In practice we know the pilot programme was not exactly a roaring success and the registries have decided they'd rather the entire mechanism went away.

But we'll see, I care mostly about Prevention of Future Harm, if we prevent Future Harm by going to RDAP successfully that's fine for me too.
I think at the time - 1999(?) (soon after rackspace had started up) we were at a $500/month server.

And... they made a mistake early on. We'd requested a new machine, but someone had done the ticket wrong, and took the old one offline for an upgrade (instead of just adding a new machine to the account). They were minutes away from wiping it when I called - if I'd had an automated attendant, we would have lost everything on there, but humans intervened to stop them in time and get it back online. "Great service!" - except they'd made the mistake in the first place...
I call it the yahoo fenomena.

buy a lot of stock on number one (google, or Amazon in this case), then use your money or previous position on number two or three company in the same market to influence the board to drive the company value to the ground. now you can claim loss on the secondary position while creating a bigger monopolistic market for your main position for the long run.
Unlikely, since RN isn’t executed in a browser.
There are constructions that provide forward secrecy when both the client and server follow them. This is what TLS aims to provide.

If the server doesn't faithfully implement the protocol, of course it will not provide the expected security guarantees. But then it isn't the committee who is lying, it's the server by claiming to implement TLS and then not.
Yes, I'm bothered, but then again I'm bothered by pretty much the entire cloud trend. Its not a matter of if shit hits the fan; the question is when. We recently saw one of the many examples of this with Facebook. When is enough enough?

The example of this application seems just like it wouldn't be too hard to implement with proper accounting (and tagging) of expenses.

You can easily self-host Firefly III in Docker [1], or use GNUCash [2].

I'm going to experiment with the former in the next months.

[1] https://hub.docker.com/r/jc5x/firefly-iii

[2] https://www.gnucash.org/
Eventually, these policies will eliminate their ability to innovate and advance.
Thank goodness someone has chimed in with this. The original article has no mention of UX.

UI developers are getting marched out the door at a well known publisher right now, their services no longer needed. UX is a different story with this mystery publisher, they now get to call a lot of the shots.

There is a bigger discussion to be had regarding the whole visual design process. In 2006 when you could have your navigation in any corner of the screen with any design for the search icon it made sense to have UI designers add their special flourishes. Now we know where the navigation goes and what the icon is for search, that has all been settled. User experience still needs some people to take care of it as we can't leave that up to the programmers, can we?
ParaView multi-platform data analysis and visualization application based on VTK
I credit Manning for my tech career. I read read Jon skeet c# and Fogus clojure books put me on another level.
> I don't think it changes until the next generation comes.

The next generation of professors.
Pedigree and social class aren't economic class. Just because you won't be let into someone's club despite having considerable wealth does not mean the two of you are in different economic classes.
Security audit finds vulnerabilities across Bitcoin forks
A Systematic Impact Study for Fuzzer-Found Compiler Bugs
Yes, SQL on blockchain is append-only. The SQLChain blocks can only be accessed with a granted private key. I think all public chains are facing the abuse problem.
Simpson's Paradox is one of the many phenomena that shows how different applied ML is from regular software engineering. Another one is feedback loops between decomposed subproblems.

In ML encapsulation, shielding away of inner details often does not work. One needs to know what is happening on the other side of the abstraction boundary. This is a problem for managers and PM coning to ML from a purely software engineering background. They are used to encapsulation and decomposition serving them well and they expect the same.
Just like with any of these data grabbing cloud services I don't believe anyone is in the target market, long term speaking. You just learned your lesson sooner rather than later.
You're hopefully kidding when you say that the costs of the hardware is not an issue. Server grade hardware costs an arm.

600 servers at $10k each, that's $6M upfront. Then another $6M within 3-5 years to renew them.

Of course in that example you'd pay someone, even multiple people in fact, to make things more efficient.
I use one, instead of a car. (Driving a car just seems lazy to me. But I do it sometimes, when I'm feeling lazy or when I have to transport my kids.)

Before 2010 or so, I used a traditional manual bike. But today, a non-powered bike seems to me like using a slow, spinning platter magnetic disk instead of an SSD. Or using a desk without a motor to adjust the height on demand. Or a kerosene lamp instead of LED lighting.

Unless you consider your bike to be only a mechanism to get exercise, in which case inefficiency is desired, the only valid argument against an e-bike in my mind is the cost. And that's valid, in some circumstances.

But you can get every bit as much of a workout on an e-bike -- it's just that you will be going faster. Alternatively, if you don't need a workout right now, you can go about as fast as a non-powered bike with minimal effort.

Where I live in Tokyo, it's 45 minutes to the office by train (due to the walking to/from stations, 35 minutes by 1970s bicyle, and 20 minutes on my battery-powered pedal-assist BESV LX-1.
I mean, at the end of the day it has to be, right? In a world where everyone runs ACME, aren't there still human operators who can deploy bug fixes when Google says "Yo, why isn't our cert renewing"? Or is the plan that there's no recourse to humans, and we're all watched over by robot CAs of loving grace?
That's a red herring. Debian's problems with such documentation were largely the licences that it comes under, often requiring doco to be separately packaged so that it could be placed in the "non-free" section. It is not omitted by default because it is doco. It is omitted by default because the Debian people do not classify it as free content.
Computer engineering is not substantially newer than aerospace engineering.
Night-vision ‘super-mice’ created using light-converting nanoparticles
What Is Your Goal?
I am not good at setting goals. And I feel that it is melancholic.
What are the goals you are feeling uplifting?
Great insight.

A few question:

1. So if an ideas guy does some basic prototyping and shows that the idea works, does it make the idea "real" ?

Or does it really require 100% execution to be considered a serious contributor ?

2. >> what I believe most stealth startups/labs are really trying to protect, the validation of a specific idea,

Could you please expand on that ?

3. What about doing serious research - finding in-depth and reliable knowledge, to show why the idea is likely to work ? Or similarly doing research to find cheap/easy ways to test the idea ?

I'm asking as someone who is strong in research skills, but relatively weak in executing.
If you think that design/redesign is a waste of time, a good exercise would be to try and understand why fashion constantly evolves, ie why you no longer see people in bellbottoms and corsets.
this is the new "sponsor a child in the third world" scam? their only actual actions I could find on the site is to publish business self regulation?

I'd love to be wrong...
With RDBMS the integrity constraints can make gradually changes to large data sets more difficult. It often means a lot of downtime or the code must tolerate old and new structures for a while. With NoSQL the constraints are probably already in the application layer.
We did have quick turnaround - we were running everything on Xen VMs on LLVM internally, it was trivial to throw up new instances, snapshot them, etc. Our demands weren’t changing that quickly, so there wasn’t that much need to bring on new hardware all the time. A small number of dual socket machines can go a very long way these days. We didn’t have the same kind of multi-DC redundancy that AWS can give you, no, but over those years, many AWS based services were down multiple times due to being focused in Virginia, so it’s not an automatic win for AWS. The amount of time we would have spent getting that running and maintaining automatic multi-zone failover on AWS likely would have swamped the benefits for us, though, and I think are usually overkill for a small company. YMMV.
Thanks Bart!

I know for PostgresCompare a lot of its utility is in finding the differences. Providing clarity into what has changed while one was building a feature.

A lot of users still write the SQL themselves. They let the tool figure out the easy stuff, get the dependencies correct, and they make a few edits here or there.
I think that's a deliberately uncharitable interpretation.

If you're admitting there are problems in the previous redesign (and you are), then why not fix those pieces rather than redesigning the colors, icons, and entire rest of the interface?

It's not so different from an engineer who rewrites a whole service because it has 3 bugs. Almost never worth.
Ask HN: Literature about the history of online communities?
Is there any in-depth literature about the history of online communities?

Which goes through how the first instant-messengers emerged/how Imageboards came to existence and the influence of communities onto each other.

Anything academic on this topic?
Redesigns usually improve the "wow"-factor - great for sales demos. They are often detrimental to actual use of N hours per week.
Interesting take. I'd ordinarily be suspicious of similar offloading of work.

But in this case, my impression was that each brand owner would be the most knowledgeable & motivated agent in the ecosystem to seek & deactivate the counterfeiters.

My biggest concern was that it could empower the brands to abuse the opportunity, and shut down competitors with false allegations of counterfeiting, like the fake DMCA notices for YouTube videos.

At least Amazon is saying that they'll be monitoring for this; we'll see how they do.

I also thought one of the most important items was buried in the text, a system to send special barcodes identifying product. I'm guessing it would be like a pre-authorization for shipments, so Brand X would send Amazon a database list of IDs tagged to production runs, and they'd send matching barcodes on the actual shipped product. Anything not matching the ID scheme would get rejected. Distributors could send product in with the IDs, and they'd match, counterfeiters would fail to match, even if they knew of the IDs in general. Seems good to me.
Please reach out to me directly with a CV - alastair@deepscope.co.uk
I did an Ask HN[0] on a related topic almost a year ago. I think the OP is right that thinking clearly about data relationships helps in the design of an app, but things do change. Which is why people give up and use Mongo.

[0]: https://news.ycombinator.com/item?id=16871789
>During the more than 30 years it was cut off from the Pearl River Delta it took in over a million refugees.

Many of those refugees came from the area, and chose to leave because they had wealth or experience. Meanwhile, US allied powers embargoed China while still providing assistance to Hong Kong. These things had far too great of an impact to really credit the trade policy.
What concurrency model do you prefer? Seems like it’s easy enough to opt into a share-nothing model in Go, and this is generally what I do unless I have performance concerns (and as a consequence, I very rarely see concurrency bugs). I’m also not sure how much static analysis a la Rust could help the problem without accepting Rust levels of productivity.
Meetanshi | Magento Developers | Bhavnagar, Gujarat, India | Full Time | ONSITE | https://meetanshi.com

Meetanshi is an eCommerce Development Agency specializing in Magento. We develop Magento Extensions and provide Development Services.

Visit https://meetanshi.com/career if you're interested. No recruiters, please.
Queued jobs which can auto-retry will help, of they can detect incompatible changes in the data structure. Of course that'll produce some false positives in the error logs. But it's a small price to pay IMO
> Cool, cool. To preface this comment, I'm a user experience designer, and I've been doing web software development and design for over 20 years.

Cool, cool. To preface this comment, I'm a guy who owns a computer and uses software.

Most GUI redesigns I've seen in the past 10 years make the interface prettier, but LESS usable. The new design usually incoroporates three categories of changes:

1. Lists of items are rendered in a larger font with more spacing between items, leading to lower information density, thus requiring more scrolling. (For bonus points, often a window that has a scrollable area isn't resizable, so you're stuck with whatever arbitrary viewport size the designer decided was large enough.)

2. Controls that used to always be visible are now hidden until you hover or click the right spot. This is done to reduce "clutter", as though controls are somehow graffiti.

3. A bunch of convenient shortcuts enjoyed by long-time power users weren't reimplimented in the new design, because the designer didn't know about them, or simply didn't think they mattered.

I have a WordPress blog. WordPress recently overhauled their entire editing UI, and I hate it. When I started the blog several years ago, I was able to figure out how to use WordPress by exploring the UI. The new UI is an extreme example of #2; when you go to write a new post, the page is entirely blank. You have to click somewhere to get a text cursor, and there isn't even a visually delineated text area before you do so. There are a couple of features I had to hunt around for, and I wouldn't have even known those features existed if I hadn't learned them from the old UI, which presented them front and center.

My company uses JIRA for bug tracking. They switched to a new GUI a while back, and I hate it. It's harder to find things that used to be presented front and center. And as an example of #3: It used to be possible to just type an issue number like "392" in the search box, hit Enter, and be brought immediately to that issue page. Not anymore; if you do that quickly, you get a "no results found" page. If you type the number and then wait a couple of seconds, you get a list of search results, which you can then click on. Pressing Enter then takes you to the first one, but often that is NOT issue #392, it's just some issue that happens to have the text "392" somewhere in it. So you have to eyeball the search results, and then click the right one. The old way was more convenient. Fortunately, I eventually found the preference to switch back to the old GUI, which they helpfully give you because they apparently realize that the new GUI sucks. (I don't know offhand if it reverts the search behavior, because I've already changed my habits to not use it anymore.)
Because companies in some sectors are required by law to inspect all traffic, while TLS 1.3 doesn’t prevent it in principle it makes it unfeasible to do so in practice given the number of sessions created in a large organization.

I work for such organization which actually took a fairly reasonable stance and told BOA to piss off when they asked us to join them in petitioning the IETF to make exemptions to PFS in TLS 1.3.

Our current stance is that we dissallow it internally until the vendors that provide us with the DPI and web traffic inspection solutions will have full scalable support for TLS 1.3 or until the regulation would change in a way that would no longer require us to capture, store and be able to decrypt all user traffic within the network.
Agree 3/3
Ask HN: Why Is This Flagged?
https://news.ycombinator.com/item?id=17468033

This is a neutral, academic article which satisfies everything the HN guidelines solicit.

Is there a hidden rule to not talk about such topics on HN?
I think the 80/20 rule applies when it comes to mature products. 20% of redesign is useful and make products better. 80% are neutral at best, and breaking at worst.

If it’s not broken, don’t fix it.

https://www.alexkras.com/death-by-redesign/
> So annual rank/stack, bell curve, fire x%. Right after performance reviews, and right before any annual raises.

Except we hadn't completed ours yet, this event was planned for several months due to leadership expecting double-digit turnover after the performance review period, about 10% of leadership in a single product got wind of it coming and has already settled in at new companies, multiple principals and architects with spotless records were let go from a single product along with nearly 80% of its other headcount, and layoffs have been quietly happening without attention being drawn (a few a week). We were also told at an Open Book that Apollo had to intervene for Rackspace to afford contracted bonus structure this year, as Rackspace literally did not have cash on hand to meet targets.

Other than all that, though, astute insight and analysis. You're right, just typical fiscal year slog. (PR is literally saying "we're a stable company, promise" in statements.)
User private OAuth token is stored in the cookie. Forum clients can share the same token and also use their own token. Same DSN(database serial num) indicates the same forum.
The OpenSSL strategy seems to be to try to leapfrog LibreSSL in terms of version numbers (which already has released a 2.x branch, hence their 3.x versioning), and revise their API, but still have considerable complexity.

The LibreSSL approach was to write a new library and API, libtls, which does away with the substantial configuration complexity in applications: https://man.openbsd.org/tls_init.3

I'd argue that LibreSSL's is the better approach.
This is hilarious for the sheer irony of a fix to one compliance issue creating a different compliance issue.
Meditations on Moloch undoubtedly deserves to make the list: https://slatestarcodex.com/2014/07/30/meditations-on-moloch/
We should avoid having human agents making these determinations because they're very bad at it. Play to human strengths. The human agent working around the fact that you keep saying "Apache" but you're actually clearly running IIS from your description is where humans are good, training an AI system to figure this out would be really hard. Figuring out that .in-addr.arpa is a Public Suffix and therefore you cannot possibly prove control over it from a Web PKI point of view is just trivial string matching and perfectly suited to a machine.

We already have had incidents where a CA mistakenly took proof of control of one-name.example.com as sufficient proof of control of example.com itself and it's part of why Facebook freaked out before we had mandatory CAA (and before Facebook wrote themselves CAA records) because a sub-contractor got themselves a certificate Facebook didn't intend to exist. So no more of that please.
TD Bank Group | Toronto, ON, Canada | DevOps Engineer / Software Engineer | Full Time | ONSITE Downtown Toronto.

We have multiple software engineering openings on my team at all seniority levels (co-op to senior). We're looking for highly-technical, hands-on software engineers who can wear multiple hats in an agile team within our Enterprise Information Management group. We do DevOps & Software Development to better manage our Big Data Lake and advanced analytics platform.

We run a cluster with thousands of cores, petabytes of data and terabytes of RAM. We have a backlog of interesting work that requires critical thinking and creativity. We're all about improving the way we work, leading by example and reducing friction.

Why TD? We offer a great work life balance, and the opportunity to work in a dedicated big data team of over 100 engineers.

Qualities

* Self-starter, Go-getter
* Bias for default
* Great communication skills

Experience

* Solid experience with Linux, Java and the JVM
* Cloudera and Elastic (ELK) stacks
* Test automation tools and techniques
* Configuration management
* DevOps practices
* CI/CD
* TDD
* Setting up VMs, environments, docker
* Front-end angular skills an asset

To reply, use email address in my profile.
Why is it better? What is the reason it's preferred?
It depends on what you care about more: certs being issued validly, or certs being issued? Processes can be put in place so that humans can fix problems when they find them, but also prevent a human from doing the wrong thing. Autonomation instead of automation. https://en.wikipedia.org/wiki/Autonomation
I'm not sure. I think this hierarchical nonsense is a German thing. I've worked for IBM and it was a different experience. Still dysfunctional, but in a different way. I never felt at IBM that I was not heard. I also see how Microsoft fixed itself and turned itself around which is an admirable achievement.
There's so much this article misses:
- most large companies a/b test their redesigns. If your company isn't big enough (for the tools or traffic needed to a/b test), then yeah, you're left to judgment calls. Really good a/b tests will actually capture things like "existing users initially hate it but eventually end up using the product more"
- a lot of UI redesigns are driven by effect on new users, which might be more important to the company. Think about it, if you're already using the product, you probably don't care what it looks like too much (and might be annoyed if it changes). For new users, anesthetics leave a lasting first impression.

Yes, at many small companies without data, redesigns can be a waste of time and even harmful. But that doesn't mean they should always be avoided.
I’ve also seen ones with hydrogen placed twice, above lithium and above fluorine.

In reactions hydrogen likes to gain an electron like the halogens rather than lose one like the alkali metals.
I know this will never happen, but it would be interesting to see the percentage of Reddit users who took the time to opt out of the new "improved" interface. I suspect that number is small, because most people have learned to just quietly sigh and accept random UI changes, but larger than the Reddit UI team would care to admit.
I'm not confusing anything. Whether people can complete tasks they need to perform is a major influence on how they feel about a design. And where they prefer an approach that makes the task harder rather than easier, that is still valuable information, and the appropriate response can easily be to give them the approach they prefer.

But I'm going to disagree that an hour is enough to reveal any advantages and disadvantages that may be present.
Neurosexism: The myth that men and women have different brains
Show HN: Hacker Hiring Hunt
> The Kernel Programming Language

Because no one uses `kernel` for anything already.

I mean, holy fucking hell, if you're creating a programming language, choose a name that you can fucking search for.