skysight-inc/HackerNews huggingface dataset:
That's an excellent history and summary of the spam situation. It adds a few pieces I'm not familiar with (I'd gotten out of the fight by the late 2000s), but validates a few approaches I've also considered.

Reputation is a crucial element, and ultimately the crucial element in large networked systems.

I'd make one correction about new accounts: if a new entity (email address, domain, IP) starts peering, SMTP actually offers a really good options for limiting: a non-permanent rejection. If new traffic shows up from an unknown source, you can simply tell it "not right now". In theory, the sending server is supposed to follow a back-off protocol, with a few minutes delay initially. This gives time to start building up reputations through other means. And failure to follow the retry schedule is a strong sign of misbehavior itself. Teergrubing uses this mechanism.

The idea of vouched reputations is another one. If all peers or senders need to have someone vouch for them, then even new agents can engage in email.

The one resource all clients, regardless of compute power, access uniformly, is time. A protocol mandating a specific time interval (say, by requesting a specific future NIST randomness server value), might be interesting.

Another element that's helpful to the spam-fighters is that most communications patterns follow a strong frequency curve -- most comms are well-established, whilst less-frequent comms are often spam. Whitelisting based on established comms (and overriding those with specific blacklists), and treating all novel comms as suspect until some token of merit is received (a vouch, time delay, earned reputation elsewhere) should help.

The idea of multiple levels of encryption, with an outer envelope which an email server can read, with an inner envelope for the actual recipient, is another option. Here trust information can be placed in the outer envelope, but contents are protected. Possibly a protocol might request contents must be readable by the server for certain classes of sender.
What makes for simple? I really need to understand this. I implemented fork many years ago for a university operating system and nothing about either the implementation nor the usage is simple. I use fork on a daily basis and the POSIX version of it is insanely complex for everybody involved.
Seriously though, this is why I'm afraid to use something like Firebase now.
Ask HN: What terminal you use? iTerm or Native Terminal? Why?
Show HN: Using Redux with PureScript
I took one look at "baasil.io" and saw the typical landing page with a "Plans" link at the top and questioned why anyone would want to take a dependency on this. If there is some OSS project behind the plan-based charade then that's fine.

"Also Baasil.io is essentially just a control panel/dashboard (Rancher-as-a-service), you can quit Baasil.io at any time and switch to your own hosted Rancher instance and you don't have to change any of your application code or change infrastructure providers."

But so you can with AWS and Azure - especially with their Docker offerings. So I'm not sure what problem baasil.io actually solves? If anything it just adds to the list of dependencies and points of failure.
It also effects your ability to find work. Being laid off can be completely out of your hands and isn't always something that works against you.
An acquittance who worked at Cisco mentioned a month back or so that it was in trouble. In fact, the person mentioned switching over to another company for the same reason.

This news suggests that those apprehensions were not unfounded.
Plus visitors != requests.

I have 200k visitors per month generating 8m page views and about 50m hits on the servers (with CDNs taking another few hundred million hits).

These all peak during the UK weekdays and wind down at nights and weekends.

Divisions over time aren't going to work, but neither is translating visitors into requests, especially as it's only the page views that have a beyond trivial computation cost.
India messaging app Hike raises $175m from Tencent and Foxconn
Not sure if it's the case here. But what works really well for us is queues with at-least-once guarantee. (For payment services you might need an additional check to guarantee exactly one execution.) I think you can find this queue offered by most providers.
I would love to read some accessible information on this - how the models can be so trustworthy. I sort of reluctantly accept climate change, and I generally support environmentally positive politics, for a host of reasons. But when I see graphs like this[1] from the IPCC I can't help but think that predicting 100 years in the future from 100 years of data is never going to be very reliable. What kind of validation have these models had? Surely they are not just fitted to the past 100 years?

1: https://www.ipcc.ch/publications_and_data/ar4/wg1/en/figure-...
While you overall point is correct, it's still likely not going to be a lot. It's highly unlikely that it's 40k per second.
New meetup site
MySpace had a record label - but they also got their start in music.

MySpace started out as a way for bands in LA to post gigs.

So their initial user-base/NDA was musicians, LA culture.

Facebook was a little more academic/ivy league.

It's hard to change one's genes :)
Yeah, sure. I always think of spawn as a plain wrapper exec/fork, hence why I wrote it like that, but you are right correcting me.
Tech Giants Gobble Startups in an Antitrust Blind Spot
Looks like a nice polished interface.
I am wondering what is Pendulum's policy on invalid input. The examples illustrate the inconsistent approach to invalid inputs:

In some cases it guesses what you meant:

>>> pendulum.create(2013, 3, 31, 2, 30, 0, 0, 'Europe/Paris')
'2013-03-31T03:30:00+02:00' # 2:30 does not exist (Skipped time)

In other cases, it raises exceptions:

pendulum.parse('2016-06-31')
# ValueError: day is out of range for month
Once you finish taking my Scaling Docker on AWS course, you'll have access to a magic command that deploys your app and you're free to optionally run migrations.

http://nickjanetakis.com/courses/scaling-docker-on-aws

It covers using RDS, ElastiCache and also handles load balancing your app + much more.
I will tell you what they do - they do freakin care, that's it!
Why would a chrome plugin affect a totally separate application?
We at Boxfuse (https://boxfuse.com) provide the same ease of deployment for running Java apps (as well as Go and Node.js ones) on AWS. All you need to type is literally: boxfuse run myapp-1.0.jar -env=prod

And you automatically get things like auto-scaling, database auto-provisioning. easy debugging and more.

Disclaimer: I'm Boxfuse's founder and CEO
Honestly, I've found (only in my experience, not trying to make a blanket statement) that people who get easily annoyed aren't very easy to work with. The question then becomes whether their technical skills are good enough to disregard their lack of people skills. Sometimes, it's not worth it and you try to move on to a different situation if that person is a mainstay for the team. I've found that on really good teams, these types of people are mostly non-existent.

I don't doubt that there are teams out there filled with these types of people who magically understand each other and are always on the same page as if they had some sort of hive mind. I've heard of them, and it gets described as "good chemistry". I've just never experienced one of those teams myself where everyone can read the minds of other team members. For more average people, communication is a really important skill, and that includes not being annoyed by simple questions. Mind you, I can easily be annoyed by simple questions too. It's not like I'm good at this stuff either.
It's "NASA", BBC. Not "Nasa".
> RFC 3339 timestamps appear in email

Where exactly in email to do they appear? In the header, it's been my experience they all conform to the RFC 2822 spec, and could be parsed with the standard library function email.utils.parsedate_tz[1].

[1] https://docs.python.org/2/library/email.util.html#email.util...
It's a single service. It just sites between us and our PSPs. That way no other system needs to worry about integrating directly with the PSPs.
There is no point in making any 'case' about climate, because it is not a matter which can be resolved by argument. Some people believe in global warming, others don't. That's all there is to it.

It is not a matter of science. Why not? Because it is not accepted as a matter of science, by those who don't think it is a matter of science. It is not a matter of evidence. Why not? Because there is no universally accepted evidence. Attitudes to global warming are irreducible essential beliefs, and therefore not amenable to any form of argument.
Oh yes here we go:

https://theconversation.com/one-nation-climate-denial-and-th...
hmm there are 7 billion people in the world, according to you 1.9 billion use Antroid or iOS.

This means there are ~5 billion that do not, thus basic math concludes that this new app is not even for the majority of people and far far far far far from the "everyone" claimed.
https://news.ycombinator.com/item?id=12293308
Ah, hiring before the formal firing. Efficient.
Da single a coppia
Then you should read what POSIX says about pthreads, regarding mandatory and optional API support, specially the implementation semantics and UB.

For example, what happens to the interactions of signal handlers semantics and thread scheduling.

Or what happens to the threads when the process does a fork().
You've just hurt "that woman" by writing this. Maybe you should be "removed" from this community?
They do, yes. Rounded up to the nearest 100ms, scaled for chosen RAM capacity: https://aws.amazon.com/lambda/pricing/ Note that this doesn't measure actual RAM use, although they do display it after lambda runs.

Data traffic is already measured and priced accordingly in AWS so that's not something new for Lambda.
The original x86 was pretty unriscy with the registers not being general purpose. The addressing modes to this day are still very CISCy
How is rancher related?
>It does contain theory, but it doesn't contain psychology or anything "pop". It's anthropology and evolutionary biology

At the very pop level. No anthropologist or biologist would make as crude presentations of the relevant arguments -- or even think their interaction with culture is some solved problem and it's 100% "evolution" at play.

>My views also aren't popular among Western people, except those who like to scientifically pick apart the origins of beloved social traditions. This makes most people uncomfortable.

No, it's mostly the crude early 20th century scientism and basic oversight of empirical data.

>The fact that you're appealing to cultural folklore about dating at all should cause you to re-consider your argument.

Well, your whole premise was that evolution trumps "cultural folklore" and customs, to which the parent's reference is completely justified as a counter-example.
> I wish companies, if possible, throttled layoffs a bit more instead of large chunks like this, but that is unlikely as the board/CEOs are looking for a stock uptick when they do and don't want to drag it out to affect the market value (translation: their own pay / stock value/price).

Have you ever actually been part of a company that did layoffs in chunks like you're suggesting? Experiencing that type of protracted wave of layoffs is not fun at all. In fact, it was down right miserable. Going to work each day with the threat of layoff looming over your head is an incredibly stressful experience.

You might consider that there is more at play than just a few executives getting greedy about dollars.
Debates like this make me realize we as a species have little hope.

Brexit, Trump, Climate Change just shows he who shouts loudest and repeats the most lies gets attention and support.
Care sharing your progress with the podcast discovery app? I'm a cofounder of Podigee which is a podcast hosting service. Maybe we can exchange know-how, find some synergies or even join forces on certain topics. Feel free to drop me a line at mati@podigee.com
This is more or less where I'm at as well, except my BS detector is still going off.

> it seems reasonable to assume it is correct and take action to reduce anyway

I'm not sure there's any reason here. There's no empirical evidence that any palatable recourse will actually stop or reverse global warming. It's good science (as far as I can tell) up until we get the the "What now?" question.

Someone having good proof of a problem does not make them qualified to rearrange entire industries, slow down global growth (when we already have widespread stagnation and growing unrest in the West), and spend trillions and trillions of dollars on things that might not even help.

The inability to predict climate at a useful granularity certainly doesn't help. It means attempts to address greenhouse gas levels won't objectively succeed or fail.

The fact that AGW proponents do not acknowledge these difficulties is what sets off my BS detector.
Or just put your app(s) into containers and run them through docker compose on a single VPS. That bypasses about 99% of the things listed in this article.

You can still easily set things up so it's a git based deploy which is hands free after the initial push.

Now you have a single $5-10/month server that runs your app's stack without a big fuss. Of course it's not "web scale" with massive resiliency but when you're just starting out, 1 server instance is totally fine and exactly what you want.

I've ran many projects for years on 1 server that did "business mission critical" tasks like accepting payments, etc..
Look, if you're a one man shop doing a small project — do LAMP. Do perl. Do cgi. Do whatever you're comfortable with; if you try to switch to the latest silver bullet tech, you'll just get disappointed.

But if you're a CTO with a startup with 10+ server-side developers and plan to hire at least as much in near future, suddenly all these dockers and microservices actually make sense.

So, unless you'll start conversations with _who_ you are and _what problem_ are you trying to solve, of course the other side will seem stupid.
Where do I fall in? I believe in climate change. I don't believe climate change is the result of only humans. And if climate change turns out to be bullshit, I'm glad it's being a driver for alternative energy sources, better production of goods, more environmentally friendly packaging, etc. I just believe the cause being humans is over hyped and the fact that we renamed it from global warming to climate change because the models didn't support global warming....
These 'concerns' are all the 'skeptics' are left with after decades of outright nonsense has been overturned.

Climate science skepticism is akin to creationism at this point.
I've spun up a lot of kubernetes clusters to test it out. A few months ago I also tested out Flynn, Deis, Deis Workflow, Openstack, and a lot of other options. I still haven't found a simple bootstrap script that gets everything set up on AWS and lets me simply deploy my application. And it's true that storage still seems to be an unsolved problem with kubernetes.

Heroku is great, and free for small services. On the other hand, a highly-available kubernetes cluster is going to set you back at least $100 per month, which is just too much for small startups and side projects before they take off.

I think I'm going to forget everything and head towards http://serverless.com/. No Heroku, no Docker, no micro-services, no servers. Just everything running on AWS Lambda and DynamoDB. And everything static in S3 behind Cloudfront.

Or maybe just Firebase. But I really am tired of managing servers.
Would it be hard for a climate scientist to present the numerical evidence in something akin to a Jupyter notebook?

So, something that says

"Here's how we collected the data, and here it is"

"Here's some transformations on it"

"If we're right about xyz, this bunch of statistical tests will turn out like so..."

I tend to give the experts the benefit of the doubt, also on this issue. But everything I hear in the media is simply "consensus" vs "conspiracy".

I actually would like to understand how the data works, and how the models work.
Yeah! I have symlinks to some directories, but I don't necessarily want to sync _all_ files in those directories. I think we're probably the 1% use-case for this though. However, you'd think some dev over at Dropbox would add this feature to scratch his own itch...
This is counterproductive. All he's doing is legitimising the shill's position by debating him on TV.
> which I think does use a (mostly) binary wire protocol, at least when calling sprocs

Hmm. I'm used to invoking storedprocedures via "select mysproc(param1, param2, ...)" which still has to be formed into a string and then parsed on the DB side using the arbitrary-SQL parser (because there's no way for the DB to know a priori that it's not a "regular" query). Does SQL server have some special case binary protocol for invoking them directly?

> It also has a pretty good query optimizer - I've spent a lot of time trying to beat it with hand-tuned queries and only come up with something better about 50% of the time.

The query planner can usually run the best query possible with the indices that exist, sure. But you have to fit your calculation into this model of indices that are built on insert and everything else happening at query time. Or you go down the route of lazy materialized views that make use of other lazy materialized views, specifying indexing strategies... I mean I think you can ultimately express any data processing pipeline in a RDBMS if you try hard enough (though you have to use database-specific features that tend to be less-well supported by the ecosystem), but at some point it's easier to just have a first-class programming language that has access to the data, and write the code that you want to run.

> And there are a lot of tools for source controlling the DB scripting and testing everything. It's not hard to do unit test style runs that set up and tear down tables and DBs.

Up to a point. It's easy to end up with "unit" tests that take a second for each test, which mean it's not really practical to get good coverage of logic there.

In terms of source controlling and so on I guess the big problem is that you now have a distributed system written in two quite different technologies. So you've got to figure out a release and deployment process that handles both, and a lot of shops don't seem to bother. If you're already running a multi-language microservice architecture then this is probably a lot less of an issue.
You could also characterise it as a risk, whereby potential downsides are amplified by age.

Young voters will have to live with the consequences for most of their lives, while old voters don't have much time left.

Then again, you could argue older voters were altruistic and voting in the interests of the next generation.
I think it's more to do with a need rather than going straight just because you have enough people on a team. For instance, if you find that some of your processing/specific request handling can outperform better by using a different framework, programming language than the ones it's currently developed on, then you should definitely consider a microservice approach by decoupling that specific service/functionality from your current stack.
"Hi, my name is dokku, and I have no idea what you're talking about" :)

This rant sounds just like any rant from old dev mocking a new tech. "This is less efficient, this is too complicated, this can't be taken seriously, this won't last".

Creating a character obsessed with "this is dead" hardly dissimulate the obsession with "this won't work". Do whatever you please, we don't care. But don't mock others about what they please.

Passing through that, let's address the critics.

Microservices and docker are not necessarily tied. I write only monolithic apps, and use them with docker through dokku.

Etcd is a microservice problem, not a docker one.

You don't need coreos or kubernetes to use docker in production. You need them if you want massively scaled applications, just like you would have many servers running the same app with replication without docker. Most of us don't need that (and those who need it probably won't find it more complicated than what is needed to do that without docker).

If you don't want to manage servers, well, don't manage them. That's what cloud services are made for. But please tolerate some people love devops and not spending much direct money into infrastructure.
You’re reading the source for a talk I “published” at Nordic Ruby by speaking while presenting.

A friend video’d the presentation, which I published on YouTube: https://www.youtube.com/watch?v=8xjntzo-mYc

I published it again in another format on SpeakerDeck: https://speakerdeck.com/raganwald/optimism

The SpeakerDeck page includes a link to download it as a PDF.

And yet, someone discovered the source and decided to share that on HN. So be it. Any criticism you have to share with me is impersonal (I didn’t tell anyone to read the source), temporary, and obviously specific to this odd scenario.

FWIW, I’m chuffed, not chastised. It’s amazing to me that he source can be viewed with a web browser and is readable enough to be criticized. More apps should work this way.

So, I am not “defending” the format. I’m explaining it.

---

p.s. To be precise, this is the source I published:

https://raw.githubusercontent.com/raganwald/presentations/ma...

The link submitted to HN above is GitHub’s attempt to preview the source as best it knows how.
> likely millions+ will die within by end of this century

That's business as usual. The key is to realise that it won't look like climate change, it'll be superficially other things that look economic or political but are related to either fossil fuel economics or changing agricultural productivity. Several million dead or displaced? Already happening in the Syrian and Yemeni civil wars. Watch out for Egypt and Turkey possibly being next.

The US (and other countries) is seeing a rise in fire and flood due to exceptional weather conditions. Fort McMurray in Canada got both. The immediate casualties may not be high but the economic damage is lasting.

The sibling comment details that sea level rise won't be that bad globally, but it's important to realise that sea level and its rise is not as uniform as you'd expect. Florida is already seeing the rise coming up through its groundwater.
I ran into this exact problem recently in a multithreaded Python app and spent two days trying to figure out wtf was going on. The multiprocessing spawn startup mode that was added in 3.4 solves this for most use cases at the expense of a small performance hit. For 2.x you are SOL however.
"The Free Tier – My whole scheme doesn’t work without the free tier"

I know it will still be cheap, but I wonder the increase after the 1-year free tier period expires.
fair enough, but I posit X users started consuming this API when SOAP was prevalent and Y users started when ReST was prevalent and Y >> X. Furthermore, SOAP is hard to maintain these days because it's so ancient. i.e. the libraries are not new and/or actively maintained.

As such, I maintain SOAP should be gone for the good of the running system.
"Message passing as the fundamental operation of the OS is just an excercise in computer science masturbation. It may feel good, but you don't actually get anything DONE."
-- Linus Torvalds

He said that about micro-kernels but it may apply to micro-services as well.

Breaking things apart too much will only cause you grief.