jkeisling/hacker-news-corpus-2007-2022 huggingface dataset:
> 1) Apparently missing some messages from Hangouts users.

Shit, Hangouts itself is an unreliable message delivery system. [0]

At least once an month in both group chats and one-on-one chats I will get messages that seem out of context. Somewhere between many minutes and an hour later, the messages between the OOC one and the previous [1] message will silently appear. The "new" messages are inserted between the previous and OOC message, and bear timestamps that make it look as if they were never missing.

I've even had this happen while I had the conversation in question open in the damn client! It's super-fun to see ten or so "new" messages slide in between two already-delivered ones. :/

So, if you've ever wondering if you had a brain fart and overlooked an important message in Hangouts, you may very well have not!

[0] Yep, I'm using the latest software.

[1] Previous at the time I received the out of context message.
I dislike tools that claim to automatically generate your configuration for you. At Google, one of the worst abuses that anyone had to deal with was auto-generated configuration; a tool purported to deal with configuration for you, but really just blutrted a boilerplate mess into your directory, many of the properties and setting set by cargo-cult or overriding sane defaults with baked-in versions of the same. Facebook is proceeding down this path; There's a new tool that will do all of your service stuff for you! I look forward to what a boondoggle those services that use it will be.

There was a discussion I recently stumbled upon about init systems in containers. Many processes spawned lots of zombies! You need a full init! Well, no; If your process is forking new processes, it should probably wait for them. If it's forking other processes that fork other processes, and they're not cleaning up zombies when they're done, that is a bug in those processes. If all else fails, your root-level process should probably implement a simple init on it's own (a wait() on loop in the background, dumping wait objects into a LRU map that other processes can do an equivalent of waitpid() on). Or just run under bash.
Y Combinator and FriendFeed don't count, naturally. Somehow, they don't go in the "job" category the same way other jobs do.
How did past generations deal with the problem of idiot and/or old law enforcers misunderstanding technology? And as technology improves more quickly, are we at risk of having even more of a problem of disconnect between the technologically proficient and the (often confused) government bureaucrats?
Paul from Mailinator here.

We get, on average 15million emails a day with peaks much higher.

Definitely don't confuse that with ad revenue. No one ever ever said we get millions of users a day. Alexa or Quantcast can show you real user traffic - please consider ad revenue to be more realistically based off those numbers.

Simply emails. Pure spam. Once a user signs you up - you're getting spam for them - forever.

If you think of a dead-simple feature Mailinator doesn't have - its because we've probably tried it and backed it out from abuse.

With no exaggeration, we get one or more subpoena inquiries or subpoenas a month. On top of that, we have more code in anti-abuse systems than features. A sad reality but otherwise we'd be long gone. Despite claims of Mailinator being often banned, we go a long way to prevent people from using a feature like forwarding to automatically do an internet vote thousands of times. While that would be fun, we'd be banned in short order and that helps no one.

The most interesting point to me is that you need very strong infrastructure, servers and bandwidth to handle the load if you become popular. In other words, there are many many Mailinator copycats and historically, once a copycat reaches a certain level of popularity, the owners need to make a decision.

Paying for all that isn't easy. As far as I know - this is exactly what happened to the now defunct disposable email sites Pookmail, 2prong, and dodgeit.

Death by popularity without revenue.
Two points:

One: I haven't really used the aggregators in a while (and even then it's only Kayak). I use ITA matrix to find sane flights at good prices. The only downside is that for peak travel periods their availability data can be out of date, but I think that affects all the aggregators.

Two: For all the folks who complain about airlines being dinosaurs who can't innovate, here you have an example of a legacy carrier attempting to innovate against Sabre/Amadeus/TravelPort by bypassing the middlemen and going straight to the consumer-facing aggregators. True, it's not operational improvements, but it is an example of shaking up the way airlines do business.

interesting reading: http://en.wikipedia.org/wiki/List_of_global_distribution_sys...
Does anyone know if this stuff is really effective for SEO and PR?
Refined Hacker News

https://github.com/plibither8/refined-hacker-news
Discord is neither decentralized nor censorship resistant. Discord (the company) has full control over what is allowed to be discussed on there.
> Hospitals don't let uninsured people die and insuring people doesn't magically save their lives.

Not sure where you're getting this. A quick Google Scholar or PubMed search shows a consensus that mortality rate is significantly higher for uninsured than for insured. [1, 2, 3]

[1] e.g. http://jpubhealth.oxfordjournals.org/content/32/2/236.short -- On multivariate analysis, uninsured compared with insured patients had an increased mortality risk (odds ratio: 1.60, 95% CI: 1.45–1.76). The excess mortality in uninsured children in the US was 37.8%, or 16 787, of the 38 649 deaths over the 18 period of the study. Children who were hospitalized without insurance have significantly increased all-cause in-hospital mortality as compared with children who present with insurance.

[2] e.g. http://journals.lww.com/jtrauma/Abstract/2012/11000/Undiagno... -- Undiagnosed preexisting comorbidities play a crucial role in determining outcomes following trauma. Diagnosis of medical comorbidities may be a marker of access to health care and may be associated with treatment, which may explain the gap in mortality rates between insured and uninsured trauma patients.

[3] e.g. https://www.sciencedirect.com/science/article/pii/S000296101... -- A total of 1,203,243 patients were analyzed, with a mortality rate of 3.7%. The death rate was significantly higher in penetrating trauma patients versus blunt trauma patients (7.9% vs 3.0%; P < .001), and higher in the uninsured (5.3% vs 3.2%; P < .001). On multivariate analysis, uninsured patients had an increased odds of death than insured patients, in both penetrating and blunt trauma patients.
It's unfortunate to see that the product uses animal-based foods, and eggs at that. Something like Soylent should in my opinion be vegan (for the environment and the animals). If I recall correctly, Soylent was pretty close to vegan.
2000 calories. We don't really know how bulk pricing will work out once we are in production, our current costs are retail.
This isn't quite accurate. It can't be easily disabled on most laptops. The way to disable it on Macs is extremely sophisticated, and no malware currently does that, except maybe NSA malware.

You still shouldn't really trust it, but the situation is not how you're making it sound.
> What makes money for the bank is the difference of interest rate between money they buy and money they sell.

But they do not have to buy the same quantity of money as to what they are selling. When making a loan money is created out of thin air.
Well all three points are big red flags in my opinion I would also move on
Sadly it become a common occurrence for me lately to be working on researching problems and google giving me tons of results that only match a single word of my queries
Java is the #1 programming language in the world, proven again!
Your comment made me think of a personal anecdote. File it under "Why I love living in Silicon Valley".

Our neighborhood blocked off the street for a Fourth of July picnic a few years ago. Sitting in a lawn chair talking to a long-retired neighbor over a beer, we got to talking about old analog TV standards. (We are both hams, so conversation tended to turn to radio-ish things.)

I remarked about how clever I thought it was mixing the video carrier and audio subcarrier to get the audio IF. And he says:

"Oh, it wasn't always like that. When I was a kid, there was a TV station in Philadelphia that transmitted 2 1/2 hours two nights a week. They taped up the schematics for a receiver inside a big picture window at their station, and we would all go down with notebooks and copy down the latest changes so that we could update our receivers. The audio subcarrier went through a lot of changes. AM, FM, and they moved the frequency around."

So... I realized that here was a guy who was watching television back when the way you got a TV receiver was to build it from scratch yourself. Wow number 1.

I said: "I suppose when the war came along you were sent to radar school like almost everybody else that worked on television?"

Answer: "No. Did you ever hear of Eckert and Mauchly?"

Me: stunned.
Maybe, but it doesn't make the alternative any less "correct". Also, "Dan" is a diminutive of both possible names, so I guess they went for the middle?
I'm 35. Does that help? Can you try to explain it to me then? :)

(I looked at the Readme, looked at the All.v file and .. I don't get it.)
Simple, diesel costs more per gallon, it's not as widely sold compared to gasoline (not every station may have it), and there are less car models availavle with diesel as an option. Therefore, even if you just look at it statistically there will be less diesel cars on the road in the USA.
The article has the black CEO, Frederick, dressed in all black with gold chains and talks about him selling drugs. The article leads with the stereotype and not what makes the company unique. I believe we need more positive images of black men. Again, let me say I love the work that CEO and Pigeon is doing but I do not like they way this article portrayed him because it is perpetuating the stereotype that all black men are drug dealers and thugs.
> Oracle and Teradata for example are proven databases with official support available worldwide and a talent pool you can draw from almost immediately.

I've watched Oracle try to strangle more than one company once they were dependent on their database. One they succeeded, one managed to migrate to PostgreSQL just in time. If you build your business to be dependent on Oracle they have you by the balls; don't think they're not going to squeeze. And IME the worldwide talent pool is much more available and... well, talented, for PostgreSQL or MySQL or any of the major open-source options.
Typically there'll be a CMS flag available to powerful users (editors). That's how it works at the Guardian.

It sets a boolean (shouldHideAdverts) in our content API[0], which we use in templates[1] to suppress commercial logic.

There are obvious business reasons for this. It's common for it not to be in the advertiser or reader's interest to show commercial messages against some content.

[0] http://content.guardianapis.com/world/live/2015/mar/24/germa...

[1] https://github.com/guardian/frontend/blob/4cb7e07c15a03568c2...
The article plays into the mythology of Americans not knowing about diesels with lines like "It is high time, America, to give diesels a better look."

However, all of us drivers have far too much life experience with driving behind/around giant bus and semi trucks that lay down a choking smokescreen.

Like it or not, diesels in America have a history of laying down choking smokescreens. Lack of regulation, lack of inspection, who knows.

Possibly new diesels or car diesels aren't as toxic. If you want to sell diesels to Americans you need to wait for them to forget about the last time they were "gassed" because they were nearby a bus or truck exhaust.

The other problem, living in a northern climate where diesel gels in the winter, its a huge hassle for the few diesel owners we actually have. And as if starting a gasoline engine at -15F isn't enough of a struggle, consider the poor diesel owner. They could sell well in Miami or New Orleans without the fuel issues, but inevitably someones going to move up north and the trash talking will commence. With extensive maintenance, expensive maintenance, they can be almost as reliable in the cold as a gasoline engine... almost. Why not save the extra maint money and buy a cheaper lighter higher powered gas engine? I have no question that the net gain to the environment tilts on the side of diesel in Louisiana, and it Might even net be cheaper. In the north... I strongly suspect the net overall system environmental costs of gas are significantly lower, as is the total system wide cost.
In JS, you know that library code that you call almost certainly won't do blocking I/O.

If you're trying to do non-blocking async stuff in other languages, you have to hope/check that none of your code and none of your dependencies try to do blocking I/O. (Unless you're using something that does async under the covers like haskell or go)
That blogpost is intriguing!

> variants of cache... anonymous, or not? mobile, or not? deflate, gzip, or no compression?

I don't understand why the markup would vary between mobile/desktop, or why they would even consider compression a varying factor to account for in cache. Maybe that's because their backends produce such specific variants that they have a hard time caching in the first place?

If 80% of pages are only requested every two weeks, then it doesn't make sense to cache those. There's still probably lots of stuff you can cache, such user profile/stats and question/answer scores for several minutes. You can also cache many parts of the markup that are not going to change often. I mean it's always even better when you cache the entire markup, but there can still be lots to gain if you cache only small bits that are expensive to acquire/template.

> But the cost of memory to store those strings (most large enough to go directly on the large object heap) is very non-trivial. And the cost of the garbage collector cleaning them up is also non-trivial.

It looks like their cache implementation could (should?) have been based on better foundations. First, i think the cache doesn't have to reside in memory: disk accesses are fast, certainly much faster than running a database query over the network which will need to access several files and cross-reference data with extra latency on top. Then, because if you're gonna store long-lived stuff in memory you should probably use a garbage collector based that's tailored for this usecase, not your language's (.Net) default GC... maybe Redis? Don't get me wrong, i find it pretty cool if some engineers want to develop a homebrew cache, but that sounds like a huge project in itself.

> the cost of egress traffic

I'm not aware of SO tech stack, but i'd be surprised if they have much egress fees. They're a very big site so they probably run off unmetered dedicated servers if not their own hardware on cheap transit. Who knows, they may even have their own AS and peer with other providers in some locations? From a quick request, it looks like stackoverflow.com is served from Fastly AS but i personally don't understand why: i don't remember seeing any heavy content (video/images) on SO so in that kind of situation a CDN would hurt more than help on slow links. Maybe that's because they bundle megabytes of javascript crap? Now that they're blocking tor users i can't check for myself :-)
Nothing to do with Rogan but then goes on to discuss Rogan quite a bit with a generous helping of other Artists who have protested Rogan. The hubris on this person. He actually believes that he can talk people out of Spotify!
Interesting, but doesn't fit the context of Stack Exchange blocking Tor. Your example there is regarding a mobile app hotlinking a image of a flower, which seems easy enough to block/fix, while Stack Exchange blocking all Tor users from even reading Stack Overflow doesn't make so much sense.
I think it can benefit both parties -- underprovisioning for a smaller bill and then increasing when demands need it so as to prevent degregation in QoS. That said, if load increases exponentially high it can induce high costs. Some cloud providers do not offer memory (or just any resource) ballooning, like AWS, so there you will experience the problem you have discussed about over-provisioning. However, we aim to alleviate some of these problems with the uniqueness of Unikernels with our soon-to-be-released Cloud Platform at https://unikraft.io. Features like memory ballooning (with hard upper limits) and other features like deep in-kernel monitoring to understand application performance.
I still don't really understand why so many devs seem to have a need for this. For me every commit I make is a good one that I would like to keep in the history. Why should I need to reorder or rename or group any of my commits? All my work (of days or even weeks) is neatly containted within one branch, and that branch gets merged at the end. Why is that not ok? Why should I hide my work history into one "blob" commit instead of just having the Merge commit on the master branch?

The only use I could imagine is, if you have very short-lived branches (i.e. 1-2 days) with lots of random commits. Like e.g. "Oh I'm going for lunch, lets commit."
Except Biden has stationed troops halfway across the world and if the MIC gets its way, we might get to pre 1800 levels of temperature, so, thanks Biden I guess. Let's go Biden
Spotify alternatives:

Tidal https://tidal.com/

Deezer https://www.deezer.com/

Bandcamp https://bandcamp.com/

Jango https://www.jango.com/

Radio Paradise https://radioparadise.com/

Qobuz
https://www.qobuz.com/

Pandora
https://www.pandora.com/
Also it is very common for these benchmarks to conveniently leave out the fastest current known methods for unclear reasons.
quick! somebody think of children and approve enough TSA expenditure to buy one of those globets for each airport checkin line!

...now seriously, the cost/result ratio would still be higher than the one for mm wave scanners...
Laughing at RMS had proven shortsighted in the past, and I don't think anything changed, it's still unwise.

It's not just about free software either (that's a higher-level target), it's also about the hardware and freedom of running your software on your machine, and owning your computer in general. For example, anticheats in multiplayer games is the major driving factor behind locking PCs down with DRM and chains of trust. It's already so bad that you practically need a separate machine for many games if you want to run anything remotely resembling a VM on your main one, and it's going to get much worse. (ex. TPM requirement in some games on Win11)

And sure, an "average teenage gamer" is happy to give it away, because the only thing they care about is cheaters. The problem is, this is imposed on everyone, directly or indirectly.
Having a candy bar melt in your pocket is mundane. Un-boiling an egg is NOT mundane.

Maybe I'm not understanding your point, obviously you aren't claiming that before the 1940's candy bars didn't melt in people pockets?
Impressive given how cheap gas is now. Solar has gone down even faster?
One reason I like using Emacs is that I can run it in a terminal - e.g. over ssh. I am skeptical I'll be able to do that with Atom (without using X forwarding).

On top of that I can be up and running with Emacs on a fresh install of just about any linux distro: install via the distro's package manager, drop in my configs, done.
Actually, we sorta tried this between 1850 and 1920, which is pretty much the highest GDP growth time period in the history of the US.
It’s harder to scale it properly over time, because every new post takes longer to regenerate aggregated pages. Obviously this can be somewhat lightened with some hard choices (e.g. only have aggregated pages by fixed period), but it is a tradeoff that dynamic sites typically don’t have to worry about.

Anybody who was around during the first blogwave in the early 2000s knows the score: after a while, with static generators you end up waiting a lot after hitting “publish”. And god help you when you change the template over the whole site.

Of course, dynamic systems have their own tradeoffs, but they tend to scale better by volume content. You can then slap a simple cache in front and be done with it until views get in the hundred millions.
You're mixing tax policy (land rent) with tax income distribution policy (UBI). I think property taxation should be improved and Geolib is one way to do it. However, if we assume that Geolib is the optimal taxation policy, by no means does it follow that UBI is the optimal distribution policy.
That was incredible. Thanks!
I bet you that their smart contract, like most other significant ones, has been designed to be upgradable. That means the authors can modify the smart contract whenever they want, which means it implicitly has a centralised trust mechanism (I.e. you had better hope that the authors don’t go rogue and screw over the users) Central point of trust => blockchain part is now pointless, as ever.
The Brexit Party Ltd. care enough that they have threatened legal action.
It’s about routing more than veth pairs (I mean you can also do simple bridging as other comment say, but it’s more limited), so look for BGP using ones, mainly Calico, but kube-router too.

I know there is simpler ones that don’t use BGP, but I don’t remember their names. For example there is one for AWS that uses ENI interfaces and pass them directly to containers (you’re obviously limited by the number of ENI you can attach to a particular host, then). There is also one that configures routes in the VPC routing table, and a similar one for GCP.
One thing I dislike about title edits, even when it is for the better, is that it makes it hard to know if you already have read the article.

Popular topics often get multiple submissions and trigger related topics. When the title changes it is hard to know whether it is a new link with new/different information or whether it is the same one that I've already read.

In my opinion once something hits the front page it is too late to edit it (other than minor things such as adding year or [pdf/video]).
It has never been more easy to self publish ... via Twitter and Instagram. But the real problem is that you only have 1 hour of free time, spread out in five minute intervals during the day. Being an adult sux.
If he published anonymously surely with machine learning these books could be identified for prose similarity?

I imagine if Google has OCRd nearly all the books this would be an interesting problem for someone there.

Unless they’ve already done it.
> Ferrets are a weirdly political issue in some areas of the USA.

They're not political except for a select group people who want to make it political. They should not be encouraged or appreciated for trying to push that outlook on others.
just let these platforms die.
It's chicken and egg problem. Nvidia was major backer of OpenGL, but their drivers were never conformant implementations that allowed a lot of incorrect shaders to compile and run. Yet Nvidia had best developer support so most of commercial apps were developed and tested against their drivers. As result those apps use non-standard codepath that simply dont work on conformant drivers. On top of that OpenGL compatibility contexts are not well documented or tested, but it's not strictly Nvidia fault.

In case of Wayland it was was opposite. It was developer by everyone, but Nvidia. Open source graphics stack developers found a way that work best for their hardware and supported it for decade. Recently Nvidia tried to join the parry while extending it with own incompatible addition that no one else needs. Obviously many open source proponents dont give a damn about their closed drivers so they only going to support primary APIs.